Joined: Nov 03, 2005 Posts: 35 Location: shibpur howrah
Posted: Thu Dec 08, 2005 9:03 pm Post subject: LINUX NEWS: FEDORA CORE 5 TEST 1 AVALABLE
Test 1 is now available for download. This release includes KDE 3.5 Beta 2 and OpenOffice.org 2.0 final.
"The Fedora Project announces the first release of the Fedora Core 5
development cycle, available for the i386, x86_64, and PPC/PPC64
architectures. Beware that Test releases are recommended only for Linux
experts/enthusiasts or for technology evaluation, as many parts are
likely to be broken and the rate of change is rapid.
Test2 is scheduled for release before Christmas giving us less than a
month of rapid development. This aggressive schedule makes vitally
important your help in testing, reporting and suggesting fixes for bugs.
Please direct bugs to http://bugzilla.redhat.com, Product Fedora Core,
Version fc5test1. As always, be sure that your bug is not already fixed
by updates and search for existing bugs before filing.
Thanks to all in the Fedora Project who have contributed to this
release. Your continued efforts is what makes Fedora possible.
Fedora Core 5 test1 Release Notes
Copyright (c) 2005 Red Hat, Inc.
This document is released under the terms of the GNU Free Documentation
License. For more details, read the full legalnotice in [1]Section\0012,
"Legalnotice".
[2][Tip] Latest Release Notes on the Web
These release notes may be updated. Visit
[3]http://fedora.redhat.com/docs/release-notes/ to view the
latest release notes for Fedora Core 5 test1.
[40]7.7. Samba (Windows File System Compatibility)
[41]7.8. X Window System (Graphics)
[42]7.8.1. xorg-x11
[43]7.9. Games and Entertainment
[44]8. Packages Movement
[45]8.1. Package Changes
[46]8.1.1. Packages Added
[47]8.1.2. Packages Removed
[48]8.2. Notes
[49]9. An Overview of the Fedora Project
1.\001Welcome to Fedora Core 5 test1
[50][Caution] Information Out-of-Date
The content in this section needs to be updated for Fedora
Core 5 test1
Fedora Core is a completely free, user friendly, and secure general
purpose platform based on Linux. The Fedora Project is an open source
project that pioneers leading edge technology and concepts sponsored by
Red Hat and supported by the Fedora community.
[51][Tip] Latest Release Notes on the Web
These release notes may be updated. Visit
[52]http://fedora.redhat.com/docs/release-notes/ to view the
latest release notes for Fedora Core 5 test1.
Refer to these webpages to find out more information about Fedora:
o [53]Section\0013, "Introduction and Technical Release Notes" --
Technical release notes
o Help and Support
([54]http://fedora.redhat.com/participate/communicate/)
o Participate in the Fedora Project
([55]http://fedora.redhat.com/participate/)
o About the Fedora Project ([56]http://fedora.redhat.com/about/)
2.\001Legalnotice
Permission is granted to copy, distribute, and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or any
later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the
license is available at [57]http://www.gnu.org/licenses/fdl.html.
This document may be copied and distributed in any medium, either
commercially or noncommercially, provided that the GNU Free Documentation
License (FDL), the copyright notices, and the license notice saying the
GNU FDL applies to the document are reproduced in all copies, and that you
add no other conditions whatsoever to those of the GNU FDL.
Garrett LeSage created the admonition graphics (note, tip, important,
caution, and warning). Tommy Reynolds <[58]Tommy.Reynolds@MegaCoder.com>
created the callout graphics. They all may be freely redistributed with
documentation produced for the Fedora Project.
RELEASE-NOTES-FC5 test1 (2005-10-25-T04:20-0700)
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red
Hat, Inc. in the United States and other countries.
All other trademarks and copyrights referred to are the property of their
respective owners.
3.\001Introduction and Technical Release Notes
The Fedora Project is an openly-developed project designed by Red Hat,
open for general participation, led by a meritocracy, and following a set
of project objectives. The results from this project include Fedora Core,
which is a complete, general-purpose operating system built exclusively
from open source software.
[59][Note] Note
Fedora Core is a community supported project.
Fedora Core is not a commercially supported product of Red Hat,
Inc..
For more information, refer to [60]Section\0015, "Overview of This
Release".
Additional important information about this release may be made available
at [61]http://fedora.redhat.com/docs/release-notes/. Users are advised to
check this link regularly for updates.
For reporting errors or other requests about these release notes, file a
bug report using this [62]pre-filled bugzilla template.
This [63]http://tinyurl.com/byvk2 will take you to the same pre-filled
bugzilla template.
4.\001Hardware Requirements
The following information represents the minimum hardware requirements
necessary to successfully install Fedora Core 5 test1.
[64][Note] Note
The compatibility/availability of other hardware components
(such as video and network cards) may be required for specific
installation modes and/or post-installation usage.
4.1.\001CPU Requirements
This section lists the CPU specifications required by Fedora Core 5 test1.
[65][Note] Note
The following CPU specifications are stated in terms of Intel
processors. Other processors (notably, offerings from AMD,
Cyrix, and VIA) that are compatible with and equivalent to the
following Intel processors may also be used with Fedora Core.
o Minimum: Pentium-class -- Fedora Core 5 test1 is optimized for Pentium
4 CPUs, but also supports earlier CPUs (such as Pentium, Pentium Pro,
Pentium II, Pentium III, and including AMD and VIA variants). This
approach has been taken because Pentium-class optimizations actually
result in reduced performance for non-Pentium-class processors, and
Pentium 4 scheduling is sufficiently different (while making up the
bulk of today's processors) to warrant this change.
o Recommended for text-mode: 200 MHz Pentium-class or better
o Recommended for graphical: 400 MHz Pentium II or better
o AMD64 processors (both Athlon64 and Opteron)
o Intel processors with Intel(R) Extended Memory 64 Technology (Intel(R)
EM64T)
4.2.\001Hard Disk Space Requirements
This section lists the disk space required to install Fedora Core 5 test1.
[66][Note] Note
The disk space requirements listed below represent the disk
space taken up by Fedora Core 5 test1 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
/Fedora/base/stage2.img (on CD-ROM 1) plus the size of the
files in /var/lib/rpm on the installed system.
In practical terms, this means that as little as an additional
90MB can be required for a minimal installation, while as much
as an additional 175MB can be required for an "everything"
installation.
Also, keep in mind that additional space will be required for
any user data, and at least 5% free space should be maintained
for proper system operation.
This list is for 32-bit x86 systems:
o Custom Installation (Minimal): 620MB
o Server: 1.1GB
o Personal Desktop: 2.3GB
o Workstation: 3.0GB
o Custom Installation (Everything): 6.9GB
This list is for 64-bit x86_64 systems:
o Custom Installation (Minimal): 900MB
o Server: 1.5GB
o Personal Desktop: 2.7GB
o Workstation: 3.4GB
o Custom Installation: (Everything) 7.5GB
4.3.\001Memory Requirements
This section lists the memory required to install Fedora Core 5 test1.
This list is for 32-bit x86 systems:
o Minimum for text-mode: 64MB
o Minimum for graphical: 192MB
o Recommended for graphical: 256MB
This list is for 64-bit x86_64 systems:
o Minimum for text-mode: 128MB
o Minimum for graphical: 256MB
o Recommended for graphical: 512MB
4.4.\001PPC Hardware Requirements
This section lists the minimum PowerPC (PPC) hardware needed to install
Fedora Core 5 test1.
o Minimum: PowerPC G3 / POWER4
o Fedora Core 5 test1 supports only the "New World" generation of Apple
Power Macintosh, shipped circa 1999 onwards. It also supports the
64-bit G5 processor and, POWER processors in IBM eServer pSeries.
Currently 32-bit IBM RS/6000 machines are not supported.
o Recommended for text-mode: 233 MHz G3 or better
o Recommended for graphical: 400 MHz G3 or better
5.\001Overview of This Release
[67][Caution] Information Out-of-Date
The content in this section needs to be updated for Fedora
Core 5 test1
6.\001Installation-Related Notes
This section outlines those issues that are related to Anaconda (the
Fedora Core installation program) and installing Fedora Core 5 test1 in
general.
[68][Note] Note
If you intend to download the Fedora Core 5 test1 DVD ISO
image, keep in mind that not all file downloading tools can
accommodate files larger than 2GB in size. For example, wget
will exit with a File size limit exceeded error.
The curl and ncftpget file downloading tools do not have this
limitation, and can successfully download files larger than
2GB.
Bittorrent is another method for downloading large files. For
information about obtaining and using the torrent file refer to
this website:
[69]http://torrent.fedoraproject.org/
6.1.\001PPC Installation Notes
6.1.1.\001PPC Hardware Requirements
This section lists the minimum PowerPC (PPC) hardware needed to install
Fedora Core 5 test1.
o Minimum: PowerPC G3 / POWER4
o Fedora Core 5 test1 supports only the "New World" generation of Apple
Power Macintosh, shipped circa 1999 onwards.
o Fedora Core 5 test1 also supports IBM eServer pSeries, IBM RS/6000,
and Genesi Pegasos II machines.
o Recommended for text-mode: 233 MHz G3 or better, 64MB RAM.
o Recommended for graphical: 400 MHz G3 or better, 128MB RAM.
The DVD or first CD of the installation set of Fedora Core is set to be
bootable on supported hardware. In addition, bootable CD images can be
found in the images/ directory of the DVD or first CD. These will behave
differently according to the hardware:
Boot Image Behavior by Hardware
Apple Macintosh
The bootloader should automatically boot the appropriate 32-bit or
64-bit installer. Power management support, including sleep and
backlight level management, is present in the apmud package, which
is in Fedora Extras. Fedora Extras for Fedora Core is configured
by default for yum. Following installation, apmud can be installed
by running the command yum install apmud in a terminal.
64-bit IBM eServer pSeries (POWER4/POWER5)
After using OpenFirmware to boot the CD, the bootloader (yaboot)
should automatically boot the 64-bit installer.
32-bit CHRP (IBM RS/6000 and others)
After using OpenFirmware to boot the CD, select the linux32 boot
image at the boot: prompt to start the 32-bit installer.
Otherwise, the 64-bit installer is started, which does not work.
Genesi Pegasos II
As of Fedora Core 5 test1, firmware with full support for ISO9660
file systems is not yet released for the Pegasos. However, the
network boot image can be used. At the OpenFirmware prompt, enter
the command:
boot cd: /images/netboot/ppc32.img
You will also need to configure OpenFirmware on the Pegasos
manually to make the installed Fedora Core system bootable. To do
this, you need to set the boot-device and boot-file environment
variables appropriately.
Network booting
There are combined images containing the installer kernel and
ramdisk in the images/netboot/ directory of the install tree.
These are intended for network booting with TFTP, but can be used
in many ways.
The command yaboot supports tftp booting for IBM eServer pSeries
and Apple Macintosh. Fedora recommends using yaboot over the
netboot images.
6.2.\001Anaconda Notes
o The Fedora Core installation program has the ability to test the
integrity of the installation media. It works with the CD, DVD, hard
drive ISO, and NFS ISO installation methods. Red Hat 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 the mediacheck, boot with the option:
linux ide=nodma
Use the sha1sum utility to verify discs before carrying out an
installation. This test accurately identifies discs that are not valid
or identical to the ISO image files.
o Memory testing may be performed prior to installing Fedora Core by
entering memtest86 at the boot: prompt. This causes the Memtest86
standalone memory testing software to run. Memtest86 memory testing
continues until the Esc key is pressed.
NOTE: You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use
this feature.
o Fedora Core 5 test1 supports graphical FTP and HTTP installations.
However, due to the necessity of containing the installer image in
RAM, only systems with more than 128MB of RAM (or systems booted from
CD-ROM 1, which contains the installer image) can use the graphical
installer. Systems with 128MB or less will continue to use the
text-based installer.
6.3.\001Installation-Related Issues
o Certain hardware configurations (particularly those with LCD displays)
may experience problems while starting the Fedora Core installation
program. In these instances, restart the installation, and add the
"nofb" option to the boot command line.
[70][Note] Note
Chinese, Japanese, and Korean graphical installations
started using the "nofb" option will start in English, and
then switch to the appropriate language once the graphical
phase of the installation process begins.
o Some Sony VAIO(R) notebook systems may experience problems installing
Fedora Core 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
This option allows the installation to proceed normally; any devices
not detected due to the use of this option will be configured the
first time Fedora Core is booted.
o Serial mice are known to be inoperative during installation. However,
there are indications that serial mice work properly in X after the
installation has completed. Refer to bug 119474 for more information:
o There have been issues observed when upgrading Red Hat Linux 7.<x>,
8.0, 9, and Fedora Core 1, 2, and 3 systems where third party packages
are installed that conflict with packages provided by Fedora Project.
One example is Ximian GNOME.
The issue with Ximian GNOME is caused by version overlap between the
official Red Hat Linux RPMs (or the ones from the Fedora Project) and
the Ximian RPMs. This configuration is not supported. You have several
choices in resolving this particular issue:
a. You may remove Ximian GNOME from your system prior to upgrading
to Fedora Core.
b. You may upgrade your system, and then immediately reinstall
Ximian GNOME.
c. You may upgrade your system, and then immediately remove all
remaining Ximian RPMs, replacing them with the corresponding
Fedora Core RPMs.
You must resolve the version overlap using one of the above choices.
Failure to do so will result in an unstable GNOME configuration.
7.\001Package-Specific Notes
The following sections contain information regarding packages that have
undergone significant changes for Fedora Core 5 test1. For easier access,
they are generally organized using the same groups used in Anaconda.
[72][Caution] Information Out-of-Date
The content in this section needs to be updated for Fedora
Core 5 test1
7.1.\001Basic Components
This section contains information related to basic system components.
7.1.1.\001Fedora Extras Repository
Fedora Extras is part of the larger Fedora Project and is a
volunteer-based community effort to create a repository of packages that
compliment Fedora Core. The Fedora Extras repository is enabled by default
from Fedora Core 5 test1 onwards.
You can lean more about Fedora Extras from:
[73]http://fedoraproject.org/wiki/Extras
If you would like to install any software available from Fedora extras you
can use yum.
yum install <packagename>
Where <packagename> is the name of the package you want to install. For
example, if you wanted to install the abiword package, the command yum
install abiword automatically installs the package and all dependencies.
7.1.2.\001Audit Daemon auditd and Log Files
The audit daemon, auditd, is now enabled by default. When auditd is
running, the kernel directs audit messages to /var/log/audit/audit.log.
The location of this file is specified in /etc/auditd.conf.
AVC messages for SELinux are sent using the audit infrastructure. These
messages are now in /var/log/audit/audit.log.
When auditd is not running, the kernel passes audit messages to syslog.
These logs are typically kept in /var/log/messages and are viewable using
dmesg.
Audit extensions are now compiled into PAM. All programs that do grant
entry to the system or change user account attributes will generate an
audit message.
To enable auditing within the kernel, you must pass the parameter audit=1
to the kernel during boot. Otherwise, you can use this command to enable
auditing during run time:
auditctl -e 1
7.1.3.\001LinuxThreads versus NPTL
As the next step in removing support for the obsolete LinuxThreads
library, code compiled and linked on Fedora Core 5 test1 now automatically
uses the NPTL headers and libraries.
In previous releases since Red Hat Linux 9, the default threading was
LinuxThreads since the interface is mostly forward compatible. The
advantages of the NPTL interface is that the cancellation handling is
faster (when -fexception is used, even in C code) and that the additional
interfaces are now available without special compiler and linker
parameters. In other words, you do not need to use -I/usr/include/nptl and
-L/usr/lib{,64}/nptl any longer. Note that lib{,64} is to be interpreted
as lib64 on platforms which place DSOs in lib64/ directories, and lib/
otherwise.
In Fedora Core 5 test1 it is still possible to create code using the
LinuxThreads definitions. For this the linuxthreads-devel package must be
installed and
Previously, you could select the version of glibc and the libpgthread DSH
using run time environment variables. You now need to also specify this
variable in the environment:
LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads
This additional variable is required because the run/time libraries have
been moved out of the way. There may be programs that will not work if the
program uses an unfortunate DT_RPATH (which overwrites the LD_LIBRARY_PATH
setting).
All this makes it more cumbersome to run programs which depend on
LinuxThreads. But this is intentional.
[74][Important] Important
FC5 will not have LinuxThreads support and all programs
have to be converted to use NPTL by then.
In general, conversion to using NPTL has not been an issue.
7.1.4.\001Enabling the slocate Database
The database needed by the locate utility is no longer created by default.
Enable the database creation by setting DAILY_UPDATE to yes in
/etc/updatedb.conf if you want to use locate.
7.1.5.\001Stricter Controls in openssh
The version of OpenSSH in Fedora Core 5 test1 is based on OpenSSH 3.9 and
includes strict permission and ownership checks for the user configuration
file ~/.ssh/config. If this file does not have appropriate ownership and
permissions, ssh will exit.
Check that ~/.ssh/config is owned by the owner of ~/, and that its
permissions are set to mode 600.
ls -l ~/.ssh/config
-rw------- 1 username username 400 May 5 18:44 /home/username/.ssh/config
The directory ~/ is command-line shorthand for the logged in user's home
directory, usually /home/username/.
In addition, OpenSSH is no longer configured to request X11 forwarding by
default when connecting to servers. To enable X11 forwarding, the -X or -Y
option must be specified, or the ForwardX11 option must be enabled in the
~/.ssh/config file.
The behavior of ssh clients that are invoked with the -X option has
changed. In OpenSSH 3.8 and later, X11 forwarding is performed in a way
that applications run as untrusted clients by default. Previously, X11
forwarding was performed so that applications always ran as trusted
clients. Some applications may not function properly when run as untrusted
clients. To forward X11 so that applications are run as trusted clients,
invoke ssh with the -Y option instead of the -X option, or set
ForwardX11Trusted in the ~/.ssh/config file.
7.1.6.\001Perl Binary Compat Symlinks
Binary compat symlinks for perl-5.8.0, perl-5.8.1, and perl-5.8.2 have
been removed. If you have perl modules built with those older versions of
perl, you need to rebuild using the perl-5.8.6 contained in Fedora Core 5
test1.
7.1.7.\001Server and System Configuration Tools
[75][Caution] Information Out-of-Date
The content in this section needs to be updated for Fedora
Core 5 test1
This section highlights changes and additions to the various GUI server
and system configuration tools in Fedora Core.
7.1.7.1.\001system-config-lvm
The new LVM tool system-config-lvm assists you in managing logical
volumes.
7.1.8.\001Java Package Recommendations
[76][Caution] Information Out-of-Date
The content in this section needs to be updated for Fedora
Core 5 test1
Fedora Core 5 test1 users are advised not to use the Java RPM provided by
Sun. It contains Provides that conflict with names used in packages
provided as part of Fedora Core 5 test1. Because of this, Sun Java might
disappear from an installed system during package upgrade operations.
Fedora Core 5 test1 users should use either the RPM from jpackage.org or
manually install the Sun Java tarball into /opt.
7.2.\001Core
This section contains the most elemental components of Fedora Core,
including the kernel.
7.2.1.\001yum
The sqllite database is now used by yum, and makes performance noticeably
faster.
The Fedora Extras repository is now enabled by default.
7.2.2.\001 Linux Kernel
7.2.2.1.\001Version
The distribution is based on the 2.6 series of the Linux kernel. Fedora
Core may include additional patches for improvements, bug fixes, or
additional features. For this reason, the Fedora Core kernel may not be
line-for-line equivalent to the vanilla kernel from the [77]kernel.org
website.
You may obtain a list of any such patches by using the command on the
Fedora Core package:
rpm -qpl kernel-version.src.rpm
7.2.2.2.\001Kernel Flavors
Fedora Core includes the following kernel builds:
o Native kernel, in both uniprocessor and SMP varieties. Configured
sources are available in the kernel-devel-version.arch.rpm package.
o Virtual kernel for use with the Xen emulator package. Configured
sources are available in the kernel-xen0-devel-version.arch.rpm
package.
Sources for both kernel flavors may be installed at the same time. The
files are installed into the /usr/src/kernels/version[-xen0]-arch/ tree.
Use the command:
rpm -Uvh kernel-devel[-xen0]-version.arch.rpm
as appropriate.
[78][Tip] Following Generic Textbooks About the Linux Kernel
Many of the tutorials, examples, and textbooks about Linux
kernel development assume the kernel sources are installed under
the /usr/src/linux directory. If you make a symbolic link, as
shown below, you should be able to use those learning materials
with the Fedora Core packages. Install the appropriate kernel
sources, as shown earlier, and then:
Fedora Core 5 test1 does not include the kernel-source package provided by
older versions. Instead, configured sources are available as described in
[79]Section\0017.2.2.2, "Kernel Flavors". Users that require access to
Fedora Core original kernel sources can find them in the kernel .src.rpm
package. To create an exploded source tree from this file, perform the
following steps:
[80][Important] These Instructions Refer to the Currently-running Kernel!
To simplify the following directions, the assumption is
that you want to configure the kernel sources to match
your currently-running kernel. In the steps below, you
must understand that the phrase version refers to the
kernel version shown by this command:
uname -r
1. Obtain the kernel-version.src.rpm file from one of the following
sources:
o The SRPMS/ directory on the appropriate SRPMS CD ISO image.
o The FTP site where you got the kernel package.
o By running the following command:
up2date --get-source kernel
2. Install kernel-version.src.rpm using the command:
rpm -Uvh kernel-version.src.rpm
This writes the RPM contents into /usr/src/redhat/SOURCES and
/usr/src/redhat/SPECS.
3. Prepare the kernel sources using the commands:
cd /usr/src/redhat/SPECS
rpmbuild -bp --target $(arch) kernel-2.6.spec
The kernel source tree is located in the
/usr/src/redhat/BUILD/kernel-version directory. It is common practice
to move the resulting linux-version directory to the /usr/src tree;
while not strictly necessary, doing so matches you with the
generally-available documentation.
cd /usr/src/redhat/BUILD/kernel-version /usr/src/
mv linux-version /usr/src/
cd /usr/src
ln -s ./linux-version linux
cd /usr/src/linux
4. The configurations for the specific kernels shipped in Fedora Core 5
test1 are in the configs/ directory. For example, the i686 SMP
configuration file is named configs/kernel-version-i686-smp.config.
Issue the following command to place the desired configuration file in
the proper place for building:
cp configs/desired-config-file .config
You can also find the .config file that matches your current kernel
configuration in the /lib/modules/version/build/.config file.
5. Every kernel gets a name based on its version number. This is the
value the uname -r command displays. The kernel name is defined by the
first four lines of the kernel Makefile. To protect the innocent, the
Makefile has been changed to generate a kernel with a different name
from that of the running kernel. Before a module can be accepted by
the running kernel, that module must have been compiled for a kernel
with the correct name. To do this, you must edit the kernel Makefile
For example, if the uname -r returns the string 2.6.11-1.234_FC4,
change the EXTRAVERSION definition from this:
EXTRAVERSION = -prep
to this:
EXTRAVERSION = -1.234_FC4
That is, substitute everything from the final dash onward.
6. Issue the following command:
make oldconfig
You can then proceed as usual.
7.2.2.4.\001Building Only Kernel Modules
An exploded source tree is not required to build a kernel module, such as
your own device driver, against the currently in-use kernel.
For example, to build the foo.ko module, create the following Makefile in
the directory containing the foo.c file:
Issue the make command to build the foo.ko module.
7.2.2.5.\001User Space Dependencies on the Kernel
Fedora Core adds support for clustered systems. This requires a special
kernel that works in conjunction with some user-space utilities, such as
management daemons. Consequently, to remove such a kernel, perhaps after
an update, you cannot simply use the rpm -e kernel-version command as in
earlier distributions because these user space packages depend on the
kernel package. You may either list both the kernel package and its user
space dependent packages on the rpm -e command, or you may wish to use the
yum remove kernel-version command instead since yum automatically removes
dependent packages if necessary.
7.2.3.\001Security
This section highlights various security items from Fedora Core.
Pam_stack is deprecated. More details available from fedora-test-list
([81]http://www.redhat.com/mailman/listinfo/fedora-test-list
7.2.3.1.\001Security Highlights
This section highlights various security items from Fedora Core.
Digital certificates are now centralised in directories under /etc/pki/.
Users performing an upgrade must relocate their digital certificates.
OpenSSL: the /usr/share/ssl/ contents have moved to /etc/pki/tls/ and
/etc/pki/CA/.
Dovecot: A dovecot-openssl.cnf file is automatically installed in
/etc/pki/dovecot/.
7.2.3.2.\001SELinux Changes
MCS SELinux is in somewhere. Major highlight. For more information, read
this informative article:
SCIM has replaced all the other input methods. Major highlight.
7.3.1.\001Language Support
This section includes information related to the support of various
languages under Fedora Core.
7.3.1.1.\001The IIIMF Input System
IIIMF is the Internet/Intranet Input Method Framework. In Fedora Core 5
test1 the iiimf package is updated to version 12.2.
File Path Changes
The names and locations of some files in the iiimf packages have
changed.
The IIIMF server has been renamed from /usr/sbin/htt to
/usr/bin/iiimd, and the XIM bridge client renamed from httx to
iiimx. The init.d script name has not changed: it is still called
iiim. All the global system configuration files are now located
under /etc/iiim/.
Language Engine (LE) developers should note that LE modules and
their data now live under ${libdir}/iiim/le/<LE_NAME>/, while
runtime data is stored under /var/lib/iiim/le/<LE_NAME>/.
For more information on the exact path and file location changes,
please refer to Fedora IIIMF FAQ:
Trigger keys, such as Ctrl-Space used to activate Input Methods,
are now configurable with the command-line tool iiimf-le-tools.
This feature is only supported by GTK2 applications currently. For
other applications using XIM the trigger key can be changed using
an X resource. Refer to the IIIMF FAQ at
[84]http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html for
more details on how to change trigger hotkeys.
Note that the keyname refers to the X key symbol name. For
example, if you want to activate with Ctrl-@, you need to specify
'<Control>at' as the keyname not '<Control>@'.
The per-user configuration of hotkeys does not work currently with
SELinux in enforcing mode due to lack of SELinux policy. In this
case, the hotkey can only be changed in the system-wide
configuration.
Qt Support
A Qt immodule for iiimf is now included. This immodule works but
lacks a status window and is considered experimental. Therefore,
the default for Qt applications is to continue using XIM for IIMF
input.
If you wish to try the immodule in a Qt application, first install
the iiimf-qt package, start the application, then click mouse
button-3 in an input area and select iiimqcf from the Select Input
Method' submenu.
7.4.\001Multimedia
Fedora Core includes applications for assorted multimedia functions,
including playback, recording, and editing. Additional packages are
available through the Fedora Extras repository.
Multimedia Players
By default, Fedora Core installs with rhythmbox, totem, and Helix
Player (hxplay) for media playback. In addition, many other
programs are available in the Fedora Core and Fedora Extras
repositories, including the popular xmms package. Both GNOME and
KDE also have specific sets of programs that can be used with a
variety of formats. Other popular programs, such as
Adobe/Macromedia's Flash Player, Real Player, VLC, MPlayer, and
Xine, can also be installed, but are excluded from the Fedora
repositories since they are not compatible with Fedora's licensing
or are usually distributed with support for restricted formats.
For more on this, refer to [85]Section\0017.4.1, "Excluded
Multimedia Software".
Fedora Core is also equipped to take full advantage of the
Advanced Linux Sound Architecture (ALSA) sound system. This means
that 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 old limitation
disappears. For more information about ALSA, visit the project
website:
[86]http://www.alsa-project.org/
Ogg and Xiph.Org Foundation Formats
Fedora includes complete support for the Ogg media container
format, the Vorbis audio, Theora video, Speex audio, and FLAC
lossless audio formats. More information on these formats and how
to use them can be found at the Xiph.Org Foundation's web site:
[87]http://www.xiph.org/
MP3 & DVD Support
Fedora Core and Fedora Extras cannot include support for MP3 or
DVD playback or recording, because the MP3 and MPEG (DVD) formats
are patented, and the patent owners have not provided the
necessary licenses. For more information, refer to
[88]Section\0017.4.1, "Excluded Multimedia Software".
7.4.1.\001Excluded Multimedia Software
Several programs are excluded from Fedora Core and Fedora Extras due to
licensing issues. These include programs that provide MP3 and DVD support,
Flash Player and Real Player. Users who wish to use these programs or
restricted formats have to acquire additional packages from third-party
repositories. Many of the multimedia applications in the Fedora
repositories support plugins, so support for new formats can be easily
added or removed. For more on this subject, please see:
[89]http://fedoraproject.org/wiki/ForbiddenItems
7.4.2.\001CD and DVD Authoring and Burning
Tools are included in Fedora Core and Fedora Extras for easily mastering
and burning CDs and DVDs. Tools that can be used from the console include
cdrecord, readcd, mkisofs, and other typical Linux applications. For GNOME
users, the xcdroast package from Fedora Core and the graveman package from
Fedora Extras allow easy preparation of audio and data discs. For KDE
users, the k3b package provides a very robust tool for these tasks.
7.5.\001Games and Entertainment
Fedora Core and Fedora Extras provide a selection of games that cover a
variety of genres. By default, Fedora Coreincludes a small package of
games for GNOME (called gnome-games). For a list of other games that are
available for installation through yum, open a terminal and enter the
following command:
yum groupinfo "Games and Entertainment"
For help using yum to install the assorted game packages, refer to the
guide available at:
[90]http://fedora.redhat.com/docs/yum/
7.6.\001Web Servers
This section contains information on Web-related applications.
7.6.1.\001httpd
The following changes have been made to the default httpd configuration:
o The mod_cern_meta and mod_asis modules are no longer loaded by
default.
o The mod_ext_filter module is now loaded by default
7.7.\001Samba (Windows File System Compatibility)
This section contains information related to Samba, the suite of software
that enables Linux to interact with Microsoft Windows systems.
Browsing of Windows shares (also known as SMB browsing) fails on Fedora
Core 5 test1 systems that have the standard firewall configured. This is
most easily noticed in the failure of the desktop to display shares.
The firewall disrupts the broadcast mode of SMB browsing, which is the
default. There are two workarounds:
o Configure a WINS server on the network, and set the "wins server"
option in smb.conf to the address of the WINS server.
o Disable the firewall.
[91][Warning] Disabling the firewall may make your system vulnerable
Make sure you fully understand the risks before undertaking
this step.
For additional information, refer to the following bug report:
[93][Caution] Information Out-of-Date
The content in this section needs to be updated for Fedora
Core 5 test1
This section contains information related to the X Window System
implementation provided with Fedora Core.
7.8.1.\001xorg-x11
Users new to the X.org X11 implementation should take note of a few
differences between it and the XFree86.org X11 implementation which
shipped in previous Red Hat and Fedora operating systems. In particular,
the names of some files have changed:
X Server Binary:
o XFree86 X11: XFree86
o X.org X11: Xorg
X Server Configuration File:
o XFree86 X11: /etc/X11/XF86Config
o X.org X11: /etc/X11/xorg.conf
X Server Log File:
o XFree86 X11: /var/log/XFree86.$DISPLAY.log
o X.org X11: /var/log/Xorg.$DISPLAY.log
When configuring or troubleshooting your X server configuration, be sure
that you are using the correct files.
There has been some confusion regarding font-related issues under the X
Window System in recent versions of Fedora Core (and versions of Red Hat
Linux before it.) At the present time, there are two font subsystems, each
with different characteristics:
o The original (15+ year old) subsystem is referred to as the core X
font subsystem. Fonts rendered by this subsystem are not anti-aliased,
are handled by the X server, and have names such as:
-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
o The newer font subsystem is known as fontconfig, and allows
applications direct access to the font files. Fontconfig is often used
along with the Xft library, which allows applications to render
fontconfig fonts to the screen with antialiasing. Fontconfig uses more
human-friendly names such as: Luxi Sans-10
Over time, fontconfig and Xft will replace the core X font subsystem. At
the present time, applications using the Qt 3 or GTK 2 toolkits (which
would include KDE and GNOME applications) use the fontconfig and Xft font
subsystem; almost everything else uses the core X fonts.
In the future, Fedora Core may support only fontconfig/Xft in place of the
XFS font server as the default local font access method.
[94][Note] Note
An exception to the font subsystem usage outlined above is
OpenOffice.org, which uses its own font rendering technology.
The steps to add new fonts to Fedora Core 5 test1 depend on the fonts
subsystem this is going to use the new fonts. For the core X font
subsystem:
1. Create the /usr/share/fonts/local/ directory (if it doesn't already
exist):
mkdir /usr/share/fonts/local/
2. Copy the new font file into /usr/share/fonts/local/
3. Update the font information by issuing the following commands (note
that, due to formatting restrictions, the following commands may
appear on more than one line; in use, each command should be entered
on a single line):
4. If you had to create /usr/share/fonts/local/, you must then add it to
the X font server (xfs) path:
chkfontpath --add /usr/share/fonts/local/
Adding new fonts to the fontconfig font subsystem is more straightforward;
the new font file only needs to be copied into the /usr/share/fonts/
directory (individual users can modify their personal font configuration
by copying the font file into the ~/.fonts/ directory).
After the new font has been copied, use fc-cache to update the font
information cache:
fc-cache <directory>
(Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
directories.)
Individual users may also install fonts graphically, by browsing fonts:///
in Nautilus, and dragging the new font files there.
[95][Note] Note
If the font filename ends with ".gz", it has been compressed
with gzip, and must be decompressed (with the gunzip command)
before the fontconfig font subsystem can use the font.
Due to the transition to the new font system based on fontconfig/Xft, GTK+
1.2 applications are not affected by any changes made via the Font
Preferences dialog. For these applications, a font can be configured by
adding the following lines to the file ~/.gtkrc.mine:
(Where <font-specification> represents a font specification in the style
used by traditional X applications, such as
"-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*".)
7.9.\001Games and Entertainment
Fedora Core and Fedora Extras provide a selection of games that cover a
variety of genres. By default, Fedora Coreincludes a small package of
games for GNOME (called gnome-games). For a list of other games that are
available for installation through yum, open a terminal and enter the
following command:
yum groupinfo "Games and Entertainment"
For help using yum to install the assorted game packages, refer to the
guide available at:
[96]http://fedora.redhat.com/docs/yum/
8.\001Packages Movement
This command was used to generate the list of package changes. The
backslash \ is used to artificially break the line for printing purposes.:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
