&NAME;, &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Ma=
ximum
RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
RHmember, RHmember More, Rough Cuts, Rawhide and all &RH;-based
trademarks and logos are trademarks or registered trademarks of
&FORMAL-RHI; in the United States and other countries.Linux is a registered trademark of Linus Torvalds.Motif and UNIX are registered trademarks of The Open Group.
Intel and Pentium are registered trademarks of Intel
Corporation. Itanium and Celeron are trademarks of Intel
Corporation.AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanc=
ed
Micro Devices, Inc.Windows is a registered trademark of Microsoft Corporation.
SSH and Secure Shell are trademarks of SSH Communications Secur=
ity,
Inc.FireWire is a trademark of Apple Computer Corporation.All other trademarks and copyrights referred to are the propert=
y of
their respective owners.The GPG fingerprint of the "Fedora Project
<fedora(a)redhat.com>" key is:CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
DIRECTORY ORGANIZATION&DISTRO; is delivered on multiple CD-ROMs consisting of installat=
ion
CD-ROMs and source code CD-ROMs.The first installation CD-ROM can be directly booted into the
installation on most modern systems, and contains the following direc=
tory
structure (where /mnt/cdrom is the mount point o=
f the
CD-ROM):
/mnt/cdrom
|----> Fedora
| |----> RPMS -- binary packages
| `----> base -- information on this release of Fedora
| Core used by the installation process
|----> images -- boot and driver disk images
|----> isolinux -- files necessary to boot from CD-ROM
|----> README -- this file
|----> RELEASE-NOTES -- the latest information about this release
| of Fedora Core
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat
The remaining Installation CD-ROMs are similar to Installation CD=
-ROM
1, except that only the Fedora subdirectory is
present.The directory layout of each source code CD-ROM is as follows:
/mnt/cdrom
|----> SRPMS -- source packages
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat
If you are setting up an installation tree for NFS, FTP, or HTTP
installations, you need to copy the RELEASE-NOTES
files and all files from the Fedora directory on
discs 1-3. On Linux and Unix systems, the following process will pro=
perly
configure the /target/directory on your server (repeat for each disc)=
:Insert discmount /mnt/cdromcp -a /mnt/cdrom/Fedora
/target/directorycp /mnt/cdrom/RELEASE-NOTES* /target/directory
(Do this only for disc 1)umount /mnt/cdromINSTALLINGMany computers can now automatically boot from CD-ROMs. If you ha=
ve
such a machine (and it is properly configured) you can boot the &DIST=
RO;
CD-ROM directly. After booting, the &DISTRO; installation program wi=
ll
start, and you will be able to install your system from the CD-ROM.=
para>
The
images/ directory contains the file
boot.iso. This file is an ISO image that can be=
used
to boot the &DISTRO; installation program. It is a handy way to start
network-based installations without having to use multiple diskettes.=
To
use boot.iso, your computer must be able to boot=
from
its CD-ROM drive, and its BIOS settings must be configured to do so. =
You
must then burn boot.iso onto a recordable/rewrit=
eable
CD-ROM. Another image
file contained in the images/ directory is
diskboot.img. This file is designed for use wit=
h USB
pen drives (or other bootable media with a capacity larger than a dis=
kette
drive). Use the dd command to write the image.
NoteThe ability to use this image file with a USB pen drive depends=
on
the ability of your system's BIOS to boot from a USB device.GETTING HELPFor those that have web access, see http://fedora.redhat.com. =
In
particular, access to &PROJ; mailing lists can be found at:https://listman.re=
dhat.com/mailman/listinfo/EXPORT CONTROLThe communication or transfer of any information received with th=
is
product may be subject to specific government export approval. User =
shall
adhere to all applicable laws, regulations and rules relating to the
export or re-export of technical data or products to any proscribed
country listed in such applicable laws, regulations and rules unless
properly authorized. The obligations under this paragraph shall surv=
ive
in perpetuity.
--- NEW FILE RELEASE-NOTES-master-it.xml ---
=
]>
&PROD; @VARIANTUPPER@ &PRODVER; Release Notes2003&FORMAL-RHI;Overview
=
The following topics are covered in these release notes:Booting AnacondaParameter file notesInstallation-related notesNotes on input methodsGeneral notesKernel notesBooting AnacondaThis section describes the process necessary to boot
Anaconda, the &PROD; installation
program.For the IBM
eServerpSeries:The first CD-ROM is bootable, and c=
an
be used to start the installation process. If a CD-ROM-based install=
ation
is not desired (for example, if you want to install &PROD; &PRODVER; =
over a
network connection), a CD-ROM image file containing only those files
required to start the installation process is also available as
boot.iso in the images/
directory on the first CD-ROM.
=
=
A network boot image (named
netboot.img) is available, and is located in the
images/ directory on Installation CD 1. Consult=
the
documentation that came with your system for instructions on setting =
up
network boot. Kernel command line arguments (such as anaconda option=
s)
must be passed from the Open Firmware prompt. For example, if there =
is a
devalias named network for the device that is
configured for network booting, the following command line would load=
a
driver disk from an HTTP server:
=
=
boot network
dd=3Dhttp://server.example.com/path/to/driverdisk.img
=
=
Additional documentation for configuring netboot on =
pSeries can be
found here:http://people.redhat.com/msw/mirror/penguinppc.org/~=
hollis/linux/rs6k-netboot.shtmlFor the IBM eServer iSeries:<=
/para>
You must direct OS/400 to boot the stream file
ppc/iSeries/boot.img, which is located on the fi=
rst
CD-ROM. You can either point directly at the CD-ROM or copy the file=
to a
location in IFS. When the installation is complete, it will boot from
side C, but this will only work until you vary off your LPAR. After
varying off your LPAR, you must change your IPL source to side B to
continue booting &PROD;.You must download the
kernel.img and initrd.img f=
iles
from the images/ directory into CMS. You can th=
en
use these with a parameter file (described in the following section) =
to
start your installation. Once the Linux kernel has booted, use ssh to
access your VM and start the installation process. When the installa=
tion
finishes, you must use a command similar to #cp ipl
0200 to bootstrap (or IPL) the Linux installation on the DA=
SD at
0200.Parameter File NotesThe IBM S/390 and IBM
eServer zSeries archite=
ctures
use a special parameter file to set up networking before the
installation program (anaconda) can be
started. This section describes the contents of the parameter
file.The parameter file should contain no more than 80 characters per
line.
=
The VM reader has a limit of 11 lines for the parameter file (for=
a
total of 880 characters).
=
The DASD and the tape IPL have a limit of 896 characters.The following parameters are required, and should always be
present:DASD=3D<dasd-list><=
/command>Where
<dasd-list>
represents the list of DASD devices to be used by &PROD;. The li=
st
can consist of one or more DASD numbers separated by commas, and =
can
also contain ranges, which are specified by two DASD numbers sepa=
rated
by a hyphen. Both constructs can be combined in a single list, a=
s in
the following example:DASD=3D10A8,10A9,10AA,10A3-10A6NOTE: Although autoprobing for DASDs is done if this paramete=
r is
omitted, &RH; highly recommend including the DASD=3D parameter as=
the
device numbers (and therefore the device names) can vary when new=
DASD
is added to the &PROD; guest. This can result in an unusable
system.root=3D<file-system>Where
<file-system>
represents the device on which the root file system can be found.=
For
for installation purposes, it should be set to
/dev/ram0, which is the ramdisk containing the
&PROD; installation program.The following parameters are required to set up networking:CHANDEV=3D<device>,=
<input>,<output>where:·
<device> is t=
he
type of device (for example, ctc0,
escon0, or lcs0)·
<input> is the
input port for this device·
<output> is t=
he
output port for this deviceFor example:CHANDEV=3Dctc0,0x600,0x601CHANDEV=3Descon0,0x605,0x608To force a specific CTC protocol, additional parameters can be
added. For example:CHANDEV=3Dctc0,0x600,0x601,0,<n><=
/replaceable>where <n> is one of the
following:· 0 for compatibility mode (used wi=
th
non-Linux peers other than S/390 and zSeries operating systems)=
para>
· 1 for extended mode· 2 for CTC-based tty (only support=
ed on
Linux-to-Linux connections)· 3 for compatibility mode with S/3=
90
and zSeries operating systemsIUCV=3D<userid>Where <userid>
represents the ID of the guest machines you want to connect to. =
Note
that the ID must be written in capital letters. For example, an =
IUCV
connection to the VM TCP/IP service machine would be written
as:IUCV=3DTCPIP
=
The following parameters are optional:HOSTNAME=3D<string>=
where <string>
is the hostname of the newly-installed Linux guest.NETTYPE=3D<type>where <type>
must be one of the following: ctc,
escon, tr,
hsi, iucv, or
eth.IPADDR=3D<IP>where <IP> is
the IP address of the new Linux guest.NETWORK=3D<network>=
where
<network> is =
the
address of your network.NETMASK=3D<netmask>=
where
<netmask> is =
the
netmask.BROADCAST=3D<broadcast>where
<broadcast> i=
s the
broadcast address.GATEWAY=3D<gw>where <gw> is
either the gateway-IP for your eth device or the IP address of the
ctc/escon/iucv point-to-point partner.MTU=3D<mtu>where <mtu> is
the Maximum Transmission Unit (MTU) for this connection.DNS=3D<server1>:<server2>:…:<serverN&g=
t;where
<server1>:=
<server2>:…:<serverN>
is a list of DNS servers, separated by colons. For example:
DNS=3D10.0.0.1:10.0.0.2SEARCHDNS=3D<domain1>:<domain2>:…:<dom=
ainN>where
<domain1>:=
<domain2>:…:<domainN>
is a list of the search domains, separated by colons. For
example:SEARCHDNS=3Dexample.com:example.orgThe following parameter for installations using a qeth device is
optional:QETHPARM=3DUse this option to specify additional parameters for your QETH
device (for CHANDEV) such as:add_parms,0x10,{lo_devno,hi_devno},portname:<port_name>The following parameter for kickstart installation is optional:=
para>
RUNKS=3D<value>Where <value>
is 1 if you want to run the installation progr=
am in
non-interactive mode in the 3270 terminal, or 0
otherwise.NOTE: Make sure that your kickstart file contains all required
parameters before you use this option.Installation-Related NotesThis section describes issues related to the &PROD; installation
program Anaconda.The sequence for processing CD-ROMs has changed for &PROD;
&PRODVER;. The first CD-ROM is required when booting the install=
ation
program, and again after subsequent CD-ROMs have been
processed.The &PROD; installation program has the ability to test the
integrity of the installation media. It works with the CD, hard
drive ISO, and NFS ISO installation methods. &RH; recommends th=
at
you test all installation media before starting the installation
process, and before reporting any installation-related bugs (ma=
ny of
the bugs reported are actually due to improperly-burned CDs). T=
o use
this test, type linux mediacheck at the
boot: prompt.The Object-code-only (OCO) driver necessary to support the IBM
3590 Tape Drive on the IBM S/390(R) and IBM eServer zSeries(R)
architectures is available for download from IBM here:
=
http://www10.software.ibm.com/developerworks/opensource/linux=
390/special_oco_rh_2.4.shtmlNOTE: You must verify that the driver you download is the cor=
rect
one for the version of the kernel running on your system.A new storage option is available on the s390 and zSeries
architectures: a SCSI subsystem. To that end, generic SCSI suppo=
rt is
enabled and a driver (known as zfcp) is
supplied.
=
=
The generic SCSI subsystem on &PROD; &PRODVER; does not use t=
he
REPORT LUNs command at this time; therefore use small LUN numbers=
for
virtual volumes. In addition, the following line must be supplie=
d in
/etc/modules.conf:options scsi_mod
max_scsi_luns=3D<NNN>(Where <NNN>
should be a number larger than the largest LUN number used.) NOT=
E:
Larger values slow the bootstrapping process somewhat.&PROD; &PRODVER; includes a new kernel known as the
hugemem kernel. This kernel supports a 4G=
B per
process user space (versus 3GB for the other kernels), and a 4GB
direct kernel space. Using this kernel allows &PROD; to run on sy=
stems
with up to 64GB of main memory. The hugemem kernel is required in
order to use all the memory in system configurations containing m=
ore
than 16GB of memory. The hugemem kernel can also benefit
configurations running with less memory (if running an application
that could benefit from the larger per process user space, for
example.)To remind you of this issue, the &PROD; &PRODVER; kernel disp=
lays a
message at boot time if your system configuration contains more t=
han
16GB of memory. After the system has booted, the following comma=
nd
can be used to see if your system displayed the message:dmesg | lessNOTE: To provide a 4GB address space for both kernel and user
space, the kernel must maintain two separate virtual memory addre=
ss
mappings. This introduces overhead when transferring from user to
kernel space; for example, in the case of system calls and interr=
upts.
The impact of this overhead on overall performance is highly
application dependent.Also note that, because some drivers were not originally writ=
ten
to work well in large-memory environments, &RH; only supports a
validated subset of drivers when the hugemem kernel is used. Dri=
vers
that have been validated by &RH; for use with the hugemem kernel =
are
contained in the kernel-hugemem package. Dr=
ivers
that have not been validated, but are still provided, are availab=
le in
the kernel-hugemem-unsupported RPM. To see =
the
list of drivers in these RPMs, use the following command:rpm -qlp
<kernel-rpm>(Where <
kernel-rpm> is the complete filena=
me of
the appropriate hugemem RPM. Note that these RPMs can be fou=
nd on
CD-ROM #2, in the RedHat/RPMS/
directory.)Should you decide that the hugemem kernel's additional overhe=
ad
and the subset of available drivers present no problem for your
hardware configuration and system environment, and you wish to us=
e the
hugemem kernel, you must first install it. To install the hugemem
kernel, enter the following command while logged in as root:
rpm -ivh
<kernel-rpm>(Where
<kernel-rpm> =
is
the name of the hugemem kernel RPM file —
kernel-hugemem-2.4.21-3.EL.i686.rpm,
for example.)After the installation is complete, reboot your system, making
sure to select the newly-installed hugemem kernel. After testing=
your
system for proper operation while running the hugemem kernel, you
should modify the /boot/grub/grub.conf file =
so
that the hugemem kernel is booted by default.&PROD; &PRODVER; can be installed on the IBM eServer xSeries 440 and 445. However, t=
he
installation process supports configurations containing no more t=
han
one chassis, and no attached RXE-100 Remote Expansion Enclosures.=
If
your system configuration does not conform to these requirements,=
you
can remove any additional chassis and/or RXE-100s, and then perfo=
rm
the installation. Once the installation is complete, the chassis
and/or RXE-100s can then be re-installed, and will operate normal=
ly
under &PROD;.Support for some Input/Output Processors/Adapters (IOP/IOA)
present in some iSeries and pSeries systems require the use of the
IBMSIS driver. This driver can be found on the &PROD; &PRODVER;
Extras CD, and can be loaded as driver media when the &PROD;
installation process is started.Loading the IBMSIS driver via CD-ROM using a non-IDE CD-ROM d=
rive
(including the iSeries virtual CD-ROM drive) is possible by addin=
g the
following command to the boot command line:dd=3DcdromYou will then be prompted if you have any driver media for
additional drivers after all drivers included on the CD-ROM are
loaded. Note that this is in addition to the other methods of us=
ing
driver media as described in the &PROD; &PRODVER;
Installation Guide for the IBM eServer iSeries and IBM eServer pS=
eries
Architectures.After installation, IBMSIS users should install the
ibmsis and ibmsis-utils
packages from the &PROD; Extras CD.
=
=
After an upgrade to a new version of the kernel, the IBMSIS d=
river
must be rebuilt and installed. The ibmsistool
program (provided in the ibmsis package on t=
he
&PROD; &PRODVER; Extras CD) largely automates this process. The
kernel-source package that corresponds to th=
e new
kernel must be installed, as it provides the headers needed to bu=
ild
IBMSIS. For example, after installing the 2.4.21-3.EL kernel and
corresponding kernel-source packages, the
following command would update the IBMSIS driver:
=
=
/usr/sbin/ibmsistool -v 2.4.21-3.EL build
install&PROD; &PRODVER; now includes support for Logical
Volume Management (LVM). LVM is a means of allocat=
ing disk
space into one or more logical volumes, which can then be used to
implement easily-resizable file systems.While most present-day computers are able to start the
installation process by booting directly from the first &PROD;
distribution CD, some hardware configurations require the use of a
boot diskette. If your hardware requires a boot diskette, you sh=
ould
be aware of the following change.&PROD; &PRODVER; uses a different boot diskette layout than
previous releases of &PROD;. There is now a single boot diskette
image file (bootdisk.img) that is used to bo=
ot
all systems requiring a boot diskette.If you are performing anything other than an installation fro=
m an
IDE or USB device, you will be asked to insert a driver diskette
created from one of the following image files:· drvnet.img — For network
installations· drvblock.img — For SCSI
installations· pcmciadd.img — For PCMCIA
installationsAs with previous releases of &PROD;, these image files can be=
found
in the images/ directory on the first instal=
lation
CD.Due to the page-oriented nature of the 3270-style console, ou=
tput
to /dev/console can fill the screen. If the
screen is filled, the &PROD; environment stops operating until the
screen is cleared. The screen can be cleared using one of two
different methods:· By issuing the keystrokes necessary to clear the scr=
een
(For example,
AltC for t=
he
x3270 terminal emulator, and
CtrlC for =
the
c3270 terminal emulator.)· By waiting for the screen to be automatically cleare=
d.
The default wait time is 60 seconds; however, this can be changed=
by
using the following command:#cp term more
<alarm-time><clear-time>Where
<alarm-time>
represents the number of seconds between the time the screen fi=
lls
and the time the terminal alarm should be sounded, and
<clear-time> is
the number of seconds between the time the terminal alarm is so=
unded
and the screen is automatically cleared. Both the
<alarm-time> and
<clear-time>
parameters must be numbers between 0 and 255.NOTE: This aspect of the 3270-style console is most likely to=
be
an issue whenever a large amount of output is sent to
/dev/console. Therefore, the console's scre=
en is
most likely to fill at the following times:· During the &PROD; installation process· When &PROD; is booted· syslog messages are sent to the
consoleText mode installations using a serial terminal work best whe=
n the
terminal supports UTF-8. Under UNIX and Linux, Kermit supports U=
TF-8.
For Windows, Kermit '95 works well. Non-UTF-8 capable terminals =
will
work as long as only English is used during installation. An enh=
anced
serial display can be used by passing "utf8" a=
s a
boot-time option to the installation program. For example:linux console=3DttyS0 utf8The firewall configuration screen in the &PROD; installation
program has been simplified. The previous
"High", "Medium", and
"No firewall" settings have been replaced by=
a
more straightforward on/off-style control. In addition, the defa=
ult
firewall configuration is now stateful, making it more secure. T=
he
new design also makes it possible for users of NIS authentication,
NFS, and DNS to deploy a firewall with no additional customization
required (although customization by specifying port and protocol =
is
still possible).NOTE: This change also applies to the Security L=
evel
Configuration Tool
(redhat-config-securitylevel).Installation via VNC is now supported. To initiate a VNC-bas=
ed
installation, pass vnc as a boot-time option. =
If
necessary, a password can be set by adding
"vncpassword=3D<password>"
to the boot-time options. The VNC display will be
"<host>:1", w=
here
<host> is the
hostname or IP address of the system installing &PROD;.It is also possible for the &PROD; installation program to
initiate a connection to a listening VNC client. This is done by
using the vncconnect boot-time option:linux vnc
vncconnect=3D<client>[:<port>](Where
<client> is t=
he
hostname or IP address of the system running the listening VNC cl=
ient,
and <port> is=
an
optional port specification that may be specified if the VNC clie=
nt is
not listening on port 5500, which the default port for this type =
of
connection). The following examples show the how the boot-time o=
ption
is specified for standard and non-standard ports:linux vnc
vncconnect=3Dpigdog.example.comlinux vnc
vncconnect=3Dpigdog.example.com:27910The system that is to run the listening VNC client must then
launch the appropriate software to run the VNC client in its list=
ening
mode. For the VNC client supplied with &PROD; &PRODVER;, the
following command is sufficient:vncviewer -listenIn addition, a new kickstart directive has been added to supp=
ort
VNC-based installations:vnc [--password
<password>] [--connect
<host>[:<port&=
gt;]](Where --password
<password> is an opt=
ional
parameter for specifying a VNC password, and [--connect
<host>[:<port&=
gt;]]
is an optional parameter for specifying the host (and optionall=
y,
port) of a system running a listening VNC client.NOTE: If you specify any of the VNC-related boot-time options,
they will override the corresponding options present in the kicks=
tart
file.&PROD; &PRODVER; for the iSeries and pSeries
architectures includes support for installation using the VNC rem=
ote
display system, and support for accessing virtual consoles via te=
lnet
for installation on iSeries. VNC and telnet clients for a variet=
y of
platforms are available for download from:
=
=
http://www.ibm.com/servers/eserver/iseries/linux=
/products.htmlThe XFree86 open source vmware video driver is provided as a
convenience to our customers and is not supported in any way by
&FORMAL-RHI; However, any problem reports with the XFree86 open s=
ource
vmware video driver received by &RH; will be forwarded to the
appropriate VMware staff, so that they can investigate. Bug fixes
that become available for this driver may be reviewed by &RH; for
potential inclusion in future errata and products as time
permits.Input MethodsThis section contains general information related to the use of i=
nput
methods.An input method allows users to enter non-Western characters into
common applications such as word-processing, email and instant messag=
ing.
&PROD; comes with input method support for the following languages:=
para>
Chinese (Simplified and Traditional)JapaneseKoreanThe following entries describe the use of input methods for each =
of
these languages.Simplified Chinese
=
=
To enter Simplified Chinese characters, you use the miniChinp=
ut
input method. To activate the input method, press
CtrlSpace.=
=
=
The miniChinput input method supports the following
modules:· intelligent pinyin input· gbk pinyin input· shuang pin input· internal code (gb18030 code) input
=
=
The miniChinput package is installed by
default if Simplified Chinese language support is selected during
installation.
=
=
Traditional Chinese
=
=
To enter Traditional Chinese characters, you use the xcin inp=
ut
method. To activate the input method, press
CtrlSpace.
Pressing
ShiftCtrl =
or
CtrlAltNum
allows you to change between input modules.
=
=
The xcin input method supports the following modules:· CJ· Simplex· Phone· CantonPing· Bimsphone· Bimspinyin· Array30· Cantonping (no intonation)
=
=
The xcin package is installed by default=
if
Traditional Chinese language support is selected during
installation.Japanese
=
=
To enter Japanese characters, you use the Canna, FreeWnn or s=
kk
input methods. To activate the input method, press
ShiftSpace=
.
=
=
The following modules are supported:· romaji· kana (only Canna — depends on the configuration
file)
=
=
The Canna, FreeWnn,=
and
skkinput packages are installed by default if
Japanese language support is selected during installation.Korean
=
=
To enter Korean characters, you use the ami input method. To
activate the input method, press
ShiftSpace=
.
=
=
The ami package is installed by default =
if
Korean language support is selected during installation.General NotesThis section contains general notes relating to post-installation
issues.&PROD; &PRODVER; for the Itanium 2 Architecture contains the
fpswa.efi binary, which is an EFI (Extensible
Firmware Interface) driver invoked by the operating system's kern=
el
whenever the processor issues FPSWA (Floating-Point Software
Assistance) requests for floating-point operations that are not f=
ully
implemented in hardware. The handler provides the result of the
operation in these cases. Presently, Itanium processors issue FPS=
WA
requests mainly when very small numbers (denormalized, or tiny
numbers) are consumed or produced by floating-point instructions.=
To
avoid the performance penalty caused by calls to the handler when=
tiny
numbers are produced, the flush-to-zero mode can be turned on, bu=
t at
the cost of a slightly less accurate computation.
=
=
FPSWA is licensed, patented and copyrighted protected materia=
l by
Intel or its supplier under the laws of the United states and oth=
er
countries and international treaty provisions. FPSWA is subject t=
o the
applicable end user license agreement which can be accessed at
http://www.redhat.com/licenses/.The Apache HTTP server has been updated to version 2.0. The
updated package replaces version 1.3 and has been renamed to
httpd.· The auth_ldap,
mod_put, mod_roaming,
mod_auth_any, mod_bandwidth,
mod_throttle, and mod_dav
modules have been removed.· WebDAV functionality is now included with the
httpd package.NOTE: Some changes to existing configuration files are needed.
Third-party Apache modules may also require updating. Refer to t=
he
migration guide at
/usr/share/doc/httpd-*/migration.html for mo=
re
details.&PROD; &PRODVER; supports booting over the network using the =
PXE
(Pre-Boot Execution Environment) protocol. As in previous releas=
es it
is possible to configure &PROD; &PRODVER; as an installation serv=
er,
which makes kernels and image files available for the purpose of
starting network installations.Also available in &PROD; &PRODVER; is support for diskless
environments. A diskless server (similar to an installation serv=
er)
makes kernels and image files available to diskless client system=
s.
After booting, the diskless client systems mount a root file syst=
em
via NFS, eliminating the need for locally-attached storage.The Network Booting Tool
(redhat-config-netboot) is a graphical
configuration tool allows you to configure both environments.
The LPRng print spooler has been replaced by CUPS, and the
Printer Configuration Tool
(redhat-config-printer) is the recommended too=
l for
configuring it. It may be launched from the System
Settings menu, using the Printing
menu entry.The Security Level Configuration Tool
(redhat-config-securitylevel) has been
simplified. The previous "High",
"Medium", and "No
firewall" settings have been replaced by a more
straightforward on/off-style control. In addition, the default
firewall configuration is now stateful, making it more secure. =
The
new design also makes it possible for users of NIS authenticati=
on,
NFS, and DNS to deploy a firewall with no additional customizat=
ion
required (although customization by specifying port and protoco=
l is
still possible).NOTE: This change also applies to the &PROD; installation
program.GNOME Print Manager, a simple grap=
hical
print queue management tool, is now included. It may be launched=
from
the System Tools menu, using the =
Print
Manager menu entry. In addition, when a print job =
is in
the queue, an icon will appear in the panel's system notification
area.&PROD; &PRODVER; includes the setarch utility. Setarch makes=
it
possible to change the output produced by the uname
command. This is useful for a number of reasons, such as running
32-bit applications (those written to expect a particular value f=
rom
uname -m) in 64-bit environments.The format for the setarch command is:setarch <arch><command>(Where <arch>
represents the desired architecture string (such as
i386), and
<command>
represents the command to be run while the architecture has been
modified.) Note that
<command> can=
be
omitted, in which case /bin/sh is run.In addition, some applications (such as older versions of Jav=
a)
are written to assume a 3GB virtual address space; when run on sy=
stems
with larger virtual address spaces (such as 64-bit AMD64-based
systems, or 32-bit systems running the hugemem kernel) such
applications can malfunction. The setarch utility makes it possi=
ble
to emulate a 3GB virtual address space, allowing such application=
s to
run properly:setarch -3 javaAccelerated 3D rendering with DRI has been disabled in &PROD;
&PRODVER; for the IA64 architecture. On this architecture,the ag=
pgart
kernel driver does not function properly; since the DRI subsystem
depends on this driver, no 3D acceleration is possible. Note,
however, that this does not affect unaccelerated 3D rendering or
third-party drivers that provide their own agpgart
implementation.&PROD; &PRODVER; includes the Native POSIX Thread Library (NP=
TL),
a new implementation of POSIX threads for Linux. This library pro=
vides
performance improvements and increased scalability.This thread library is designed to be binary compatible with =
the
old LinuxThreads implementation; however, applications that rely =
on
the places where the LinuxThreads implementation deviates from the
POSIX standard will need to be fixed. Notable differences includ=
e:· Signal handling has changed from per-thread signal
handling to POSIX process signal handling.· getpid() returns the same value i=
n all
threads.· Thread handlers registered with
pthread_atfork are not run if
vfork() is used.· No manager thread.Applications that are known to have problems us=
ing
NPTL include:- Sun JRE prior to version 1.4.1- IBM JREIf an application does not work properly with NPTL, it can be=
run
using the old LinuxThreads implementation by setting the following
environment variable:LD_ASSUME_KERNEL=3D<kernel-version>=
The following versions are available:· 2.4.19 — Linuxthreads with floating stacks
· 2.2.5 — Linuxthreads without flo=
ating
stacksNote that software using errno,
h_errno, and _res must
#include the appropriate header file
(errno.h, netdb.h, and
resolv.h respectively) before they are used.
However, LD_ASSUME_KERNEL=3D2.4.19 can be used as a
workaround until the software can be fixed.Multi-threaded C++ programs using thread cancellation might n=
eed
to be forced to use the LinuxThreads library using the
LD_ASSUME_KERNEL=3D2.4.19 environment variable set=
ting.
Otherwise, the program will terminate abnormally if the cancellat=
ion
is acted on (since the generated exception is not caught).
=
=
Newly-written C++ code that uses functions from the C runtime
environment might have to be adjusted to take the cancellation in=
to
account. This can be done by one of the following methods:
=
=
· Not marking the C++ function with
throw() (so that callers are aware that an
exception might be thrown) and by compiling the code with excepti=
ons.
This is the default compilation option; users should not specify
-fno-exceptions when compiling.
=
=
· Disabling cancellation completely before entering the
functions that call the cancel-able C runtime functions. This ca=
n be
done with the following call:
=
=
pthread_setcancelstate (PTHREAD_CANCEL_DISABLE,
&oldstate)
=
=
After the C functions are called cancellation can be enabled =
again
with the following call:
=
=
pthread_setcancelstate (oldstate, NULL)
=
=
NOTE: At this point the cancellations are acted upon and ther=
efore
the function calling pthread_setcancelstate() must be compiled wi=
th
exceptions enabled and must be marked as throwing exceptions.
A new system message has been added to &PROD; &PRODVER;:
application bug:
<app-name>(<ap=
p-pid>)
has SIGCHLD set to SIG_IGN but calls wait(). (see the NOTES se=
ction
of 'man 2 wait'). Workaround activated.This message (which is displayed on the system console and/or=
in
the system log files) indicates that the application is not compl=
etely
standards compliant with respect to its handling of child process=
es.
If you notice this message, you should alert the application's
developers.&PROD; &PRODVER; includes the capability of producing Position
Independent Executables (PIE) for C, C++, and Java. This feature=
is
enabled with the -fpie and -fPIE
GCC options to compile, which are similar in usage to the
-fpic and -fPIC options,
respectively, and at link time with the -pie
option.The fileutils, textutils,
sh-utils, and stat packages=
have
been replaced by the newer coreutils package.<=
/para>
The RPMs containing the Network Administration
Tool (redhat-config-network) h=
ave
changed names and functions. The
redhat-config-network RPM contains the too=
l's
graphical user interface, while
redhat-config-network-tui contains the tool
itself (along with its text-based user interface).Support for XHTML1 — the reformulation of HTML in XML
— has been improved. This has been done by adding the
xhtml1-dtd package, installing the DTDs in the
system catalog, and adding native support in the
libxml2 and xsltproc
tools.The XML toolkit have been extended to support Relax-NG valida=
tion,
and streaming of large files.The OProfile system-wide profiler has been added to &PROD;
&PRODVER;. OProfile is a programmer's tool for analyzing system
performance, using special hardware built into many modern comput=
ers.
Documentation for OProfile exists in the oprofile
package; after installing &PROD; &PRODVER;, issue the command
rpm -qd oprofile to obtain a listing of the
available documentation. Visit the OProfile website at
http://oprofile.sourceforge.net for more details.NOTE: The kernel support for OProfile in &PROD; &PRODVER; is =
based
on the backported code from the 2.5 development kernel. Therefor=
e, if
you refer to the OProfile documentation, keep in mind that featur=
es
listed as being 2.5-specific actually apply to the &PROD; kernel,=
even
though the kernel version is 2.4. Likewise, this means that feat=
ures
listed as being specific to the 2.4 kernel do not
apply to the &PROD; kernel.At the present time, the X Window System makes use of two font
subsystems, each with different characteristics:· The original (15+ year old) subsystem is referred to=
as
the "core X font subsystem". Fonts rendered by this subsystem ar=
e not
anti-aliased, are handled by the X server, and have names like:=
para>
-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
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 r=
ender
fontconfig fonts to the screen with antialiasing. Fontconfig uses
more human-friendly names like:Luxi Sans-10Over time, fontconfig/Xft will replace the core X font subsys=
tem.
At the present time, applications using the Qt 3 or GTK 2 toolkits
(which would include KDE and GNOME applications) use the fontconf=
ig
and Xft font subsystem; most everything else uses the core X
fonts.In the future, &RH; may support only fontconfig/Xft in place =
of
the XFS font server as the default local font access method.
NOTE: One exception to the font subsystem usage outlined abov=
e is
OpenOffice.org, which uses its own font rendering technology.
If you wish to add new fonts to your &PROD; &PRODVER; system,=
you
must be aware that the steps necessary depend on which font subsy=
stem
is to use the new fonts. For the core X font subsystem, you
must:1. Create the /usr/share/fonts/local/
directory (if it does not 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 comma=
nds
(note that, due to formatting restrictions, the following command=
s may
appear on more than one line; in use, each commands should be ent=
ered
on a single line):ttmkfdir -d /usr/share/fonts/local/ -o
/usr/share/fonts/local/fonts.scalemkfontdir /usr/share/fonts/local/4. If you had to create
/usr/share/fonts/local/, you must then add i=
t 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 t=
he
/usr/share/fonts/ directory (individual user=
s 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> w=
ould
be either the /usr/share/fonts/ or
~/.fonts/ directories.)Individual users may also install fonts graphically, by brows=
ing
fonts:/// in Nautilus,
and dragging the new font files there.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 cha=
nges
made via the Font Preferences dialog. For t=
hese
applications, a font can be configured by adding the following li=
nes
to the file ~/.gtkrc.mine:style "user-font" {fontset =3D
"<font-specification>"}widget_class "*" style "user-font"(Where
<font-specification>
represents a font specification in the style used by traditional X
applications, such as
"-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-=
*-*".)By default, the Sendmail mail transport agent (MTA) does not
accept network connections from any host other than the local
computer. If you want to configure Sendmail as a server for other
clients, you must edit /etc/mail/sendmail.mc=
and
change the DAEMON_OPTIONS line to also lis=
ten
on network devices (or comment out this option entirely using the
dnl comment delimiter). You must then regener=
ate
/etc/mail/sendmail.cf by running the followi=
ng
command (as root):make -C /etc/mailNote that you must have the sendmail-cf
package installed for this to work.The default FTP server in &PROD; &PRODVER; is now
vsftpd, and runs as a SysV service.Change to fdisk's interpretation of partit=
ion
size multipliersThe fdisk command now has a different
interpretation of the size multipliers that may be used when crea=
ting
new disk partitions. The size suffixes K,
M, and G now refer to multi=
ples
of thousands, millions, and billions of bytes, respectively. Thi=
s is
more consistent with the disk size specifications provided by disk
drive manufacturers.Therefore, if a user wants to create a 512MB partition, the s=
ize
value specified with an "M" suffix would be 512*1024*1024
(536,870,912), rounded up to a multiple of a million (537,000,000=
),
and then divided by a million (537), resulting in a size specific=
ation
of +537M.While compatibility for executables and dynamic shared objects
(DSOs, also known as shared libraries) created on earlier &RHL; a=
nd
&PROD; is supported, the same does not apply to object
(.o) files. Object files created on earlier
versions can be used on &PROD; &PRODVER; to create new executable=
s or
DSOs only if they were built without including any system header
files.Otherwise, the only way to use these files is to link the obj=
ect
files to the compatibility version of glibc (part of the
compat-glibc package). Any newly-generated
object file must use the headers from the compatibility package. =
For
example, to compile object files, add the following to the beginn=
ing
of the compiler command line:-I/usr/lib/i386-redhat-linux7/includeTo link the resulting executable or DSO add the following to =
the
command line:-L/usr/lib/i386-redhat-linux7/libAny mixture of old object files and those compiled against the
current system headers can have negative results. Linking old ob=
ject
files with the regular system libraries may result in completely
unusable executables or executables with subtle bugs (such as mem=
ory
corruption).Kernel NotesThis section contains notes relating to the &PROD; &PRODVER;
kernel.The &PROD; &PRODVER; kernel makes use of a new kernel packagi=
ng
technique. Due to the almost limitless variety of available hard=
ware,
it is not possible for &RH; to fully support all hardware compone=
nts.
Therefore, while kernel modules for fully-supported hardware rema=
in in
the standard kernel packages, a series of new
unsupported kernel packages are included w=
ith
&PROD; &PRODVER;.For each kernel package shipped there is a corresponding
unsupported kernel package. For example, the unsupported kernel
package for
kernel-smp-2.4.21-3.EL.i686.rpm
is
kernel-smp-unsupported-2.4.21-3.EL.i686.rpm.=
NOTE: The unsupported kernel packages are not installed by the
&PROD; installation program; therefore, in order to use unsupport=
ed
kernel modules, you must manually install the unsupported kernel
package corresponding to the kernel your system uses.After installing the appropriate unsupported kernel package, =
you
must use the following command to update the module dependency tr=
ee
and your initrd:/sbin/new-kernel-pkg --mkinitrd --depmod --install
<kernel-version>(Where
<kernel-version>
represents the version of the installed kernel.)Drivers contained within the unsupported kernel packages are
provided on a best-effort basis. This means that updates and upst=
ream
fixes may or may not be incorporated over time, and are not cover=
ed by
the same support expectations as the fully supported drivers. Cus=
tom
support arrangements covering drivers in the unsupported package =
may
be worked out with Red Hat in some situations.The &PROD; &PRODVER; kernel includes more accurate process ti=
ming
functionality. This new process timing mode uses timestamps to
provide more accurate timing of idle and process times. When ena=
bled,
this information is available via the usual monitoring tools (suc=
h as
top, vmstat, and
procinfo), and the getrusage
system call.To enable timestamp-based process timing, you must boot your
system using the following boot-time option:process_timing=3D<value>Where <value>
can be one or more of the following, with multiple values separat=
ed by
commas:· irq — Use timestamps to acc=
ount
for IRQ interrupts· softirq — Use timestamps to
account for softirq time in the kernel· process — Allow processes to
enable timestamp-based process timing on themselves (It is then
disabled for all processes by default)· all_process — Force
timestamp-based process timing on all processes (including the id=
le
tasks)· everything — Same as specif=
ying
irq,softirq,all_processIf the system is booted with the process
option, no processes initially have timestamp-based process timing
enabled by default. However, processes can use the
prctl() system call to both determine and modi=
fy
their process timing mode. The system call to determine the proc=
ess
timing mode is:mode =3D prctl(PR_GET_TIMING, 0, 0, 0, 0);=
The system call to set the process timing mode is:status =3D prctl(PR_SET_TIMING,
<mode>, 0, 0, 0)(Where <mode>
is PR_TIMING_STATISTICAL for enabling the
traditional process timing mode, or
PR_TIMING_TIMESTAMP for enabling timestamp-bas=
ed
process timing mode .) Note that enabling one process timing mode
automatically disables the other.NOTE: The prctl() system call can only be =
used
on systems booted with the process value.
Otherwise, the system call will return -EINVAL.
This includes attempts to disable timestamp-based process timing =
on
systems booted with the all_process option.
A child process's timing mode is inherited from its parent;
however, the child can use the prctl() system =
call
to modify its own process timing mode (subject to the conditions
outlined in the previous note).The BusLogic driver (for certain Mylex SCSI host bus adapters=
) is
provided in the standard kernel packages, but it is only supported
when the kernel is a guest operating system within
VMWare virtual machine software. This is
because VMWare presents an emulated SCSI adapter to the BusLogic
driver, and this environment has been thoroughly tested and suppo=
rted
by VMWare, Inc. The BusLogic driver is not supported on physical =
SCSI
host adapters because this driver has not been maintained in the
official Linux kernel for several years, and has not received
extensive testing in the &RHEL; kernel.The qla1280 driver (for the Qlogic ISP1x80/1x160 SCSI adapter=
s)
has not been maintained in the official Linux kernel for many yea=
rs.
As a result, although this driver works correctly with the Intel =
x86
architecture, it does not work correctly with other architectures.
Therefore, &RH; only supports the qla1280 driver on Intel x86
platforms.The netdump facility is currently disabled. The
netdump package is included so that, if the
netdump facility is enabled in a future kernel update, netdump
functionality will be available after the netdump-capable kernel =
is
installed.Systems based on the Intel I865/I875 chipsets and utilizing t=
hese
chipsets' ICH5 integrated AC97 audio functionality may experience=
a
failure to produce any sound when running &PROD; &PRODVER;.The ICH5 integrated AC97 audio subsystem can be identified by
reviewing the output from the following command:/sbin/lspci -nThe PCI vendor:device code for the ICH5 AC97 audio is
8086:24d5.Systems based on the Intel I865/I875 chipsets and utilizing t=
hese
chipsets' ICH5 Serial ATA (SATA) functionality should configure t=
he
BIOS settings for their SATA devices to "enhanced" or "native" mo=
de.
"Legacy" or "combined" mode SATA is supported, but discouraged.=
para>
NOTE: Not all BIOS implementations offer the ability to change
these settings.New kernel support has been added to provide IPv6 capabilitie=
s.
This support is consistent with the upstream 2.6-based implementa=
tion
as of 2.6.0-test3.
=
Note that &RH; will not be implementing additional IPv6 featu=
res
(such as any of the draft standards for Mobile IP) for this relea=
se of
&PROD;; our goal is to focus exclusively on bugs in existing
features.EA (Extended Attributes) and ACL (Access Control Lists)
functionality is now available for ext3 file systems. In
addition, ACL functionality is available for NFS.&PROD; &PRODVER; contains a kernel providing EA and ACL suppo=
rt
for the ext3 file system. Protocol extensions were also added to=
NFS
to support ACL-related operations for NFS-exported file
systems.To enable ACLs on a locally-mounted file system, the file sys=
tem
must be mounted with the -o acl mount option. =
By
default, the NFS server makes use of ACLs if the underlying file
system supports them. To disable this feature, you must specify =
the
no_acl export option.EAs are used intrinsically for ACL support. To use EAs
separately, the file system must be mounted with the -o
user_xattr mount option.The support for this comes in several packages:· kernel — Provides support for storing EAs and =
ACLs
on disk for ext3 file systems, as well the system calls to manipu=
late
EAs and ACLs. Finally, the kernel package provides the mechanism=
s to
enforce ACLs on file access.· e2fsprogs — Includes knowledge of the new on-d=
isk
extended attribute formats so that fsck can ch=
eck
file systems using the new feature.· attr, libattr — Provides access to extended
attributes attached to files.· acl, libacl — Provides tools to set, modify, a=
nd
query the ACLs set on files.· libattr-devel, libacl-devel — Libraries and in=
clude
files to build programs using the acl and attr libraries.· star — An archiving tool which can create and
unpack both tar and pax for=
mat
archives, and which can backup and restore EAs and ACLs.NOTE: The options available for star are n=
ot
completely equivalent with those available for tar;
therefore, make sure you review the star man
page.· samba — Samba can export ACL functionality in =
this
release. Refer to the samba documentation for information on how=
to
enable this in your configuration.In addition, the coreutils package has been
updated so that the cp and mv
commands copy the ACLs and EAs associated with a file.For more information on setting and reading ACLs, refer to the
setfacl and getfacl man pag=
es.
General information about ACLs can be found in the
acl man page.NOTE: The normal tar and
dump commands will not ba=
ckup
ACLs and EAs.Compatibility with older systems:Any ext3 file system that has not had any ACLs or EAs set on =
it
will work unchanged on older kernels, and can be checked using ol=
der
e2fsprogs utilities.Once an EA or an ACL has been set on any file on a given file
system, that file system will acquire the ext_attr
attribute. This attribute can be observed by using the following
command:tune2fs -l
<filesystemdevice>=
para>
A file system that has acquired the ext_attr
attribute can be mounted with older kernels, but obviously those
kernels are incapable of enforcing any ACLs that have been set.=
para>
NOTE: Older versions of the file system checking program
e2fsck refuse to check any file system with the
ext_attr attribute. This corresponds to versi=
ons
of the e2fsprogs package prior to 1.22.The &PROD; &PRODVER; kernel now includes support for NFS over=
TCP.
To use NFS over TCP, you must include the "-o tcp"
option to mount when mounting the NFS-exported=
file
system on the client system.NOTE: The default transport protocol for NFS remains UDP. Use=
the
mount command with the "-o tcp"
option to mount an NFS-exported file system using TCP; otherwise,=
UDP
will be used by default.In this kernel, the following command has been added to scan =
for
new devices on all attached SCSI host adapters:echo "scsi scan-new-devices" >
/proc/scsi/scsiThis is currently a non-standard addition. In future kernels a
different parameter may be used to provide the same capability, o=
r the
semantics of the same parameter
(scan-new-devices) may change, as
&RH; tracks the official Linux kernel in this area.Logical Partitions on iSeries platforms that have been config=
ured
to use more than one processor (either directly or from a shared =
pool)
may wish to share interrupt processing across all processors. Do=
ing
so may improve performance for some workloads. By default, &PROD;=
will
only service interrupts on one processor in the LPAR. To change =
this
behavior, the following boot-time option must be entered:spread_lpevents=3D<N>Where <N>
represents the number of processors in the LPAR that should proce=
ss
interrupts. This number should be less than or equal to
either:· The number of virtual processors (if a shared proces=
sor
pool is being used)· The number of direct processors assigned to the LPAR=
Change in permission semantics for user-mode memory locking=
para>
=
=
&PROD; &PRODVER; now allows non-root processes to use user-mo=
de
memory locking system calls within the bounds of their
RLIMIT_MEMLOCK resource limit. The default li=
mit
is one physical page per process. Limits can be reassigned by the
system administrator on a per user-id, per group-id, or system-wi=
de
basis via the /etc/security/limits.conf file.
Root processes are no longer constrained by this resource
limit.
=
=
The system calls affected by this change in semantics are
mlock(2), munlock(2),
mlockall(2), munlockall(2),=
and
shmctl(2).(
x86ia64s390s390xamd64ppc
)
--- NEW FILE splash-it.xml ---
Welcome to &FC; &LOCALVER;Information Out-of-Date
The content in this section needs to be updated for &DISTRO;
&DISTROVER;
&FC; is a completely free, user friendly, and secure general purpose
platform based on Linux. The &FP; is an open source project that
pioneers leading edge technology and concepts sponsored by &RH; and
supported by the &FED; community.
Latest Release Notes on the Web
These release notes may be updated. Visit http://fedora.redhat.=
com/docs/release-notes/
to view the latest release notes for &DISTRO; &DISTROVER;.
Refer to these webpages to find out more information about &FED;:
— Technical release notes
Help and Support (http://fedora.=
redhat.com/participate/communicate/) =
Participate in the &FP; (http://fedora.redhat.com/p=
articipate/) =
About the &FP; (http://fedora.redhat.com/about/<=
/ulink>)
--- NEW FILE xorg-it.xml ---
X Window System (Graphics)Information Out-of-Date
The content in this section needs to be updated for &DISTRO;
&DISTROVER;
This section contains information related to the X Window System
implementation provided with &DISTRO;.
xorg-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 &RH; and &FED; operating systems. In
particular, the names of some files have changed:
X Server Binary:
XFree86 X11: XFree86X.org X11: Xorg
X Server Configuration File:
XFree86 X11:
/etc/X11/XF86ConfigX.org X11: /etc/X11/xorg.conf
X Server Log File:
XFree86 X11:
/var/log/XFree86.$DISPLAY.logX.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 &DISTRO; (and
versions of &RHL; before it.) At the present time, there are two
font subsystems, each with different characteristics:
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=
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, &FC; may support only fontconfig/Xft in
place of the XFS font server as the default local font access
method.
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 &DISTRO; &DISTROVER; depend on the
fonts subsystem this is going to use the new fonts. For the core X
font subsystem:
Create the /usr/share/fonts/local/
directory (if it doesn't already exist):
mkdir /usr/share/fonts/local/
Copy the new font file into
/usr/share/fonts/local/
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):
ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/font=
s.scalemkfontdir /usr/share/fonts/local/
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.
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:
=
style "user-font" {
fontset =3D "<font-specification>"
}
widget_class "*" style "user-font"
(Where
<font-specification> =
represents a font specification in the style used by traditional X
applications, such as
"-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*<=
/computeroutput>".)
--===============5893273253064115340==--