Copyright © 2007 Momonga Project. and others
This document is released under the terms of the Open Publication License.
For more details, read the full legalnotice in Section 3, “Legal Notice”.
| Revision History |
|---|
| Revision 4 |
2007-08-18 |
|
|
|
The Momonga Project is a community supported open source project.
Its goal is the rapid progress of free and open source software and content.
The Momonga Project makes use of public forums, open processes, rapid innovation,
meritocracy, and transparency in pursuit of the best operating system and platform
that free and open source software can provide.
To find out more general information about Momonga, refer to the
following Web pages:
![[Note]](./stylesheet-images/note.png) |
Document Links |
Many links may not work properly from within the installation environment,
due to resource constraints. The release notes are also available
post-installation as part of the desktop Web browser's default home page.
If you are connected to the internet, use these links to find other
helpful information about Momonga and the community that creates and
supports it.
|
For the first time, Momonga includes several different
spins, which are variations of Momonga
built from a specific set of software packages. Each spin has a
combination of software to meet the requirements of a specific
kind of end user. In addition to a very small
minimal iso (Momonga-4-minimal-i686-DVD.iso)
image for network installation,
users have the following spin choices:
GNOME and KDE desktop environment based bootable Live
images that can be installed to a hard disk. These spins are
meant for desktop users who prefer a single disk
installation and for sharing Momonga with friends, family,
and event attendees.
GNOME iso (Momonga-4-GNOME-i686-DVD.iso)
KDE iso (Momonga-4-KDE-i686-DVD.iso)
A regular image for desktops, workstations, and server
users. This spin provides a good upgrade path and similar
environment for users of previous releases of Momonga.
A set of DVD images that includes all software available
in the Momonga repository. This spin is intended for
distribution to users who do not have broadband Internet
access and prefer to have software available on disc.
-
This release features GNOME 2.18.3 and KDE 3.5.7.
http://www.gnome.org/start/2.18/notes/en/
http://kde.org/info/3.5.7.php
Display devices can be hot plugged and work
automatically, thanks to the inclusion of Xorg Server
1.3.
This release provides a number of firmware packages for
enhanced wireless networking.
NetworkManager presents a
graphical interface that allows user to quickly switch
between wireless and wired networks for increased mobility.
NetworkManager is installed by
default in both GNOME and KDE Live CDs.
-
Firefox 2 includes a host of new features including an
inline spell checker, built-in phishing protection, and
the ability to resume browsing sessions.
http://www.mozilla.com/en-US/firefox/2.0/releasenotes/
I18N support is much improved by the presence of SCIM
input methods, which now work automatically after
installation without any configuration. SCIM can handle
nearly every alphabet/set of characters in use. Momonga is
now more accessible to a wider audience by the default
inclusion of a number of language packages and input methods
in the GNOME based Live CD.
The SELinux troubleshooting tool setroubleshoot is
enabled by default in this release. This tool provides
notifications and detailed information to desktop users
about any access denials by SELinux policy, along with
suggestions on handling them.
-
This release features integration of a new FireWire
stack in the kernel for more robust device handling.
http://thread.gmane.org/gmane.linux.kernel/472789
-
Momonga now includes improved power management through
implementation of dynamic ticks in the kernel.
http://lwn.net/Articles/223185/
This release partially consolidates dictionaries used by
desktop applications, which provides a consistent desktop
experience while saving resources.
Momonga now integrates the experimental
nouveau driver within Xorg and the
kernel. The nouveau driver aims to provide free and open
source 3D drivers for nVidia cards. End users are asked to
provide feedback on this feature to the project developers,
to further the goal of having fully functional 3D drivers by
default.
2.4. System Administration
-
This release integrates Kernel-based Virtual Machine (KVM)
technology with Momonga's graphical
virt-manager and command-line
virsh tools. KVM provides a hardware
accelerated virtualization solution, and users have a choice
between KVM and Xen, along with Qemu, in this release.
http://kvm.sourceforge.net/
In this release, all hard disk partitions follow a
/dev/sd* naming convention due to a new
libata driver interface in the kernel.
The Anaconda installer eases the
transition for release upgrades.
-
Smolt, an opt-in tool that sends anonymous hardware
profile information to the Momonga Project, is integrated
with firstboot in the installer.
All data is available on the Smolt homepage. This profile
information is used to leverage cooperation from vendors in
improving end user hardware experience, and to priortize
development and quality assurance on commonly used
hardware.
https://hosted.fedoraproject.org/projects/smolt
http://smolt.fedoraproject.org
-
The Directory Server base is now part of the
Fedora software repository. The graphical console and
administration servers are available on the website and are
planned to be included in the repository after a review
process.
http://directory.fedoraproject.org/
-
Python 2.5 is included in this release, and all of the
Python software available in the repository uses it.
http://docs.python.org/whatsnew/whatsnew25.html
The proposed plans for the next release of Momonga are available at 2008 Summer.
Copyright (c) 2007 by Momonga Project and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at http://www.opencontent.org/openpub/.
All other trademarks and copyrights referred to are the property of their
respective owners.
Thank you for taking the time to provide your comments, suggestions,
and bug reports to the Momonga community. By doing so, you help
improve the state of Momonga, Linux, and free software worldwide.
Anaconda is the name of the
Momonga installer. This section outlines issues related to
Anaconda and installing Momonga Linux 4.
|
Downloading Large Files |
If you intend to download the Momonga DVD ISO image, keep in mind that not
all file downloading tools can accommodate files larger than 2 GiB in
size. Tools without this limitation include wget
1.8.2-6m and above, curl, and
ncftpget.
|
Anaconda tests the integrity of
installation media by default. This function works with the CD, DVD,
hard drive ISO, and NFS ISO installation methods. The Momonga Project
recommends that you test all installation media before starting the
installation process and before reporting any installation-related
bugs. Many of the bugs reported are actually due to
improperly-burned CDs. To use this test, type linux
mediacheck at the boot: prompt.
The mediacheck function is highly sensitive, and may
report some usable discs as faulty. This result is often caused by
disc writing software that does not include padding when creating
discs from ISO files. For best results with mediacheck,
boot with the following option:
linux ide=nodma mediacheck
After you complete the mediacheck function
successfully, reboot to return DMA mode to its normal state. On many
systems, this results in a faster installation process from the
disc. You may skip the mediacheck option when
rebooting.
You may perform memory testing before you install Momonga by entering
memtest86 at the boot: prompt. This option
runs the Memtest86 stand alone
memory testing software in place of
Anaconda.
Memtest86 memory testing
continues until the Esc key is pressed.
|
Memtest86 Availability |
You must boot from Installation Disc 1 or a rescue CD in order to use this
feature.
|
Momonga Linux 4 supports graphical FTP and HTTP installations.
However, the installer image must either fit in RAM or appear on
local storage, such as Installation Disc 1. Therefore, only systems
with more than 192MiB of RAM, or which boot from Installation Disc 1,
can use the graphical installer. Systems with 192MiB RAM or less fall
back to using the text-based installer automatically. If you prefer
to use the text-based installer, type linux text at the boot: prompt.
-
Many minor user interface changes:
Ability to select the boot drive
Advanced storage options, including the ability to add
an iSCSI target and disable dmraid devices
The time zone page includes a magnification slider to
zoom into different areas of the world when choosing
location
Improved LiveCD support
Ability to install from Live image running from RAM or USB
stick
Improved IEEE-1394 (Firewire) support
Improved installation for Sony PlayStation 3
French keyboard layout uses latin9
Improved kickstart installation
5.2. Installation Related Issues
5.2.1. Sony VAIO Notebooks
Some Sony VAIO notebook systems may experience problems
installing Momonga from CD-ROM. If this happens, restart the
installation process and add the following option to the boot
command line:
pci=off ide1=0x180,0x386
Installation should proceed normally, and any devices not
detected are configured the first time Momonga is booted.
Not all IDE RAID controllers are supported. If your RAID
controller is not yet supported by dmraid, you may
combine drives into RAID arrays by configuring Linux software
RAID. For supported controllers, configure the RAID functions in
the computer BIOS.
5.2.3. Multiple NICs and PXE Installation
Some servers with multiple network interfaces may not assign
eth0 to the first network interface as BIOS knows it, which can
cause the installer to try using a different network interface
than was used by PXE. To change this behavior, use the following
in pxelinux.cfg/* config files:
IPAPPEND 2
APPEND ksdevice=bootif
The configuration options above causes the installer to use the
same network interface as BIOS and PXE use. You can also use the
following option:
ksdevice=link
This option causes the installer to use the first network device
it finds that is linked to a network switch.
5.2.4. Compaq DL360 with Smart Array
If you have difficulties with this installation not detecting
the Smart Array card, try entering linux isa on the
installer prompt. This lets you manually select the card.
5.3. Upgrade Related Issues
Upgrade Install is not tested throughly.
In general, fresh installations are recommended over upgrades,
particularly for systems that include software from third-party
repositories. Third-party packages remaining from a previous
installation may not work as expected on an upgraded Momonga
system. If you decide to perform an upgrade anyway, the following
information may be helpful:
-
Before you upgrade, back up the system completely. In
particular, preserve /etc, /home,
and possibly /opt and /usr/local if
customized packages are installed there. You may wish to use a
multi-boot approach with a "clone" of the old installation on
alternate partition(s) as a fallback. In that case, create
alternate boot media, such as a GRUB boot floppy.
![[Tip]](./stylesheet-images/tip.png) |
System Configuration Backups |
Backups of configurations in /etc are also
useful in reconstructing system settings after a fresh installation.
|
After you complete the upgrade, run the following
command:
-
rpm -qa --last > RPMS_by_Install_Time.txt
Inspect the end of the output for packages that pre-date the
upgrade. Remove or upgrade those packages from third-party repositories,
or otherwise deal with them as necessary.
6.1. RPM multiarch support on 64-bit platforms (x86_64, ppc64)
RPM supports parallel installation of
multiple architectures of the same package. A default package
listing such as rpm -qa might appear to include
duplicate packages, since the architecture is not displayed.
Instead, use the repoquery command, part of the
yum-utils package, which
displays architecture by default. To install
yum-utils, run the following command:
su -c 'yum install yum-utils'
To list all packages with their architecture using
rpm, run the following command:
rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
You can add this to /etc/rpm/macros (for a
system wide setting) or ~/.rpmmacros (for a
per-user setting). It changes the default query to list the
architecture:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
6.2. PPC Specifics for Momonga
This section covers specific information about Momonga and the PPC
hardware platform.
6.2.1. Hardware Requirements for PPC
6.2.1.1. Processor and memory
Minimum CPU: PowerPC G3 / POWER3
Momonga Linux 4 supports only the "New World" generation of Apple
Power Macintosh, shipped from circa 1999 onward.
Momonga Linux 4 also supports Genesi Pegasos II, and IBM Cell
Broadband Engine machines.
Momonga Linux 4 includes new hardware support for Genesi Efika,
and for the Sony PlayStation 3.
Recommended for text-mode: 233 MHz G3 or better, 128MiB
RAM.
Recommended for graphical: 400 MHz G3 or better,
256MiB RAM.
The disk space requirements listed below represent the disk
space taken up by Momonga Linux 4 after installation is complete.
However, additional disk space is required during installation
to support the installation environment. This additional disk
space corresponds to the size of
/Momonga/base/stage2.img (on Installation
Disc 1) plus the size of the files in /var/lib/rpm on the installed
system.
In practical terms, additional space requirements may range
from as little as 90 MiB for a minimal installation to as much
as an additional 175 MiB for an "everything" installation. The
complete packages can occupy over 9 GB of disk space.
Additional space is also required for any user data, and at
least 5% free space should be maintained for proper system
operation.
6.2.2. 4 KiB Pages on 64-bit machines
After a brief experiment with 64KiB pages in Momonga Linux 4, the
PowerPC64 kernel has now been switched back to 4KiB pages. The
installer should reformat any swap partitions automatically
during an upgrade.
6.2.3. The Apple keyboard
The Option key on Apple systems is equivalent
to the Alt key on the PC. Where documentation
and the installer refer to the Alt key, use the
Option key. For some key combinations you may
need to use the Option key in conjunction with
the Fn key, such as Option-Fn-F3 to switch to virtual terminal tty3.
6.2.4. PPC installation notes
Momonga Installation Disc 1 is bootable on supported hardware. In
addition, a bootable CD image appears in the images/ directory of this disc.
These images behave differently according to your system
hardware:
-
On most machines, the bootloader automatically boots the
appropriate 32-bit or 64-bit installer from the install
disc. The default gnome-power-manager
package includes power management support, including sleep
and backlight level management. Users with more complex
requirements can use the apmud package.
To install apmud after installation, use the
following command:
su -c 'yum install apmud'
-
Genesi Pegasos II.
At the time of writing, firmware with full support for
ISO9660 file systems has not yet been released for the
Pegasos. You can use the network boot image, however. At
the OpenFirmware prompt, enter the following command:
boot cd: /images/netboot/ppc32.img
You must also configure OpenFirmware on the Pegasos manually
to make the installed Momonga system bootable. To do this,
set the boot-device and
boot-file environment variables
appropriately.
Genesi Efika.
At the time of writing, the firmware of the Efika has bugs
which prevent correct operation of the
yaboot bootloader. An updated firmware
should be available by April 2007, in advance of the
release of Momonga Linux 4. With a fixed firmware, installation
on Efika should be the same as on Pegasos II.
Sony PlayStation 3.
For installation on PlayStation 3, first update to
firmware 1.60 or later. The "Other OS" boot loader must be
installed into the flash, following the instructions at
http://www.playstation.com/ps3-openplatform/manual.html.
A suitable boot loader image ia located on the Momonga Linux 4
install media. Once the boot loader is installed, the
PlayStation 3 should boot from the Momonga install media.
Select the linux64 from the graphical
boot menu.
-
Network booting.
Combined images containing the installer kernel and
ramdisk are located in the images/netboot/ directory
of the installation tree. They are intended for network
booting with TFTP, but can be used in many ways.
The yaboot loader supports TFTP booting
for IBM pSeries and Apple Macintosh. The Momonga Project
encourages the use of yaboot over the
netboot images.
6.3. x86 Specifics for Momonga
This section covers specific information about Momonga and the x86
hardware platform.
6.3.1. Hardware requirements for x86
In order to use specific features of Momonga Linux 4 during or after
installation, you may need to know details of other hardware
components such as video and network cards.
6.3.1.1. Processor and memory
The following CPU specifications are stated in terms of Intel
processors. Other processors, such as those from AMD, Cyrix,
and VIA that are compatible with and equivalent to the
following Intel processors, may also be used with Momonga.
Momonga Linux 4 requires an Intel Pentium or better processor, and is
optimized for Pentium 4 and later processors.
Recommended for text-mode: Pentium 4 or better
Recommended for graphical: Pentium 4 or better
Minimum RAM for text-mode: 128MiB
Minimum RAM for graphical: 192MiB
Recommended RAM for graphical: 256MiB
The disk space requirements listed below represent the disk
space taken up by Momonga Linux 4 after the installation is complete.
However, additional disk space is required during the
installation to support the installation environment. This
additional disk space corresponds to the size of
/Momonga/base/stage2.img on Installation
Disc 1 plus the size of the files in /var/lib/rpm on the installed
system.
In practical terms, additional space requirements may range
from as little as 1.0 GiB for a minimal installation. The
complete packages can occupy over 16 GiB of disk space.
Additional space is also required for any user data, and at
least 5% free space should be maintained for proper system
operation.
6.4. x86_64 Specifics for Momonga
This section covers specific information about Momonga and the
x86_64 hardware platform.
6.4.1. Hardware requirements for x86_64
In order to use specific features of Momonga Linux 4 during or after
installation, you may need to know details of other hardware
components such as video and network cards.
6.4.1.1. Memory requirements for x86_64
Minimum RAM for text-mode: 128MiB
Minimum RAM for graphical: 256MiB
Recommended RAM for graphical: 512MiB
6.4.1.2. Hard disk space requirements for x86_64
The disk space requirements listed below represent the disk
space taken up by Momonga Linux 4 after the installation is complete.
However, additional disk space is required during the
installation to support the installation environment. This
additional disk space corresponds to the size of
/Momonga/base/stage2.img on Installation
Disc 1 plus the size of the files in /var/lib/rpm on the installed
system.
In practical terms, additional space requirements may range
from as little as 1.1 GiB for a minimal installation. The
complete packages can occupy over 17 GiB of disk space.
Additional space is also required for any user data, and at
least 5% free space should be maintained for proper system
operation.
The following sections contain information regarding software
packages that have undergone significant changes for Momonga Linux 4. For
easier access, they are generally organized using the same groups
that are shown in the installation system.
The PC speaker is enabled by default in this release, but can
be circumvented in a number of ways:
Reduce its volume to an acceptable level or completely mute
the PC speaker in alsamixer with the
setting for PC Speak.
-
As the root
user, disable the PC speaker system-wide by runing the
following command in a console.
su -c '/sbin/modprobe -r pcspkr ; echo "install pcspkr :" >>/etc/modprobe.conf'
8.5. Packages with ".mo4" Tag
There have not been any major changes in the toolchain in
Momonga Linux 4. Therefore, some packages in Momonga Linux 4 might retain ".mo4"
in the release tag if they have been inherited from the previous
release without any changes. Momonga maintainers have not rebuilt
these packages for Momonga Linux 4 to avoid making end users download the
packages for only a release tag change. This measure ensures that
the robustness is not affected by any potential changes evoked by
rebuilds. This naming of packages is merely cosmetic, and does not
in any way affect the functionality of the software.
Development related files have been split from Perl and are
now available in the perl-devel package.
perl requires perl-devel to
avoid rebuilding some perl dependent packages
late in the development cycle. During the next release cycle of
Momonga, maintainers will split up the rest of the dependent
packages.
8.8. Engineering and Scientific
The mpi build and sub-package of
paraview have been removed until
cmake related build issues are resolved.
8.10.1. Handling of GIMP Plugins Contained in Other Packages
The GIMP package in Momonga
includes a helper script
/usr/sbin/gimp-plugin-mgr for plugins
contained in other packages, for example,
xsane-gimp. This script manages symlinks from
the GIMP plugin directory (which may
change between upgrades) to the actual location of the
plugins.
A bug has been fixed in the Momonga Linux 4 release of
GIMP that was in all older
GIMP packages, including all those in
the test releases. The bug concerns the execution order in which
the symlinks are installed and removed, causing the symlinks to
vanish when the GIMP package is
updated.
Although the GIMP package
contained in the final release has the execution order fixed,
due to the nature of the problem it will show up once more when
updating from an affected version to a fixed version. To add
these symlinks back in, run this command, providing the
root password when
prompted:
su -c "/usr/sbin/gimp-plugin-mgr --install '*'"
This section covers changes and important information regarding the
2.6.21 based kernel in Momonga Linux 4. The 2.6.21 kernel includes:
Support for KVM virtualization.
Tickless support for x86 32bit, which greatly improves power
management.
The devicescape wireless network stack, which includes support for
several new wireless drivers.
-
New IDE drivers that use the same libata code as the SATA
drivers.
![[Important]](./stylesheet-images/important.png) |
IDE Device Names Changed |
|
The new IDE drivers now cause all IDE drives to have
device names such as /dev/sdX instead of
/dev/hdX.
If the /etc/fstab or
/etc/crypttab files reference these
devices by name, they must be migrated before the system can
access those partitions.
|
Support for version 2 of the Global File System (GFS2) has
been integrated into the upstream kernel.
Some elements of the realtime kernel project.
Momonga may include additional patches to the kernel for
improvements, bug fixes, or additional features. For this reason,
the Momonga kernel may not be line-for-line equivalent to the
so-called vanilla kernel from the kernel.org
web site:
http://www.kernel.org/
To obtain a list of these patches, download the source RPM package
and run the following command against it:
rpm -qpl kernel-<version>.src.rpm
Momonga Linux 4 includes the following kernel builds:
Native kernel, for use in most systems. Configured sources are
available in the
kernel-devel-<version>.<arch>.rpm package.
The kernel-PAE, for use in 32-bit x86 systems with > 4GB of
RAM, or with CPUs that have an 'NX (No eXecute)' feature. This
kernel support both uniprocessor and multi-processor systems.
Virtualization kernel for use with the Xen emulator package.
Configured sources are available in the
kernel-xen-devel-<version>.<arch>.rpm
package.
Virtualization kernel for use with the openvz emulator package.
Configured sources are available in the
kernel-openvz-devel-<version>.<arch>.rpm
package.
You may install kernel headers for all kernel flavors at the same
time. The files are installed in the
/usr/src/kernels/<version>-[PAE|xen]-<arch>/
tree. Use the following command:
su -c 'yum install kernel-{PAE,xen}-devel'
Select one or more of these flavors, separated by commas and no
spaces, as appropriate. Enter the root password when prompted.
|
Default Kernel Provides SMP |
There is no separate SMP kernel available for Momonga on i686, x86_64,
and ppc64. Multiprocessor support is provided by the native kernel.
|
|
PowerPC Kernel Support |
There is no support for Xen or kdump for the PowerPC architecture in
Momonga. 32-bit PowerPC does still have a separate SMP kernel.
|
9.5. Preparing for Kernel Development
Momonga Linux 4 does not include the kernel-source package
provided by older versions since only the kernel-devel
package is required now to build external modules. Configured sources are
available, as described in the kernel flavors section.
This section details changes that affect Momonga graphical desktop
users.
This release features
GNOME 2.18.3 (http://www.gnome.org/start/2.18/)
The GNOME splash screen has been disabled upstream intentionally.
To enable it, use gconf-editor or the following
command:
gconftool-2 --set /apps/gnome-session/options/show_splash_screen --type bool true
The lock screen dialog theme is not connected to the selected
screensaver in this release. To enable it, use
gconf-editor or the following command:
gconftool-2 --set --type string /apps/gnome-screensaver/lock_dialog_theme "system"
This release of Momonga includes version 2.0 of the popular
Firefox web browser. Refer to http://firefox.com/ for more information about Firefox.
This release contains Thunderbird
version 2.0, which has numerous performance improvements, folder
viewing enhancements, and enhanced mail notification
support.
This release also contains Sylpheed
version 2.4.4.
You can install Momonga Linux 4 ion
ext3, ext2, jfs, XFS, ReiserFS,, orReiser4 file system.
Momonga Linux 4 provides unionfs, nilfs and btrfs by kernel modules.
It also provides filesystem related tools.
Momonga Linux 4 provides basic support for encrypted swap partitions and
non-root file systems. To use it, add entries to
/etc/crypttab and reference the created devices in
/etc/fstab.
|
Encrypted FS Support Unavailable During
Install |
Enable file system encryption after installation.
Anaconda does not have support for creating encrypted block
devices.
|
The following example shows an /etc/crypttab entry for
a swap partition:
my_swap /dev/sdb1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
This creates an encrypted block device
/dev/mapper/my_swap, which can be referenced in
/etc/fstab. The next example shows an entry for a
filesystem volume:
my_volume /dev/sda5 /etc/volume_key cipher=aes-cbc-essiv:sha256
The /etc/volume_key file contains a plaintext
encryption key. You can also specify none as the key
file name, and the system instead asks for the encryption key during
boot.
The recommended method is to use LUKS for file system
volumes: (using LUKS you can drop the
cipher= part in
crypttab).
Create the encrypted volume using cryptsetup
luksFormat
Add the necessary entry to /etc/crypttab
Set up the volume manually using cryptsetup
luksOpen or reboot
Create a filesystem on the encrypted volume
Set up an /etc/fstab entry
This section concerns electronic mail servers or mail transfer
agents (MTAs).
Momonga Linux 4 includes the following MTAs:
sendmail (use alternatives mechanism)
postfix (use alternatives mechanism)
exim (Alter: package is not prepared)
The
exim-sa package is deprecated since the
previous release. It was the original implementation of
SpamAssassin integration
with Exim, and was functionally similar to
sendmail milters or
postfix filters. However, that functionality is rather limited,
and Exim now has far better support for content checking, fully
integrated into its general-purpose Access Control Lists.
Since the sa_exim feature was not enabled in the
default configuration, the package can normally be safely
uninstalled to allow Exim to be upgraded. Users who have modified
their configuration to use sa_exim features should
either reconfigure to use Exim's full content scanning abilities
or rebuild the package for themselves to include the
exim-sa subpackage. For further details on Exim's
built-in content scanning, refer to the Exim documentation:
http://www.exim.org/exim-html-4.67/doc/html/spec_html/ch40.html
This section covers various development tools and features.
13.1.1. GCC Compiler Collection
This release of Momonga has been built with GCC 4.1, which is
included with the distribution.
This release of Momonga includes Eclipse, based on the
Eclipse SDK version 3.3.0 (http://www.eclipse.org).
The "New and Noteworthy" page for the 3.3.x series of releases
can be accessed at http://www.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500/index.php.
Release notes specific to 3.3.0 are available at http://www.eclipse.org/eclipse/development/readme_eclipse_3.3.html.
The Eclipse SDK is known variously as "the Eclipse Platform,"
"the Eclipse IDE," and "Eclipse." The Eclipse SDK is the
foundation for the combined release of ten Eclipse projects
under the Callisto combined release umbrella (http://www.eclipse.org/callisto).
A few of these Callisto projects are included in Momonga: CDT
(http://www.eclipse.org/cdt,
for C/C++ development, EMF (http://www.eclipse.org/emf)
the Eclipse Modeling Framework, and GEF (http://www.eclipse.org/gef),
the Graphical Editing Framework.
Many third-party Eclipse projects are also available, including
Subclipse (http://subclipse.tigris.org/)
for integrating Subversion version control, PyDev (http://pydev.sf.net) for
developing in Python, and PHPeclipse (http://www.phpeclipse.de/)
for developing in PHP. Mylar (http://eclipse.org/mylar),
a task-focused UI for Eclipse, is also available in Momonga with
task connectors for Bugzilla and Trac. It was not part of
Callisto but will be part of the forthcoming Europa combined
Eclipse release.
Assistance in getting more projects packaged and tested with GCJ
is always welcome.
Momonga also includes plugins and features that are particularly
useful to FLOSS hackers, ChangeLog editing with
eclipse-changelog, and Bugzilla interaction
with eclipse-mylar-bugzilla. Our CDT package
also includes the work-in-progress GNU Autotools plugin. This
plugin allows end-users to use Eclipse to build and maintain
C/C++ projects that use GNU autotools. Enhancements to the CDT
include:
Performing configuration prior to build
Special editors for
autoconf/automake
input files
Special help for autoconf macros
Hover help for C library functions
A special console for configuration
13.1.2.1. Non-packaged Plugins/Features
Momonga Eclipse contains a patch to allow non-root users to make use of the
Update Manager functionality for installing non-packaged
plugins and features. Such plugins are installed in the user's
home directory under the .eclipse directory.
Please note, however, that these plugins do not have
associated GCJ-compiled bits and may therefore run slower than
expected.
13.1.2.2. Alternative Java Runtime Environments
The Momonga free JRE does not satisfy every user, so Momonga
does allow the installation of alternative JREs. A caveat
exists, however, for installing proprietary JREs on 64-bit
machines.
The 64-bit JNI libraries shipped by default on x86_64 systems
in Momonga do not run on 32-bit proprietary JREs. In other
words, do not try to run Momonga's x86_64 Eclipse packages on
Sun's 32-bit JRE. They fail in confusing ways. Either switch
to a 64-bit proprietary JRE, or install the 32-bit version of
the packages, if available. To install a 32-bit version, use
the following command:
yum install <package_name>.i386
Likewise, the 32-bit JNI libraries shipped by default on ppc64
systems do not run with a 64-bit JRE. To install the 64-bit
version, use the following command:
yum install <package_name>.ppc64
13.1.2.3. Europa/Eclipse 3.3
In June 2007, the Eclipse community is releasing the Europa
combined release of an assortment of plugins and features.
This will be based on and include version 3.3 of the Eclipse
SDK. This is a major change and because of that, Momonga
Eclipse is not going to be re-basing on Europa until Momonga 5.
This means that versions of Eclipse-based applications
included in Momonga such as RSSOwl and Azureus may lag upstream
releases if they require features only available in Eclipse
3.3.
This section highlights various security items from Momonga.
14.1. General Information
A general introduction to the many proactive security features in
Momonga.
The SELinux project pages have troubleshooting tips,
explanations, and pointers to documentation and references.
Some useful links include the following:
15. Java and java-gcj-compat
This release of Momonga includes a free and open source Java
environment called java-gcj-compat. The
java-gcj-compat collection includes a tool suite and
execution environment that is capable of building and running many
useful programs that are written in the Java programming language.
|
Momonga is Include Java |
Java is a trademark of Sun Microsystems.
|
The java-gcj infrastructure has three key components: a GNU Java runtime
(libgcj), the Eclipse Java
compiler (ecj), and a set of wrappers and links
(java-gcj-compat) that present the runtime and compiler
to the user in a manner similar to other Java environments.
The Java software packages in this Momonga release use the
java-gcj-compat environment. These packages
include OpenOffice.org Base,
Eclipse, and Apache
Tomcat.
|
Include Location and Version Information in Bug Reports |
|
When making a bug report, be sure to include the
output from these commands:
which java && java -version && which javac && javac -version
|
15.1. Handling Java and Java-like Packages
In addition to the java-gcj-compat free
software stack, Momonga lets you install multiple Java
implementations and switch between them using the
alternatives command line tool. However, every
Java system you install must be packaged using the JPackage
Project packaging guidelines to take advantage of
alternatives. Once these packages are installed
properly, the root user
may switch between java and
javac implementations using the
alternatives command:
alternatives --config java
alternatives --config javac
15.2. Handling Java Applets
This release of Momonga includes a preview release of
gcjwebplugin, a Firefox plugin for Java applets.
gcjwebplugin is not enabled by default because although
the security implementation in GNU Classpath is being actively developed,
it is not mature enough to run untrusted applets safely. That said, the
AWT and Swing implementations in GNU Classpath are now sufficiently mature
that they can run many applets deployed on the web. Adventurous users who
want to try gcjwebplugin can read
/usr/share/doc/libgcj-4.1.2/README.libgcjwebplugin.so,
as installed by the libgcj package. The
README explains how to enable the plugin and the
risks associated with doing so.
15.3. Momonga and the JPackage Java Packages
Momonga includes many packages derived from the JPackage Project,
which provides a Java software repository. These packages are
modified in Momonga to remove proprietary software dependencies and
to make use of GCJ's ahead-of-time compilation feature. Use the
Momonga repositories to update these packages, or use the JPackage
repository for packages not provided by Momonga. Refer to the
JPackage website at
http://jpackage.org for
more information on the project and the software it provides.
![[Warning]](./stylesheet-images/warning.png) |
Mixing Packages from Momonga and JPackage |
Research package compatibility before you install software from both the
Momonga and JPackage repositories on the same system. Incompatible
packages may cause complex issues.
|
Momonga includes applications for assorted multimedia functions,
including playback, recording, and editing. Additional packages are
available through the Momonga Package Collection software repository.
The default installation of Momonga includes
Rhythmbox and Totem
for media playback. The Momonga repositories include many other popular
programs such as the XMMS player and KDE's
amaroK. Both GNOME and KDE have a selection of
players that can be used with a variety of formats. Third parties may
offer additional programs to handle other formats.
Momonga also takes full advantage of the Advanced Linux Sound
Architecture (ALSA) sound system. Many programs can play sound
simultaneously, which was once difficult on Linux systems. When
all multimedia software is configured to use ALSA for sound
support, this limitation disappears. For more information about
ALSA, visit the project website at
http://www.alsa-project.org/.
Users may still experience issues when multiple users log into the
system. Depending upon hardware and software configurations,
multiple users may not be able to use the sound hardware
simultaneously.
16.2. Ogg and Xiph.Org Foundation Formats
Momonga includes complete support for the Ogg media container
format and the Vorbis audio, Theora video, Speex audio, and FLAC
lossless audio formats. These freely-distributable formats are not
encumbered by patent or license restrictions. They provide
powerful and flexible alternatives to more popular, restricted
formats. The Momonga Project encourages the use of open formats in
place of restricted ones. For more information on these formats
and how to use them, refer to the Xiph.Org Foundation's web site
at http://www.xiph.org/.
16.3. MP3, DVD, and Other Excluded Multimedia Formats
Momonga software repositories include support for MP3 or DVD
video playback or recording. MP3 decode is available, but on default,
MP3 encode is disalbed. Please install lame (Nonfree) package,
and you can use MP3 encode.
While other MP3 options may be available for Momonga, Fluendo now
offers a free MP3 plugin for GStreamer that has the necessary
patent license for end users. This plugin enables MP3 support in
applications that use the GStreamer framework as a backend. Momonga
does not include this plugin since we prefer to support and
encourage the use of patent unrestricted open formats instead. For
more information about the MP3 plugin, visit Fluendo's website at
http://www.fluendo.com/.
16.4. CD and DVD Authoring and Burning
Momonga software repositories includes a variety of tools for
easily mastering and burning CDs and DVDs. GNOME users can burn
directly from the Nautilus file manager, choose the
gnomebaker packages, or utilize the older
xcdroast package from Momonga.
KDE users can use the robust k3b
package for these tasks. Console tools include
cdrecord, readcd,
mkisofs, and other popular applications.
16.6. Extended Support through Plugins
Most of the media players in Momonga software repositories can use
plugins to add support for additional media formats and sound
output systems. Some use powerful multimedia frameworks, like the
gstreamer package, to handle media format support and
sound output. Momonga software repositories offer plugin packages
for these backends and for individual applications. Third parties
may provide additional plugins to add even greater capabilities.
17. Games and Entertainment
Momonga provides a selection of games that cover a variety of genres.
Users can install a small package of games for GNOME (called
gnome-games) and KDE (kdegames). There are
also many additional games that span every major genre available in
the repositories.
For a list of other games that are available for installation, use
the Pirut graphical utility
(), or via
the command line:
yum groupinfo "Games and Entertainment"
Virtualization in Momonga Linux 4 supports both Xen and KVM virtualization
platforms. The libvirt API
and its corresponding tools, virt-manager
and virsh, have been updated to support both KVM
and Xen. Users can choose which virtualization platform to install,
and use the same tools without regard to that choice.
Xen in Momonga Linux 4 is based on version 3.1.0.
KVM in Momonga Linux 4 is based on version 28.
For more information on the differences between Xen and KVM, refer
to http://virt.kernelnewbies.org/TechComparison. For
more information on installing and using virtualization in Momonga Linux 4,
refer to http://fedoraproject.org/wiki/Docs/Momonga7VirtQuickStart.
18.1. Types of Virtualization
Using Xen 3.1.0, both paravirtualization and full virtualization
can be implemented. Under KVM, only full virtualization is
supported. Full virtualization requires a VT-capable processor.
Paravirtualization does not require special hardware, but does
require the guest OS to be modified.
18.3. Changes to the Virtualization Packages
The following improvements have been made in the virtualization
packages in Momonga Linux 4:
The applications virt-manager and
virsh can now work with inactive domains.
Previously, only xm could handle inactive
domains.
The mouse cursor problems with the virtual frame buffer have been
fixed, for a better user experience in GUI modes.
Miscellaneous other small improvements and fixes have been made.
19. X Window System (Graphics)
This section contains information related to the X Window System
implementation, X.org, provided with Momonga.
19.1. X Configuration Changes
The X.org 7.2 X server has been modified to automatically detect and
configure most hardware, eliminating the need for users or administrators
to modify the /etc/X11/xorg.conf configuration file.
The only hardware configured by default in the
xorg.conf file written by anaconda is:
The graphics driver
The keyboard map
All other hardware, such as monitors (both LCD and CRT), USB mice,
and touchpads should be detected and configured automatically.
The X server queries the attached monitor for supported resolution ranges,
and attempts to pick the highest resolution available with the correct
aspect ratio for the display. Users can set their preferred resolution in
→ → , and the default resolution for the system can
be changed with
→ → .
If the /etc/X11/xorg.conf configuration file is not
present, X also automatically detects the appropriate driver, and assumes
a 105-key US keyboard layout.
Momonga Linux 4 contains two drivers for Intel integrated graphics
controllers:
The default i810 driver, which contains support for
Intel graphics chipsets up to and including i945 and i965
The experimental intel driver, which contains
support for Intel graphics chipsets up to and including i945
The i810 driver is limited to resolutions available
in the BIOS. If you need support for non-standard resolutions, such as
those used in some widescreen displays, you may want to switch to the
intel driver. You may switch drivers by using
system-config-display, available in the menus under
→ → .
21. Internationalization (i18n)
This section includes information on language support under Momonga.
21.1. Language Installation
To install additional language support from the Languages group,
use Pirut via
→ , or run this command:
su -c 'yum groupinstall <language>-support'
In the command above, <language>
is one of assamese, bengali,
chinese, gujarati,
hindi, japanese,
kannada, korean,
malayalam, marathi,
oriya, punjabi,
sinhala, tamil,
thai, or telegu.
21.2. SCIM Input Method Defaults
The core SCIM packages are now installed by default, but SCIM
only runs by default on desktops running in an Asian locale (the
current list is: as,
bn, gu,
hi, ja,
kn, ko,
ml, mr,
ne, or,
pa, si,
ta, te,
th, ur,
vi, zh). You can
use im-chooser via → → → to enable
or disable SCIM on your desktop, or to select
other installed input methods.
Users upgrading from earlier releases of Momonga are strongly
recommended to install scim-bridge-gtk, which
works well with 3rd party C++ applications linked against older
versions of libstdc++.
When SCIM is installed, it runs by default for users of all
locales.
The following table lists the default trigger hotkeys for
different languages:
| Language |
Trigger hotkeys |
| all |
Ctrl-Space
|
| Japanese |
Zenkaku_Hankaku or Alt-`
|
| Korean |
Shift-Space or
Hangul
|
22. Backwards Compatibility
Momonga provides legacy system libraries for compatibility with older
software. This software is part of the Legacy Software
Development group, which is not installed by default.
Users who require this functionality may select this group either
during installation or after the installation process is complete.
To install the package group on a Momonga system, use →
(Pirut) or enter the following command in
a terminal window:
su -c 'yum groupinstall "Legacy Software Development"'
Enter the password for the root account when prompted.
The goal of the Momonga Project is to work with the Linux community
to build a complete, general-purpose operating system exclusively
from open source software. Development is done in a public forum.
The project produces releases of Momonga approximately 1 time a
year.
For more information, refer to the Momonga Project website at
http://www.momonga-linux.org.
The Momonga Project is driven by the individuals that contribute to
it. As a tester, developer, documenter, or translator, you can make
a difference. See
http://www.momonga-linux.org/project.html.ja
for details.
In addition to the website, the following mailing lists are
available:
To subscribe to any of these lists, send an email with the word "subscribe"
in the subject to <listname>-request, where
<listname> is one of the above list names.
For more information, refer to the Momonga Project website mailing list page at
http://www.momonga-linux.org/mailinglist.html.
The Momonga Project also uses several IRC (Internet Relay Chat)
channels. IRC is a real-time, text-based form of communication,
similar to Instant Messaging. With it, you may have conversations
with multiple people in an open channel, or chat with someone
privately one-on-one. To talk with other Momonga Project participants
via IRC, access the IRC network.
Momonga Project participants frequent the #momonga channel.
In order to talk on the #momonga channel, you need to
register your nickname, or nick. Instructions
are given when you /join the channel.
|
IRC Channels |
The Momonga Project have no control over the Momonga Project IRC
channels or their content.
|
As we use the term, a colophon:
dai (ppc64)
futoshi (GNOME)
h_nakamura (tester)
ichiro (KDE)
kajiwara (tester)
kazuhiko and yuuna (graphics)
kourin (translate_English)
meke (compiz, anaconda and kernel)
minakami (tester)
muradaikan (kernel and translate_English)
mutecat (ppc32)
nakaya (emacs and elisp)
nosanosa (scientific)
pulsar (KDE and perl)
ryu (security)
sanuki (GNOME and graphics)
satoshiga (tester)
smbd (security)
t (tester)
tab (release_manager)
takahata (package_builder and graphics)
tamo (tester)
y (Java and development_tools)
yohgaki (PHP)
zaki (tester)
zunda (tester)
and you.