From fedora-docs-commits at redhat.com Mon May 2 20:05:55 2005
From: fedora-docs-commits at redhat.com (Elliot Lee (sopwith))
Date: Mon, 2 May 2005 16:05:55 -0400
Subject: fedora-docs README,1.3,1.4
Message-ID: <200505022005.j42K5t6n015782@cvs-int.fedora.redhat.com>
Author: sopwith
Update of /cvs/docs/fedora-docs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15774
Modified Files:
README
Log Message:
test
Index: README
===================================================================
RCS file: /cvs/docs/fedora-docs/README,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- README 22 Sep 2003 16:42:43 -0000 1.3
+++ README 2 May 2005 20:05:53 -0000 1.4
@@ -12,3 +12,4 @@
guides.
Questions? Email fedora-docs-list at redhat.com.
+
From fedora-docs-commits at redhat.com Mon May 2 20:12:31 2005
From: fedora-docs-commits at redhat.com (fedora-docs-commits at redhat.com)
Date: Mon, 2 May 2005 16:12:31 -0400
Subject: fedora-docs README,1.4,1.5
Message-ID: <200505022012.j42KCVK8015800@cvs-int.fedora.redhat.com>
Author: sopwith
Update of /cvs/docs/fedora-docs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15792
Modified Files:
README
Log Message:
test
Index: README
===================================================================
RCS file: /cvs/docs/fedora-docs/README,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- README 2 May 2005 20:05:53 -0000 1.4
+++ README 2 May 2005 20:12:29 -0000 1.5
@@ -12,4 +12,3 @@
guides.
Questions? Email fedora-docs-list at redhat.com.
-
From fedora-docs-commits at redhat.com Mon May 2 20:13:38 2005
From: fedora-docs-commits at redhat.com (fedora-docs-commits at redhat.com)
Date: Mon, 2 May 2005 16:13:38 -0400
Subject: fedora-docs README,1.5,1.6
Message-ID: <200505022013.j42KDcSx015814@cvs-int.fedora.redhat.com>
Author: sopwith
Update of /cvs/docs/fedora-docs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15806
Modified Files:
README
Log Message:
test
Index: README
===================================================================
RCS file: /cvs/docs/fedora-docs/README,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- README 2 May 2005 20:12:29 -0000 1.5
+++ README 2 May 2005 20:13:36 -0000 1.6
@@ -12,3 +12,4 @@
guides.
Questions? Email fedora-docs-list at redhat.com.
+
From fedora-docs-commits at redhat.com Mon May 2 20:18:09 2005
From: fedora-docs-commits at redhat.com (fedora-docs-commits at redhat.com)
Date: Mon, 2 May 2005 16:18:09 -0400
Subject: fedora-docs README,1.6,1.7
Message-ID: <200505022018.j42KI9DT015835@cvs-int.fedora.redhat.com>
Author: sopwith
Update of /cvs/docs/fedora-docs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15827
Modified Files:
README
Log Message:
nomoretest
Index: README
===================================================================
RCS file: /cvs/docs/fedora-docs/README,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- README 2 May 2005 20:13:36 -0000 1.6
+++ README 2 May 2005 20:18:07 -0000 1.7
@@ -12,4 +12,3 @@
guides.
Questions? Email fedora-docs-list at redhat.com.
-
From fedora-docs-commits at redhat.com Mon May 2 22:18:44 2005
From: fedora-docs-commits at redhat.com (fedora-docs-commits at redhat.com)
Date: Mon, 2 May 2005 18:18:44 -0400
Subject: fedora-docs/install-guide fedora-install-guide-locale-en.xml, NONE,
1.1 fedora-install-guide-beginninginstallation-en.xml, 1.1,
1.2 fedora-install-guide-en.xml, 1.7, 1.8
Message-ID: <200505022218.j42MIiHn017904@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17896
Modified Files:
fedora-install-guide-beginninginstallation-en.xml
fedora-install-guide-en.xml
Added Files:
fedora-install-guide-locale-en.xml
Log Message:
- Broke locale section into separate chapter and file; amended parent
- Edited beginninginstallation file
--- NEW FILE fedora-install-guide-locale-en.xml ---
Identifying Your Locale
If the installation system fails to identify the display hardware on
your computer, it will display text screens rather than the default
graphical interface. The text screens provide the same functions as
the standard screens. Later in the installation process you can
manually specify your display hardware.
Network installations with HTTP and FTP will always use text
screens on systems with less than 128Mb of memory.
Language Selection
The installation program displays a list of languages supported by
&FED;. The installation process continues in this language. This
language also becomes the default language for your system. The
installation program provides additional language support at a
later stage.
Highlight the correct language on the list and select
Next.
Keyboard Configuration
The installation program display a list of the keyboard layouts
supported by &FED;:
Highlight the correct layout on the list, and select
Next.
Index: fedora-install-guide-beginninginstallation-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-beginninginstallation-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-beginninginstallation-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-beginninginstallation-en.xml 2 May 2005 22:18:42 -0000 1.2
@@ -1,482 +1,575 @@
-
Beginning the Installation
- The most common method of installing &FC; is to boot the computer from
- the first disc and proceed through the screens. You can also use USB
- pen drives, hard drives and network servers to carry out an installation.
+ To begin installation of &FC;, boot the computer from the boot
+ media. You may install from CD or DVD discs, USB pen drives, hard
+ drives or network servers.
- &FC; does not support installation from diskettes
-
+ Installation from Diskettes
+
Current versions of Linux cannot be booted from diskettes.
-
+
-
- Whichever type of boot media you choose to use must be supported by the
- firmware, or BIOS, of your computer. Any computer that meets the
- minimum recommended specification for &FC; can boot from a CD or DVD
- drive with the first disc. USB drives and flash media are much newer
- technologies, and many existing computers do not have the capability to
- use these as boot media. Not all network cards and chipsets include
- support for network booting with PXE.
-
-
-
- If you are uncertain of the capabilities of your computer, or how to
- configure the BIOS, consult the documentation provided by the
- manufacturer. Detailed information on hardware specifications and
- configuration is beyond the scope of this document.
-
-
-
- When using a network server to boot or install &FC;, ensure that the
- network cable is attached prior to booting. The link indicator light on
- the network socket should be lit, even if the computer is not switched on.
-
-
-
- You should also plug in any USB devices you will be using to carry out
- the installation before switching on the computer.
-
-
-
- You can safely abort the installation if necessary
-
- You can abort the installation process at any time before the
- Installing Packages screen by either pressing
- CtrlAltDel,
- or rebooting the computer. No changes are made to your computer until
- package installation begins.
+
+ Your computer's firmware, or BIOS, must support the type of boot
+ media you select. Any computer that meets the minimum recommended
+ specification for &FC; can boot from a CD or DVD drive with the
+ first disc. USB drives and flash media are newer technologies, and
+ many computers cannot use them as boot media. Some network cards
+ and chipsets do not include support for network booting with PXE.
+
+
+
+ If you are not sure what capabilities your computer has, or how to
+ configure the BIOS, consult the documentation provided by the
+ manufacturer. Detailed information on hardware specifications and
+ configuration is beyond the scope of this document.
+
+
+
+ When using a network server to install &FC;, ensure that the network
+ cable is attached prior to booting. The link indicator light on the
+ network socket should be lit, even if the computer is not switched
+ on.
+
+
+
+ If you are installing from a USB device, plug it in before you
+ switch on the computer.
+
+
+
+ Aborting the Installation
+
+ You can abort the installation process at any time before the
+ Installing Packages screen by either pressing
+ CtrlAltDel
+ or rebooting the computer. No changes are made to your computer
+ until package installation begins.
-
+
-
+ Booting from Disc
- To boot your computer from disc:
+ To boot your computer from disc:
-
-
- Switch on the computer.
-
-
- Insert the first disc into the CD or DVD drive.
-
-
- A boot screen should appear, with a boot:
- prompt at the bottom. To begin, simply Enter key.
- To have the option of running the
- installation system from a hard drive or network server, type
- linux askmethod and press the Enter key.
-
-
+
+
+ Switch on the computer.
+
+
+ Insert the first disc into the CD or DVD drive.
+
+
+ A boot screen appears, with a boot:
+ prompt at the bottom.
+
+
- If you did not specify linux askmethod then it is
- assumed that you wish to install &FC; from the disc. This screen will
- then be displayed:
+ If you hit Enter, the installation runs in
+ default mode. In the default mode, the installation runs from CD
+ or DVD discs, and will try to use a graphical interface.
+
+
+ If you need to change the installation mode, at the
+ boot: prompt, type linux
+ followed by one or more of the following options:
+
+
+
+
+ If you are installing from a hard drive or network server, add
+ the directive askmethod.
+
+
+
+
+ To use a text interface, add the directive
+ text.
+
+
+
+
+ If you are trying again because the installation aborted at an
+ early stage, add the directive
+ acpi=off.
+
+
+
+
+
+ After you issue a command at the boot: prompt,
+ the first stage of the installation program starts. After it
+ loads, the following screen appears:
- Select OK to test the disc, or
- Skip to proceed with the installation without
- testing the disc.
+ Select OK to test the disc, or select
+ Skip to proceed with the installation
+ without testing the disc.
+
+ Testing Discs
+
+ Test any discs which you have not previously tested. A disc
+ error during the installation process may force you to restart
+ the entire procedure.
+
+
+
- Once the first disc has been tested another screen will appear, showing
- the result:
+ After you test the first disc, another screen appears, showing the
+ result:
- Select OK. On the next screen you can choose to
- either Test the next disc in the set, or
- Continue with the installation:
+ Select OK. The following screen appears:
- If this is the first time that you have used this set of discs then it
- is advisable to test all of the discs prior to starting the installation.
+ Select Test to test the next disc in the
+ set, or Continue to proceed with the
+ installation.
-
- The Media Check may fail usable discs
-
- Discs that are valid and usable may still fail to pass the
- Media Check.
-
-
+
- Once you have chosen to either Skip the media
- check or Continue onward, the main graphical
- installation program will load.
+ After you test your discs and select
+ Continue, or if you choose to skip testing,
+ the main graphical installation program loads.
- It is possible to merely boot from a disc, and run the rest of the
- installation from another device or a network server. This can be done
- by specifying linux askmethod at the boot prompt.
- Alternatively, you can use a boot-only CD for this purpose. The ISO
- file images/boot.iso on the first disc is an image
- of a boot CD.
+ You may use a disc only to boot, and install from another device
+ or a network server, using the linux
+ askmethod command at the boot:
+ prompt. You can also use a boot-only CD for this purpose. The
+ ISO file images/boot.iso on the first &FC;
+ installation disc is an image of a boot CD.
-
- If booting fails, check the boot order in the BIOS
- By default, your computer will check the CD or DVD drives for bootable
- discs before attempting to boot from the internal hard drive. This
- behavior is controlled by settings in the computer firmware, or BIOS.
- If your PC does not boot from the disc then you should ensure that the
- boot order is set correctly in the BIOS.
+ Use the option in your CD-writing program that burns a CD image
+ file to a CD. If you copy the file to a CD instead, the disc will
+ not boot or work correctly. Refer to your CD-writing program's
+ documentation for instructions. If you are using Linux, use the
+ following command to burn a CD image file to a blank recordable
+ CD:
+
+
+cdrecord --device=/dev/cdwriter -tao -eject image-file.iso
+
+
+
+ BIOS Boot Order
+
+ The computer firmware, or BIOS, contains settings that control
+ the order of boot devices. If your PC boots from a device other
+ than the &FC; boot media, check the BIOS boot configuration.
+
-
+
-
+ Using Other Removable Media
-
- In order to use a USB device or Compact Flash card as boot media it must
- first be reformatted with the supplied image file. The size of the
- media is not a limitation, as the boot software is only a total of 6Mb in size.
-
+
+ To use a USB device such as a pen drive or Compact Flash card as
+ boot media, write the supplied image file to the device. The
+ media must be large enough to contain the image.
+
-
- Preparing the Boot Media
+
+ Preparing the Boot Media
- Pen drives are reformatted to make them bootable
-
- Any data on the device will be lost. This procedure also replaces all
- of the partitions and software on the device with a single 6Mb boot
- partition. Some models of pen drive use additional partitions or
- software to provide functions such as encryption.
-
+ Data Loss
+
+ This procedure will destroy data on the
+ media. Back up any important information before
+ you begin. Some models of pen drive use additional partitions
+ or software to provide functions such as encryption. This
+ procedure may make it difficult or impossible to access these
+ special areas on your boot media.
+
- You will need the image file matching your version of &FC;, called
- diskboot.img. This file is on the first disc, in
- the images/ directory. FTP and Web sites providing
- &FC; will also have an images/ directory.
+ The diskboot.img file in the
+ images/ directory on the first disc is a
+ boot image designed for USB media. You may also find this file
+ on FTP and Web sites providing &FC;.
- There are several software utilities available for Windows and Linux
- that can write image files to a device. All UNIX-like systems include
- the dd command for this purpose. To write the image
- file to the boot media with dd on a current version
- of &FC;:
+ Several software utilities are available for Windows and Linux
+ that can write image files to a device. All UNIX-like systems
+ such as Linux include the dd command for this
+ purpose. To write the image file to the boot media with
+ dd on a current version of &FC;:
-
-
- Locate the image file.
-
-
- Attach the device, or insert the Compact Flash card.
-
-
- Your system may automatically detect and open the media. If
- this is the case, then close and unmount the media before continuing.
-
-
- Open a terminal window.
-
-
- In the terminal window, type the following: dd
- if=diskboot.img of=/dev/sda1
-
-
+
+
+
+ Locate the image file.
+
+
+
+
+ Attach or insert the media.
+
+
+
+
+ Your system may automatically detect and open the media. If
+ that happens, close or unmount the media before continuing.
+
+
+
+
+ Open a terminal window.
+
+
+
+
+ In the terminal window, type the following:
+
+
+dd if=diskboot.img of=/dev/sda1
+
+
+
+
+
-
+
-
- Booting from the Media
+
+ Booting from the Media
-
- To boot your computer with the media that you have prepared:
-
+
+ Boot your computer with the prepared media:
+
-
-
- Attach the boot device, or insert the prepared Compact Flash card.
-
-
- Switch on the computer.
-
-
- A boot screen should appear, with a boot:
- prompt at the bottom. To begin, simply press the Enter key.
-
-
+
+
+
+ Attach or insert the media.
+
+
+
+
+ Switch on the computer.
+
+
+
+
+ A boot screen appears, with a boot: prompt
+ at the bottom. To begin, simply press the
+ Enter key.
+
+
+
+
+
+ BIOS Boot Order
+
+ The computer firmware, or BIOS, contains settings that control
+ the order of boot devices. If your PC boots from a device
+ other than the &FC; boot media, check the BIOS boot
+ configuration.
+
+
-
+
-
+
-
+ Booting from the Network using PXE
- PXE booting requires a netboot server to be configured first. Setting
- up a netboot facility is detailed in a separate tutorial.
+ Booting using PXE requires a properly configured netboot server,
+ and a network interface in your computer that supports PXE.
+
- The computers must then be set to use PXE as the boot device. This
- option is in the computer firmware, or BIOS. Once this has been done
- the computers can boot into the &FED; installation system without
- requiring any other media.
+ Configure the computer to boot from the network interface. This
+ option is in the BIOS, and may be labeled or . Once you
+ properly configure PXE booting, the computer can boot into the
+ &FED; installation system without any other media.
- Network boot support in the BIOS
-
- Your computer must be configured to boot from a network connection
- that specifically supports PXE. It may be labeled Network
- Boot or Boot Services. If your PC does not
- boot from the netboot server then you should ensure that PXE is set as the
- first boot device in the BIOS. Sometimes a BIOS will specify LAN or Network
- Boot as a possible boot device, but not support the PXE standard.
-
-
-
-
- To boot a computer from a netboot server:
-
-
-
-
- Switch on the computer.
-
-
- A menu screen will appear. Press the number key that corresponds to the option
- you want. To boot the machine as normal either wait without
- pressing a key, or select menu option 0.
-
-
+ PXE Troubleshooting
+
+ If your PC does not boot from the netboot server, ensure that
+ the BIOS is configured to boot first from the correct network
+ interface. Some BIOS systems specify the network interface as a
+ possible boot device, but do not support the PXE standard.
+ Refer to your hardware documentation for more information.
+
+
+
+
+ To boot a computer from a PXE server:
+
+
+
+
+
+ Switch on the computer.
+
+
+
+
+ A menu screen appears. Press the number key that corresponds
+ to the desired option.
+
+
+
-
- If you chose a network installation option, the first locale screen will then appear.
-
+
+ Choose a network installation option to continue.
+
-
+
-
- Identifying Your Locale
+
+ Identifying Your Locale
- Before beginning the main installation, you must set the interface to
- match your locale. For this reason, you will always be presented
- with Language Selection and Keyboard
- Configuration screens.
+ If the installation system fails to identify the display hardware
+ on your computer, it will display text screens rather than the
+ default graphical interface. The text screens provide the same
+ functions as the standard screens. Later in the installation
+ process you can manually specify your display hardware.
-
- You will see text screens if your graphics hardware cannot be identified
+
+
+ Network installations with HTTP and FTP will always use text
+ screens on systems with less than 128Mb of memory.
+
+
+
- If the installation system is unable to identify the monitor or graphics
- hardware on your computer then you will be shown text screens, rather than
- the default graphical interface. The text screens provide the same
- functions as the standard screens. Later on in the installation process you have the
- opportunity to manually specify the details of your hardware configuration.
-
-
- Network installations with HTTP and FTP will always use text screens on
- systems with less than 128Mb of memory.
-
-
-
-
-
- Language Selection
-
-
- This screen shows an alphabetical list of the languages that &FED;
- supports. The language that you choose will be used for the
- installation process, and become the default language for your system.
-
+ The &FC; installation program supports many languages. You must
+ choose a locale and keyboard to continue installation in your
+ native language.
+
-
-
- Highlight the language on the list that you would like to use, and
- select Next.
-
-
-
- Here is the alternate, text-based, screen:
-
+
+ Language Selection
-
+
+ The installation program displays a list of languages supported
+ by &FED;. The installation process continues in this language.
+ This language also becomes the default language for your system.
+ The installation program provides additional language support at
+ a later stage.
+
+
+
+
+
+ Highlight the correct language on the list and select
+ Next.
+
-
+
-
- Keyboard Configuration
+
+ Keyboard Configuration
-
- This screen shows an alphabetical list of the keyboard layouts that &FED; supports:
-
+
+ The installation program display a list of the keyboard layouts
+ supported by &FED;:
+
-
+
-
- Highlight the layout on the list that matches the keyboard that you are
- using, and select Next.
-
+
+ Highlight the correct layout on the list, and select
+ Next.
+
-
+
-
+
+
+
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-en.xml 1 May 2005 17:45:44 -0000 1.7
+++ fedora-install-guide-en.xml 2 May 2005 22:18:42 -0000 1.8
@@ -16,6 +16,7 @@
+
@@ -75,6 +76,8 @@
&OTHERINSTALLMETHODS;
+ &LOCALE;
+
&UPGRADING;
&INSTALLTYPES;
From fedora-docs-commits at redhat.com Mon May 2 22:24:30 2005
From: fedora-docs-commits at redhat.com (fedora-docs-commits at redhat.com)
Date: Mon, 2 May 2005 18:24:30 -0400
Subject: fedora-docs/install-guide
fedora-install-guide-abouttoinstall-en.xml, 1.1,
1.2 fedora-install-guide-acknowledgements-en.xml, 1.1,
1.2 fedora-install-guide-bootloader-en.xml, 1.2,
1.3 fedora-install-guide-diskpartitioning-en.xml, 1.1,
1.2 fedora-install-guide-firewallconfig-en.xml, 1.1,
1.2 fedora-install-guide-firstboot-en.xml, 1.1,
1.2 fedora-install-guide-installingpackages-en.xml, 1.1,
1.2 fedora-install-guide-installtypes-en.xml, 1.1,
1.2 fedora-install-guide-networkconfig-en.xml, 1.1,
1.2 fedora-install-guide-nextsteps-en.xml, 1.1,
1.2 fedora-install-guide-other-instmethods-en.xml, 1.1,
1.2 fedora-install-guide-packageselection-en.xml, 1.1,
1.2 fedora-install-guide-rootpassword-en.xml, 1.1,
1.2 fedora-install-guide-timezone-en.xml, 1.1,
1.2 fedora-install-guide-upgrading-en.xml, 1.1, 1.2
Message-ID: <200505022224.j42MOUmx017935@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17923
Modified Files:
fedora-install-guide-abouttoinstall-en.xml
fedora-install-guide-acknowledgements-en.xml
fedora-install-guide-bootloader-en.xml
fedora-install-guide-diskpartitioning-en.xml
fedora-install-guide-firewallconfig-en.xml
fedora-install-guide-firstboot-en.xml
fedora-install-guide-installingpackages-en.xml
fedora-install-guide-installtypes-en.xml
fedora-install-guide-networkconfig-en.xml
fedora-install-guide-nextsteps-en.xml
fedora-install-guide-other-instmethods-en.xml
fedora-install-guide-packageselection-en.xml
fedora-install-guide-rootpassword-en.xml
fedora-install-guide-timezone-en.xml
fedora-install-guide-upgrading-en.xml
Log Message:
Added Emacs local variables for all remaining chapter files
Index: fedora-install-guide-abouttoinstall-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-abouttoinstall-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-abouttoinstall-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-abouttoinstall-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -49,3 +49,11 @@
+
+
Index: fedora-install-guide-acknowledgements-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-acknowledgements-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-acknowledgements-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-acknowledgements-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -13,3 +13,11 @@
+
+
Index: fedora-install-guide-bootloader-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-bootloader-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-bootloader-en.xml 2 May 2005 17:02:43 -0000 1.2
+++ fedora-install-guide-bootloader-en.xml 2 May 2005 22:24:28 -0000 1.3
@@ -236,3 +236,11 @@
+
+
Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-diskpartitioning-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-diskpartitioning-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -468,3 +468,11 @@
+
+
Index: fedora-install-guide-firewallconfig-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-firewallconfig-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-firewallconfig-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-firewallconfig-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -123,3 +123,11 @@
+
+
Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-firstboot-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-firstboot-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -412,3 +412,11 @@
+
+
Index: fedora-install-guide-installingpackages-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-installingpackages-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-installingpackages-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-installingpackages-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -46,3 +46,11 @@
+
+
Index: fedora-install-guide-installtypes-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-installtypes-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-installtypes-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-installtypes-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -83,3 +83,11 @@
+
+
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-networkconfig-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-networkconfig-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -149,3 +149,11 @@
+
+
Index: fedora-install-guide-nextsteps-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-nextsteps-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-nextsteps-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-nextsteps-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -365,3 +365,11 @@
+
+
Index: fedora-install-guide-other-instmethods-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-other-instmethods-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-other-instmethods-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-other-instmethods-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -206,3 +206,11 @@
+
+
Index: fedora-install-guide-packageselection-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-packageselection-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-packageselection-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-packageselection-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -195,3 +195,11 @@
+
+
Index: fedora-install-guide-rootpassword-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-rootpassword-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-rootpassword-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-rootpassword-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -71,3 +71,11 @@
+
+
Index: fedora-install-guide-timezone-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-timezone-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-timezone-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-timezone-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -78,3 +78,11 @@
+
+
Index: fedora-install-guide-upgrading-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-upgrading-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-upgrading-en.xml 30 Apr 2005 17:52:19 -0000 1.1
+++ fedora-install-guide-upgrading-en.xml 2 May 2005 22:24:28 -0000 1.2
@@ -133,3 +133,11 @@
+
+
From fedora-docs-commits at redhat.com Mon May 2 22:26:59 2005
From: fedora-docs-commits at redhat.com (fedora-docs-commits at redhat.com)
Date: Mon, 2 May 2005 18:26:59 -0400
Subject: fedora-docs/install-guide
fedora-install-guide-beginninginstallation-en.xml, 1.2, 1.3
Message-ID: <200505022226.j42MQxpx017977@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17969
Modified Files:
fedora-install-guide-beginninginstallation-en.xml
Log Message:
Fixed beginninginstallation chapter
Index: fedora-install-guide-beginninginstallation-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-beginninginstallation-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-beginninginstallation-en.xml 2 May 2005 22:18:42 -0000 1.2
+++ fedora-install-guide-beginninginstallation-en.xml 2 May 2005 22:26:57 -0000 1.3
@@ -468,102 +468,6 @@
-
- Identifying Your Locale
-
-
- If the installation system fails to identify the display hardware
- on your computer, it will display text screens rather than the
- default graphical interface. The text screens provide the same
- functions as the standard screens. Later in the installation
- process you can manually specify your display hardware.
-
-
-
-
- Network installations with HTTP and FTP will always use text
- screens on systems with less than 128Mb of memory.
-
-
-
-
- The &FC; installation program supports many languages. You must
- choose a locale and keyboard to continue installation in your
- native language.
-
-
-
-
- Language Selection
-
-
- The installation program displays a list of languages supported
- by &FED;. The installation process continues in this language.
- This language also becomes the default language for your system.
- The installation program provides additional language support at
- a later stage.
-
-
-
-
-
- Highlight the correct language on the list and select
- Next.
-
-
-
-
-
-
- Keyboard Configuration
-
-
- The installation program display a list of the keyboard layouts
- supported by &FED;:
-
-
-
-
-
- Highlight the correct layout on the list, and select
- Next.
-
-
-
-
-
-
-
- Ninth Step: About to Install
+ Ninth Step: About to Install
-
- This is the last point at which you can decide to stop the installation
+
+ This is the last point at which you can decide to stop the
+ installation
- No changes will be made to your computer until you click
- the Next button. If you abort the installation
- process after leaving this screen the &FC; system will be incomplete and
- unusable.
-
-
-
-
- You can still return to previous screens to alter any details by
- selecting Back.
+ No changes will be made to your computer until you click the
+ Next button. If you abort the installation
+ process after leaving this screen the &FC; system will be
+ incomplete and unusable.
-
-
+
+
+ You can still return to previous screens to alter any details by
+ selecting Back.
+
+
+
-
-
- Click Next to begin the installation.
-
-
-
- If you are installing &FC; from disc then an extra dialog will appear to list
- all of the discs that you will need in order to complete the
- installation process. You should click Continue
- if you have the discs required. You are offered the option to
- Reboot, aborting the installation, in case you do
- not have all of the necessary discs.
-
+
+
+
+
+
+ Click Next to begin the installation.
+
+
+
+ If you are installing &FC; from disc then an extra dialog will
+ appear to list all of the discs that you will need in order to
+ complete the installation process. You should click
+ Continue if you have the discs required. You
+ are offered the option to Reboot, aborting
+ the installation, in case you do not have all of the necessary
+ discs.
+
Index: fedora-install-guide-acknowledgements-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-acknowledgements-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-acknowledgements-en.xml 2 May 2005 22:24:28 -0000 1.2
+++ fedora-install-guide-acknowledgements-en.xml 3 May 2005 12:19:44 -0000 1.3
@@ -4,12 +4,13 @@
Acknowledgements
- This version of the &IG; was written by Stuart Ellis, with the sections on Disk
- Partitioning contributed by Paul Frields.
+ This version of the &IG; was written by Stuart Ellis, with the
+ sections on Disk Partitioning contributed by Paul W. Frields.
- Many useful comments and suggestions were provided by Rahul Sundaram.
+ Many useful comments and suggestions were provided by Rahul
+ Sundaram.
Index: fedora-install-guide-bootloader-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-bootloader-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-bootloader-en.xml 2 May 2005 22:24:28 -0000 1.3
+++ fedora-install-guide-bootloader-en.xml 3 May 2005 12:19:44 -0000 1.4
@@ -1,32 +1,33 @@
-
+
Third Step: Boot Loader
- A boot loader is a small program that reads the operating system from mass storage and gets it ready to be run in main memory.
- &FED; defaults to the GRUB boot loader.
+ A boot loader is a small program that reads
+ the operating system from mass storage and gets it ready to be run
+ in main memory. &FED; defaults to the
+ GRUB boot loader.
- If you are building a multi-boot system, you probably already have a boot loader.
- While you can continue to use the existing boot loader, it does not recognize the Linux partitions and you will not be able to boot &FED; easily.
- We recommend that you use GRUB as your boot loader because it boots both Linux and most other operating systems as well.
- Simply follow the directions in this section and GRUB will replace any existing boot loader.
+ If you are building a multi-boot system, you probably already have a
+ boot loader. While you can continue to use the existing boot loader,
+ it does not recognize the Linux partitions and you will not be able
+ to boot &FED; easily. We recommend that you use
+ GRUB as your boot loader because it boots
+ both Linux and most other operating systems as well. Simply follow
+ the directions in this section and GRUB
+ will replace any existing boot loader.
- Figure shows the boot loader configuration choices.
-
+ Figure shows the boot
+ loader configuration choices.
+
Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-diskpartitioning-en.xml 2 May 2005 22:24:28 -0000 1.2
+++ fedora-install-guide-diskpartitioning-en.xml 3 May 2005 12:19:44 -0000 1.3
@@ -1,163 +1,162 @@
-
- Disk Partitioning
+
+ Disk Partitioning
-
- This section describes how to use the installation program to
- partition disks attached to your &FED; system. If you are new to
- Linux, you may want to simply use the automatic partitioning
- method. If you are a more experienced Linux user, you can use the
- manual partitioning method to have more control over your system
- configuration.
-
+
+ This section describes how to use the installation program to
+ partition disks attached to your &FED; system. If you are new to
+ Linux, you may want to simply use the automatic partitioning method.
+ If you are a more experienced Linux user, you can use the manual
+ partitioning method to have more control over your system
+ configuration.
+
-
- Choosing a Partitioning Method
+
+ Choosing a Partitioning Method
-
- Setting Up Partitions Automatically
+
+ Setting Up Partitions Automatically
-
- Choose Automatic partitioning at the
- partitioning menu to have a partition scheme set up for you.
- Disk Druid then displays additional
- options. Select Remove all Linux partitions on this
- system to remove all ext2,
- ext3, or Linux
- swap partitions from all hard disks. Select
- Remove all partitions on this system to
- remove all partitions from all hard disks. Select
- Keep all partitions and use only existing free
- space to use only the unpartitioned space on the
- hard disk(s) to install &FC;.
-
-
- Next, select the drive(s) you wish to use for Linux
- partitions. If your system contains only one disk, that disk
- will automatically be selected. If you are confused about the
- device names used in this box, consult the Linux
- Partition-HOWTO at http://www.tldp.org/HOWTO/Partition/partition-2.html.
- Any drives you select will be used for Linux partitions
- according to the option selected above. The option selection
- is global, and you may not select a different option for each
- disk.
-
-
- If you wish to review the automatic partition configuration,
- select the Review checkbox.
-
-
+
+ Choose Automatic partitioning at the
+ partitioning menu to have a partition scheme set up for you.
+ Disk Druid then displays additional
+ options. Select Remove all Linux partitions on this
+ system to remove all ext2,
+ ext3, or Linux
+ swap partitions from all hard disks. Select
+ Remove all partitions on this system to
+ remove all partitions from all hard disks. Select
+ Keep all partitions and use only existing free
+ space to use only the unpartitioned space on the
+ hard disk(s) to install &FC;.
+
+
+ Next, select the drive(s) you wish to use for Linux partitions.
+ If your system contains only one disk, that disk will
+ automatically be selected. If you are confused about the device
+ names used in this box, consult the Linux Partition-HOWTO at
+ http://www.tldp.org/HOWTO/Partition/partition-2.html.
+ Any drives you select will be used for Linux partitions
+ according to the option selected above. The option selection is
+ global, and you may not select a different option for each disk.
+
+
+ If you wish to review the automatic partition configuration,
+ select the Review checkbox.
+
+
If you chose to remove any existing partitions, the
- installation program will ask you to confirm this choice. Once
- you have reviewed and approve of the partition configuration,
- select Next to continue to the next
- installation step. Proceed with Next to continue to the next
+ installation step. Proceed with .
-
+
-
+
-
- Setting Up Partitions Manually
+
+ Setting Up Partitions Manually
-
+
If you wish to manually set up all disk partitions, choose
- Manually partition with Disk Druid. You
- should choose this method if you require a special partition
- configuration. If you are familiar with how disk partitions
- and the Linux file system work, move on to Manually partition with Disk Druid. You
+ should choose this method if you require a special partition
+ configuration. If you are familiar with how disk partitions and
+ the Linux file system work, move on to . Otherwise, read .
-
-
-
+
+
+
-
- General Information
+
+ General Information
-
- A &FC; system should have at least three partitions installed:
-
-
-
-
- A data partition mounted at /boot
-
-
-
-
- A data partition mounted at /
-
-
-
-
- A swap partition
-
-
-
-
+
+ A &FC; system should have at least three partitions installed:
+
+
+
+
+ A data partition mounted at /boot
+
+
+
+
+ A data partition mounted at /
+
+
+
+
+ A swap partition
+
+
+
+
Most systems have more partitions than the minimum listed above.
- Choose partitions based on your particular system needs. If you
- are not sure what to choose, use the "Automatic partitioning"
- method shown in .
-
-
- Every partition must have a partition
- type. The partition type indicates the file system
- expected on that partition. The most common partition type for
- &FED; is ext3 or
- ext2. The ext3 file system provides more
- robust features for preventing data loss. Most &FED;
- administrators choose this type for data partitions.
-
-
- Most partitions have a mount point. The
- mount point indicates the directory whose contents will reside
- on that partition. Data that does not reside on any other
- partition will be in the / (or
- "root") partition. In the minimum
- configuration shown above:
-
-
-
-
- All data under the /boot directory
- resides on the /boot partition. For
- example, the file /boot/grub/grub.conf
- resides on the /boot partition.
-
-
-
-
- Any file outside of the /boot
- partition, such as /etc/passwd, resides
- on the / partition.
-
-
-
-
- Subdirectories may be assigned to partitions as well. Some
- administrators create both /usr and
- /usr/local partitions. In that case, files
- under /usr/local, such as
- /usr/local/bin/foo, will be on the
- /usr/local partition. Any other files in
- /usr, such as the
- /usr/bin directory, will be in the
- /usr partition.
-
-
- When you create partitions in this manner, as opposed to using
- one large / partition, upgrades may be
- easier. See the description of Disk
- Druid's Edit
- option for more information.
-
+ Choose partitions based on your particular system needs. If you
+ are not sure what to choose, use the "Automatic partitioning"
+ method shown in .
+
+
+ Every partition must have a partition type.
+ The partition type indicates the file system expected on that
+ partition. The most common partition type for &FED; is
+ ext3 or ext2. The
+ ext3 file system provides more robust features for preventing data
+ loss. Most &FED; administrators choose this type for data
+ partitions.
+
+
+ Most partitions have a mount point. The
+ mount point indicates the directory whose contents will reside on
+ that partition. Data that does not reside on any other partition
+ will be in the / (or
+ "root") partition. In the minimum
+ configuration shown above:
+
+
+
+
+ All data under the /boot directory
+ resides on the /boot partition. For
+ example, the file /boot/grub/grub.conf
+ resides on the /boot partition.
+
+
+
+
+ Any file outside of the /boot partition,
+ such as /etc/passwd, resides on the
+ / partition.
+
+
+
+
+ Subdirectories may be assigned to partitions as well. Some
+ administrators create both /usr and
+ /usr/local partitions. In that case, files
+ under /usr/local, such as
+ /usr/local/bin/foo, will be on the
+ /usr/local partition. Any other files in
+ /usr, such as the
+ /usr/bin directory, will be in the
+ /usr partition.
+
+
+ When you create partitions in this manner, as opposed to using one
+ large / partition, upgrades may be easier.
+ See the description of Disk Druid's
+ Edit option for more
+ information.
+
-
+
-
- Disk Druid
+
+ Disk Druid
-
+ Disk Druid
- Disk Druid
+ Disk Druid is an interactive program for editing disk
- partitions. It is only available within the &FC; installation
- system. Disk Druid supports advanced technologies such as
- RAID and LVM,
- which provide more extensible and reliable data storage for
- servers and workstations.
-
-
- Disk Druid displays the following
- actions in the installation program:
-
-
-
- New
-
+ partitions. It is only available within the &FC; installation
+ system. Disk Druid supports advanced technologies such as
+ RAID and LVM, which
+ provide more extensible and reliable data storage for servers and
+ workstations.
+
+
+ Disk Druid displays the following
+ actions in the installation program:
+
+
+
+ New
+
+
+ Select this option to add a partition or LVM physical volume
+ to the disk. In the Add partition
+ dialog, choose a mount point and a partition type. If you
+ have more than one disk on the system, choose which disks
+ the partition may inhabit. Indicate a size in megabytes for
+ the partition.
+
+
+ Some Partitions Not Allowed
- Select this option to add a partition or LVM physical
- volume to the disk. In the Add
- partition dialog, choose a mount point and a
- partition type. If you have more than one disk on the
- system, choose which disks the partition may inhabit.
- Indicate a size in megabytes for the partition.
+ The /bin, /dev,
+ /etc, /lib,
+ /proc, /root,
+ and /sbin directories may not be used
+ for separate partitions in Disk
+ Druid. These directories reside on the
+ / (root) partition.
+
+
+
+ Root and /root
+
+ The / (or "root") partition is the
+ top of the file system. The /root
+ (or "slash-root") directory is the home directory of the
+ administrator.
+
+
+
+ You may also choose from three options for sizing your
+ partition:
+
+
+
+ Fixed size
+
+
+ Use a fixed size, as close to your entry as possible.
+
+
+
+
+ Fill all space up to
+
+
+ Grow the partition to a maximum size of your choice.
+
+
+
+
+ Fill to maximum allowable
+ size
+
+
+ Grow the partition until it fills the remainder of the
+ selected disks.
+
+
+
+
+
+ Partition sizes
+
+ The actual partition on the disk may be slightly smaller
+ or larger than your choice. Disk geometry issues cause
+ this effect, not an error or bug.
-
- Some Partitions Not Allowed
+
+
+ After you enter the details for your partition, select
+ OK to continue.
+
+
+
+
+ Edit
+
+
+ Select this option to edit an existing partition, LVM volume
+ group, or a LVM physical volume that is not yet part of a
+ volume group. If you need to change the size of a LVM
+ physical volume partition, you will need to remove it from
+ any volume groups, which will erase any logical volumes it
+ contains.
+
+
+ Edit a partition to change its size, mount point, or file
+ system type. Use this function to:
+
+
+
- The /bin,
- /dev, /etc,
- /lib, /proc,
- /root, and
- /sbin directories may not be used
- for separate partitions in Disk
- Druid. These directories reside on the
- / (root) partition.
+ correct a mistake in setting up your partitions;
-
-
- Root and /root
+
+
- The / (or "root") partition is the
- top of the file system. The /root
- (or "slash-root") directory is the home directory of the
- administrator.
+ migrate Linux partitions if you are upgrading or
+ reinstalling &FC;; or
-
-
- You may also choose from three options for sizing your
- partition:
-
-
-
- Fixed size
-
-
- Use a fixed size, as close to your entry as
- possible.
-
-
-
-
- Fill all space up to
-
-
- Grow the partition to a maximum size of your choice.
-
-
-
-
- Fill to maximum allowable
- size
-
-
- Grow the partition until it fills the remainder of
- the selected disks.
-
-
-
-
-
- Partition sizes
+
+
- The actual partition on the disk may be slightly smaller
- or larger than your choice. Disk geometry issues cause
- this effect, not an error or bug.
+ provide a mount point for non-Linux partitions such as
+ those used on some Windows operating systems.
-
-
- After you enter the details for your partition, select
- OK to continue.
-
-
-
-
- Edit
-
-
- Select this option to edit an existing partition, LVM
- volume group, or a LVM physical volume that is not yet
- part of a volume group. If you need to change the size of
- a LVM physical volume partition, you will need to remove
- it from any volume groups, which will erase any logical
- volumes it contains.
-
-
- Edit a partition to change its size, mount point, or file
- system type. Use this function to:
+
+
+
+ Windows Partitions
+
+ You may not label Windows partitions that use the NTFS
+ file system with a mount point in the &FC; installer. You
+ may label vfat (FAT-16 or FAT-32)
+ partitions with a mount point.
-
+
+
+ If you need to make sweeping changes to your partition
+ configuration, consider starting over. If your disk
+ contains data that you need to keep, back it up before you
+ edit your partitions. If you edit the sizes of your
+ partitions, you will likely lose all data on those
+ partitions.
+
+
+ If you have many separate partitions for system and user
+ data, it will be easier for you to upgrade your system. The
+ installation program allows you to erase or retain data on
+ specific partitions. If your user data is on a separate
+ /home partition, you may retain that
+ data while erasing system partitions like
+ /boot.
+
+
+
+
+ Delete
+
+
+ Select a partition and then this option to erase an existing
+ partition or LVM physical volume. To delete a LVM physical
+ volume, you must first delete any volume groups of which
+ that physical volume is a member.
+
+
+ If you make a mistake, use the Reset
+ option to abandon all the changes you have made.
+
+
+
+
+ Reset
+
+
+ Select this option to force Disk
+ Druid to abandon all changes made to disk
+ partitions.
+
+
+
+
+ RAID
+
+
+ Select this button to set up software RAID on your &FED;
+ system.
+
+
+
+ Create a software RAID
+ partition
- correct a mistake in setting up your partitions;
+ Choose this option to add a partition for software
+ RAID. This option is the only choice available if
+ your disk contains no software RAID partitions.
+
+
+ Create a RAID device
- migrate Linux partitions if you are upgrading or
- reinstalling &FC;; or
+ Choose this option to construct a RAID device from two
+ or more existing software RAID partitions. This
+ option is only available if two or more software RAID
+ partitions have been configured.
+
+
+ Clone a drive to create a RAID
+ device
- provide a mount point for non-Linux partitions such as
- those used on some Windows operating systems.
+ Choose this option to set up a RAID
+ mirror of an existing disk.
+ This option is only available if two or more disks are
+ attached to the system.
-
-
- Windows Partitions
-
- You may not label Windows partitions that use the NTFS
- file system with a mount point in the &FC; installer.
- You may label vfat (FAT-16 or
- FAT-32) partitions with a mount point.
-
-
-
- If you need to make sweeping changes to your partition
- configuration, consider starting over. If your disk
- contains data that you need to keep, back it up before you
- edit your partitions. If you edit the sizes of your
- partitions, you will likely lose all data on those
- partitions.
-
-
- If you have many separate partitions for system and user
- data, it will be easier for you to upgrade your system.
- The installation program allows you to erase or retain
- data on specific partitions. If your user data is on a
- separate /home partition, you may
- retain that data while erasing system partitions like
- /boot.
-
-
-
-
- Delete
-
-
- Select a partition and then this option to erase an
- existing partition or LVM physical volume. To delete a
- LVM physical volume, you must first delete any volume
- groups of which that physical volume is a member.
-
-
- If you make a mistake, use the Reset
- option to abandon all the changes you have made.
-
-
-
-
- Reset
-
+
+
+
+
+
+ LVM
+
+
+ Select this button to set up LVM on your &FED; system. You
+ must first create at least one partition or software RAID
+ device as a LVM physical volume, using the
+ Add option in the main
+ Disk Druid dialog.
+
+
+ Understanding LVM Components
- Select this option to force Disk
- Druid to abandon all changes made to disk
+ In LVM, one or more physical volumes are combined to form
+ a volume group. Each volume group's total storage may be
+ apportioned for one or more logical volumes. Logical
+ volumes function much like standard data partitions. They
+ have a file system type, such as ext3, and a mount point.
+ An administrator may grow or shrink logical volumes
+ without disturbing any data, unlike standard disk
partitions.
-
-
-
- RAID
-
-
- Select this button to set up software RAID on your &FED;
- system.
-
-
-
- Create a software RAID
- partition
-
-
- Choose this option to add a partition for software
- RAID. This option is the only choice available if
- your disk contains no software RAID partitions.
-
-
-
-
- Create a RAID device
-
-
- Choose this option to construct a RAID device from
- two or more existing software RAID partitions. This
- option is only available if two or more software
- RAID partitions have been configured.
-
-
-
-
- Clone a drive to create a RAID
- device
-
-
- Choose this option to set up a RAID
- mirror of an existing disk.
- This option is only available if two or more disks
- are attached to the system.
-
-
-
-
-
-
-
- LVM
-
-
- Select this button to set up LVM on your &FED; system. You
- must first create at least one partition or software RAID
- device as a LVM physical volume, using the
- Add option in the main
- Disk Druid dialog.
-
-
- Understanding LVM Components
-
- In LVM, one or more physical volumes are combined to
- form a volume group. Each volume group's total storage
- may be apportioned for one or more logical volumes.
- Logical volumes function much like standard data
- partitions. They have a file system type, such as ext3,
- and a mount point. An administrator may grow or shrink
- logical volumes without disturbing any data, unlike
- standard disk partitions.
-
-
-
- To assign one or more physical volumes to a volume group,
- first name the volume group. Then select the physical
- volumes to be used in the volume group. Finally, create
- and/or edit logical volumes on any volume groups using the
- Add, Edit and
- Delete options.
-
-
- You may not remove a physical volume from a volume group
- if doing so would leave insufficient space for that
- group's logical volumes. For example, imagine a volume
- group made up of two 5 GB LVM physical volume partitions,
- which houses a logical volume that is 8 GB in size. The
- installer will not allow you to remove either of the
- component physical volumes, since that would leave only 5
- GB in the group for an 8 GB logical volume. If you reduce
- the total size of any logical volumes appropriately, you
- may then remove a physical volume from the volume group.
-
-
-
-
-
- When you have finished setting up and reviewing your partition
- configuration, select Next to continue the
- installation process.
-
+
+
+ To assign one or more physical volumes to a volume group,
+ first name the volume group. Then select the physical
+ volumes to be used in the volume group. Finally, create
+ and/or edit logical volumes on any volume groups using the
+ Add, Edit and
+ Delete options.
+
+
+ You may not remove a physical volume from a volume group if
+ doing so would leave insufficient space for that group's
+ logical volumes. For example, imagine a volume group made
+ up of two 5 GB LVM physical volume partitions, which houses
+ a logical volume that is 8 GB in size. The installer will
+ not allow you to remove either of the component physical
+ volumes, since that would leave only 5 GB in the group for
+ an 8 GB logical volume. If you reduce the total size of any
+ logical volumes appropriately, you may then remove a
+ physical volume from the volume group.
+
+
+
+
+
+ When you have finished setting up and reviewing your partition
+ configuration, select Next to continue the
+ installation process.
+
-
+
-
+
Index: fedora-install-guide-firewallconfig-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-firewallconfig-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-firewallconfig-en.xml 2 May 2005 22:24:28 -0000 1.2
+++ fedora-install-guide-firewallconfig-en.xml 3 May 2005 12:19:44 -0000 1.3
@@ -4,124 +4,130 @@
Fifth Step: Firewall Configuration
- The default security configuration for &FC; will protect your system
- without restricting any of the functions of a desktop or laptop
- computer. If you are installing a server then you will need to alter
- the settings in order to enable others to access the system.
+ The default security configuration for &FC; will protect your system
+ without restricting any of the functions of a desktop or laptop
+ computer. If you are installing a server then you will need to
+ alter the settings in order to enable others to access the system.
- Click Next to proceed after you have reviewed the
- security configuration and made any necessary changes.
+ Click Next to proceed after you have reviewed
+ the security configuration and made any necessary changes.
- Firewall
+ Firewall
-
- The firewall built into Linux checks every incoming and outgoing network
- connection between your machine and another against a set of rules.
- These rules specify which types of connections are permitted and which
- are denied.
-
-
-
- By default the firewall is enabled, with a simple set of rules that
- allow connections to be made from your system to others, but block
- incoming connections from other systems. You can then choose to allow access
- to specific network services on your &FC; system.
+
+ The firewall built into Linux checks every incoming and outgoing
+ network connection between your machine and another against a set
+ of rules. These rules specify which types of connections are
+ permitted and which are denied.
+
+
+
+ By default the firewall is enabled, with a simple set of rules
+ that allow connections to be made from your system to others, but
+ block incoming connections from other systems. You can then
+ choose to allow access to specific network services on your &FC;
+ system.
- To enable access to services listed on this screen, click the checkbox next to
- the name of the service. After the installation is complete you can
- enable access to other services as well.
+ To enable access to services listed on this screen, click the
+ checkbox next to the name of the service. After the installation
+ is complete you can enable access to other services as well.
- Firewall Configuration Screen
+ Firewall Configuration Screen
-
-
-
-
-
-
-
-
- Firewall configuration screen.
-
-
+
+
+
+
+
+
+
+
+ Firewall configuration screen.
+
+
-
- It is recommended that you do not disable the firewall. If it is
- necessary to do so, then select No firewall.
-
-
-
- Changing the firewall settings
+ It is recommended that you do not disable the firewall. If it is
+ necessary to do so, then select No firewall.
+
+
+
+ Changing the firewall settings
+
To change these settings later, use the
- system-config-securitylevel utility. From the
- main menu, choose System
- SettingsSecurity Level and Firewall.
-
-
+ system-config-securitylevel utility.
+ From the main menu, choose System
+ SettingsSecurity Level and
+ Firewall.
+
+
- &SEL;
+ &SEL;
-
- The &SEL; (Security Enhanced Linux) framework that is part of &FC;
- limits the actions of both users and programs by enforcing defined
- security policies throughout the operating system. Software bugs or
- configuration changes can render a system vulnerable, and the
- restrictions imposed by the &SEL; policies provide an extra line of defense.
-
-
-
- An inflexible set of &SEL; policies could also inhibit many normal
- activities. For this reason &FC; uses targeted policies, which only
- affect specific network services. These services cannot perform actions
- that are not part of their normal functions. This means that &SEL; can
- be Active without causing users any inconvenience.
-
+
+ The &SEL; (Security Enhanced Linux) framework that is part of &FC;
+ limits the actions of both users and programs by enforcing defined
+ security policies throughout the operating system. Software bugs
+ or configuration changes can render a system vulnerable, and the
+ restrictions imposed by the &SEL; policies provide an extra line
+ of defense.
+
-
- As &SEL; is a new technology, a diagnostic mode is provided. If you set
- &SEL; to Warn then the system is configured, but
- any breach of security policies will merely cause an error message to
- appear. No activities are actually prohibited when &SEL; is installed
- in this mode. You can make &SEL; fully active at a later time.
-
+
+ An inflexible set of &SEL; policies could also inhibit many normal
+ activities. For this reason &FC; uses targeted policies, which
+ only affect specific network services. These services cannot
+ perform actions that are not part of their normal functions. This
+ means that &SEL; can be Active without
+ causing users any inconvenience.
+
-
- If you choose to have &SEL; Disabled then the
- access control system will not be configured at all. To make &SEL;
- active later you should use the
- system-config-securitylevel utility.
-
+
+ As &SEL; is a new technology, a diagnostic mode is provided. If
+ you set &SEL; to Warn then the system is
+ configured, but any breach of security policies will merely cause
+ an error message to appear. No activities are actually prohibited
+ when &SEL; is installed in this mode. You can make &SEL; fully
+ active at a later time.
+
-
- Changing the &SEL; policy
- &SEL; is unique in that it cannot be bypassed, even by the system
- administrators. You can configure the behavior of &SEL; with the
- system-config-securitylevel utility. From the
- main menu, choose System
- SettingsSecurity Level and Firewall.
+ If you choose to have &SEL; Disabled then the
+ access control system will not be configured at all. To make
+ &SEL; active later you should use the
+ system-config-securitylevel utility.
-
-
+
+ Changing the &SEL; policy
+
+ &SEL; is unique in that it cannot be bypassed, even by the
+ system administrators. You can configure the behavior of &SEL;
+ with the system-config-securitylevel
+ utility. From the main menu, choose System
+ SettingsSecurity Level and
+ Firewall.
+
+
+
+
- Installing Packages
+ Installing Packages
-
- The installation process will now take place. As the installation is
- carried out you will see the progress reported on screen.
-
-
-
- If you are using CDs to install &FC; you will be prompted to change discs
- periodically. After inserting a disc allow two or three seconds for
- the CD to be detected before clicking OK to
- resume the installation.
-
-
-
- Installing Packages Screen
-
-
+
+ The installation process will now take place. As the installation
+ is carried out you will see the progress reported on screen.
+
+
+
+ If you are using CDs to install &FC; you will be prompted to change
+ discs periodically. After inserting a disc allow two or three
+ seconds for the CD to be detected before clicking
+ OK to resume the installation.
+
+
+
+ Installing Packages Screen
+
+
-
-
+
+
-
-
+
+
- Installing packages screen.
+ Installing packages screen.
-
-
-
+
+
+
-
- When the installation has completed you will be prompted to
- Reboot your computer. Any installation disc in
- the CD or DVD drive will automatically be ejected.
-
-
-
- The first time that your computer loads &FC; you will be presented with
- a Welcome screen and given the opportunity to
- configure various aspects of your new system. This process is explained
- in the next section.
-
+
+ When the installation has completed you will be prompted to
+ Reboot your computer. Any installation disc
+ in the CD or DVD drive will automatically be ejected.
+
+
+
+ The first time that your computer loads &FC; you will be presented
+ with a Welcome screen and given the opportunity
+ to configure various aspects of your new system. This process is
+ explained in the next section.
+
Index: fedora-install-guide-installtypes-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-installtypes-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-installtypes-en.xml 2 May 2005 22:24:28 -0000 1.2
+++ fedora-install-guide-installtypes-en.xml 3 May 2005 12:19:44 -0000 1.3
@@ -4,83 +4,88 @@
First Step: Installation Type
- Installation types enable you to ensure that your &FED; system is loaded
- with the correct software without needing to specify individual
- packages. The installation type that you choose determines the
- suggested software later on in the installation process. You can
- customize the package selection at that point if you wish to do so.
+ Installation types enable you to ensure that your &FED; system is
+ loaded with the correct software without needing to specify
+ individual packages. The installation type that you choose
+ determines the suggested software later on in the installation
+ process. You can customize the package selection at that point if
+ you wish to do so.
-
- Installation Type Screen
-
-
+
+ Installation Type Screen
+
+
-
-
+
+
-
-
+
+
- Installation type screen.
+ Installation type screen.
-
-
-
+
+
+
- A Personal Desktop installation is the default. It
- provides a graphical working environment with an office suite, Internet
- applications and multimedia software.
+ A Personal Desktop installation is the default.
+ It provides a graphical working environment with an office suite,
+ Internet applications and multimedia software.
- A Workstation installation includes the same
- software as a Personal Desktop. Extra software
- will also be installed for development and systems administration.
- Choose this installation type if you will be compiling software from source code.
+ A Workstation installation includes the same
+ software as a Personal Desktop. Extra software
+ will also be installed for development and systems administration.
+ Choose this installation type if you will be compiling software from
+ source code.
- A Server installation automatically provides the
- Apache Web server and the Samba suite of services, along with
- administration tools. By default, no graphical environment is included.
+ A Server installation automatically provides
+ the Apache Web server and the Samba suite of services, along with
+ administration tools. By default, no graphical environment is
+ included.
- If you choose to perform a Custom installation then
- you will automatically be presented with the Package Group
- Selection screen later on in the installation process.
+ If you choose to perform a Custom installation
+ then you will automatically be presented with the Package
+ Group Selection screen later on in the installation
+ process.
- Default network services
-
- All &FC; installations include e-mail (SMTP), file sharing (NFS), printing
- (CUPS) and remote login (SSH) services. Various automated processes on
- your &FED; system use the e-mail service to send reports and messages to
- the system administrator. By default the e-mail and printing services do
- not accept connections from other systems.
-
+ Default network services
+
+ All &FC; installations include e-mail (SMTP), file sharing (NFS),
+ printing (CUPS) and remote login (SSH) services. Various
+ automated processes on your &FED; system use the e-mail service to
+ send reports and messages to the system administrator. By default
+ the e-mail and printing services do not accept connections from
+ other systems.
+
- Click Next once you have made a selection.
-
+ Click Next once you have made a selection.
+
-
+ Minimal installations
-
+
To install a system with the minimum of software choose the
- Custom installation type. On the Package
- Group Selection screen select the
- Minimal package group. A small command-line only
- system will then be installed. The only services that are included in a
- Minimal installation are CUPS, NFS, SMTP and SSH. This
- type of installation is useful as a basis for preparing
- specialized systems.
-
-
+ Custom installation type. On the
+ Package Group Selection screen select the
+ Minimal package group. A small command-line
+ only system will then be installed. The only services that are
+ included in a Minimal installation are CUPS,
+ NFS, SMTP and SSH. This type of installation is useful as a basis
+ for preparing specialized systems.
+
+
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-networkconfig-en.xml 2 May 2005 22:24:28 -0000 1.2
+++ fedora-install-guide-networkconfig-en.xml 3 May 2005 12:19:44 -0000 1.3
@@ -4,150 +4,163 @@
Fourth Step: Network Configuration
- This screen enables you to customize the network settings of the final
- system.
+ This screen enables you to customize the network settings of the
+ final system.
- It is not necessary to manually configure these settings if your computer
- will be part of an existing network, or if it is a laptop that will move
- between networks. By default, &FC; will activate all of the network
- interfaces on your computer and configure them to use DHCP. Most networks
- have a DHCP service that can automatically supply your system with
- connection information.
+ It is not necessary to manually configure these settings if your
+ computer will be part of an existing network, or if it is a laptop
+ that will move between networks. By default, &FC; will activate
+ all of the network interfaces on your computer and configure them to
+ use DHCP. Most networks have a DHCP service that can automatically
+ supply your system with connection information.
- Wireless interfaces using DHCP will join an open wireless network once
- it is in range. Many wireless networks are restricted, and will only
- accept systems which also have the correct security credentials.
+ Wireless interfaces using DHCP will join an open wireless network
+ once it is in range. Many wireless networks are restricted, and
+ will only accept systems which also have the correct security
+ credentials.
- Click Next once you are satisfied with the
- network settings for your system.
+ Click Next once you are satisfied with the
+ network settings for your system.
-
- Network Configuration Screen
-
-
+
+ Network Configuration Screen
+
+
-
-
+
+
-
-
+
+
- Network configuration screen.
+ Network configuration screen.
-
-
-
+
+
+
- Network Devices
+ Network Devices
- The list on the screen shows the network interfaces that the
- installation system has detected on your computer. Each interface will
- have a unique address on the network that it is attached to. This IP
- address can be assigned by the network DHCP service.
+ The list on the screen shows the network interfaces that the
+ installation system has detected on your computer. Each interface
+ will have a unique address on the network that it is attached to.
+ This IP address can be assigned by the network DHCP service.
- To set an IP address yourself, highlight the interface on the
-Network Device list and then
- click Edit. This will open a dialog box. Click
- the Configure using DHCP checkbox, so that it is empty.
- Type the correct numbers of the IP Address in the
- boxes. You must also set the appropriate Netmask
- for the interface. Then click OK.
+ To set an IP address yourself, highlight the interface on the
+ Network Device list and then click
+ Edit. This will open a dialog box. Click
+ the Configure using DHCP checkbox, so that it
+ is empty. Type the correct numbers of the IP
+ Address in the boxes. You must also set the
+ appropriate Netmask for the interface. Then
+ click OK.
- You can also choose to set an interface as inactive, so that it will not
- be enabled as your machine starts. Interfaces can be activated at any
- time. To set an interface to be inactive, click the Active on
- Boot checkbox next to the name of the interface.
+ You can also choose to set an interface as inactive, so that it
+ will not be enabled as your machine starts. Interfaces can be
+ activated at any time. To set an interface to be inactive, click
+ the Active on Boot checkbox next to the name
+ of the interface.
-
- Modems are configured after the installation process
-
- Modems are not listed on the Network Configuration
- screen. Use either Internet Connection
- Wizard or system-config-network
- to set up Internet access on your &FED; system. The settings for your
- modem are specific to your particular Internet Service Provider (ISP).
-
-
+
+ Modems are configured after the installation
+ process
+
+ Modems are not listed on the Network
+ Configuration screen. Use either
+ Internet Connection Wizard or
+ system-config-network to set up
+ Internet access on your &FED; system. The settings for your
+ modem are specific to your particular Internet Service Provider
+ (ISP).
+
+
-
+
- Computer Hostname
+ Computer Hostname
- On some networks the DHCP provider will also set the name of the
- computer itself. To specify the name of your computer select
- manual and type the complete name in the box. A
- full computer hostname includes both the name of the machine and the
- name of the DNS domain that it is a member of, e.g. machine1.example.com.
+ On some networks the DHCP provider will also set the name of the
+ computer itself. To specify the name of your computer select
+ manual and type the complete name in the box.
+ A full computer hostname includes both the name of the machine and
+ the name of the DNS domain that it is a member of, e.g.
+ machine1.example.com.
- Valid Hostnames
+ Valid Hostnames
- You can give your system any name that you wish, provided that the full
- hostname is unique. The system name may include letters, numbers and
- hyphens. You can change the name of your system at any time.
+ You can give your system any name that you wish, provided that
+ the full hostname is unique. The system name may include
+ letters, numbers and hyphens. You can change the name of your
+ system at any time.
-
+
- Miscellaneous Settings
+ Miscellaneous Settings
- If you have chosen to manually configure a network interface then you
- may also wish to determine the other network settings for your computer.
- All of these settings are the IP addresses of other systems on the network.
+ If you have chosen to manually configure a network interface then
+ you may also wish to determine the other network settings for your
+ computer. All of these settings are the IP addresses of other
+ systems on the network.
- The Gateway is the device that provides access to
- other networks. Gateways are also referred to as routers.
+ The Gateway is the device that provides
+ access to other networks. Gateways are also referred to as
+ routers.
- Most software relies on the DNS (Domain Name Service) provider to locate
- machines and services on the network. A &FC; system may use more than one DNS
- server. If the Primary DNS server does not respond
- then the query is resubmitted to the Secondary DNS
- server, and so on. This screen enables you to specify the IP addresses
- of up to three DNS servers.
+ Most software relies on the DNS (Domain Name Service) provider to
+ locate machines and services on the network. A &FC; system may
+ use more than one DNS server. If the Primary
+ DNS server does not respond then the query is
+ resubmitted to the Secondary DNS server, and
+ so on. This screen enables you to specify the IP addresses of up
+ to three DNS servers.
- The Gateway is the device that provides access to
- other networks. Gateways are also referred to as routers.
+ The Gateway is the device that provides
+ access to other networks. Gateways are also referred to as
+ routers.
- Most software relies on the DNS (Domain Name Service) provider to locate
- machines and services on the network. A &FC; system may use more than one DNS
- server. If the Primary DNS server does not respond
- then the query is resubmitted to the Secondary DNS
- server, and so on. This screen enables you to specify the IP addresses
- of up to three DNS servers.
+ Most software relies on the DNS (Domain Name Service) provider to
+ locate machines and services on the network. A &FC; system may
+ use more than one DNS server. If the Primary
+ DNS server does not respond then the query is
+ resubmitted to the Secondary DNS server, and
+ so on. This screen enables you to specify the IP addresses of up
+ to three DNS servers.
-
+
+
-
+
@@ -82,5 +82,5 @@
&ACKNOWLEDGMENTS;
-
+
From fedora-docs-commits at redhat.com Tue May 3 22:09:23 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 3 May 2005 18:09:23 -0400
Subject: fedora-docs/install-guide
fedora-install-guide-other-instmethods-en.xml, 1.3, 1.4
Message-ID: <200505032209.j43M9N0f016586@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16578
Modified Files:
fedora-install-guide-other-instmethods-en.xml
Log Message:
Ran scripts from wiki (DocsProject/UsefulScripts) as a test
Index: fedora-install-guide-other-instmethods-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-other-instmethods-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-other-instmethods-en.xml 3 May 2005 12:19:44 -0000 1.3
+++ fedora-install-guide-other-instmethods-en.xml 3 May 2005 22:09:21 -0000 1.4
@@ -43,18 +43,18 @@
-
+ Installing from a Network Server with FTP, HTTP or
NFS
These installation methods require a server to be configured
- first. Setting up an installation server is detailed in a separate
+ first. Setting up an installation server is detailed in a separate
tutorial.
-
+ Configuring TCP/IP
@@ -84,14 +84,14 @@
This settings on this screen only apply during the installation
- process. You configure the network settings for the final system
+ process. You configure the network settings for the final system
on a later screen.
-
+
-
+ Network Service Setup
@@ -126,10 +126,10 @@
-
+
-
+ Further FTP Setup
@@ -156,12 +156,12 @@
-
+
-
+
-
+ Installing from a Hard Drive
@@ -169,7 +169,7 @@
&FED; discs. The hard drive can be either internal to the
computer, or attached by USB. The partition on the hard drive
holding the ISO files must be formatted with either ext2, ext3 or
- the FAT file system. External hard drives are supplied formatted
+ the FAT file system. External hard drives are supplied formatted
as FAT.
@@ -212,7 +212,7 @@
Select OK to continue.
-
+
From fedora-docs-commits at redhat.com Tue May 3 23:21:22 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 3 May 2005 19:21:22 -0400
Subject: fedora-docs/release-notes - New directory
Message-ID: <200505032321.j43NLMWH017768@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17762/release-notes
Log Message:
Directory /cvs/docs/fedora-docs/release-notes added to the repository
From fedora-docs-commits at redhat.com Tue May 3 23:23:49 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 3 May 2005 19:23:49 -0400
Subject: fedora-docs/release-notes fc4test1-relnotes.wiki, NONE,
1.1 fc4test2-relnotes, NONE, 1.1
Message-ID: <200505032323.j43NNnRb017791@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17784
Added Files:
fc4test1-relnotes.wiki fc4test2-relnotes
Log Message:
Capturing these interim release notes, to be deleted when this directory is properly filled out.
--- NEW FILE fc4test1-relnotes.wiki ---
= Release Notes for Fedora Core 4 test 1 =
This page currently supplements the release notes shipped with Fedora Core 4 test 1, which were not able to be updated in time for packaging. We are discussing the idea of using a Wiki within the release notes creation process, which would still need to be converted to DocBook and packaged with the release. This first usage will let us test this idea.
For details on how to edit this document, refer to FedoraDocs/RelNotes/RelNotesProcess.
If you are not a developer and see a bug in the document such as incorrect information or unclear writing, or have an enhancement request, use this [https://bugzilla.redhat.com/beta/enter_bug.cgi?product=Fedora%20Core&op_sys=Linux&bug_status=NEW&version=fc4test1&component=fedora-docs&rep_platform=All&priority=normal&bug_severity=normal&assigned_to=kwade%40redhat.com&cc=&estimated_time_presets=0.0&estimated_time=0.0&bug_file_loc=http%3A%2F%2Ffedoraproject.org%2Fwiki%2FFedoraDocs_2fRelNotes_2fCore4Test1RelNotes&short_desc=Describe%20problem%2C%20fix%2C%20or%20request%20for%20release%20notes&comment=Description%20of%20problem%2C%20bug%2C%20incorrect%20information%2C%20or%20enhancement%20request%3A%0D%0A%0D%0A%0D%0AVersion%20of%20release%20notes%20this%20bug%20refers%20to%3A%0D%0A%0D%0AFC4test1%0D%0A%0D%0AURL%20of%20bug%2Fenhancement%20%28change%20if%20different%29%3A%0D%0A%0D%0Ahttp%3A%2F%2Ffedoraproject.org%2Fwiki%2FFedoraDocs_2fRelNotes_2fCore4Test1RelNotes&keywords=&dependso!
n=&blocked=151189&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug pre-filled bugzilla request].
When you use this pre-filled bug, your report blocks bugzilla #151189, which is a master tracker for Fedora Core release notes work. This helps us keep track of your report so that it is not lost.
[[TableOfContents]]
== Fedora Core 4test1 Release Notes ==
Copyright (c) 2005 Red Hat, Inc.
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 [1]http://www.gnu.org/licenses/fdl.html.
This document may be copied and distributed in any medium, either commercially or non-commercially, 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.
Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.
The Fedora trademark is a trademark of Red Hat, Inc. in the United States and other countries.
Linux is a registered trademark of Linus Torvalds.
All other trademarks and copyrights referred to are the property of their respective owners.
The GPG fingerprint of the "Fedora Project " key is:
CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
---------------------------------------------------------------------------
== Introduction ==
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, a complete, general-purpose operating system built exclusively from open source software.
NOTE: Fedora Core is not a supported product of Red Hat, Inc.
For more information, refer to the Fedora Project overview later in this document.
The following topics related to Fedora Core 4test1 are covered in this document:
* Introduction (this section)
* Hardware requirements
* Overview of this release
* Installation-related notes
* Package-specific notes
* Packages added/removed/deprecated
* An overview of the Fedora Project
== Hardware Requirements ==
The following information represents the minimum hardware requirements necessary to successfully install Fedora Core 4test1.
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.
=== CPU Requirements ===
This section lists the CPU specifications required by Fedora Core 4test1.
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.
* Minimum: Pentium-class
Fedora Core 4test1 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.
* Recommended for text-mode: 200 MHz Pentium-class or better
* Recommended for graphical: 400 MHz Pentium II or better
=== Hard Disk Space Requirements ===
This section lists the disk space required to install Fedora Core 4test1.
Note
The disk space requirements listed below represent the disk space taken up by Fedora Core 4test1 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.
* Custom Installation (Minimal): 620MB
* Server: 1.1GB
* Personal Desktop: 2.3GB
* Workstation: 3.0GB
* Custom Installation (Everything): 6.9GB
=== Memory Requirements ===
This section lists the memory required to install Fedora Core 4test1.
* Minimum for text-mode: 64MB
* Minimum for graphical: 192MB
* Recommended for graphical: 256MB
== Overview of This Release ==
The following list includes brief summaries of some of the more significant aspects of Fedora Core 4test1:
* Fedora Core 4test1 contains the following changes:
* GCC 4.0
* GNOME 2.10
* KDE 3.4
* SELinux -- This includes a new "targeted" policy that monitors specific daemons with less intrusion than the strict policy in use before. This policy is enabled by default. For more information, refer to:
[2]http://fedora.redhat.com/docs/selinux-faq/
* Indic language support
* Firefox and Mozilla can be enabled with pango rendering support, which enables many text layout features, including the rendering of CTL (Complex Text Layout) such as Indic languages. To enable this, set the following environment variable when running Firefox or Mozilla:
MOZ_ENABLE_PANGO=1
* Kernel and e2fsprogs support for online growing of ext3 file systems.
* Various desktop-related features, including, but not limited to:
* Remote desktops using VNC
([3]http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html)
* Printing improvements
([4]http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html)
* Evolution 2.0
Note
VMware WS 4.5.2 is known to work on Fedora Core 4test1 after the following workarounds are used:
* You must upgrade the kernel modules and configuration using the unofficial vmware-any-any- * toolkit available from:
[5]http://platan.vc.cvut.cz/ftp/pub/vmware/
* After vmware-config.pl is run and the VMware modules are loaded, the following command creates the /sys/class/ * nodes needed for udev:
cp -rp /dev/vm * /etc/udev/devices/
== Installation-Related Notes ==
This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core 4test1 in general.
Note
If you intend to download the Fedora Core 4test1 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.
Anaconda Notes
* 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.
* 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.
* Fedora Core 4test1 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.
== Installation-Related Issues ==
* 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.
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.
* 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.
* 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:
[6]http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
* There have been issues observed when upgrading Red Hat Linux 7., 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The issue 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 issue:
1) You may remove Ximian GNOME from your system prior to upgrading to Fedora Core.
2) You may upgrade your system, and then immediately reinstall Ximian GNOME.
3) 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.
== Package-Specific Notes ==
The following sections contain information regarding packages that have undergone significant changes for Fedora Core 4test1. For easier access, they are organized using the same groups used in Anaconda.
=== Base ===
This section contains information related to basic system components.
openssh
Fedora Core 4test1 contains OpenSSH 3.9, which includes strict permission and ownership checks for the ~/.ssh/config file. These checks mean that ssh will exit if this file does not have appropriate ownership and permissions.
Therefore, make sure that ~/.ssh/config is owned by the owner of ~/, and that its permissions are set to mode 600.
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 flag 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 flag instead of the -X flag, or set ForwardX11Trusted in the ~/.ssh/config file.
=== Core ===
This section contains the most elemental components of Fedora Core, including the kernel.
e2fsprogs
The ext2online utility has been added for online growing of existing ext3 file systems.
Note
It is important to keep in mind that ext2online does not grow the underlying block device itself -- there must be sufficient unused space already present on the device. The easiest way to ensure this is to use LVM volumes and to run lvresize or lvextend to extend the device.
In addition, file systems must be specially prepared in order to be resized past a certain point. The preparation involves reserving a small amount of space into which on-disk tables can grow. For newly-created file systems, mke2fs reserves such space automatically; the space reserved is sufficient to grow the file system by a factor of 1000. The creation of this reserved space can be disabled by the following command:
mke2fs -O ^resize_inode
Future releases of Fedora Core will allow the creation of this reserved space on existing file systems.
glibc
* The version of glibc provided with Fedora Core 4test1 performs additional internal sanity checks to prevent and detect data corruption as early as possible. By default, should corruption be detected, a message similar to the following will be displayed on standard error (or logged via syslog if stderr is not open):
* * * glibc detected * * * double free or corruption: 0x0937d008 * * *
By default, the program that generated this error will also be killed; however, this (and whether or not an error message is generated) can be controlled via the MALLOC_CHECK_ environment variable. The following settings are supported:
* 0 -- Do not generate an error message, and do not kill the program
* 1 -- Generate an error message, but do not kill the program
* 2 -- Do not generate an error message, but kill the program
* 3 -- Generate an error message and kill the program
Note
If MALLOC_CHECK_ is explicitly set a value other than 0, this causes glibc to perform more tests that are more extensive than the default, and may impact performance.
Should you have a program from a third party ISV that triggers these corruption checks and displays a message, you should file a defect report with the application's vendor, since this indicates a serious bug.
hotplug
The location where hotplug expects firmware to be loaded into (for example, firmware for Cardbus cards) has changed from /usr/lib/hotplug/firmware to /lib/firmware. Existing firmware files must be moved into the new directory.
kernel
* In the past, the process of updating the kernel did not change the default kernel in the system's boot loader configuration.
Fedora Core 4test1 changes this behavior to set newly-installed kernels as the default. This behavior applies to all installation methods (including rpm -i).
This behavior is controlled by two lines in the /etc/sysconfig/kernel file:
* UPGRADEDEFAULT -- Controls whether new kernels will be booted by default (default value: yes)
* DEFAULTKERNEL -- kernel RPMs whose names match this value will be booted by default (default value: depends on hardware configuration)
* In order to eliminate the redundancy inherent in providing a separate package for the kernel source code when that source code already exists in the kernel's .src.rpm file, Fedora Core 4test1 no longer includes the kernel-source package. Users that require access to the kernel sources can find them in the kernel .src.rpm file. To create an exploded source tree from this file, perform the following steps (note that refers to the version specification for your currently-running kernel):
1. Obtain the kernel-.src.rpm file from one of the following sources:
* The SRPMS directory on the appropriate "SRPMS" CD iso image
* The FTP site where you got the kernel package
* By running the following command:
up2date --get-source kernel
2. Install kernel-.src.rpm (given the default RPM configuration, the files this package contains will be written to /usr/src/redhat/)
3. Change directory to /usr/src/redhat/SPECS/, and issue the following command:
rpmbuild -bp --target= kernel.spec
(Where is the desired target architecture.)
On a default RPM configuration, the kernel tree will be located in /usr/src/redhat/BUILD/.
4. In resulting tree, the configurations for the specific kernels shipped in Fedora Core 4test1 are in the /configs/ directory. For example, the i686 SMP configuration file is named /configs/kernel--i686-smp.config. Issue the following command to place the desired configuration file in the proper place for building:
cp ./.config
5. Issue the following command:
make oldconfig
You can then proceed as usual.
Note
An exploded source tree is not required to build kernel modules against the currently in-use kernel.
For example, to build the foo.ko module, create the following file (named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
Issue the make command to build the foo.ko module.
* I[2]O SCSI RAID adapters from manufacturers such as Adaptec now use the i2o_block driver, rather than the dpt_i2o driver used by Fedora Core 1 and earlier distributions.
Be aware that block devices used by the i2o_block driver are /dev/i2o/hd * rather than the /dev/sd * SCSI devices. This may be problematic for those upgrading from older distributions that used the dpt_i2o driver. Therefore, after an upgrade to Fedora Core 4test1, you may need to boot using a rescue disk and edit your /etc/fstab file to use the new devices.
For more information about the new I[2]O device layer and Fedora Core-specific notes, visit the I[2]O homepage:
[7]http://i2o.shadowconnect.com/
=== Language Support ===
This section includes information related to the support of various languages under Fedora Core.
iiimf
* The default Input Method (IM) for Chinese (Simplified and Traditional), Japanese, and Korean has been changed to IIIMF -- the Internet/Intranet Input Method Framework. IIIMF is supported as a native GTK2 IM module, and also through XIM using the httx client. IIIMF supports the use of multiple Language Engines (LEs) at the same time; using the GNOME Input Method Language Engine Tool (GIMLET -- an applet) it is possible to switch between LEs of different languages inside GTK2 applications.
IIIMF currently defaults to using Ctrl-Space or Shift-Space for toggling the input method on and off (Emacs users can use Ctrl-@ instead of Ctrl-Space to set the mark.)
Depending on your selection at the language support screen during installation, one or more IIIMF language engines may be installed. The IIIMF server package (iiimf-server) will also be installed if a language engine has been selected. The language to language engine (LE) package mappings are as follows:
* ja_JP -- iiimf-le-canna
* zh_CN -- iiimf-le-chinput
* zh_TW -- iiimf-le-xcin
* ko_KR -- iiimf-le-hangul
* {bn,gu,pa,ta,hi}_IN -- iiimf-le-unit
Accordingly, input via IIIMF will be enabled if you have chosen one of the following as your default locale:
* ja_JP
* zh_CN
* zh_TW
* ko_KR
* {bn,gu,pa,ta,hi}_IN
To aid your use of IIIMF, if you have selected one of the above locales and you are using the GNOME Desktop, when you first login the GIMLET utility (part of the iiimf-gnome-im-switcher package) will automatically be added to your panel.
GIMLET is a utility for switching between the different LEs that are installed on your system. Using a different language engine allows you to enter text in different languages. Alternatively you may add GIMLET manually to your panel by right clicking on the panel and selecting:
Add to Panel -> GIMLET
Should you wish to switch between IIIMF or the legacy input method framework XIM, you can use the system-switch-im application. After changing the input method framework your changes will be reflected when you next start the X Window System.
=== Mail Server ===
This section contains information related to the mail transport agents included with Fedora Core.
mailman
Earlier mailman RPMs installed all files under the /var/mailman/ directory. Unfortunately, this did not conform to the Filesystem Hierarchy Standard (FHS) and also created security violations when SELinux was enabled.
If you previously had mailman installed and had edited files in /var/mailman/ (such as mm_cfg.py) you must move those changes to their new location, as documented in the following file:
/usr/share/doc/mailman- */INSTALL.REDHAT
sendmail
* 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 listen on network devices (or comment out this option entirely using the dnl comment delimiter). You must then regenerate /etc/mail/sendmail.cf by running the following command (as root):
make -C /etc/mail
Note that you must have the sendmail-cf package installed for this to work.
=== Server Configuration Tools ===
This section contains information related to various server configuration tools.
system-config-securitylevel
The firewall constructed by the system-config-securitylevel configuration tool now allows CUPS and Multicast DNS (mDNS) browsing. Note that, at the present time, these services cannot be disabled by system-config-securitylevel.
=== Sound and Video ===
This section contains information related to multimedia applications.
k3b
Past users of the CD/DVD burning application k3b may notice that the program k3bsetup is missing. This is because k3bsetup is not necessary under Fedora Core 4test1.
=== Web Server ===
This section contains information related to Web-related tools.
crypto-utils
The certwatch(1) tool has been added to the crypto-utils package. This tool is used to send warning mail to root when any configured SSL certificates have expired or are approaching the expiration date. By default, the tool checks any certificates that are enabled in the mod_ssl configuration.
httpd
By default, the httpd daemon is now started using the C locale, rather than using the configured system locale setting. This behavior can be changed by setting the HTTPD_LANG variable in the /etc/sysconfig/httpd file.
php
The gd, mbstring, and ncurses extensions have been moved to the php-gd, php-mbstring, and php-ncurses packages, respectively. Note that you will need to install these packages manually (if required) when upgrading from an earlier release.
=== Windows File Server ===
This section contains information related to Samba, software that makes it possible to share files between Linux and Windows systems.
samba
Browsing of Windows shares (also known as SMB browsing) fails on Fedora Core 4test1 systems that have the standard firewall configured. This is most easily noticed in the failure of Nautilus to display shares. The failure is due to the firewall disrupting the broadcast mode of SMB browsing, which is Samba's default setting. There are two workarounds:
* Configure a WINS server on the network, and set the "wins server" option in smb.conf to the address of the WINS server.
* Disable the firewall
Warning
Depending on your system and network configurations, disabling the firewall can greatly increase the chance of your system being attacked and compromised. Make sure you fully understand the risks before undertaking this step.
For additional information, refer to the following bug report:
[8]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
=== X Window System ===
This section contains information related to the X Window System implementation provided with Fedora Core.
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 Red Hat operating systems. In particular, the names of some files have changed:
X Server Binary:
* XFree86 X11: XFree86
* X.org X11: Xorg
X Server Configuration File:
* XFree86 X11: /etc/X11/XF86Config
* X.org X11: /etc/X11/xorg.conf
X Server Log File
* XFree86 X11: /var/log/XFree86.$DISPLAY.log
* 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:
- 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 like:
-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 like:
Luxi Sans-10
* Over time, fontconfig/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.
NOTE: An exception to the font subsystem usage outlined above is OpenOffice.org (which uses its own font rendering technology).
If you wish to add new fonts to your Fedora Core 4test1 system, you must be aware that the steps necessary depend on which font subsystem is to use the new fonts. For the core X font subsystem, you must:
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):
ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale
mkfontdir /usr/share/fonts/local/
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
(Where 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 = ""
}
widget_class " *" style "user-font"
(Where represents a font specification in the style used by traditional X applications, such as "-adobe-helvetica-medium-r-normal-- *-120- *- *- *- *- *- *".)
=== Miscellaneous Notes ===
This section contains information related to packages that do not fit in any of the proceeding categories.
compat-db
C++ and TCL bindings are no longer contained in the compat-db package. Applications requiring these bindings must be ported to the currently-shipping DB library.
nscd
The nscd name service cache daemon may now maintain a persistent cache across restarts or system reboots. Each database (user, group, and host, respectively) can be made selected to be persistent by setting the appropriate line in /etc/nscd.conf to "yes". Entries are not removed from the cache until they are proven to be no longer of interest. All entries whose time-to-live expires but are otherwise interesting are automatically reloaded, which helps in situations where the directory and name services become temporarily unavailable.
The nscd name service daemon is also able to communicate faster with client programs. This feature must be enabled explicitly by setting the "shared" entry for the appropriate database in /etc/nscd.conf to "yes".
udev
Fedora Core 4test1 has switched from a static /dev/ directory to one that is dynamically managed via udev. This allows device nodes to be created on demand as drivers are loaded.
For more information on udev, refer to the udev(8) man page and the following link:
[9]http://people.redhat.com/~harald/udev.html
Additional rules for udev should be placed in a separate file in the /etc/udev/rules.d/ directory.
Additional permission rules for udev should be placed in a separate file in the /etc/udev/permissions.d/ directory.
Systems upgraded to Fedora Core 4test1 using Anaconda will automatically be reconfigured to use udev. However (although NOT recommended) it is possible to perform a "live" upgrade to udev using the following steps:
1. Ensure that you are running a 2.6 kernel
2. Ensure that /sys/ is mounted
3. Install the initscripts RPM supplied with Fedora Core 4test1
4. Install the new udev RPM supplied with Fedora Core 4test1
5. Execute /sbin/start_udev
6. Install the new mkinitrd RPM supplied with Fedora Core 4test1
7. Perform one of the following steps:
. Install the new kernel RPM supplied with Fedora Core 4test1
OR:
. Re-run mkinitrd for your existing kernel(s)
Warning
Improperly performing these steps can result in a system configuration that will not boot properly.
== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
For an overview of orphaned packages, visit [:Extras/OrphanedPackages:this list].
This section contains lists of packages that fit into the following categories:
* Packages that have been added to Fedora Core 4test1
* Packages that have been moved out of Fedora Core 4test1
* Packages that have a changed version since Fedora Core 3
* Packages that have been deprecated, and may be removed from a future
release of Fedora Core
=== Packages Added ===
The following packages have been added to Fedora Core 4test1:
* ant-1.6.2-3jpp_2fc
* antlr-2.7.4-2jpp_1fc
* aqbanking-1.0.4beta-2
* aqhbci-1.0.2beta-2
* avalon-framework-4.1.4-2jpp_5fc
* avalon-logkit-1.2-2jpp_4fc
* bcel-5.1-1jpp_4fc
* classpath-inetlib-1.0-1jpp_1fc
* classpathx-jaf-1.0-2jpp_3fc
* classpathx-mail-1.0-3jpp_1fc
* compat-gcc-296-2.96-132.fc4
* compat-gcc-32-3.2.3-47.fc4
* compat-readline43-4.3-2
* cpufreq-utils-0.2-1.1.12
* cpuspeed-1.2.1-1.19
* cryptix-3.2.0-4jpp_1fc
* cryptix-asn1-20011119-4jpp_1fc
* cryptsetup-luks-0.993-1
* dcraw-0.0.20050227-1
* device-mapper-multipath-0.4.2-1.0
* dmidecode-2.6-1.13
* eclipse-3.1.0_fc-0.M5.12
* eclipse-bugzilla-0.1.0_fc-7
* eclipse-cdt-2.0.2_fc-3
* eclipse-changelog-2.0.1_fc-17
* eclipse-pydev-0.9.0_fc-4
* evince-0.1.9-1
* fonts-chinese-2.15-1
* fonts-indic-1.9-1
* fonts-japanese-0.20050222-2
* fonts-korean-1.0.11-2
* gjdoc-0.7.1-4
* gnome-doc-utils-0.1.2-2
* gnome-menus-2.9.90-4
* gnome-python2-extras-2.9.3-1
* gnu-crypto-2.0.1-1jpp_1fc
* gnu.getopt-1.0.9-4jpp_1fc
* gwenhywfar-1.7.2-2
* hardlink-1.0-1.11
* ipv6calc-0.48-3
* irqbalance-1.12-1.18
* jakarta-commons-beanutils-1.7.0-1jpp_1fc
* jakarta-commons-collections-3.1-1jpp_1fc
* jakarta-commons-daemon-1.0-2jpp_1fc
* jakarta-commons-dbcp-1.2.1-3jpp_1fc
* jakarta-commons-digester-1.6-2jpp_1fc
* jakarta-commons-el-1.0-2jpp_1fc
* jakarta-commons-fileupload-1.0-3jpp_1fc
* jakarta-commons-lang-2.0-2jpp_1fc
* jakarta-commons-launcher-0.9-3jpp_1fc
* jakarta-commons-logging-1.0.4-2jpp_1fc
* jakarta-commons-modeler-1.1-3jpp_1fc
* jakarta-commons-pool-1.2-2jpp_1fc
* jakarta-commons-validator-1.1.3-1jpp_1fc
* jakarta-taglibs-standard-1.1.1-4jpp_1fc
* java_cup-0.10-0.k.1jpp_2fc
* jdepend-2.6-2jpp_3fc
* jessie-1.0.0-1
* jlex-1.2.6-1jpp_2fc
* junit-3.8.1-3jpp_4fc
* kdeaccessibility-3.4.0-0.rc1.1
* ksh-20050202-1
* ldapjdk-4.17-1jpp_2fc
* libdbi-drivers-0.7.1-2
* libgconf-java-2.9.92-1
* libglade-java-2.9.92-1
* libgnome-java-2.9.92-1
* libgtk-java-2.6.0-3
* linux-atm-2.5.0-0.20050118.2
* lksctp-tools-1.0.2-5
* log4j-1.2.8-7jpp_3fc
* longrun-0.9-1.8
* lvm2-cluster-2.00.29-1.22.FC4
* mcelog-0.4-1.8
* microcode_ctl-1.11-1.21
* mx4j-2.1.0-1jpp_2fc
* mysqlclient10-3.23.58-5
* openhpi-1.9.2-3
* OpenIPMI-1.4.11-2
* openssl097a-0.9.7a-1
* oro-2.0.8-1jpp_2fc
* poppler-0.1.2-1
* puretls-0.9-0.b4.1jpp_2fc
* python-numeric-23.7-2
* python-sqlite-1.1.6-1
* python-twisted-1.3.0-4
* python-urlgrabber-2.9.6-1
* readahead-1.0-1.7
* regexp-1.3-1jpp_4fc
* rng-utils-2.0-1.5
* salinfo-0.5-1.4
* servletapi5-5.0.18-1jpp_3fc
* slib-3a1-2
* smartmontools-5.33-1.5
* sqlite-3.1.2-1
* struts11-1.1-1jpp_2fc
* system-config-lvm-0.9.18-1.1
* texi2html-1.76-2
* tomcat5-5.0.30-1jpp_2fc
* ufraw-0.2-2
* x86info-1.13-1.9
* xalan-j2-2.6.0-2jpp_1fc
* xen-2-20050308
* xerces-j2-2.6.2-4jpp_1fc
* xml-commons-1.0-0.b2.6jpp_5fc
* xml-commons-resolver-1.1-1jpp_4fc
=== Packages Moved Out Of Core ===
This is a new section to the release notes. This is based on a treediff of dist-fc3 and dist-fc4 on 14-MAR-2005. The following packages have been moved out of core from Fedora Core 4test1:
* abiword-2.0.12-3
* aiksaurus-1.2.1-2
* ash-0.3.8-20
* asp2php-0.76.18-3
* aspell-ia-0.50-1
* aumix-2.8-9
* balsa-2.2.4-1.FC3.1
* bluez-bluefw-1.0-6
* bonobo-1.0.22-9
* bzflag-1.10.6-2
* cdecl-2.5-30
* cdlabelgen-3.0.0-1
* cdp-0.33-32
* compat-gcc-8-3.3.4.2
* comsat-0.17-11
* cproto-4.7c-3
* cryptsetup-0.1-4
* dbh-1.0.18-5
* dbskkd-cdb-1.01-21
* ddskk-12.2.0-4
* dietlibc-0.27-4
* diskcheck-1.6-2
* dmalloc-5.3.0-3
* exim-4.43-1
* flim-1.14.7-1
* fonts-bengali-0.1-3
* fonts-ja-8.0-16
* freeciv-1.14.2-1
* FreeWnn-1.10pl020-5
* ftpcopy-0.6.2-7
* gcc4-4.0.0-0.8
* ggv-2.8.0-1
* giftrans-1.12.2-20
* gnome-vfs-1.0.5-21
* gnome-vfs-extras-0.2.0-9
* gnuchess-5.07-4
* gnumeric-1.2.13-6
* gpdf-2.8.0-5
* grip-3.2.0-3
* gv-3.5.8-29
* jed-0.99.16-6
* jisksp14-0.1-16
* jisksp16-1990-0.1-16
* kappa20-0.3-15
* kdetoys-3.3.0-1
* kernel-utils-2.4-13.1.39
* kinput2-v3.1-23
* knm_new-1.1-16
* koffice-1.3.3-1
* lapack-3.0-25
* lesstif-0.93.36-6
* libesmtp-1.0.3r1-2
* libgda-1.0.4-3
* libgnomedb-1.0.4-3
* libtool-libs13-1.3.5-10
* libxfce4mcs-4.0.6-1
* libxfce4util-4.0.6-1
* libxfcegui4-4.0.6-1
* Maelstrom-3.0.6-6
* MagicPoint-1.11b-1
* mew-3.3-4
* miniChinput-0.0.3-58
* nabi-0.14-3
* nautilus-media-0.8.1-3
* ncftp-3.1.8-2
* nedit-5.4-3
* octave-2.1.57-7
* Omni-0.9.1-7
* openhbci-0.9.17-1
* openssl096b-0.9.6b-19
* ots-0.4.2-2
* pan-0.14.2-8
* pccts-1.33mr33-11
* pdksh-5.2.14-30
* qmkbootdisk-1.0.2-3
* Regina-2.3-1
* routed-0.17-18
* skkinput-2.06.4-7
* sylpheed-0.9.12-1
* system-switch-im-0.1.2-3
* THE-3.1-2
* tora-1.3.14.1-2
* ttfonts-ja-1.2-36
* ttfonts-ko-1.0.11-32.2
* ttfonts-zh_CN-2.14-10
* ttfonts-zh_TW-2.11-28
* tuxracer-0.61-28
* w3m-el-1.4.3-2
* wl-2.10.1-4
* xboard-4.2.7-6
* xcin-2.5.3.pre3-24
* xemacs-21.4.15-9
* xemacs-sumo-20040818-2
* xfce4-iconbox-4.0.6-2
* xfce4-panel-4.0.6-1
* xfce4-systray-4.0.6-2
* xfce-mcs-manager-4.0.6-2
* xfce-mcs-plugins-4.0.6-2
* xfce-utils-4.0.6-1
* xfdesktop-4.0.6-2
* xffm-4.0.6-1
* xffm-icons-4.0.6-2
* xfprint-4.0.6-2
* xfwm4-4.0.6-1
* xfwm4-themes-4.0.6-2
* xloadimage-4.1-32
* xosview-1.8.2-1
* xsnow-1.42-15
* ytalk-3.1.2-1
=== Packages Changed Between Releases ===
This is a new section of the relnotes. It might not be useful, so could get nuked at any time. This shows the version change between packages in the release base for FC3 and FC4. This was done using a treediff tool against dist-fc3 and dist-fc4 on 14-MAR-2005.
* 4Suite-1.0-3 -> 4Suite-1.0-5
* a2ps-4.13b-41 -> a2ps-4.13b-45
* acl-2.2.23-5 -> acl-2.2.23-7
* adjtimex-1.13-13 -> adjtimex-1.13-16
* alchemist-1.0.34-1 -> alchemist-1.0.36-1
* alsa-lib-1.0.6-3 -> alsa-lib-1.0.8-4.devel
* alsa-utils-1.0.6-3 -> alsa-utils-1.0.8-3
* amanda-2.4.4p3-1 -> amanda-2.4.4p4-3
* anaconda-10.1.0.2-1 -> anaconda-10.2.0.28-1
* anacron-2.3-32 -> anacron-2.3-33
* apel-10.6-5 -> apel-10.6-6
* apmd-3.0.2-24 -> apmd-3.0.2-25
* apr-0.9.4-23 -> apr-0.9.6-2
* apr-util-0.9.4-17 -> apr-util-0.9.6-2
* arptables_jf-0.0.8-2 -> arptables_jf-0.0.8-4
* arts-1.3.0-4 -> arts-1.4.0-0.rc1.5
* aspell-0.50.5-3.fc3 -> aspell-0.50.5-6
* aspell-bg-0.50-5 -> aspell-bg-0.50-9
* aspell-pt-0.50-8 -> aspell-pt-0.50-9
* at-3.1.8-60 -> at-3.1.8-68_FC4
* atk-1.8.0-2 -> atk-1.9.1-1
* at-spi-1.6.0-3 -> at-spi-1.6.3-1
* attr-2.4.16-3 -> attr-2.4.16-4
* audit-0.5-1 -> audit-0.6.8-1
* authconfig-4.6.5-3.1 -> authconfig-4.6.11-1
* authd-1.4.2-8 -> authd-1.4.3-1.devel
* autoconf213-2.13-9 -> autoconf213-2.13-10
* autoconvert-0.3.7-15 -> autoconvert-0.3.7-16
* autofs-4.1.3-28 -> autofs-4.1.3-107
* automake17-1.7.9-5 -> automake17-1.7.9-6
* automake-1.9.2-3 -> automake-1.9.5-1
* autorun-3.14-1 -> autorun-3.15-2
* awesfx-0.4.3a-16 -> awesfx-0.5.0d-2
* basesystem-8.0-4 -> basesystem-8.0-5
* bash-3.0-17 -> bash-3.0-29
* bc-1.06-17.1 -> bc-1.06-18
* beecrypt-3.1.0-6 -> beecrypt-4.1.2-2
* bind-9.2.4-2 -> bind-9.3.1-1_FC4
* binutils-2.15.92.0.2-5 -> binutils-2.15.94.0.2-4
* bison-1.875c-2 -> bison-2.0-4
* bitstream-vera-fonts-1.10-4 -> bitstream-vera-fonts-1.10-5
* bluez-hcidump-1.11-1 -> bluez-hcidump-1.18-1
* bluez-libs-2.10-2 -> bluez-libs-2.15-1
* bluez-pin-0.23-3 -> bluez-pin-0.24-2
* bluez-utils-2.10-2 -> bluez-utils-2.15-4
* bogl-0.1.18-4 -> bogl-0.1.18-7
* boost-1.31.0-9 -> boost-1.32.0-3
* bootparamd-0.17-18 -> bootparamd-0.17-22.devel
* booty-0.44-1 -> booty-0.50-1
* bridge-utils-1.0.4-4 -> bridge-utils-1.0.4-6
* brltty-3.2-4 -> brltty-3.2-9
* bug-buddy-2.8.0-3 -> bug-buddy-2.9.92-1
* busybox-1.00.rc1-5 -> busybox-1.00-4
* byacc-1.9-28 -> byacc-1.9-29
* bzip2-1.0.2-13 -> bzip2-1.0.2-15
* cadaver-0.22.1-3 -> cadaver-0.22.2-2
* Canna-3.7p3-6 -> Canna-3.7p3-13
* cdicconf-0.2-9 -> cdicconf-0.2-10
* cdparanoia-alpha9.8-24 -> cdparanoia-alpha9.8-24.2
* cdrdao-1.1.9-6 -> cdrdao-1.1.9-9
* cdrtools-2.01.1-5 -> cdrtools-2.01.1-8
* checkpolicy-1.17.5-1 -> checkpolicy-1.22-1
* chkconfig-1.3.11.1-1 -> chkconfig-1.3.18-1
* chkfontpath-1.10.0-2 -> chkfontpath-1.10.0-4
* ckermit-8.0.209-9 -> ckermit-8.0.209-11
* compat-db-4.1.25-6 -> compat-db-4.2.52-2
* compat-slang-1.4.5-8 -> compat-slang-1.4.5-10
* control-center-2.8.0-12 -> control-center-2.9.91-1
* coreutils-5.2.1-31 -> coreutils-5.2.1-41
* cpio-2.5-7 -> cpio-2.6-4
* cracklib-2.7-28 -> cracklib-2.7-30
* crash-3.8-5 -> crash-3.10-13
* createrepo-0.4.1-1 -> createrepo-0.4.2-2
* crypto-utils-2.1-4 -> crypto-utils-2.1-6
* cscope-15.5-3 -> cscope-15.5-11
* ctags-5.5.4-1 -> ctags-5.5.4-3
* cups-1.1.22-0.rc1.8 -> cups-1.1.23-14
* curl-7.12.1-1 -> curl-7.13.1-1
* cvs-1.11.17-3 -> cvs-1.11.19-6
* cyrus-imapd-2.2.6-2.FC3.6 -> cyrus-imapd-2.2.10-11.4.fc4
* cyrus-sasl-2.1.19-3 -> cyrus-sasl-2.1.20-4
* dasher-3.2.11-4 -> dasher-3.2.15-1
* db4-4.2.52-6 -> db4-4.3.27-2
* dbus-0.22-10 -> dbus-0.31-2
* ddd-3.3.9-1 -> ddd-3.3.10-2
* dejagnu-1.4.4-2 -> dejagnu-1.4.4-4
* desktop-backgrounds-2.0-26.2 -> desktop-backgrounds-2.0-27
* desktop-file-utils-0.9-2 -> desktop-file-utils-0.10-1
* desktop-printing-0.17-3 -> desktop-printing-0.18-6
* dev86-0.16.16-1 -> dev86-0.16.17-1
* devhelp-0.9.2-2 -> devhelp-0.9.3-4
* device-mapper-1.00.19-2 -> device-mapper-1.01.00-1.1
* dhcp-3.0.1-11 -> dhcp-3.0.2-3
* dhcpv6-0.10-8 -> dhcpv6-0.10-11_FC4
* dia-0.94-5 -> dia-0.94-8
* dialog-1.0.20040731-3 -> dialog-1.0.20050206-1
* dictd-1.9.7-4 -> dictd-1.9.7-7
* diffstat-1.31-5 -> diffstat-1.38-2
* diffutils-2.8.1-12 -> diffutils-2.8.1-14
* diskdumputils-0.6.1-1 -> diskdumputils-1.0.1-6
* distcache-1.4.5-6 -> distcache-1.4.5-7
* dmraid-1.0.0-rc5 -> dmraid-1.0.0.rc6-2_FC4
* docbook-dtds-1.0-25 -> docbook-dtds-1.0-26
* docbook-style-dsssl-1.78-4 -> docbook-style-dsssl-1.79-1
* docbook-style-xsl-1.65.1-2 -> docbook-style-xsl-1.68.1-1
* dos2unix-3.1-21 -> dos2unix-3.1-23
* dosfstools-2.8-15 -> dosfstools-2.10-1
* dovecot-0.99.11-1.FC3.4 -> dovecot-0.99.14-2.fc4
* doxygen-1.3.9.1-1 -> doxygen-1.4.1-2
* dump-0.4b37-1 -> dump-0.4b39-3
* dvd+rw-tools-5.21.4.10.8-2 -> dvd+rw-tools-5.21.4.10.8-6
* dvgrab-1.6-1 -> dvgrab-1.7-2
* e2fsprogs-1.35-11.2 -> e2fsprogs-1.36-1.3
* ecj-2.1.3-5 -> ecj-3.1-0.M4.9
* ed-0.2-36 -> ed-0.2-38
* eel2-2.8.1-2 -> eel2-2.9.91-2
* efax-0.9-22 -> efax-0.9-24
* eject-2.0.13-10 -> eject-2.0.13-14
* ElectricFence-2.2.2-19 -> ElectricFence-2.2.2-20
* elfutils-0.96-1 -> elfutils-0.101-2
* elilo-3.4-10 -> elilo-3.4-11
* elinks-0.9.2-2 -> elinks-0.10.2-2
* emacs-21.3-17 -> emacs-21.3-25
* emacspeak-17.0-7 -> emacspeak-21.0-2
* enscript-1.6.1-28 -> enscript-1.6.1-31
* eog-2.8.0-3 -> eog-2.9.0-2
* epic-1.0.1-18 -> epic-1.0.1-19
* epiphany-1.4.4-4 -> epiphany-1.5.8-3
* eruby-1.0.5-3 -> eruby-1.0.5-4
* esound-0.2.35-2 -> esound-0.2.35-4
* ethereal-0.10.6-3 -> ethereal-0.10.10-1
* ethtool-1.8-4 -> ethtool-3-1
* evolution-2.0.2-3 -> evolution-2.2.0-5
* evolution-connector-2.0.2-1 -> evolution-connector-2.2.0-1
* evolution-data-server-1.0.2-3 -> evolution-data-server-1.2.0-2
* evolution-webcal-1.0.10-1 -> evolution-webcal-2.2.0-1
* expat-1.95.7-4 -> expat-1.95.8-6
* expect-5.42.1-1 -> expect-5.43.0-1
* fbset-2.1-17 -> fbset-2.1-20
* fedora-release-3-9 -> fedora-release-3.90-2
* festival-1.4.2-25 -> festival-1.95-1
* file-4.10-2 -> file-4.13-3
* file-roller-2.8.1-1 -> file-roller-2.9.92-1
* filesystem-2.3.0-1 -> filesystem-2.3.1-1
* findutils-4.1.20-7 -> findutils-4.2.18-3
* finger-0.17-26 -> finger-0.17-28
* firefox-0.10.1-1.0PR1.20 -> firefox-1.0.1-5
* firstboot-1.3.33-1 -> firstboot-1.3.39-3
* flac-1.1.0-7 -> flac-1.1.0-9
* fontconfig-2.2.3-5 -> fontconfig-2.2.3-12
* fonts-ISO8859-2-1.0-13 -> fonts-ISO8859-2-1.0-14
* fonts-xorg-6.8.1-1 -> fonts-xorg-6.8.1.1-1
* foomatic-3.0.2-3 -> foomatic-3.0.2-18
* freeglut-2.2.0-14 -> freeglut-2.2.0-16
* freeradius-1.0.1-1 -> freeradius-1.0.1-3
* freetype-2.1.9-1 -> freetype-2.1.9-2
* fribidi-0.10.4-6 -> fribidi-0.10.4-8
* fsh-1.2-5 -> fsh-1.2-6
* ftp-0.17-22 -> ftp-0.17-25
* gail-1.8.0-2 -> gail-1.8.2-2
* gaim-1.0.1-3 -> gaim-1.1.4-4
* gal-0.24-4 -> gal-0.24-6
* gamin-0.0.15-1 -> gamin-0.0.25-4
* gawk-3.1.3-9 -> gawk-3.1.4-5
* gcc-3.4.2-6.fc3 -> gcc-4.0.0-0.33
* GConf-1.0.9-15 -> GConf-1.0.9-16
* GConf2-2.8.1-1 -> GConf2-2.9.91-2
* gconf-editor-2.8.0-2 -> gconf-editor-2.9.91-2
* gd-2.0.28-1 -> gd-2.0.32-3
* gdb-6.1post-1.20040607.41 -> gdb-6.3.0.0-0.29
* gdk-pixbuf-0.22.0-15.0 -> gdk-pixbuf-0.22.0-17
* gdm-2.6.0.5-6 -> gdm-2.6.0.7-5
* gedit-2.8.1-1 -> gedit-2.9.7-1
* genromfs-0.5.1-1 -> genromfs-0.5.1-3
* gettext-0.14.1-12 -> gettext-0.14.1-14
* gftp-2.0.17-3 -> gftp-2.0.18-2
* ghostscript-7.07-33 -> ghostscript-7.07-40
* gimp-2.0.5-5 -> gimp-2.2.4-3
* gimp-data-extras-1.2.0-12 -> gimp-data-extras-2.0.1-1
* gimp-gap-2.0.2-2 -> gimp-gap-2.0.2-4
* gimp-help-2-0.1.0.3 -> gimp-help-2-0.1.0.7.1
* gimp-print-4.2.7-2 -> gimp-print-4.2.7-5
* gkrellm-2.2.2-2 -> gkrellm-2.2.4-3
* glade2-2.6.0-1 -> glade2-2.9.0-2
* glib-1.2.10-15 -> glib-1.2.10-16
* glib2-2.4.7-1 -> glib2-2.6.3-4
* glibc-2.3.3-74 -> glibc-2.3.4-14
* glibc-kernheaders-2.4-9.1.87 -> glibc-kernheaders-2.4-9.1.90
* gmp-4.1.4-3 -> gmp-4.1.4-4
* gnome-applets-2.8.0-5 -> gnome-applets-2.9.6-2
* gnome-audio-2.0.0-1 -> gnome-audio-2.0.0-2
* gnome-bluetooth-0.5.1-5 -> gnome-bluetooth-0.5.1-10
* gnome-desktop-2.8.0-3 -> gnome-desktop-2.9.91-3
* gnome-games-2.8.0-4 -> gnome-games-2.9.6-1
* gnome-icon-theme-2.8.0-1 -> gnome-icon-theme-2.9.91-2
* gnome-keyring-0.4.0-1 -> gnome-keyring-0.4.1-2
* gnome-keyring-manager-0.0.3-1 -> gnome-keyring-manager-0.0.4-2
* gnome-libs-1.4.1.2.90-44 -> gnome-libs-1.4.1.2.90-45
* gnome-mag-0.11.7-1 -> gnome-mag-0.12.0-1
* gnome-media-2.8.0-3 -> gnome-media-2.9.90-1
* gnomemeeting-1.0.2-8 -> gnomemeeting-1.2.0-5
* gnome-mime-data-2.4.1-5 -> gnome-mime-data-2.4.2-1
* gnome-netstatus-2.8.0-3 -> gnome-netstatus-2.9.4-2
* gnome-nettool-0.99.3-2 -> gnome-nettool-0.99.3-3
* gnome-panel-2.8.1-3 -> gnome-panel-2.10.0-1
* gnome-pilot-2.0.12-4 -> gnome-pilot-2.0.12-5
* gnome-print-0.37-10 -> gnome-print-0.37-11
* gnome-python2-2.6.0-3 -> gnome-python2-2.10.0-1
* gnome-session-2.8.0-4 -> gnome-session-2.9.4-1
* gnome-speech-0.3.5-4 -> gnome-speech-0.3.6-1
* gnome-spell-1.0.5-6 -> gnome-spell-1.0.5-8
* gnome-system-monitor-2.7.0-2 -> gnome-system-monitor-2.10.0-1
* gnome-terminal-2.7.3-1 -> gnome-terminal-2.9.2-1
* gnome-themes-2.8.0-1 -> gnome-themes-2.10.0-1
* gnome-user-docs-2.8.0.1-1 -> gnome-user-docs-2.8.1-2
* gnome-utils-2.8.0-5 -> gnome-utils-2.9.92-3
* gnome-vfs2-2.8.2-8 -> gnome-vfs2-2.9.91-8
* gnome-volume-manager-1.1.0-5 -> gnome-volume-manager-1.1.3-3
* gnopernicus-0.9.12-1 -> gnopernicus-0.10.4-1
* gnucash-1.8.9-2 -> gnucash-1.8.11-2
* gnu-efi-3.0a-6 -> gnu-efi-3.0a-7
* gnupg-1.2.6-1 -> gnupg-1.4.0-2
* gnuplot-4.0.0-4 -> gnuplot-4.0.0-7
* gnutls-1.0.20-3 -> gnutls-1.0.20-6
* gob2-2.0.6-5 -> gob2-2.0.11-3
* gok-0.11.8-1 -> gok-1.0.2-1
* gperf-3.0.1-4 -> gperf-3.0.1-6
* gphoto2-2.1.4-7 -> gphoto2-2.1.5-5
* gpm-1.20.1-66 -> gpm-1.20.1-71
* grep-2.5.1-31 -> grep-2.5.1-48
* groff-1.18.1.1-3 -> groff-1.18.1.1-5
* grub-0.95-3 -> grub-0.95-11
* gsl-1.5-1 -> gsl-1.6-2
* gstreamer-0.8.7-3 -> gstreamer-0.8.8-2
* gstreamer-plugins-0.8.5-1 -> gstreamer-plugins-0.8.7-3
* gthumb-2.4.2-5 -> gthumb-2.6.3-2
* gtk2-2.4.13-9 -> gtk2-2.6.4-2
* gtk2-engines-2.2.0-6 -> gtk2-engines-2.6.2-1
* gtk-doc-1.2-2 -> gtk-doc-1.3-1
* gtk-engines-0.12-5 -> gtk-engines-0.12-6
* gtkhtml-1.1.9-10 -> gtkhtml-1.1.9-11
* gtkhtml2-2.6.2-1 -> gtkhtml2-2.6.3-1
* gtkhtml3-3.3.2-3 -> gtkhtml3-3.6.0-2
* gtksourceview-1.1.0-3 -> gtksourceview-1.1.92-1
* guile-1.6.4-14 -> guile-1.6.7-2
* Guppi-0.40.3-21 -> Guppi-0.40.3-23
* g-wrap-1.3.4-7 -> g-wrap-1.3.4-8
* gzip-1.3.3-13 -> gzip-1.3.3-16
* hal-0.4.0-10 -> hal-0.5.0.cvs20050310-1
* hal-cups-utils-0.5.2-8 -> hal-cups-utils-0.5.3-2
* hdparm-5.7-2 -> hdparm-5.9-1
* HelixPlayer-1.0.1.gold-6 -> HelixPlayer-1.0.3-4
* hexedit-1.2.10-1 -> hexedit-1.2.10-4
* hfsutils-3.2.6-4 -> hfsutils-3.2.6-7
* hicolor-icon-theme-0.3-3 -> hicolor-icon-theme-0.7-1
* hotplug-2004_04_01-6 -> hotplug-2004_09_23-3
* howl-0.9.6-6 -> howl-0.9.8-3
* hpijs-1.6-2 -> hpijs-1.7.1-3
* hpoj-0.91-9 -> hpoj-0.91-13
* htdig-3.2.0b6-3 -> htdig-3.2.0b6-5
* httpd-2.0.52-3 -> httpd-2.0.53-5
* hwbrowser-0.15-5 -> hwbrowser-0.20-1
* hwdata-0.145-1 -> hwdata-0.152-1
* iiimf-le-chinput-0.3-11 -> iiimf-le-chinput-0.3-13
* iiimf-le-xcin-0.1.7-9 -> iiimf-le-xcin-0.1.7-11.1
* ImageMagick-6.0.7.1-4 -> ImageMagick-6.0.7.1-7
* im-sdk-12.1-4 -> im-sdk-12.1.1-7.svn2208
* initscripts-7.93.2-1 -> initscripts-8.05-1
* inn-2.3.5-11.1 -> inn-2.4.2-2
* intltool-0.31.2-1 -> intltool-0.33-2
* iproute-2.6.9-3 -> iproute-2.6.10-2
* iprutils-2.0.13-1 -> iprutils-2.0.13.5-1
* ipsec-tools-0.3.3-1 -> ipsec-tools-0.5-3
* iptables-1.2.11-3.1 -> iptables-1.3.0-1
* iptraf-2.7.0-11 -> iptraf-2.7.0-13
* iptstate-1.3-4 -> iptstate-1.3-5
* iputils-20020927-16 -> iputils-20020927-20
* irda-utils-0.9.16-3 -> irda-utils-0.9.16-7
* isdn4k-utils-3.2-18.p1.1 -> isdn4k-utils-3.2-26
* isicom-3.05-16 -> isicom-3.05-18
* jadetex-3.12-11 -> jadetex-3.12-13
* java-1.4.2-gcj-compat-1.4.2.0-11jpp -> java-1.4.2-gcj-compat-1.4.2.0-40jpp_7rh
* joe-3.1-6 -> joe-3.1-8
* joystick-1.2.15-18 -> joystick-1.2.15-20
* jpackage-utils-1.5.38-1jpp_3rh -> jpackage-utils-1.6.2-1jpp_3rh
* jpilot-0.99.7-2 -> jpilot-0.99.7-6
* jwhois-3.2.2-6 -> jwhois-3.2.2-11
* k3b-0.11.14-2 -> k3b-0.11.17-2
* kakasi-2.3.4-17 -> kakasi-2.3.4-18
* kbd-1.12-2 -> kbd-1.12-8
* kcc-2.3-22 -> kcc-2.3-23
* kdbg-1.2.9-6 -> kdbg-1.2.10-2
* kdeaddons-3.3.0-2 -> kdeaddons-3.4.0-0.rc1.2
* kdeadmin-3.3.0-1 -> kdeadmin-3.4.0-0.rc1.2
* kdeartwork-3.3.0-1 -> kdeartwork-3.4.0-0.rc1.2
* kdebase-3.3.0-8 -> kdebase-3.4.0-0.rc1.4
* kdebindings-3.3.0-3 -> kdebindings-3.4.0-0.rc1.2
* kdeedu-3.3.0-1 -> kdeedu-3.4.0-0.rc1.2
* kdegames-3.3.0-2 -> kdegames-3.4.0-0.rc1.2
* kdegraphics-3.3.0-3 -> kdegraphics-3.4.0-0.rc1.2
* kde-i18n-3.3.0-2 -> kde-i18n-3.4.0-0.rc1.2
* kdelibs-3.3.0-5 -> kdelibs-3.4.0-0.rc1.5
* kdemultimedia-3.3.0-2 -> kdemultimedia-3.4.0-0.rc1.2
* kdenetwork-3.3.0-5 -> kdenetwork-3.4.0-0.rc1.2
* kdepim-3.3.0-2 -> kdepim-3.4.0-0.rc1.4
* kdesdk-3.3.0-1 -> kdesdk-3.4.0-0.rc1.2
* kdeutils-3.3.0-2 -> kdeutils-3.4.0-0.rc1.2
* kdevelop-3.1.0-2 -> kdevelop-3.2.0-0.rc1.2
* kdewebdev-3.3.0-1 -> kdewebdev-3.4.0-0.rc1.2
* kernel-2.6.9-1.667 -> kernel-2.6.11-1.1177_FC4
* krb5-1.3.4-7 -> krb5-1.4-1
* krb5-auth-dialog-0.2-1 -> krb5-auth-dialog-0.2-2
* kudzu-1.1.95-1 -> kudzu-1.1.111-1
* lam-7.0.6-3 -> lam-7.1.1-3
* less-382-4 -> less-382-7
* lftp-3.0.6-3 -> lftp-3.1.0-1
* lha-1.14i-17 -> lha-1.14i-19
* libaio-0.3.102-1 -> libaio-0.3.103-4
* libao-0.8.5-2 -> libao-0.8.5-3
* libart_lgpl-2.3.16-3 -> libart_lgpl-2.3.17-2
* libavc1394-0.4.1-3 -> libavc1394-0.4.1-7
* libbonobo-2.8.0-2 -> libbonobo-2.8.1-1
* libbonoboui-2.8.0.99cvs20040929-2 -> libbonoboui-2.8.1-2
* libbtctl-0.4.1-3 -> libbtctl-0.4.1-5
* libcap-1.10-20 -> libcap-1.10-22
* libc-client-2002e-8 -> libc-client-2002e-9
* libcroco-0.6.0-4 -> libcroco-0.6.0-5
* libdbi-0.6.5-9 -> libdbi-0.7.2-2
* libdv-0.103-1 -> libdv-0.103-3
* libexif-0.5.12-3 -> libexif-0.5.12-7
* libgail-gnome-1.1.0-1 -> libgail-gnome-1.1.0-3
* libgal2-2.2.3-3 -> libgal2-2.4.0-1
* libghttp-1.0.9-10 -> libghttp-1.0.9-11
* libglade-0.17-15 -> libglade-0.17-16
* libglade2-2.4.0-5 -> libglade2-2.5.1-2
* libgnome-2.8.0-2 -> libgnome-2.9.1-1
* libgnomecanvas-2.8.0-1 -> libgnomecanvas-2.10.0-1
* libgnomecups-0.1.12-5 -> libgnomecups-0.1.14-3
* libgnomeprint22-2.8.0-2 -> libgnomeprint22-2.8.2-2
* libgnomeprintui22-2.8.0-1 -> libgnomeprintui22-2.8.2-2
* libgnomeui-2.8.0-1 -> libgnomeui-2.9.1-1
* libgpg-error-1.0-1 -> libgpg-error-1.0-2
* libgsf-1.10.1-1 -> libgsf-1.11.1-2
* libgtop2-2.8.0-1 -> libgtop2-2.9.91-2
* libIDL-0.8.4-1 -> libIDL-0.8.5-2
* libidn-0.5.6-1 -> libidn-0.5.13-2
* libieee1284-0.2.8-4 -> libieee1284-0.2.9-2
* libjpeg-6b-33 -> libjpeg-6b-34
* libmng-1.0.8-1 -> libmng-1.0.9-1
* libmusicbrainz-2.0.2-11 -> libmusicbrainz-2.0.2-14
* libofx-0.6.6-2 -> libofx-0.7.0-2
* libogg-1.1.2-1 -> libogg-1.1.2-2
* libpfm-3.0-2 -> libpfm-3.0-3
* libpng10-1.0.16-1 -> libpng10-1.0.18-2
* libpng-1.2.7-1 -> libpng-1.2.8-2
* libraw1394-0.10.1-3 -> libraw1394-1.1.0-2
* librsvg2-2.8.1-1 -> librsvg2-2.9.5-2
* libselinux-1.17.14-1 -> libselinux-1.22-1
* libsepol-1.1.1-2 -> libsepol-1.4-1
* libsilc-0.9.12-7 -> libsilc-0.9.12-8
* libsoup-2.2.1-1 -> libsoup-2.2.2-3
* libtabe-0.2.6-9 -> libtabe-0.2.6-12
* libtheora-1.0alpha3-5 -> libtheora-1.0alpha4-2
* libtiff-3.6.1-7 -> libtiff-3.7.1-5
* libtool-1.5.6-4 -> libtool-1.5.14.multilib2-5
* libungif-4.1.3-1 -> libungif-4.1.3-3
* libunwind-0.97-3 -> libunwind-0.98.2-3
* libusb-0.1.8-3 -> libusb-0.1.10a-1
* libuser-0.52.5-1 -> libuser-0.53.3-1
* libvorbis-1.1.0-1 -> libvorbis-1.1.0-2
* libwmf-0.2.8.3-5 -> libwmf-0.2.8.3-8
* libwnck-2.8.1-1 -> libwnck-2.10.0-1
* libwpd-0.7.2-1 -> libwpd-0.8.0-2
* libwvstreams-3.75.0-2 -> libwvstreams-3.75.0-5
* libxklavier-1.02-3 -> libxklavier-1.14-1
* libxml-1.8.17-11 -> libxml-1.8.17-13
* libxml2-2.6.14-2 -> libxml2-2.6.18-2
* libxslt-1.1.11-1 -> libxslt-1.1.13-2
* lilo-21.4.4-26 -> lilo-21.4.4-27
* linuxdoc-tools-0.9.20-14 -> linuxdoc-tools-0.9.21-5
* linuxwacom-0.6.4-6 -> linuxwacom-0.6.6-1
* lm_sensors-2.8.7-2 -> lm_sensors-2.8.8-5
* lockdev-1.0.1-3 -> lockdev-1.0.1-7
* logrotate-3.7.1-2 -> logrotate-3.7.1-7
* logwatch-5.2.2-1 -> logwatch-5.2.2-3
* lrzsz-0.12.20-19 -> lrzsz-0.12.20-21
* lslk-1.29-12 -> lslk-1.29-15
* lsof-4.72-1 -> lsof-4.74-5
* ltrace-0.3.35-1 -> ltrace-0.3.36-3
* lv-4.51-3.1 -> lv-4.51-4
* lvm2-2.00.25-1.01 -> lvm2-2.01.07-1.3
* lynx-2.8.5-18 -> lynx-2.8.5-22
* m2crypto-0.09-6 -> m2crypto-0.13-1
* m4-1.4.1-16 -> m4-1.4.2-3
* macutils-2.0b3-29 -> macutils-2.0b3-32
* mailcap-2.1.17-1 -> mailcap-2.1.19-1
* mailman-2.1.5-26 -> mailman-2.1.5-35.fc4
* mailx-8.1.1-33 -> mailx-8.1.1-44
* make-3.80-5 -> make-3.80-7
* MAKEDEV-3.11-1 -> MAKEDEV-3.16-3
* man-1.5m2-9 -> man-1.5p-1
* man-pages-1.67-3 -> man-pages-1.67-6
* man-pages-ja-20040915-1 -> man-pages-ja-20050215-1
* man-pages-ko-1.48-14 -> man-pages-ko-1.48-15
* man-pages-pl-0.23-2 -> man-pages-pl-0.23-4
* man-pages-ru-0.7-8 -> man-pages-ru-0.97-1
* mc-4.6.1-0.8 -> mc-4.6.1a-0.4
* mdadm-1.6.0-2 -> mdadm-1.9.0-1
* memtest86+-1.26-2 -> memtest86+-1.51-1
* metacity-2.8.6-2 -> metacity-2.9.21-1
* mgetty-1.1.31-2 -> mgetty-1.1.31-3
* mikmod-3.1.6-30 -> mikmod-3.1.6-34
* mingetty-1.07-3 -> mingetty-1.07-5
* minicom-2.00.0-19 -> minicom-2.00.0-21
* mkbootdisk-1.5.2-1 -> mkbootdisk-1.5.2-4
* mkinitrd-4.1.18-2 -> mkinitrd-4.2.1-1
* mktemp-1.5-10 -> mktemp-1.5-23
* mod_auth_kerb-5.0-1 -> mod_auth_kerb-5.0-3
* mod_auth_mysql-20030510-5 -> mod_auth_mysql-2.6.1-4
* mod_auth_pgsql-2.0.1-6 -> mod_auth_pgsql-2.0.1-7
* mod_authz_ldap-0.26-2 -> mod_authz_ldap-0.26-3
* mod_perl-1.99_16-3 -> mod_perl-1.99_17-2
* mod_python-3.1.3-5 -> mod_python-3.1.4-2
* module-init-tools-3.1-0.pre5.3 -> module-init-tools-3.1-2
* mozilla-1.7.3-17 -> mozilla-1.7.6-0.cvs.20050313
* mozplugger-1.6.2-1 -> mozplugger-1.7.1-3
* mpage-2.5.4-2 -> mpage-2.5.4-5
* mrtg-2.10.15-1 -> mrtg-2.11.1-3
* mtools-3.9.9-9 -> mtools-3.9.9-11
* mtr-0.54-10 -> mtr-0.69-3
* mt-st-0.8-1 -> mt-st-0.8-4
* mtx-1.2.18-5 -> mtx-1.2.18-8
* mutt-1.4.1-10 -> mutt-1.4.2.1-2
* mx-2.0.5-3 -> mx-2.0.6-1
* MyODBC-2.50.39-19 -> MyODBC-2.50.39-24
* mysql-3.23.58-13 -> mysql-4.1.10a-1
* MySQL-python-0.9.2-4 -> MySQL-python-1.0.0-3
* namazu-2.0.13-3 -> namazu-2.0.14-1
* nano-1.2.4-1 -> nano-1.3.5-0.20050302
* nautilus-2.8.1-4 -> nautilus-2.9.91-2
* nautilus-cd-burner-2.8.3-6 -> nautilus-cd-burner-2.10.0-1
* nc-1.10-22 -> nc-1.10-25
* ncompress-4.2.4-40 -> ncompress-4.2.4-41
* ncpfs-2.2.4-4 -> ncpfs-2.2.4-5
* ncurses-5.4-13 -> ncurses-5.4-16
* neon-0.24.7-4 -> neon-0.24.7-6
* netatalk-1.6.4-3 -> netatalk-2.0.2-2
* netdump-0.7.0-1 -> netdump-0.7.7-5
* netpbm-10.25-2 -> netpbm-10.26.4-3
* net-snmp-5.1.2-11 -> net-snmp-5.2.1-5
* net-tools-1.60-37 -> net-tools-1.60-48
* NetworkManager-0.3.1-3 -> NetworkManager-0.4-1.cvs20050307.3.0
* newt-0.51.6-5 -> newt-0.51.6-7
* newt-perl-1.08-7 -> newt-perl-1.08-8
* nfs-utils-1.0.6-39 -> nfs-utils-1.0.7-1
* nkf-2.04-3 -> nkf-2.04-4
* nmap-3.70-1 -> nmap-3.81-1
* nss_db-2.2-29 -> nss_db-2.2-30
* nss_ldap-220-3 -> nss_ldap-234-1
* ntp-4.2.0.a.20040617-4 -> ntp-4.2.0.a.20040617-7
* numactl-0.6.4-1.9 -> numactl-0.6.4-1.18
* nut-2.0.0-5 -> nut-2.0.1-1
* nvi-m17n-1.79-20011024.20 -> nvi-m17n-1.79-20040401.22
* oaf-0.6.10-11 -> oaf-0.6.10-12
* open-1.4-21 -> open-1.4-24
* openCryptoki-2.1.5-8 -> openCryptoki-2.1.5-9
* openh323-1.13.4-7 -> openh323-1.15.2-2
* openjade-1.3.2-14 -> openjade-1.3.2-16
* openldap-2.2.13-2 -> openldap-2.2.23-4
* openmotif21-2.1.30-11 -> openmotif21-2.1.30-13.1
* openmotif-2.2.3-6 -> openmotif-2.2.3-9
* openobex-1.0.1-1 -> openobex-1.0.1-3
* openobex-apps-1.0.0-6 -> openobex-apps-1.0.0-8
* openoffice.org-1.1.2-10 -> openoffice.org-1.9.83-1
* openssh-3.9p1-7 -> openssh-3.9p1-12
* openssl-0.9.7a-40 -> openssl-0.9.7e-3
* openswan-2.1.5-2 -> openswan-2.3.0-5
* oprofile-0.8.1-11 -> oprofile-0.8.1-13
* ORBit-0.5.17-14 -> ORBit-0.5.17-15
* ORBit2-2.12.0-3 -> ORBit2-2.12.1-2
* pam-0.77-65 -> pam-0.78-7
* pam_ccreds-1-3 -> pam_ccreds-1-4
* pam_krb5-2.1.2-1 -> pam_krb5-2.1.4-1
* pango-1.6.0-7 -> pango-1.8.1-2
* parted-1.6.15-5 -> parted-1.6.21-3
* passivetex-1.25-3 -> passivetex-1.25-5
* passwd-0.68-10 -> passwd-0.69-2
* patch-2.5.4-20 -> patch-2.5.4-22
* patchutils-0.2.30-1 -> patchutils-0.2.30-4
* pax-3.0-9 -> pax-3.0-10
* pciutils-2.1.99.test8-3 -> pciutils-2.1.99.test8-8
* pcmcia-cs-3.2.7-1.14 -> pcmcia-cs-3.2.8-4.12
* pcre-4.5-3 -> pcre-5.0-4
* perl-5.8.5-9 -> perl-5.8.6-4
* perl-Crypt-SSLeay-0.51-5 -> perl-Crypt-SSLeay-0.51-6
* perl-Date-Calc-5.3-9 -> perl-Date-Calc-5.3-10
* perl-DBD-MySQL-2.9003-5 -> perl-DBD-MySQL-2.9004-4
* perl-HTML-Parser-3.35-6 -> perl-HTML-Parser-3.35-7
* perl-libwww-perl-5.79-5 -> perl-libwww-perl-5.79-6
* perl-PDL-2.4.1-5 -> perl-PDL-2.4.1-9
* perl-RPM2-0.66-7 -> perl-RPM2-0.66-8
* perl-Text-Kakasi-1.05-11 -> perl-Text-Kakasi-1.05-12
* php-4.3.9-3 -> php-5.0.3-3
* pilot-link-0.11.8-8 -> pilot-link-0.12.0-0.pre2.0
* pinfo-0.6.8-7 -> pinfo-0.6.8-10
* pkgconfig-0.15.0-3 -> pkgconfig-0.15.0-5
* planner-0.12.1-1 -> planner-0.12.1-4
* pnm2ppa-1.04-11 -> pnm2ppa-1.04-12
* policycoreutils-1.17.6-2 -> policycoreutils-1.22-2
* postfix-2.1.5-2.2 -> postfix-2.1.5-5.1
* postgresql-7.4.6-1.FC3.1 -> postgresql-8.0.1-5
* postgresql-odbc-7.3-8 -> postgresql-odbc-08.00.0100-1
* ppp-2.4.2-6.4.FC3 -> ppp-2.4.2-7
* prctl-1.4-3 -> prctl-1.4-5
* prelink-0.3.2-11 -> prelink-0.3.4-2
* privoxy-3.0.3-5 -> privoxy-3.0.3-7
* procinfo-18-13 -> procinfo-18-15
* procmail-3.22-14 -> procmail-3.22-15
* procps-3.2.3-5 -> procps-3.2.5-2
* psacct-6.3.2-31 -> psacct-6.3.2-37
* psmisc-21.4-4 -> psmisc-21.5-4
* psutils-1.17-23 -> psutils-1.17-24
* pump-0.8.21-1 -> pump-0.8.21-3
* pvm-3.4.4-21 -> pvm-3.4.5-3_FC4
* pwlib-1.6.5-11 -> pwlib-1.8.3-1
* pychecker-0.8.14-1 -> pychecker-0.8.14-3
* pydict-0.3.0-7 -> pydict-0.3.0-8
* pygtk2-2.4.0-1 -> pygtk2-2.6.0-2
* pyOpenSSL-0.6-1.p23 -> pyOpenSSL-0.6-1.p23.1
* pyorbit-2.0.1-1 -> pyorbit-2.0.1-3
* pyparted-1.6.8-2 -> pyparted-1.6.9-2
* PyQt-3.13-1 -> PyQt-3.14-1
* Pyrex-0.9.2.1-2 -> Pyrex-0.9.2.1-3
* python-2.3.4-11 -> python-2.4-4
* python-ldap-2.0.1-2 -> python-ldap-2.0.6-1
* pyxf86config-0.3.19-1 -> pyxf86config-0.3.19-2
* PyXML-0.8.3-6 -> PyXML-0.8.4-3
* qt-3.3.3-8 -> qt-3.3.4-9
* quagga-0.97.0-1 -> quagga-0.98.2-2
* radvd-0.7.2-9 -> radvd-0.7.3-1_FC4
* rarpd-ss981107-18 -> rarpd-ss981107-20
* rcs-5.7-26 -> rcs-5.7-28
* rdate-1.4-2 -> rdate-1.4-4
* rdesktop-1.3.1-5 -> rdesktop-1.3.1-7
* rdist-6.1.5-38 -> rdist-6.1.5-40
* readline-4.3-13 -> readline-5.0-3
* recode-3.6-13 -> recode-3.6-16
* redhat-artwork-0.117-1 -> redhat-artwork-0.120-8
* redhat-lsb-1.3-4 -> redhat-lsb-1.3-9
* redhat-menus-1.13-1 -> redhat-menus-3.7.1-6
* redhat-rpm-config-8.0.32-1 -> redhat-rpm-config-8.0.33-2
* reiserfs-utils-3.6.18-1 -> reiserfs-utils-3.6.19-1
* rhdb-utils-3.0-3 -> rhdb-utils-4.0-3
* rhgb-0.14.1-1 -> rhgb-0.16.2-2
* rhnlib-1.8-6.p23.fc3 -> rhnlib-1.8-6.p23.fc3.1
* rhpl-0.148-1 -> rhpl-0.157-1
* rootfiles-8-1 -> rootfiles-8.1-1
* rpm-4.3.2-21 -> rpm-4.4.1-7
* rp-pppoe-3.5-22 -> rp-pppoe-3.5-27
* rsh-0.17-23 -> rsh-0.17-29
* rsync-2.6.3-1 -> rsync-2.6.3-3
* ruby-1.8.1-7 -> ruby-1.8.2-4
* rusers-0.17-41 -> rusers-0.17-43
* rwall-0.17-23 -> rwall-0.17-25
* rwho-0.17-22 -> rwho-0.17-23
* s390utils-1.3.2-1 -> s390utils-1.3.2-4
* samba-3.0.8-0.pre1.3 -> samba-3.0.11-5
* sane-backends-1.0.14-6 -> sane-backends-1.0.15-9
* sane-frontends-1.0.12-4 -> sane-frontends-1.0.13-2
* sash-3.7-4 -> sash-3.7-6
* schedutils-1.4.0-1 -> schedutils-1.4.0-4
* screen-4.0.2-5 -> screen-4.0.2-7
* SDL_image-1.2.3-6 -> SDL_image-1.2.3-7
* SDL_mixer-1.2.5-4 -> SDL_mixer-1.2.5-5
* SDL_net-1.2.5-2 -> SDL_net-1.2.5-3
* sed-4.1.2-4 -> sed-4.1.2-5
* selinux-doc-1.14.1-1 -> selinux-doc-1.18-1
* selinux-policy-strict-1.17.30-2 -> selinux-policy-strict-1.23.1-1
* selinux-policy-targeted-1.17.30-2.19 -> selinux-policy-targeted-1.23.1-1
* sendmail-8.13.1-2 -> sendmail-8.13.3-1.2
* setarch-1.6-1 -> setarch-1.7-2
* setools-1.4.1-5 -> setools-2.0.0-1
* setserial-2.17-17 -> setserial-2.17-19
* setup-2.5.36-1 -> setup-2.5.40-1
* sg3_utils-1.06-3 -> sg3_utils-1.06-5
* shadow-utils-4.0.3-37 -> shadow-utils-4.0.7-3
* shared-mime-info-0.15-10 -> shared-mime-info-0.15-11
* sharutils-4.2.1-22 -> sharutils-4.2.1-25
* sip-4.1-1 -> sip-4.2-1
* slang-1.4.9-6 -> slang-1.4.9-16
* slocate-2.7-12 -> slocate-2.7-16
* slrn-0.9.8.1-1 -> slrn-0.9.8.1-4
* sound-juicer-0.5.14-1 -> sound-juicer-2.10.0-1
* sox-12.17.5-3 -> sox-12.17.6-2
* spamassassin-3.0.0-3 -> spamassassin-3.0.2-1
* speex-1.0.4-4 -> speex-1.0.4-5
* splint-3.1.1-4 -> splint-3.1.1-5
* squid-2.5.STABLE6-3 -> squid-2.5.STABLE8-2
* squirrelmail-1.4.3a-5 -> squirrelmail-1.4.4-2
* star-1.5a25-6 -> star-1.5a54-1
* stardict-1.31-21 -> stardict-2.4.4-1
* startup-notification-0.7-1 -> startup-notification-0.8-2
* statserial-1.1-35 -> statserial-1.1-37
* strace-4.5.8-1 -> strace-4.5.9-2
* stunnel-4.05-3 -> stunnel-4.05-4
* subversion-1.1.0-5 -> subversion-1.1.3-6
* sudo-1.6.7p5-30.1 -> sudo-1.6.7p5-31
* swig-1.3.21-6 -> swig-1.3.24-2
* symlinks-1.2-22 -> symlinks-1.2-24
* synaptics-0.13.5-5 -> synaptics-0.14.0-1
* sysfsutils-1.2.0-1 -> sysfsutils-1.2.0-4
* sysklogd-1.4.1-22 -> sysklogd-1.4.1-26_FC4
* syslinux-2.11-1 -> syslinux-3.07-1
* sysreport-1.3.13-1 -> sysreport-1.4.0-1
* sysstat-5.0.5-1 -> sysstat-5.0.5-9.fc
* system-config-bind-2.0.3-1 -> system-config-bind-4.0.0-4
* system-config-boot-0.2.7-1 -> system-config-boot-0.2.8-1
* system-config-date-1.7.8-1 -> system-config-date-1.7.15-1
* system-config-display-1.0.23-1 -> system-config-display-1.0.25-1
* system-config-httpd-1.3.1-1 -> system-config-httpd-1.3.1-2
* system-config-kickstart-2.5.15-1 -> system-config-kickstart-2.5.20-1
* system-config-netboot-0.1.8-1 -> system-config-netboot-0.1.12-1
* system-config-network-1.3.22-1 -> system-config-network-1.3.23-1
* system-config-packages-1.2.20-1 -> system-config-packages-1.2.21-2
* system-config-printer-0.6.116-1 -> system-config-printer-0.6.125-1
* system-config-samba-1.2.21-1 -> system-config-samba-1.2.27-1
* system-config-securitylevel-1.4.14-1 -> system-config-securitylevel-1.5.1-1
* system-config-services-0.8.15-1 -> system-config-services-0.8.19-1
* system-config-users-1.2.25-1 -> system-config-users-1.2.28-1
* system-logviewer-0.9.11-1 -> system-logviewer-0.9.14-1
* SysVinit-2.85-34 -> SysVinit-2.85-37
* talk-0.17-26 -> talk-0.17-28
* tar-1.14-4 -> tar-1.15.1-4
* tcl-8.4.7-2 -> tcl-8.4.9-3
* tclx-8.3.5-4 -> tclx-8.3.5-5
* tcpdump-3.8.2-7 -> tcpdump-3.8.2-11
* tcp_wrappers-7.6-37.2 -> tcp_wrappers-7.6-38
* tcsh-6.13-6 -> tcsh-6.13-13
* telnet-0.17-30 -> telnet-0.17-34
* tetex-2.0.2-21 -> tetex-3.0-3
* texinfo-4.7-5 -> texinfo-4.8-4
* tftp-0.39-1 -> tftp-0.40-4
* thunderbird-0.8.0-9 -> thunderbird-1.0-5
* time-1.7-25 -> time-1.7-27
* timidity++-2.13.0-3 -> timidity++-2.13.2-1
* tix-8.1.4-98 -> tix-8.1.4-99
* tk-8.4.7-2 -> tk-8.4.9-3
* tmpwatch-2.9.1-1 -> tmpwatch-2.9.2-2
* tn5250-0.16.5-2 -> tn5250-0.16.5-4
* totem-0.99.19-1 -> totem-0.101-4
* traceroute-1.4a12-24 -> traceroute-1.4a12-26
* transfig-3.2.4-8 -> transfig-3.2.4-11
* tree-1.5.0-1 -> tree-1.5.0-3
* tsclient-0.132-4 -> tsclient-0.132-5
* ttcp-1.12-10 -> ttcp-1.12-13
* tvtime-0.9.13-1 -> tvtime-0.9.15-4
* tzdata-2004e-2 -> tzdata-2005f-2
* udev-039-8.FC3 -> udev-050-9
* umb-scheme-3.2-35 -> umb-scheme-3.2-37
* units-1.80-10 -> units-1.80-12
* unix2dos-2.2-24 -> unix2dos-2.2-25
* unixODBC-2.2.9-1 -> unixODBC-2.2.10-3
* unzip-5.51-4 -> unzip-5.51-10
* up2date-4.3.47-5 -> up2date-4.4.9-1
* urw-fonts-2.2-6 -> urw-fonts-2.2-8
* usbutils-0.11-6.1 -> usbutils-0.11-6.2
* usermode-1.74-1 -> usermode-1.79-1
* utempter-0.5.5-5 -> utempter-0.5.5-6
* util-linux-2.12a-16 -> util-linux-2.12p-2
* uucp-1.07-3 -> uucp-1.07-6
* valgrind-2.2.0-3 -> valgrind-2.2.0-8
* valgrind-callgrind-0.9.9-1 -> valgrind-callgrind-0.9.9-2
* vconfig-1.8-4 -> vconfig-1.8-7
* VFlib2-2.25.6-25 -> VFlib2-2.25.6-28
* vim-6.3.030-3 -> vim-6.3.064-1
* vino-2.8.1-1 -> vino-2.9.2-2
* vixie-cron-4.1-19 -> vixie-cron-4.1-24_FC4
* vlock-1.3-16 -> vlock-1.3-17
* vnc-4.0-8 -> vnc-4.1.1-2
* vorbis-tools-1.0.1-4 -> vorbis-tools-1.0.1-5
* vsftpd-2.0.1-5 -> vsftpd-2.0.2-1
* vte-0.11.11-6 -> vte-0.11.12-1
* w3c-libwww-5.4.0-10 -> w3c-libwww-5.4.0-13
* w3m-0.5.1-4 -> w3m-0.5.1-6
* webalizer-2.01_10-25 -> webalizer-2.01_10-28
* wget-1.9.1-17 -> wget-1.9.1-22
* which-2.16-4 -> which-2.16-6
* wireless-tools-27-0.pre25.2 -> wireless-tools-28-0.pre4.3
* words-2-23 -> words-3.0-2
* wordtrans-1.1pre13-8 -> wordtrans-1.1pre13-10
* wvdial-1.54.0-3 -> wvdial-1.54.0-5
* x3270-3.3.2.p1-6 -> x3270-3.3.3.b2-1
* Xaw3d-1.5-23 -> Xaw3d-1.5E-4
* xcdroast-0.98a15-6 -> xcdroast-0.98a15-10
* xchat-2.4.0-3 -> xchat-2.4.1-4
* xferstats-2.16-11 -> xferstats-2.16-12
* xfig-3.2.4-5 -> xfig-3.2.4-9
* xfsprogs-2.6.13-2 -> xfsprogs-2.6.13-3
* xinetd-2.3.13-4 -> xinetd-2.3.13-6
* xmlsec1-1.2.6-3 -> xmlsec1-1.2.7-4
* xmltex-20020625-3 -> xmltex-20020625-5
* xmlto-0.0.18-4 -> xmlto-0.0.18-6
* xmms-1.2.10-9 -> xmms-1.2.10-11
* xorg-x11-6.8.1-12 -> xorg-x11-6.8.2-10
* xpdf-3.00-10 -> xpdf-3.00-18
* xrestop-0.2-4 -> xrestop-0.2-5
* xsane-0.92-13 -> xsane-0.95-3
* xscreensaver-4.18-4 -> xscreensaver-4.18-19
* xsri-2.1.0-8 -> xsri-2.1.0-9
* xterm-192-1 -> xterm-200-4
* yaboot-1.3.12-7 -> yaboot-1.3.12-8
* yelp-2.6.3-1 -> yelp-2.9.3-3
* ypbind-1.17.2-3 -> ypbind-1.17.2-5
* yum-2.1.11-3 -> yum-2.3.1-2
* zip-2.3-24 -> zip-2.3-30
* zisofs-tools-1.0.6-1 -> zisofs-tools-1.0.6-3
* zlib-1.2.1.2-1 -> zlib-1.2.2.2-2
* zsh-4.2.0-3 -> zsh-4.2.1-2
=== Packages Deprecated or Nuked ===
The following packages have been deprecated or nuked, and may be removed from a future release of Fedora Core:
* This List
* Is
* Blank
* Until We Decide
* What This Section
* Means
== An Overview of the Fedora Project ==
The goal of the Fedora Project is to work with the Linux community to build a complete, general purpose operating system exclusively from open source software. Development will be done in a public forum. The project will produce time-based releases of Fedora Core about 2-3 times a year, with a public release schedule. The Red Hat engineering team will continue to participate in building Fedora Core and will invite and encourage more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community.
For more information, refer to the Fedora Project website:
[10]http://fedora.redhat.com/
In addition to the website, the following mailing lists are available:
* fedora-list at redhat.com -- For users of Fedora Core releases
* fedora-test-list at redhat.com -- For testers of Fedora Core test releases
* fedora-devel-list at redhat.com -- For developers, developers, developers
* fedora-docs-list at redhat.com -- For participants of the docs project
To subscribe to any of these lists, send an email with the word "subscribe" in the subject to -request (where is one of the above list names.)
NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list, rhl-devel-list, or rhl-docs-list, your subscriptions have been retained.
The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC is a real-time, text-based form of communication. With it, you can have conversations with multiple people in an open channel or chat with someone privately one-on-one.
To talk with other Fedora Project participants via IRC, access freenode IRC network. Initially, you can use irc.freenode.net as the IRC server, although you may decide to select a server that is geographically closer to you. Refer to the freenode website ([11]http://www.freenode.net/) for more information. Fedora Project participants frequent the #fedora channel, while Fedora Project developers can often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well; this information can be found on the project pages.
NOTE: Red Hat has no control over the Fedora IRC channels or their content.
( x86 )
== References ==
Visible links
1. http://www.gnu.org/licenses/fdl.html
2. http://fedora.redhat.com/docs/selinux-faq/
3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
5. http://platan.vc.cvut.cz/ftp/pub/vmware/
6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
7. http://i2o.shadowconnect.com/
8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
9. http://people.redhat.com/~harald/udev.html
10. http://fedora.redhat.com/
11. http://www.freenode.net/
--- NEW FILE fc4test2-relnotes ---
== Fedora Core 4test2 Release Notes ==
Copyright (c) 2005 Red Hat, Inc.
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 [1]http://www.gnu.org/licenses/fdl.html.
This document may be copied and distributed in any medium, either commercially or non-commercially, 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.
Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.
The Fedora trademark is a trademark of Red Hat, Inc. in the United States and other countries.
Linux is a registered trademark of Linus Torvalds.
All other trademarks and copyrights referred to are the property of their respective owners.
The GPG fingerprint of the "Fedora Project " key is:
CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
---------------------------------------------------------------------------
1. Fedora Core 4test2 Release Notes
2. Introduction
3. Hardware Requirements
1. CPU Requirements
2. Hard Disk Space Requirements
3. Memory Requirements
4. Overview of This Release
5. Installation-Related Notes
6. Installation-Related Issues
7. Package-Specific Notes
1. Base
2. Core
3. Language Support
4. Server Configuration Tools
5. Sound and Video
6. Web Server
7. Windows File Server
8. Macintosh File Server
9. X Window System
10. Miscellaneous Notes
8. Packages Added, Moved From Core, Changed, or Deprecated/Nuked
1. Packages Added
2. Packages Moved Out Of Core
9. An Overview of the Fedora Project
10. References
== Introduction ==
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, a complete, general-purpose operating system built exclusively from open source software.
NOTE: Fedora Core is not a supported product of Red Hat, Inc.
For more information, refer to the Fedora Project overview later in this document.
The following topics related to Fedora Core 4test2 are covered in this document:
* Introduction (this section)
* Hardware requirements
* Overview of this release
* Installation-related notes
* Package-specific notes
* Packages added/removed/deprecated
* An overview of the Fedora Project
== Hardware Requirements ==
The following information represents the minimum hardware requirements necessary to successfully install Fedora Core 4test2.
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.
=== CPU Requirements ===
This section lists the CPU specifications required by Fedora Core 4test2.
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.
* Minimum: Pentium-class
Fedora Core 4test2 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.
* Recommended for text-mode: 200 MHz Pentium-class or better
* Recommended for graphical: 400 MHz Pentium II or better
=== Hard Disk Space Requirements ===
This section lists the disk space required to install Fedora Core 4test2.
Note
The disk space requirements listed below represent the disk space taken up by Fedora Core 4test2 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.
* Custom Installation (Minimal): 620MB
* Server: 1.1GB
* Personal Desktop: 2.3GB
* Workstation: 3.0GB
* Custom Installation (Everything): 6.9GB
=== Memory Requirements ===
This section lists the memory required to install Fedora Core 4test2.
* Minimum for text-mode: 64MB
* Minimum for graphical: 192MB
* Recommended for graphical: 256MB
== Overview of This Release ==
The following list highlights certain new features of Fedora Core 4test2:
* GCC 4.0
* GNOME 2.10
* KDE 3.4
* Native Eclipse 3.1M5
* MySQL 4.1
* PHP 5.0
* SELinux -- New daemons have been added to the targeted policy For
more information, refer to the SELinux FAQ at
http://fedora.redhat.com/docs/selinux-faq/ .
* amanda
* apache
* chkpwd
* cups
* dhcpc
* dhcpd
* dictd
* dovecot
* fingerd
* ftpd
* howl
* i18n_input
* ifconfig
* init
* initrc
* inetd
* innd
* kerberos
* ktalkd
* ldconfig
* login
* lpd
* mailman
* modutil
* mta
* mysqld
* NetworkManager
* named
* nscd
* ntpd
* portmap
* postgresql
* privoxy
* radius
* radvd
* rlogind
* rpcd
* rshd
* rsync
* samba
* slapd
* snmpd
* squid
* stunnel
* syslogd
* telnetd
* tftpd
* winbind
* ypbind
* ypserv
* zebra
== Installation-Related Notes ==
This section outlines anything noteworthy that is related to Anaconda (the Fedora Core installation program) and installing Fedora Core 4test2 in general.
Note
If you intend to download the Fedora Core 4test2 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.
Anaconda Notes
* 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.
* 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.
* Fedora Core 4test2 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.
== Installation-Related Issues ==
* 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.
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.
* 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.
* 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:
[6]http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
* There have been issues observed when upgrading Red Hat Linux 7., 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The issue 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 issue:
1) You may remove Ximian GNOME from your system prior to upgrading to Fedora Core.
2) You may upgrade your system, and then immediately reinstall Ximian GNOME.
3) 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.
== Package-Specific Notes ==
The following sections contain information regarding packages that have undergone significant changes for Fedora Core 4test2. For easier access, they are organized using the same groups used in Anaconda.
=== Base ===
This section contains information related to basic system components.
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.
openssh
The version of OpenSSH in Fedora Core 4test2 contains OpenSSH 3.9 includes strict permission and ownership checks for the ~/.ssh/config file. These checks mean that ssh will exit if this file does not have appropriate ownership and permissions.
Therefore, make sure that ~/.ssh/config is owned by the owner of ~/, and that its permissions are set to mode 600.
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 flag 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 flag instead of the -X flag, or set ForwardX11Trusted in the ~/.ssh/config file.
=== Core ===
This section contains the most elemental components of Fedora Core, including the kernel.
* In order to eliminate the redundancy inherent in providing a separate package for the kernel source code when that source code already exists in the kernel's .src.rpm file, Fedora Core 4test2 no longer includes the kernel-source package. Users that require access to the kernel sources can find them in the kernel .src.rpm file. To create an exploded source tree from this file, perform the following steps (note that refers to the version specification for your currently-running kernel):
1. Obtain the kernel-.src.rpm file from one of the following sources:
* The SRPMS directory on the appropriate "SRPMS" CD iso image
* The FTP site where you got the kernel package
* By running the following command:
up2date --get-source kernel
2. Install kernel-.src.rpm (given the default RPM configuration, the files this package contains will be written to /usr/src/redhat/)
3. Change directory to /usr/src/redhat/SPECS/, and issue the following command:
rpmbuild -bp --target= kernel.spec
(Where is the desired target architecture.)
On a default RPM configuration, the kernel tree will be located in /usr/src/redhat/BUILD/.
4. In resulting tree, the configurations for the specific kernels shipped in Fedora Core 4test2 are in the /configs/ directory. For example, the i686 SMP configuration file is named /configs/kernel--i686-smp.config. Issue the following command to place the desired configuration file in the proper place for building:
cp ./.config
5. Issue the following command:
make oldconfig
You can then proceed as usual.
Note
An exploded source tree is not required to build kernel modules against the currently in-use kernel.
For example, to build the foo.ko module, create the following file (named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
Issue the make command to build the foo.ko module.
=== Language Support ===
This section includes information related to the support of various languages under Fedora Core.
=== Server Configuration Tools ===
This section contains information related to various server configuration tools.
=== Sound and Video ===
This section contains information related to multimedia applications.
=== Web Server ===
This section contains information related to Web-related tools.
php
Version 5.0 of PHP is now included, which includes a number of changes
to the language along with significant performance improvements.
Please refer to the PHP documentation for more information on
migrating from PHP 4.3 to PHP 5.0:
http://www.php.net/manual/en/migration5.php
The following extensions have been added:
* the "mysqli" extension, the newly MySQL interface designed
specifically for MySQL 4; included in the php-mysql
* the "soap" extension, which can be used to implement a SOAP server
or client
=== Windows File Server ===
This section contains information related to Samba, software that makes it possible to share files between Linux and Windows systems.
samba
Browsing of Windows shares (also known as SMB browsing) fails on Fedora Core 4test2 systems that have the standard firewall configured. This is most easily noticed in the failure of Nautilus to display shares. The failure is due to the firewall disrupting the broadcast mode of SMB browsing, which is Samba's default setting. There are two workarounds:
* Configure a WINS server on the network, and set the "wins server" option in smb.conf to the address of the WINS server.
* Disable the firewall
Warning
Depending on your system and network configurations, disabling the firewall can greatly increase the chance of your system being attacked and compromised. Make sure you fully understand the risks before undertaking this step.
For additional information, refer to the following bug report:
[8]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
=== Macintosh File Server ===
This section contains information related to netatalk, software that
makes it possible to share files between Linux and Macintosh systems.
netatalk
The 2.x version of netatalk uses a different method to store resource
forks, and may use a different file name encoding scheme. Upgrading to
Fedora Core 4 may result in data loss. Please read the documentation of
the netatalk 1.x to 2.x upgrade before upgrading to Fedora Core 4.
The netatalk upgrade information is available directly from the
netatalk site:
http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html
It is also included in the netatalk installation for Fedora Core 4, the
files are at:
/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf - numbered page
25, document page 33.
or
/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html
=== X Window System ===
This section contains information related to the X Window System implementation provided with Fedora Core.
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 Red Hat operating systems. In particular, the names of some files have changed:
X Server Binary:
* XFree86 X11: XFree86
* X.org X11: Xorg
X Server Configuration File:
* XFree86 X11: /etc/X11/XF86Config
* X.org X11: /etc/X11/xorg.conf
X Server Log File
* XFree86 X11: /var/log/XFree86.$DISPLAY.log
* 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:
- 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 like:
-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 like:
Luxi Sans-10
* Over time, fontconfig/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.
NOTE: An exception to the font subsystem usage outlined above is OpenOffice.org (which uses its own font rendering technology).
If you wish to add new fonts to your Fedora Core 4test2 system, you must be aware that the steps necessary depend on which font subsystem is to use the new fonts. For the core X font subsystem, you must:
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):
ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale
mkfontdir /usr/share/fonts/local/
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
(Where 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 = ""
}
widget_class " *" style "user-font"
(Where represents a font specification in the style used by traditional X applications, such as "-adobe-helvetica-medium-r-normal-- *-120- *- *- *- *- *- *".)
=== Miscellaneous Notes ===
This section contains information related to packages that do not fit in any of the proceeding categories.
== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
For an overview of orphaned packages, visit [:Extras/OrphanedPackages:this list].
This section contains lists of packages that fit into the following categories:
* Packages that have been added to Fedora Core 4test2
* Packages that have been moved out of Fedora Core 4test2
* Packages that have a changed version since Fedora Core 3
* Packages that have been deprecated, and may be removed from a future
release of Fedora Core
=== Packages Added ===
The following packages have been added to Fedora Core 4test2:
* ant-1.6.2-3jpp_2fc
* antlr-2.7.4-2jpp_1fc
* aqbanking-1.0.4beta-2
* aqhbci-1.0.2beta-2
* avalon-framework-4.1.4-2jpp_5fc
* avalon-logkit-1.2-2jpp_4fc
* bcel-5.1-1jpp_4fc
* classpath-inetlib-1.0-1jpp_1fc
* classpathx-jaf-1.0-2jpp_3fc
* classpathx-mail-1.0-3jpp_1fc
* compat-gcc-296-2.96-132.fc4
* compat-gcc-32-3.2.3-47.fc4
* compat-readline43-4.3-2
* cpufreq-utils-0.2-1.1.12
* cpuspeed-1.2.1-1.19
* cryptix-3.2.0-4jpp_1fc
* cryptix-asn1-20011119-4jpp_1fc
* cryptsetup-luks-1.0-1
* dcraw-0.0.20050227-1
* device-mapper-multipath-0.4.4-0.pre8.0
* dmidecode-2.6-1.13
* eclipse-3.1.0_fc-0.M5.17
* eclipse-bugzilla-0.1.0_fc-9
* eclipse-cdt-3.0.0_fc-0.M5.3
* eclipse-changelog-2.0.1_fc-19
* eclipse-pydev-0.9.0_fc-4
* evince-0.1.9-1
* fonts-chinese-2.15-1
* fonts-indic-1.9-2
* fonts-japanese-0.20050222-2
* fonts-korean-1.0.11-2
* gjdoc-0.7.3-1
* gnome-doc-utils-0.1.3-1
* gnome-menus-2.10.1-1
* gnome-python2-extras-2.10.0-2.1
* gnu-crypto-2.0.1-1jpp_1fc
* gnu.getopt-1.0.9-4jpp_1fc
* gwenhywfar-1.7.2-2
* hardlink-1.0-1.11
* iiimf-12.1.1-11.svn2435
* ipv6calc-0.48-3
* irqbalance-1.12-1.18
* jakarta-commons-beanutils-1.7.0-1jpp_1fc
* jakarta-commons-collections-3.1-1jpp_1fc
* jakarta-commons-daemon-1.0-2jpp_1fc
* jakarta-commons-dbcp-1.2.1-3jpp_1fc
* jakarta-commons-digester-1.6-2jpp_1fc
* jakarta-commons-el-1.0-2jpp_1fc
* jakarta-commons-fileupload-1.0-3jpp_1fc
* jakarta-commons-lang-2.0-2jpp_1fc
* jakarta-commons-launcher-0.9-3jpp_1fc
* jakarta-commons-logging-1.0.4-2jpp_1fc
* jakarta-commons-modeler-1.1-3jpp_1fc
* jakarta-commons-pool-1.2-2jpp_1fc
* jakarta-commons-validator-1.1.3-1jpp_1fc
* jakarta-taglibs-standard-1.1.1-4jpp_1fc
* java_cup-0.10-0.k.1jpp_2fc
* jdepend-2.6-2jpp_3fc
* jessie-1.0.0-3
* jlex-1.2.6-1jpp_2fc
* jsch-0.1.17-2jpp_1fc
* junit-3.8.1-3jpp_4fc
* jzlib-1.0.5-2jpp_1fc
* kdeaccessibility-3.4.0-1
* ksh-20050202-1
* latex2html-2002.2.1-1
* ldapjdk-4.17-1jpp_2fc
* libdbi-drivers-0.7.1-2
* libgconf-java-2.10.0-1
* libglade-java-2.9.92-1
* libgnome-java-2.9.92-1
* libgtk-java-2.6.1.1-1
* linux-atm-2.5.0-0.20050118.2
* lksctp-tools-1.0.2-5
* log4j-1.2.8-7jpp_3fc
* longrun-0.9-1.8
* lvm2-cluster-2.00.29-1.22.FC4
* mcelog-0.4-1.8
* microcode_ctl-1.11-1.21
* mod_jk-1.2.6-3jpp_1fc
* mx4j-2.1.0-1jpp_2fc
* mysqlclient10-3.23.58-5
* openhpi-2.0.3-2
* OpenIPMI-1.4.11-5
* openssl097a-0.9.7a-2
* oro-2.0.8-1jpp_2fc
* poppler-0.1.2-1
* puretls-0.9-0.b4.1jpp_2fc
* python-docs-2.4-102
* python-elementtree-1.2.6-4
* python-numeric-23.7-2
* python-sqlite-1.1.6-1
* python-twisted-1.3.0-4
* python-urlgrabber-2.9.6-1
* readahead-1.0-1.7
* regexp-1.3-1jpp_4fc
* rng-utils-2.0-1.5
* salinfo-0.5-1.4
* servletapi5-5.0.18-1jpp_3fc
* slib-3a1-2
* smartmontools-5.33-1.5
* sqlite-3.1.2-2
* struts11-1.1-1jpp_2fc
* system-config-lvm-0.9.22-1.0
* texi2html-1.76-2
* tomcat5-5.0.30-1jpp_2fc
* x86info-1.13-1.9
* xalan-j2-2.6.0-2jpp_1fc
* xen-2-20050403
* xerces-j2-2.6.2-4jpp_1fc
* xml-commons-1.0-0.b2.6jpp_5fc
* xml-commons-resolver-1.1-1jpp_4fc
=== Packages Moved Out Of Core ===
This is a new section to the release notes. This is based on a treediff of dist-fc3 and dist-fc4 on 14-MAR-2005. The following packages have been moved out of core from Fedora Core 4test2:
* abiword-2.0.12-3
* aiksaurus-1.2.1-2
* ash-0.3.8-20
* asp2php-0.76.18-3
* aspell-ia-0.50-1
* aumix-2.8-9
* balsa-2.2.4-1.FC3.1
* bluez-bluefw-1.0-6
* bonobo-1.0.22-9
* bzflag-1.10.6-2
* cdecl-2.5-30
* cdlabelgen-3.0.0-1
* cdp-0.33-32
* compat-gcc-8-3.3.4.2
* compat-pwdb-0.62-9
* comsat-0.17-11
* cproto-4.7c-3
* cryptsetup-0.1-4
* cyrus-imapd-2.2.6-2.FC3.6
* dbh-1.0.18-5
* dbskkd-cdb-1.01-21
* ddskk-12.2.0-4
* dietlibc-0.27-4
* diskcheck-1.6-2
* dmalloc-5.3.0-3
* exim-4.43-1
* flim-1.14.7-1
* fonts-bengali-0.1-3
* fonts-ja-8.0-16
* freeciv-1.14.2-1
* FreeWnn-1.10pl020-5
* fsh-1.2-5
* ftpcopy-0.6.2-7
* gcc4-4.0.0-0.8
* ggv-2.8.0-1
* giftrans-1.12.2-20
* Glide3-20010520-33
* gnome-vfs-1.0.5-21
* gnome-vfs-extras-0.2.0-9
* gnuchess-5.07-4
* gnumeric-1.2.13-6
* gpdf-2.8.0-5
* grip-3.2.0-3
* gv-3.5.8-29
* im-sdk-12.1-4
* jed-0.99.16-6
* jisksp14-0.1-16
* jisksp16-1990-0.1-16
* kappa20-0.3-15
* kdetoys-3.3.0-1
* kernel-utils-2.4-13.1.39
* kinput2-v3.1-23
* knm_new-1.1-16
* koffice-1.3.3-1
* lapack-3.0-25
* lesstif-0.93.36-6
* libesmtp-1.0.3r1-2
* libgda-1.0.4-3
* libgnomedb-1.0.4-3
* libtool-libs13-1.3.5-10
* libxfce4mcs-4.0.6-1
* libxfce4util-4.0.6-1
* libxfcegui4-4.0.6-1
* lilo-21.4.4-26
* Maelstrom-3.0.6-6
* MagicPoint-1.11b-1
* memprof-0.5.1-5
* mew-3.3-4
* miniChinput-0.0.3-58
* nabi-0.14-3
* namazu-2.0.13-3
* nautilus-media-0.8.1-3
* ncftp-3.1.8-2
* nedit-5.4-3
* octave-2.1.57-7
* Omni-0.9.1-7
* openhbci-0.9.17-1
* openssl096b-0.9.6b-19
* ots-0.4.2-2
* pan-0.14.2-8
* pccts-1.33mr33-11
* pdksh-5.2.14-30
* qmkbootdisk-1.0.2-3
* Regina-2.3-1
* routed-0.17-18
* skkinput-2.06.4-7
* splint-3.1.1-4
* sylpheed-0.9.12-1
* system-logviewer-0.9.11-1
* system-switch-im-0.1.2-3
* THE-3.1-2
* tora-1.3.14.1-2
* ttfonts-indic-1.6-1
* ttfonts-ja-1.2-36
* ttfonts-ko-1.0.11-32.2
* ttfonts-zh_CN-2.14-10
* ttfonts-zh_TW-2.11-28
* ttfprint-0.9-13
* tuxracer-0.61-28
* w3m-el-1.4.3-2
* wl-2.10.1-4
* x3270-3.3.2.p1-6
* xboard-4.2.7-6
* xcin-2.5.3.pre3-24
* xemacs-21.4.15-9
* xemacs-sumo-20040818-2
* xfce4-iconbox-4.0.6-2
* xfce4-panel-4.0.6-1
* xfce4-systray-4.0.6-2
* xfce-mcs-manager-4.0.6-2
* xfce-mcs-plugins-4.0.6-2
* xfce-utils-4.0.6-1
* xfdesktop-4.0.6-2
* xffm-4.0.6-1
* xffm-icons-4.0.6-2
* xfprint-4.0.6-2
* xfwm4-4.0.6-1
* xfwm4-themes-4.0.6-2
* xloadimage-4.1-32
* xmms-1.2.10-9
* xosview-1.8.2-1
* xsnow-1.42-15
* ytalk-3.1.2-1
== An Overview of the Fedora Project ==
The goal of the Fedora Project is to work with the Linux community to build a complete, general purpose operating system exclusively from open source software. Development will be done in a public forum. The project will produce time-based releases of Fedora Core about 2-3 times a year, with a public release schedule. The Red Hat engineering team will continue to participate in building Fedora Core and will invite and encourage more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community.
For more information, refer to the Fedora Project website:
[10]http://fedora.redhat.com/
In addition to the website, the following mailing lists are available:
* fedora-list at redhat.com -- For users of Fedora Core releases
* fedora-test-list at redhat.com -- For testers of Fedora Core test releases
* fedora-devel-list at redhat.com -- For developers, developers, developers
* fedora-docs-list at redhat.com -- For participants of the docs project
To subscribe to any of these lists, send an email with the word "subscribe" in the subject to -request (where is one of the above list names.)
NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list, rhl-devel-list, or rhl-docs-list, your subscriptions have been retained.
The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC is a real-time, text-based form of communication. With it, you can have conversations with multiple people in an open channel or chat with someone privately one-on-one.
To talk with other Fedora Project participants via IRC, access freenode IRC network. Initially, you can use irc.freenode.net as the IRC server, although you may decide to select a server that is geographically closer to you. Refer to the freenode website ([11]http://www.freenode.net/) for more information. Fedora Project participants frequent the #fedora channel, while Fedora Project developers can often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well; this information can be found on the project pages.
NOTE: Red Hat has no control over the Fedora IRC channels or their content.
( x86 )
== References ==
Visible links
1. http://www.gnu.org/licenses/fdl.html
2. http://fedora.redhat.com/docs/selinux-faq/
3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
5. http://platan.vc.cvut.cz/ftp/pub/vmware/
6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
7. http://i2o.shadowconnect.com/
8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
9. http://people.redhat.com/~harald/udev.html
10. http://fedora.redhat.com/
11. http://www.freenode.net/
From fedora-docs-commits at redhat.com Tue May 3 23:29:56 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 3 May 2005 19:29:56 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,NONE,1.1
Message-ID: <200505032329.j43NTuQF017826@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17817
Added Files:
fc4test3-relnotes
Log Message:
test2 -> test3, some text fill, general preparation.
--- NEW FILE fc4test3-relnotes ---
== Fedora Core 4test3 Release Notes ==
Copyright (c) 2005 Red Hat, Inc.
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
[1]http://www.gnu.org/licenses/fdl.html.
This document may be copied and distributed in any medium, either
commercially or non-commercially, 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.
Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum
RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based
trademarks and logos are trademarks or registered trademarks of Red
Hat, Inc. in the United States and other countries.
The Fedora trademark is a trademark of Red Hat, Inc. in the United
States and other countries.
Linux is a registered trademark of Linus Torvalds.
All other trademarks and copyrights referred to are the property of
their respective owners.
The GPG fingerprint of the "Fedora Project " key is:
CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
---------------------------------------------------------------------------
1. Fedora Core 4test3 Release Notes
2. Introduction
3. Hardware Requirements
1. CPU Requirements
2. Hard Disk Space Requirements
3. Memory Requirements
4. Overview of This Release
5. Installation-Related Notes
6. Installation-Related Issues
7. Package-Specific Notes
1. Base
2. Core
3. Language Support
4. Server Configuration Tools
5. Sound and Video
6. Web Server
7. Windows File Server
8. Macintosh File Server
9. X Window System
10. Miscellaneous Notes
8. Packages Added, Moved From Core, Changed, or Deprecated/Nuked
1. Packages Added
2. Packages Moved Out Of Core
9. An Overview of the Fedora Project
10. References
== Introduction ==
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, a complete, general-purpose operating system built
exclusively from open source software.
NOTE: Fedora Core is not a supported product of Red Hat, Inc.
For more information, refer to the Fedora Project overview later in this document.
The following topics related to Fedora Core 4test3 are covered in this document:
* Introduction (this section)
* Hardware requirements
* Overview of this release
* Installation-related notes
* Package-specific notes
* Packages added/removed/deprecated
* An overview of the Fedora Project
== Hardware Requirements ==
The following information represents the minimum hardware requirements
necessary to successfully install Fedora Core 4test3.
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.
=== CPU Requirements ===
This section lists the CPU specifications required by Fedora Core
4test3.
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.
* Minimum: Pentium-class
Fedora Core 4test3 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.
* Recommended for text-mode: 200 MHz Pentium-class or better
* Recommended for graphical: 400 MHz Pentium II or better
=== Hard Disk Space Requirements ===
This section lists the disk space required to install Fedora Core 4test3.
Note
The disk space requirements listed below represent the disk space
taken up by Fedora Core 4test3 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.
* Custom Installation (Minimal): 620MB
* Server: 1.1GB
* Personal Desktop: 2.3GB
* Workstation: 3.0GB
* Custom Installation (Everything): 6.9GB
=== Memory Requirements ===
This section lists the memory required to install Fedora Core 4test3.
* Minimum for text-mode: 64MB
* Minimum for graphical: 192MB
* Recommended for graphical: 256MB
== Overview of This Release ==
The following list highlights certain new features of Fedora Core 4test3:
* GCC 4.0
* GNOME 2.10
* KDE 3.4
* Native Eclipse 3.1M5
* MySQL 4.1
* PHP 5.0
* SELinux -- New daemons have been added to the targeted policy For
more information, refer to the SELinux FAQ at
http://fedora.redhat.com/docs/selinux-faq/ .
* amanda
* apache
* chkpwd
* cups
* dhcpc
* dhcpd
* dictd
* dovecot
* fingerd
* ftpd
* howl
* i18n_input
* ifconfig
* init
* initrc
* inetd
* innd
* kerberos
* ktalkd
* ldconfig
* login
* lpd
* mailman
* modutil
* mta
* mysqld
* NetworkManager
* named
* nscd
* ntpd
* portmap
* postgresql
* privoxy
* radius
* radvd
* rlogind
* rpcd
* rshd
* rsync
* samba
* slapd
* snmpd
* squid
* stunnel
* syslogd
* telnetd
* tftpd
* winbind
* ypbind
* ypserv
* zebra
== Installation-Related Notes ==
This section outlines anything noteworthy that is related to Anaconda
(the Fedora Core installation program) and installing Fedora Core
4test3 in general.
Note
If you intend to download the Fedora Core 4test3 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.
Anaconda Notes
* 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.
* 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.
* Fedora Core 4test3 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.
== Installation-Related Issues ==
* 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.
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.
* 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.
* 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:
[6]http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
* There have been issues observed when upgrading Red Hat Linux
7., 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The
issue 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 issue:
1) You may remove Ximian GNOME from your system prior to upgrading to
Fedora Core.
2) You may upgrade your system, and then immediately reinstall Ximian
GNOME.
3) 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.
== Package-Specific Notes ==
The following sections contain information regarding packages that
have undergone significant changes for Fedora Core 4test3. For easier
access, they are organized using the same groups used in Anaconda.
=== Base ===
This section contains information related to basic system components.
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.
openssh
The version of OpenSSH in Fedora Core 4test3 contains OpenSSH 3.9
includes strict permission and ownership checks for the ~/.ssh/config
file. These checks mean that ssh will exit if this file does not have
appropriate ownership and permissions.
Therefore, make sure that ~/.ssh/config is owned by the owner of ~/,
and that its permissions are set to mode 600.
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 flag 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 flag instead of the -X flag,
or set ForwardX11Trusted in the ~/.ssh/config file.
=== Core ===
This section contains the most elemental components of Fedora Core,
including the kernel.
* In order to eliminate the redundancy inherent in providing a
separate package for the kernel source code when that source code
already exists in the kernel's .src.rpm file, Fedora Core 4test3
no longer includes the kernel-source package. Users that require
access to the kernel sources can find them in the kernel .src.rpm
file. To create an exploded source tree from this file, perform
the following steps (note that refers to the version
specification for your currently-running kernel):
1. Obtain the kernel-.src.rpm file from one of the
following sources:
* The SRPMS directory on the appropriate "SRPMS" CD iso image
* The FTP site where you got the kernel package
* By running the following command:
up2date --get-source kernel
2. Install kernel-.src.rpm (given the default RPM
configuration, the files this package contains will be
written to /usr/src/redhat/)
3. Change directory to /usr/src/redhat/SPECS/, and issue the
following command:
rpmbuild -bp --target= kernel.spec
(Where is the desired target architecture.)
On a default RPM configuration, the kernel tree will be
located in /usr/src/redhat/BUILD/.
4. In resulting tree, the configurations for the specific
kernels shipped in Fedora Core 4test3 are in the /configs/
directory. For example, the i686 SMP configuration file is
named /configs/kernel--i686-smp.config. Issue the
following command to place the desired configuration file
in the proper place for building:
cp ./.config
5. Issue the following command:
make oldconfig
You can then proceed as usual.
Note
An exploded source tree is not required to build kernel modules
against the currently in-use kernel.
For example, to build the foo.ko module, create the following file
(named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
Issue the make command to build the foo.ko module.
=== Language Support ===
This section includes information related to the support of various
languages under Fedora Core.
=== Server Configuration Tools ===
This section contains information related to various server
configuration tools.
=== Sound and Video ===
This section contains information related to multimedia applications.
=== Web Server ===
This section contains information related to Web-related tools.
php
Version 5.0 of PHP is now included, which includes a number of changes
to the language along with significant performance improvements.
Please refer to the PHP documentation for more information on
migrating from PHP 4.3 to PHP 5.0:
http://www.php.net/manual/en/migration5.php
The following extensions have been added:
* the "mysqli" extension, the newly MySQL interface designed
specifically for MySQL 4; included in the php-mysql
* the "soap" extension, which can be used to implement a SOAP server
or client
=== Windows File Server ===
This section contains information related to Samba, software that
makes it possible to share files between Linux and Windows systems.
samba
Browsing of Windows shares (also known as SMB browsing) fails on
Fedora Core 4test3 systems that have the standard firewall
configured. This is most easily noticed in the failure of Nautilus to
display shares. The failure is due to the firewall disrupting the
broadcast mode of SMB browsing, which is Samba's default
setting. There are two workarounds:
* Configure a WINS server on the network, and set the "wins server"
option in smb.conf to the address of the WINS server.
* Disable the firewall
Warning
Depending on your system and network configurations, disabling the
firewall can greatly increase the chance of your system being attacked
and compromised. Make sure you fully understand the risks before
undertaking this step.
For additional information, refer to the following bug report:
[8]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
=== Macintosh File Server ===
This section contains information related to netatalk, software that
makes it possible to share files between Linux and Macintosh systems.
netatalk
The 2.x version of netatalk uses a different method to store resource
forks, and may use a different file name encoding scheme. Upgrading to
Fedora Core 4 may result in data loss. Please read the documentation of
the netatalk 1.x to 2.x upgrade before upgrading to Fedora Core 4.
The netatalk upgrade information is available directly from the
netatalk site:
http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html
It is also included in the netatalk installation for Fedora Core 4, the
files are at:
/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf - numbered page
25, document page 33.
or
/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html
=== X Window System ===
This section contains information related to the X Window System
implementation provided with Fedora Core.
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 Red Hat operating systems. In
particular, the names of some files have changed:
X Server Binary:
* XFree86 X11: XFree86
* X.org X11: Xorg
X Server Configuration File:
* XFree86 X11: /etc/X11/XF86Config
* X.org X11: /etc/X11/xorg.conf
X Server Log File
* XFree86 X11: /var/log/XFree86.$DISPLAY.log
* 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:
- 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 like:
-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 like:
Luxi Sans-10
* Over time, fontconfig/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.
NOTE: An exception to the font subsystem usage outlined above is
OpenOffice.org (which uses its own font rendering technology).
If you wish to add new fonts to your Fedora Core 4test3 system, you
must be aware that the steps necessary depend on which font subsystem
is to use the new fonts. For the core X font subsystem, you must:
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):
ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale
mkfontdir /usr/share/fonts/local/
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
(Where 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 = ""
}
widget_class " *" style "user-font"
(Where represents a font specification in the
style used by traditional X applications, such as
"-adobe-helvetica-medium-r-normal-- *-120- *- *- *- *- *- *".)
=== Miscellaneous Notes ===
This section contains information related to packages that do not fit
in any of the proceeding categories.
== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
For an overview of orphaned packages, visit
[:Extras/OrphanedPackages:this list].
This section contains lists of packages that fit into the following
categories:
* Packages that have been added to Fedora Core 4test3
* Packages that have been moved out of Fedora Core 4test3
* Packages that have a changed version since Fedora Core 3
* Packages that have been deprecated, and may be removed from a future
release of Fedora Core
=== Packages Added ===
The following packages have been added to Fedora Core 4test3:
* ant-1.6.2-3jpp_2fc
* antlr-2.7.4-2jpp_1fc
* aqbanking-1.0.4beta-2
* aqhbci-1.0.2beta-2
* avalon-framework-4.1.4-2jpp_5fc
* avalon-logkit-1.2-2jpp_4fc
* bcel-5.1-1jpp_4fc
* classpath-inetlib-1.0-1jpp_1fc
* classpathx-jaf-1.0-2jpp_3fc
* classpathx-mail-1.0-3jpp_1fc
* compat-gcc-296-2.96-132.fc4
* compat-gcc-32-3.2.3-47.fc4
* compat-readline43-4.3-2
* cpufreq-utils-0.2-1.1.12
* cpuspeed-1.2.1-1.19
* cryptix-3.2.0-4jpp_1fc
* cryptix-asn1-20011119-4jpp_1fc
* cryptsetup-luks-1.0-1
* dcraw-0.0.20050227-1
* device-mapper-multipath-0.4.4-0.pre8.0
* dmidecode-2.6-1.13
* eclipse-3.1.0_fc-0.M5.17
* eclipse-bugzilla-0.1.0_fc-9
* eclipse-cdt-3.0.0_fc-0.M5.3
* eclipse-changelog-2.0.1_fc-19
* eclipse-pydev-0.9.0_fc-4
* evince-0.1.9-1
* fonts-chinese-2.15-1
* fonts-indic-1.9-2
* fonts-japanese-0.20050222-2
* fonts-korean-1.0.11-2
* gjdoc-0.7.3-1
* gnome-doc-utils-0.1.3-1
* gnome-menus-2.10.1-1
* gnome-python2-extras-2.10.0-2.1
* gnu-crypto-2.0.1-1jpp_1fc
* gnu.getopt-1.0.9-4jpp_1fc
* gwenhywfar-1.7.2-2
* hardlink-1.0-1.11
* iiimf-12.1.1-11.svn2435
* ipv6calc-0.48-3
* irqbalance-1.12-1.18
* jakarta-commons-beanutils-1.7.0-1jpp_1fc
* jakarta-commons-collections-3.1-1jpp_1fc
* jakarta-commons-daemon-1.0-2jpp_1fc
* jakarta-commons-dbcp-1.2.1-3jpp_1fc
* jakarta-commons-digester-1.6-2jpp_1fc
* jakarta-commons-el-1.0-2jpp_1fc
* jakarta-commons-fileupload-1.0-3jpp_1fc
* jakarta-commons-lang-2.0-2jpp_1fc
* jakarta-commons-launcher-0.9-3jpp_1fc
* jakarta-commons-logging-1.0.4-2jpp_1fc
* jakarta-commons-modeler-1.1-3jpp_1fc
* jakarta-commons-pool-1.2-2jpp_1fc
* jakarta-commons-validator-1.1.3-1jpp_1fc
* jakarta-taglibs-standard-1.1.1-4jpp_1fc
* java_cup-0.10-0.k.1jpp_2fc
* jdepend-2.6-2jpp_3fc
* jessie-1.0.0-3
* jlex-1.2.6-1jpp_2fc
* jsch-0.1.17-2jpp_1fc
* junit-3.8.1-3jpp_4fc
* jzlib-1.0.5-2jpp_1fc
* kdeaccessibility-3.4.0-1
* ksh-20050202-1
* latex2html-2002.2.1-1
* ldapjdk-4.17-1jpp_2fc
* libdbi-drivers-0.7.1-2
* libgconf-java-2.10.0-1
* libglade-java-2.9.92-1
* libgnome-java-2.9.92-1
* libgtk-java-2.6.1.1-1
* linux-atm-2.5.0-0.20050118.2
* lksctp-tools-1.0.2-5
* log4j-1.2.8-7jpp_3fc
* longrun-0.9-1.8
* lvm2-cluster-2.00.29-1.22.FC4
* mcelog-0.4-1.8
* microcode_ctl-1.11-1.21
* mod_jk-1.2.6-3jpp_1fc
* mx4j-2.1.0-1jpp_2fc
* mysqlclient10-3.23.58-5
* openhpi-2.0.3-2
* OpenIPMI-1.4.11-5
* openssl097a-0.9.7a-2
* oro-2.0.8-1jpp_2fc
* poppler-0.1.2-1
* puretls-0.9-0.b4.1jpp_2fc
* python-docs-2.4-102
* python-elementtree-1.2.6-4
* python-numeric-23.7-2
* python-sqlite-1.1.6-1
* python-twisted-1.3.0-4
* python-urlgrabber-2.9.6-1
* readahead-1.0-1.7
* regexp-1.3-1jpp_4fc
* rng-utils-2.0-1.5
* salinfo-0.5-1.4
* servletapi5-5.0.18-1jpp_3fc
* slib-3a1-2
* smartmontools-5.33-1.5
* sqlite-3.1.2-2
* struts11-1.1-1jpp_2fc
* system-config-lvm-0.9.22-1.0
* texi2html-1.76-2
* tomcat5-5.0.30-1jpp_2fc
* x86info-1.13-1.9
* xalan-j2-2.6.0-2jpp_1fc
* xen-2-20050403
* xerces-j2-2.6.2-4jpp_1fc
* xml-commons-1.0-0.b2.6jpp_5fc
* xml-commons-resolver-1.1-1jpp_4fc
=== Packages Moved Out Of Core ===
This is a new section to the release notes. This is based on a
treediff of dist-fc3 and dist-fc4 on 14-MAR-2005. The following
packages have been moved out of core from Fedora Core 4test3:
* abiword-2.0.12-3
* aiksaurus-1.2.1-2
* ash-0.3.8-20
* asp2php-0.76.18-3
* aspell-ia-0.50-1
* aumix-2.8-9
* balsa-2.2.4-1.FC3.1
* bluez-bluefw-1.0-6
* bonobo-1.0.22-9
* bzflag-1.10.6-2
* cdecl-2.5-30
* cdlabelgen-3.0.0-1
* cdp-0.33-32
* compat-gcc-8-3.3.4.2
* compat-pwdb-0.62-9
* comsat-0.17-11
* cproto-4.7c-3
* cryptsetup-0.1-4
* cyrus-imapd-2.2.6-2.FC3.6
* dbh-1.0.18-5
* dbskkd-cdb-1.01-21
* ddskk-12.2.0-4
* dietlibc-0.27-4
* diskcheck-1.6-2
* dmalloc-5.3.0-3
* exim-4.43-1
* flim-1.14.7-1
* fonts-bengali-0.1-3
* fonts-ja-8.0-16
* freeciv-1.14.2-1
* FreeWnn-1.10pl020-5
* fsh-1.2-5
* ftpcopy-0.6.2-7
* gcc4-4.0.0-0.8
* ggv-2.8.0-1
* giftrans-1.12.2-20
* Glide3-20010520-33
* gnome-vfs-1.0.5-21
* gnome-vfs-extras-0.2.0-9
* gnuchess-5.07-4
* gnumeric-1.2.13-6
* gpdf-2.8.0-5
* grip-3.2.0-3
* gv-3.5.8-29
* im-sdk-12.1-4
* jed-0.99.16-6
* jisksp14-0.1-16
* jisksp16-1990-0.1-16
* kappa20-0.3-15
* kdetoys-3.3.0-1
* kernel-utils-2.4-13.1.39
* kinput2-v3.1-23
* knm_new-1.1-16
* koffice-1.3.3-1
* lapack-3.0-25
* lesstif-0.93.36-6
* libesmtp-1.0.3r1-2
* libgda-1.0.4-3
* libgnomedb-1.0.4-3
* libtool-libs13-1.3.5-10
* libxfce4mcs-4.0.6-1
* libxfce4util-4.0.6-1
* libxfcegui4-4.0.6-1
* lilo-21.4.4-26
* Maelstrom-3.0.6-6
* MagicPoint-1.11b-1
* memprof-0.5.1-5
* mew-3.3-4
* miniChinput-0.0.3-58
* nabi-0.14-3
* namazu-2.0.13-3
* nautilus-media-0.8.1-3
* ncftp-3.1.8-2
* nedit-5.4-3
* octave-2.1.57-7
* Omni-0.9.1-7
* openhbci-0.9.17-1
* openssl096b-0.9.6b-19
* ots-0.4.2-2
* pan-0.14.2-8
* pccts-1.33mr33-11
* pdksh-5.2.14-30
* qmkbootdisk-1.0.2-3
* Regina-2.3-1
* routed-0.17-18
* skkinput-2.06.4-7
* splint-3.1.1-4
* sylpheed-0.9.12-1
* system-logviewer-0.9.11-1
* system-switch-im-0.1.2-3
* THE-3.1-2
* tora-1.3.14.1-2
* ttfonts-indic-1.6-1
* ttfonts-ja-1.2-36
* ttfonts-ko-1.0.11-32.2
* ttfonts-zh_CN-2.14-10
* ttfonts-zh_TW-2.11-28
* ttfprint-0.9-13
* tuxracer-0.61-28
* w3m-el-1.4.3-2
* wl-2.10.1-4
* x3270-3.3.2.p1-6
* xboard-4.2.7-6
* xcin-2.5.3.pre3-24
* xemacs-21.4.15-9
* xemacs-sumo-20040818-2
* xfce4-iconbox-4.0.6-2
* xfce4-panel-4.0.6-1
* xfce4-systray-4.0.6-2
* xfce-mcs-manager-4.0.6-2
* xfce-mcs-plugins-4.0.6-2
* xfce-utils-4.0.6-1
* xfdesktop-4.0.6-2
* xffm-4.0.6-1
* xffm-icons-4.0.6-2
* xfprint-4.0.6-2
* xfwm4-4.0.6-1
* xfwm4-themes-4.0.6-2
* xloadimage-4.1-32
* xmms-1.2.10-9
* xosview-1.8.2-1
* xsnow-1.42-15
* ytalk-3.1.2-1
== An Overview of the Fedora Project ==
The goal of the Fedora Project is to work with the Linux community to
build a complete, general purpose operating system exclusively from
open source software. Development will be done in a public forum. The
project will produce time-based releases of Fedora Core about 2-3
times a year, with a public release schedule. The Red Hat engineering
team will continue to participate in building Fedora Core and will
invite and encourage more outside participation than was possible in
the past. By using this more open process, we hope to provide an
operating system more in line with the ideals of free software and
more appealing to the open source community.
For more information, refer to the Fedora Project website:
[10]http://fedora.redhat.com/
In addition to the website, the following mailing lists are available:
* fedora-list at redhat.com -- For users of Fedora Core releases
* fedora-test-list at redhat.com -- For testers of Fedora Core test releases
* fedora-devel-list at redhat.com -- For developers, developers, developers
* fedora-docs-list at redhat.com -- For participants of the docs project
To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to -request (where is
one of the above list names.)
NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
rhl-devel-list, or rhl-docs-list, your subscriptions have been
retained.
The Fedora Project also includes an IRC (Internet Relay Chat)
channel. IRC is a real-time, text-based form of communication. With
it, you can have conversations with multiple people in an open channel
or chat with someone privately one-on-one.
To talk with other Fedora Project participants via IRC, access
freenode IRC network. Initially, you can use irc.freenode.net as the
IRC server, although you may decide to select a server that is
geographically closer to you. Refer to the freenode website
([11]http://www.freenode.net/) for more information. Fedora Project
participants frequent the #fedora channel, while Fedora Project
developers can often be found on the #fedora-devel channel. Some of
the larger projects may have their own channels as well; this
information can be found on the project pages.
NOTE: Red Hat has no control over the Fedora IRC channels or their content.
( x86 )
== References ==
Visible links
1. http://www.gnu.org/licenses/fdl.html
2. http://fedora.redhat.com/docs/selinux-faq/
3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
5. http://platan.vc.cvut.cz/ftp/pub/vmware/
6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
7. http://i2o.shadowconnect.com/
8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
9. http://people.redhat.com/~harald/udev.html
10. http://fedora.redhat.com/
11. http://www.freenode.net/
From fedora-docs-commits at redhat.com Wed May 4 01:12:31 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 3 May 2005 21:12:31 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.1,1.2
Message-ID: <200505040112.j441CVao019753@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19745
Modified Files:
fc4test3-relnotes
Log Message:
Release notes about audit daemon, changes to log locations, and enabling kernel auditing.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fc4test3-relnotes 3 May 2005 23:29:53 -0000 1.1
+++ fc4test3-relnotes 4 May 2005 01:12:29 -0000 1.2
@@ -72,9 +72,11 @@
NOTE: Fedora Core is not a supported product of Red Hat, Inc.
-For more information, refer to the Fedora Project overview later in this document.
+For more information, refer to the Fedora Project overview later in
+this document.
-The following topics related to Fedora Core 4test3 are covered in this document:
+The following topics related to Fedora Core 4test3 are covered in this
+document:
* Introduction (this section)
* Hardware requirements
@@ -257,7 +259,8 @@
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.
+NOTE: You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use
+this feature.
* Fedora Core 4test3 supports graphical FTP and HTTP
installations. However, due to the necessity of containing the
@@ -326,6 +329,30 @@
This section contains information related to basic system components.
+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'
+
slocate database
The database needed by the locate utility is no longer created by default.
@@ -590,7 +617,8 @@
must be aware that the steps necessary depend on which font subsystem
is to use the new fonts. For the core X font subsystem, you must:
-1. Create the /usr/share/fonts/local/ directory (if it doesn't already exist):
+1. Create the /usr/share/fonts/local/ directory (if it doesn't already
+ exist):
mkdir /usr/share/fonts/local/
@@ -654,6 +682,10 @@
This section contains information related to packages that do not fit
in any of the proceeding categories.
+ OpenOffice and upgrading test releases
+
+
+
== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
@@ -669,8 +701,8 @@
* Packages that have a changed version since Fedora Core 3
- * Packages that have been deprecated, and may be removed from a future
- release of Fedora Core
+ * Packages that have been deprecated, and may be removed from a
+ future release of Fedora Core
=== Packages Added ===
@@ -966,7 +998,8 @@
the larger projects may have their own channels as well; this
information can be found on the project pages.
-NOTE: Red Hat has no control over the Fedora IRC channels or their content.
+NOTE: Red Hat has no control over the Fedora IRC channels or their
+content.
( x86 )
From fedora-docs-commits at redhat.com Wed May 4 12:00:09 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 4 May 2005 08:00:09 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.2,1.3
Message-ID: <200505041200.j44C09QW031217@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31209
Modified Files:
fc4test3-relnotes
Log Message:
New Web server details - mod_perl and PHP release notes.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fc4test3-relnotes 4 May 2005 01:12:29 -0000 1.2
+++ fc4test3-relnotes 4 May 2005 12:00:07 -0000 1.3
@@ -475,6 +475,15 @@
This section contains information related to Web-related tools.
+mod_perl
+
+The "RC5" release of mod_perl 2.0 is now included; the API provided by
+this release is incompatible with previous 1.99_xx releases. Please
+refer to the following document for discussion of how to adapt code to
+use the new API:
+
+ http://perl.apache.org/docs/2.0/rename.html
+
php
Version 5.0 of PHP is now included, which includes a number of changes
@@ -484,6 +493,10 @@
http://www.php.net/manual/en/migration5.php
+The /usr/bin/php binary is now built using the "CLI" command-line
+SAPI, rather than the CGI SAPI. The CGI SAPI is now available as
+/usr/bin/php-cgi; this binary also includes FastCGI support.
+
The following extensions have been added:
* the "mysqli" extension, the newly MySQL interface designed
@@ -491,6 +504,12 @@
* the "soap" extension, which can be used to implement a SOAP server
or client
+The following extensions are now available as optional loadable
+extensions, rather than being built in to the php binaries:
+
+ * dba, now available in the php-dba package
+ * bcmath, now available in the php-bcmath package
+
=== Windows File Server ===
This section contains information related to Samba, software that
From fedora-docs-commits at redhat.com Wed May 4 12:21:14 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 4 May 2005 08:21:14 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.3,1.4
Message-ID: <200505041221.j44CLEJ3032224@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32216
Modified Files:
fc4test3-relnotes
Log Message:
Updates to new features and enhancements.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fc4test3-relnotes 4 May 2005 12:00:07 -0000 1.3
+++ fc4test3-relnotes 4 May 2005 12:21:12 -0000 1.4
@@ -166,9 +166,13 @@
* GCC 4.0
* GNOME 2.10
* KDE 3.4
- * Native Eclipse 3.1M5
+ * Native Eclipse 3.1M6 - Part of free Java stack
* MySQL 4.1
* PHP 5.0
+ * Xen 2 - Virtualization to run multiple versions of an OS
+ * GFS 6.1-0.pre22 - Cluster file system
+ * Evince 0.2.1 - Universal document viewer
+ * GDM 2.6 - Includes early login capability
* SELinux -- New daemons have been added to the targeted policy For
more information, refer to the SELinux FAQ at
@@ -388,50 +392,59 @@
This section contains the most elemental components of Fedora Core,
including the kernel.
- * In order to eliminate the redundancy inherent in providing a
- separate package for the kernel source code when that source code
- already exists in the kernel's .src.rpm file, Fedora Core 4test3
- no longer includes the kernel-source package. Users that require
- access to the kernel sources can find them in the kernel .src.rpm
- file. To create an exploded source tree from this file, perform
- the following steps (note that refers to the version
- specification for your currently-running kernel):
+yum
- 1. Obtain the kernel-.src.rpm file from one of the
- following sources:
+The sqllite database is now used by yum, and makes performance
+noticeably faster.
- * The SRPMS directory on the appropriate "SRPMS" CD iso image
+The Fedora Extras repository is now enabled by default.
- * The FTP site where you got the kernel package
+kernel source
- * By running the following command:
+In order to eliminate the redundancy inherent in providing a separate
+package for the kernel source code when that source code already
+exists in the kernel's .src.rpm file, Fedora Core 4test3 no longer
+includes the kernel-source package. Users that require access to the
+kernel sources can find them in the kernel .src.rpm file. To create an
+exploded source tree from this file, perform the following steps (note
+that refers to the version specification for your
+currently-running kernel):
- up2date --get-source kernel
+ 1. Obtain the kernel-.src.rpm file from one of the
+ following sources:
- 2. Install kernel-.src.rpm (given the default RPM
- configuration, the files this package contains will be
- written to /usr/src/redhat/)
+ * The SRPMS directory on the appropriate "SRPMS" CD iso image
- 3. Change directory to /usr/src/redhat/SPECS/, and issue the
- following command:
+ * The FTP site where you got the kernel package
- rpmbuild -bp --target= kernel.spec
+ * By running the following command:
- (Where is the desired target architecture.)
+ up2date --get-source kernel
- On a default RPM configuration, the kernel tree will be
- located in /usr/src/redhat/BUILD/.
+ 2. Install kernel-.src.rpm (given the default RPM
+ configuration, the files this package contains will be written to
+ /usr/src/redhat/)
- 4. In resulting tree, the configurations for the specific
- kernels shipped in Fedora Core 4test3 are in the /configs/
- directory. For example, the i686 SMP configuration file is
- named /configs/kernel--i686-smp.config. Issue the
- following command to place the desired configuration file
- in the proper place for building:
+ 3. Change directory to /usr/src/redhat/SPECS/, and issue the
+ following command:
+
+ rpmbuild -bp --target= kernel.spec
+
+ (Where is the desired target architecture.)
+
+ On a default RPM configuration, the kernel tree will be located
+ in /usr/src/redhat/BUILD/.
+
+ 4. In resulting tree, the configurations for the specific kernels
+ shipped in Fedora Core 4test3 are in the /configs/
+ directory. For example, the i686 SMP configuration file is named
+ /configs/kernel--i686-smp.config. Issue the following
+ command to place the desired configuration file in the proper
+ place for building:
cp ./.config
- 5. Issue the following command:
+ 5. Issue the following command:
make oldconfig
From fedora-docs-commits at redhat.com Wed May 4 12:31:02 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 4 May 2005 08:31:02 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.4,1.5
Message-ID: <200505041231.j44CV2wI032387@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32379
Modified Files:
fc4test3-relnotes
Log Message:
LinuxThreads are heavily deprecated, as discussed in this new release note originally authored by Ulrich Drepper.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fc4test3-relnotes 4 May 2005 12:21:12 -0000 1.4
+++ fc4test3-relnotes 4 May 2005 12:30:59 -0000 1.5
@@ -91,23 +91,23 @@
The following information represents the minimum hardware requirements
necessary to successfully install Fedora Core 4test3.
-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.
+ 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.
=== CPU Requirements ===
This section lists the CPU specifications required by Fedora Core
4test3.
-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.
+ 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.
* Minimum: Pentium-class
@@ -127,15 +127,15 @@
This section lists the disk space required to install Fedora Core 4test3.
-Note
+ Note
-The disk space requirements listed below represent the disk space
-taken up by Fedora Core 4test3 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.
+ The disk space requirements listed below represent the disk space
+ taken up by Fedora Core 4test3 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
@@ -235,18 +235,19 @@
(the Fedora Core installation program) and installing Fedora Core
4test3 in general.
-Note
+ Note
-If you intend to download the Fedora Core 4test3 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.
+ If you intend to download the Fedora Core 4test3 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.
+
Anaconda Notes
* The Fedora Core installation program has the ability to test the
@@ -310,15 +311,15 @@
RPMs. This configuration is not supported. You have several
choices in resolving this issue:
-1) You may remove Ximian GNOME from your system prior to upgrading to
- Fedora Core.
+ 1) You may remove Ximian GNOME from your system prior to upgrading
+ to Fedora Core.
-2) You may upgrade your system, and then immediately reinstall Ximian
- GNOME.
+ 2) You may upgrade your system, and then immediately reinstall
+ Ximian GNOME.
-3) You may upgrade your system, and then immediately remove all
- remaining Ximian RPMs, replacing them with the corresponding Fedora
- Core RPMs.
+ 3) 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.
@@ -333,6 +334,7 @@
This section contains information related to basic system components.
+
auditd and log files
The audit daemon, auditd, is now enabled by default. When auditd is
@@ -357,12 +359,60 @@
'auditctl -e 1'
+
+LinuxThreads v. NPTL
+
+As the next step in removing support for the obsolete LinuxThreads
+library, code compiled and linked on FC4 now automatically uses the NPTL
+headers and libraries.
+
+In previous releases, since Red Hat Linux 9, the default was to use
+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 FC4 it is still possible to create code using the LinuxThreads
+definitions. For this the linuxthreads-devel package must be
+installed and
+
+ -I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads
+
+must be passed to the compiler.
+
+At runtime, it used to be possible to use the LD_ASSUME_KERNEL
+environment variable to select the appropriate version of glibc and the
+libpthread DSO. Now it is additionally necessary to specify
+
+ LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads
+
+in the environment. This is because the runtime libraries have also
+been moved out of the way. There might 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.
+
+ 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.
+
+
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.
+
openssh
The version of OpenSSH in Fedora Core 4test3 contains OpenSSH 3.9
@@ -392,6 +442,7 @@
This section contains the most elemental components of Fedora Core,
including the kernel.
+
yum
The sqllite database is now used by yum, and makes performance
@@ -399,6 +450,7 @@
The Fedora Extras repository is now enabled by default.
+
kernel source
In order to eliminate the redundancy inherent in providing a separate
@@ -488,6 +540,7 @@
This section contains information related to Web-related tools.
+
mod_perl
The "RC5" release of mod_perl 2.0 is now included; the API provided by
@@ -497,6 +550,7 @@
http://perl.apache.org/docs/2.0/rename.html
+
php
Version 5.0 of PHP is now included, which includes a number of changes
@@ -528,6 +582,7 @@
This section contains information related to Samba, software that
makes it possible to share files between Linux and Windows systems.
+
samba
Browsing of Windows shares (also known as SMB browsing) fails on
@@ -559,6 +614,7 @@
This section contains information related to netatalk, software that
makes it possible to share files between Linux and Macintosh systems.
+
netatalk
The 2.x version of netatalk uses a different method to store resource
@@ -649,8 +705,8 @@
must be aware that the steps necessary depend on which font subsystem
is to use the new fonts. For the core X font subsystem, you must:
-1. Create the /usr/share/fonts/local/ directory (if it doesn't already
- exist):
+1. Create the /usr/share/fonts/local/ directory (if it does not
+ already exist):
mkdir /usr/share/fonts/local/
From fedora-docs-commits at redhat.com Wed May 4 12:47:52 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 4 May 2005 08:47:52 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.5,1.6
Message-ID: <200505041247.j44Clqmf032449@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32441
Modified Files:
fc4test3-relnotes
Log Message:
Updated and possibly accurate list of targeted daemons. It is certain that at least a few of those in the list are _not_ targeted daemons but merely TE files to enable policy to work smoothly, e.g. when switching from targeted to strict.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fc4test3-relnotes 4 May 2005 12:30:59 -0000 1.5
+++ fc4test3-relnotes 4 May 2005 12:47:50 -0000 1.6
@@ -174,61 +174,103 @@
* Evince 0.2.1 - Universal document viewer
* GDM 2.6 - Includes early login capability
- * SELinux -- New daemons have been added to the targeted policy For
- more information, refer to the SELinux FAQ at
- http://fedora.redhat.com/docs/selinux-faq/ .
+ * SELinux -- New daemons have been added to the targeted policy.
+ http://fedora.redhat.com/docs/selinux-faq/ . This is a list of
+ daemons protected by the targeted policy:
+
+ * NetworkManager
* amanda
* apache
+ * apmd
+ * arpwatch
+ * auditd
+ * bluetooth
+ * canna
+ * cardmgr
+ * checkpolicy
* chkpwd
+ * compat
+ * comsat
+ * consoletype
+ * cpucontrol
+ * cpuspeed
+ * crond
* cups
+ * cvs
+ * cyrus
+ * dbskkd
+ * dbusd
* dhcpc
* dhcpd
- * dictd
+ * dictd
+ * dmidecode
* dovecot
* fingerd
+ * fsadm
* ftpd
+ * getty
+ * hald
+ * hostname
+ * hotplug
* howl
+ * hwclock
* i18n_input
* ifconfig
- * init
- * initrc
* inetd
+ * init
+ * initrc
* innd
* kerberos
+ * klogd
* ktalkd
+ * kudzu
* ldconfig
- * login
+ * load_policy
+ * login
* lpd
* mailman
* modutil
* mta
* mysqld
- * NetworkManager
- * named
+ * named
+ * netutils
* nscd
* ntpd
* portmap
* postgresql
+ * pppd
* privoxy
* radius
- * radvd
+ * radvd
+ * restorecon
* rlogind
* rpcd
+ * rpm
* rshd
* rsync
* samba
+ * saslauthd
+ * sendmail
+ * setfiles
* slapd
* snmpd
- * squid
+ * squid
+ * ssh
* stunnel
* syslogd
* telnetd
* tftpd
+ * udev
+ * updfstab
+ * uucpd
+ * webalizer
* winbind
+ * xdm
* ypbind
- * ypserv
+ * ypserv
* zebra
+
== Installation-Related Notes ==
This section outlines anything noteworthy that is related to Anaconda
From fedora-docs-commits at redhat.com Wed May 4 13:08:22 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 4 May 2005 09:08:22 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.6,1.7
Message-ID: <200505041308.j44D8Mqb000940@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv932
Modified Files:
fc4test3-relnotes
Log Message:
Updating packakes added and removed from Core.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fc4test3-relnotes 4 May 2005 12:47:50 -0000 1.6
+++ fc4test3-relnotes 4 May 2005 13:08:20 -0000 1.7
@@ -836,49 +836,62 @@
=== Packages Added ===
-The following packages have been added to Fedora Core 4test3:
+The following packages have been added to Fedora Core 4test3. This is
+based on a treediff of dist-fc3 and dist-fc4 on 04-MAY-2005:
- * ant-1.6.2-3jpp_2fc
+ * ant-1.6.2-3jpp_5fc
* antlr-2.7.4-2jpp_1fc
* aqbanking-1.0.4beta-2
* aqhbci-1.0.2beta-2
+ * aspell-is-0.51.1-1
* avalon-framework-4.1.4-2jpp_5fc
* avalon-logkit-1.2-2jpp_4fc
* bcel-5.1-1jpp_4fc
- * classpath-inetlib-1.0-1jpp_1fc
+ * ccs-0.25-0.1
* classpathx-jaf-1.0-2jpp_3fc
* classpathx-mail-1.0-3jpp_1fc
+ * cman-1.0-0.pre33.2
+ * cman-kernel-2.6.11.3-20050425.154843.FC4.5
* compat-gcc-296-2.96-132.fc4
* compat-gcc-32-3.2.3-47.fc4
* compat-readline43-4.3-2
- * cpufreq-utils-0.2-1.1.12
- * cpuspeed-1.2.1-1.19
+ * cpufreq-utils-0.2-1.1.14
+ * cpuspeed-1.2.1-1.20
* cryptix-3.2.0-4jpp_1fc
* cryptix-asn1-20011119-4jpp_1fc
* cryptsetup-luks-1.0-1
* dcraw-0.0.20050227-1
- * device-mapper-multipath-0.4.4-0.pre8.0
- * dmidecode-2.6-1.13
- * eclipse-3.1.0_fc-0.M5.17
- * eclipse-bugzilla-0.1.0_fc-9
- * eclipse-cdt-3.0.0_fc-0.M5.3
- * eclipse-changelog-2.0.1_fc-19
- * eclipse-pydev-0.9.0_fc-4
- * evince-0.1.9-1
- * fonts-chinese-2.15-1
+ * device-mapper-multipath-0.4.4-2.0
+ * dlm-1.0-0.pre21.2
+ * dlm-kernel-2.6.11.3-20050425.154843.FC4.6
+ * dmidecode-2.6-1.14
+ * eclipse-3.1.0_fc-0.M6.14
+ * eclipse-bugzilla-0.1.0_fc-14
+ * eclipse-cdt-3.0.0_fc-0.M6.5
+ * eclipse-changelog-2.0.1_fc-21
+ * eclipse-pydev-0.9.3_fc-7
+ * evince-0.2.1-1
+ * fence-1.27-1
+ * fonts-chinese-2.15-2
* fonts-indic-1.9-2
- * fonts-japanese-0.20050222-2
- * fonts-korean-1.0.11-2
- * gjdoc-0.7.3-1
- * gnome-doc-utils-0.1.3-1
- * gnome-menus-2.10.1-1
+ * fonts-japanese-0.20050222-3
+ * fonts-korean-1.0.11-4
+ * GFS-6.1-0.pre22.1
+ * GFS-kernel-2.6.11.4-20050503.144108.FC4.1
+ * gjdoc-0.7.4-4
+ * gnbd-1.0-0.pre13.1
+ * gnbd-kernel-2.6.11.2-20050420.133124.FC4.10
+ * gnome-doc-utils-0.2.0-2
+ * gnome-menus-2.10.1-3
* gnome-python2-extras-2.10.0-2.1
- * gnu-crypto-2.0.1-1jpp_1fc
+ * gnu-crypto-2.0.1-1jpp_3fc
* gnu.getopt-1.0.9-4jpp_1fc
+ * gulm-1.0-0.pre28.3
* gwenhywfar-1.7.2-2
- * hardlink-1.0-1.11
- * iiimf-12.1.1-11.svn2435
- * ipv6calc-0.48-3
+ * hardlink-1.0-1.13
+ * iddev-1.9-19
+ * iiimf-12.2-0.7.svn2578
+ * ipv6calc-0.48-5
* irqbalance-1.12-1.18
* jakarta-commons-beanutils-1.7.0-1jpp_1fc
* jakarta-commons-collections-3.1-1jpp_1fc
@@ -896,37 +909,45 @@
* jakarta-taglibs-standard-1.1.1-4jpp_1fc
* java_cup-0.10-0.k.1jpp_2fc
* jdepend-2.6-2jpp_3fc
- * jessie-1.0.0-3
+ * jessie-1.0.0-6
* jlex-1.2.6-1jpp_2fc
- * jsch-0.1.17-2jpp_1fc
+ * jsch-0.1.18-1jpp_1fc
* junit-3.8.1-3jpp_4fc
* jzlib-1.0.5-2jpp_1fc
* kdeaccessibility-3.4.0-1
* ksh-20050202-1
* latex2html-2002.2.1-1
* ldapjdk-4.17-1jpp_2fc
- * libdbi-drivers-0.7.1-2
- * libgconf-java-2.10.0-1
- * libglade-java-2.9.92-1
- * libgnome-java-2.9.92-1
- * libgtk-java-2.6.1.1-1
+ * libdbi-drivers-0.7.1-3
+ * libgconf-java-2.10.1-1
+ * libglade-java-2.10.1-3
+ * libgnome-java-2.10.1-1
+ * libgtk-java-2.6.2-1
* linux-atm-2.5.0-0.20050118.2
* lksctp-tools-1.0.2-5
* log4j-1.2.8-7jpp_3fc
- * longrun-0.9-1.8
- * lvm2-cluster-2.00.29-1.22.FC4
+ * longrun-0.9-1.9
+ * lvm2-cluster-2.01.09-2.1
+ * magma-1.0-0.pre21.4
+ * magma-plugins-1.0-0.pre16.11
* mcelog-0.4-1.8
* microcode_ctl-1.11-1.21
- * mod_jk-1.2.6-3jpp_1fc
- * mx4j-2.1.0-1jpp_2fc
- * mysqlclient10-3.23.58-5
+ * mod_jk-1.2.6-3jpp_2fc
+ * mx4j-2.1.0-1jpp_5fc
+ * mysqlclient10-3.23.58-6
* openhpi-2.0.3-2
* OpenIPMI-1.4.11-5
* openssl097a-0.9.7a-2
* oro-2.0.8-1jpp_2fc
- * poppler-0.1.2-1
+ * perl-Archive-Zip-1.14-1
+ * perl-Carp-Clan-5.3-1
+ * perl-IO-String-1.06-3
+ * perl-IO-Zlib-1.04-4
+ * perl-Net-Telnet-3.03-4
+ * pm-utils-0.01-1
+ * poppler-0.3.0-2
* puretls-0.9-0.b4.1jpp_2fc
- * python-docs-2.4-102
+ * python-docs-2.4.1-1
* python-elementtree-1.2.6-4
* python-numeric-23.7-2
* python-sqlite-1.1.6-1
@@ -934,27 +955,27 @@
* python-urlgrabber-2.9.6-1
* readahead-1.0-1.7
* regexp-1.3-1jpp_4fc
- * rng-utils-2.0-1.5
+ * rgmanager-1.9.31-0
+ * rng-utils-2.0-1.6
* salinfo-0.5-1.4
- * servletapi5-5.0.18-1jpp_3fc
* slib-3a1-2
* smartmontools-5.33-1.5
- * sqlite-3.1.2-2
- * struts11-1.1-1jpp_2fc
- * system-config-lvm-0.9.22-1.0
+ * sqlite-3.1.2-3
+ * struts11-1.1-1jpp_4fc
+ * system-config-lvm-0.9.25-1.0
* texi2html-1.76-2
- * tomcat5-5.0.30-1jpp_2fc
- * x86info-1.13-1.9
+ * tomcat5-5.0.30-5jpp_1fc
+ * x86info-1.13-1.10
* xalan-j2-2.6.0-2jpp_1fc
- * xen-2-20050403
- * xerces-j2-2.6.2-4jpp_1fc
- * xml-commons-1.0-0.b2.6jpp_5fc
+ * xen-2-20050424
+ * xerces-j2-2.6.2-4jpp_4fc
+ * xml-commons-1.0-0.b2.6jpp_10fc
* xml-commons-resolver-1.1-1jpp_4fc
=== Packages Moved Out Of Core ===
This is a new section to the release notes. This is based on a
-treediff of dist-fc3 and dist-fc4 on 14-MAR-2005. The following
+treediff of dist-fc3 and dist-fc4 on 04-MAY-2005. The following
packages have been moved out of core from Fedora Core 4test3:
* abiword-2.0.12-3
@@ -1002,10 +1023,12 @@
* grip-3.2.0-3
* gv-3.5.8-29
* im-sdk-12.1-4
+ * jcode.pl-2.13-11
* jed-0.99.16-6
* jisksp14-0.1-16
* jisksp16-1990-0.1-16
* kappa20-0.3-15
+ * katana-2.0.0-1
* kdetoys-3.3.0-1
* kernel-utils-2.4-13.1.39
* kinput2-v3.1-23
@@ -1081,6 +1104,7 @@
* xsnow-1.42-15
* ytalk-3.1.2-1
+
== An Overview of the Fedora Project ==
The goal of the Fedora Project is to work with the Linux community to
From fedora-docs-commits at redhat.com Wed May 4 13:19:14 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 4 May 2005 09:19:14 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.7,1.8
Message-ID: <200505041319.j44DJEGR001029@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1021
Modified Files:
fc4test3-relnotes
Log Message:
This is likely to be the relnotes that goes into FC4test3.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fc4test3-relnotes 4 May 2005 13:08:20 -0000 1.7
+++ fc4test3-relnotes 4 May 2005 13:19:12 -0000 1.8
@@ -1,4 +1,4 @@
-== Fedora Core 4test3 Release Notes ==
+= Fedora Core 4test3 Release Notes =
Copyright (c) 2005 Red Hat, Inc.
@@ -518,6 +518,8 @@
2. Install kernel-.src.rpm (given the default RPM
configuration, the files this package contains will be written to
/usr/src/redhat/)
+
+ rpm -ivh kernel-.src.rpm
3. Change directory to /usr/src/redhat/SPECS/, and issue the
following command:
From fedora-docs-commits at redhat.com Wed May 4 18:14:23 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 4 May 2005 14:14:23 -0400
Subject: fedora-docs/release-notes fc4test3-relnotes,1.8,1.9
Message-ID: <200505041814.j44IENvN011943@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11935
Modified Files:
fc4test3-relnotes
Log Message:
Guess the problem with openoffice.org continues for now ... better safe than sorry.
Index: fc4test3-relnotes
===================================================================
RCS file: /cvs/docs/fedora-docs/release-notes/fc4test3-relnotes,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fc4test3-relnotes 4 May 2005 13:19:12 -0000 1.8
+++ fc4test3-relnotes 4 May 2005 18:14:20 -0000 1.9
@@ -816,7 +816,14 @@
OpenOffice and upgrading test releases
+If you choose to go counter to the recommendation to *not* upgrade
+from a previous test release, you may encounter a problem with
+OpenOffice following the upgrade.
+To resolve this, you must do the following command *before* doing the
+upgrade:
+
+ rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap
== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
From fedora-docs-commits at redhat.com Thu May 5 19:03:59 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 5 May 2005 15:03:59 -0400
Subject: fedora-docs/mirror-tutorial - New directory
Message-ID: <200505051903.j45J3xa4008552@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8546/mirror-tutorial
Log Message:
Directory /cvs/docs/fedora-docs/mirror-tutorial added to the repository
From fedora-docs-commits at redhat.com Thu May 5 19:04:46 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 5 May 2005 15:04:46 -0400
Subject: fedora-docs/mirror-tutorial Makefile, NONE,
1.1 mirror-tutorial-en.xml, NONE, 1.1
Message-ID: <200505051904.j45J4kN4008575@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/fedora-docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8568
Added Files:
Makefile mirror-tutorial-en.xml
Log Message:
These should be the latest changes I made to Paul's original, hopefully the diff is still sane.
--- NEW FILE Makefile ---
###############################################################################
# Makefile for RHLP docs project
# Created by: Tammy Fox
# Last edited by: Tammy Fox
# WARNING: need passivetex 1.24 for pdf generation to work
# License: GPL
# Copyright 2003 Tammy Fox, Red Hat, Inc.
###############################################################################
XSLPDF = ../xsl/main-pdf.xsl
XSLHTML = ../xsl/main-html.xsl
LANG = en
DOCNAME = mirror-tutorial-$(LANG)
XMLFILE = $(DOCNAME).xml
######################################################
html:
@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
@mkdir -p $(DOCNAME)/stylesheet-images
@cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images
@cp ../css/fedora.css $(DOCNAME)
pdf-%:
@xmlto pdf -x $(XSLPDF) $(XMLFILE)
######################################################
clean:
@rm -rfv *.html *.pdf *.tex $(DOCNAME)
--- NEW FILE mirror-tutorial-en.xml ---
%FEDORA-ENTITIES-EN;
]>
Mirror Tutorial
2004
Paul W. Frields
Frields
Paul
W.
&LEGALNOTICE;
0.22004-08-31PaulWFrields
Initial version for editorial process.
0.212004-09-02PaulWFrields
Revised screen sections to use inline tags as discussed on
fedora-docs-list; minor error corrections.
0.222004-09-06PaulWFrields
Style editing.
0.232004-09-08PaulWFrields
Additional style editing.
IntroductionPurpose
This tutorial presents a number of related topics that allow an
administrator to seamlessly integrate mirroring and update services for
&FC;. These services are used to provision a classroom, laboratory, or
office. These service provisions also increase ease of use and enhance
user experience, adding to the perceived value of non-proprietary
operating systems and software.
A note about &FC; and this document
This document applies to &FC; &FCVER;, which may not be the newest
release of &FC;. Find more information about the newest version at
&FP-URL;.
Audience
You will find this tutorial more useful if you are a system
administrator, or a &FC; power user familiar with the
following topics:
&FC; system installation
Basic Internet protocols (HTTP/Web, FTP)
Using a command line interface
About Mirrors
A mirrormirror is a server that
provides a copy of one or more collections of files. Mirroring a site
reduces traffic to the original source site, thus spreading the stress
and bandwidth costs of many users across many sites. Side benefits of
running a local mirror include very fast access through the local
network, providing custom services to local users, and increasing your
skills in managing Internet services.
The site from which you retrieve files to build your mirror is called an
upstream mirrormirrorupstream. If possible, choose an upstream mirror that is located
close to you geographically. This reduces unnecessary traffic across
transcontinental sections of the Internet, where bandwidth is limited
and expensive.
Additional Resources
For more information on installing &FC; see the &FC; &IG;. For more information on basic Internet protocols, see
http://library.albany.edu/internet/internet.html,
or search Google at http://www.google.com/. For more
general information about mirrors, see http://en.wikipedia.org/wiki/Mirror_(computing).
Acknowledgements
Karsten Wade provided editorial services, keeping the style crisp and
consistent.
Planning and Setup
A mirrormirror is a server that provides
a copy of one or more collections of files. Mirroring a site reduces
traffic to the original source site, thus spreading the stress and
bandwidth costs of many users across many sites. Side benefits of running
a local mirror include very fast access through the local network,
providing custom services to local users, and increasing your skills in
managing Internet services.
The upstream mirrormirrorupstream is the site you retrieve
files from to build your mirror. If possible, choose an upstream mirror
that is located close to you geographically. This reduces unnecessary
traffic across transcontinental sections of the Internet, where bandwidth
is limited and expensive.
The Distribution Structure
The &FED; distributiondistribution, which is the collection of all &FED;-related files, uses
the directory tree in . It may
include multiple versions of &FC;. The tree design makes trimming of
unnecessary or undesired files easier. When setting up a mirror,
duplicate this tree exactly, or as closely as possible. Doing so makes
automating nightly updates easier.
Fedora directory treefedora
+-- linux
+-- core
|-- 1
| ...
+-- &FCVER;
| +-- SRPMS
| +-- i386
| | +-- debug
| | +-- iso
| | +-- os
| | +-- Fedora
| | +-- SRPMS
| | +-- images
| | +-- isolinux
| +-- x86_64
+-- development
| ...
+-- test
| ...
+-- updates
+-- 1
| ...
+-- &FCVER;
| +-- SRPMS
| +-- i386
| +-- x86_64
+-- testing
+-- 1
| ...
+-- &FCVER;
+-- SRPMS
+-- i386
+-- x86_64Naming conventions
Throughout the rest of the document,
/var/ftp/pub/mirror represents the folder where
all your mirrored files are stored. You may substitute a different
location. This location simplifies sharing your mirror, due to the
shipping configuration of &FC;. See
for more information. The site name
mirror.example.com represents the
upstream mirror.
The
fedora/linux/core/&FCVER;/arch/os
directory contains a copy of all the original distribution files for
&FC; &FCVER;. They are the same files found on the CD-ROM version of the
distribution. The &FED; subfolder contains all the
files that are necessary for installation, including the entire
collection of &FC; RPM packages. The images folder
contains copies of any floppy diskette or CD-ROM images that boot a
system into installation or rescue modes. The
fedora/linux/core/&FCVER;/arch/iso
folder contains images of the CD-ROM version of the distribution.
RPM packagesRPMRPM, originally the Red Hat Package Manager, now the RPM
Package Manager, is not just a file format. RPM is also a system which
tracks and interconnects software and version information. The RPM
system is quite popular, and many other Linux distributions use RPM as
well. Read more information on RPM at http://www.rpm.org/. This document
contains helpful hints on making the most of RPM, in and
.
The SRPMS folders under architecture-specific
branches are links which point to the main SRPMS
folder for that distribution. For example,
fedora/linux/core/2/i386/os/SRPMS is a link which
points to fedora/linux/core/2/SRPMS.
A &FED; mirror consists of at least the original ISO images
or the distribution files. If possible, include
both, provided you have sufficient disk space and/or bandwidth.
Copying the Original Distribution
If you already have reliable CD-ROM installation discs of a
distribution, reduce your initial bandwidth and time spent mirroring by
copying the files from the discs to your server. Copy all files from
Installation Disc 1 into the
fedora/linux/core/&FCVER;/arch/os
folder. Then copy all files from the &FED; folder
of each of the remaining installation discs into the
fedora/linux/core/&FCVER;/arch/os/&FED;
folder on the server.
Copy all the files from the SRPMS folder on each of
the Sources discs to the
fedora/linux/core/&FCVER;/SRPMS folder on the
server. Make a link in the os folder that occurs
under each architecture. Follow this example:
cd /var/ftp/pub/mirror/fedora/linux/core/&FCVER;/i386/os/Fedora
ln ../../SRPMS SRPMS
The documentation for anacondaanaconda, the &FC; installation program, calls this directory
structure an exploded treeexploded tree. This is because the package data on each CD is extracted,
or exploded, to a large directory tree with a predetermined structure.
The anaconda installer expects this structure
to some extent.
If you only include CD images, create a mirror
suitable for installation services by mounting each CD image under the
arch/os/ directory. Make
a directory for each disc, naming them disc1,
disc2, and so on. Mount each disc on the
appropriate folder, and add entries to /etc/fstab
to perform this mount automatically in case of a reboot. Each entry
looks like this:
/path/i386/iso/FC&FCVER;-i386-disc1.iso /path/i386/os/disc1 iso9660 defaults 0 0
The anaconda application automatically
detects these folders and uses them properly. In addition, system
configuration tools such as
system-config-packages also continue to work
properly when pointed at the parent of the ISO image mount points.
There are drawbacks to using CD ISO images in this fashion. For
instance, no one directory contains the entire distribution of RPM
packages. Soft links circumvent this problem, but your server security
policies may not permit them. &FC; also comes in a ISO format DVD image,
which alleviates this problem. Users who do not have DVD burning
hardware, however, cannot use this image to make discs for their own
use.
Trimming Branches
You may omit almost any branch of the tree that you do not plan to use.
Consider carefully the impact of excluding that folder. Branches you
might trim from your mirror include:
Older versions of &FC; (any numbered directory).
Before you exclude an old version, ensure this does not adversely
affect any of your users. These adverse affects can come in many
forms. For example, the level of support for certain hardware
sometimes changes between releases of &FC;. Users who cannot
install a previous version may not be able to use &FC;. Your users
might need to perform software-related tasks such as building
packages for different &FC; releases. Always remain aware of the
needs of your users during the planning stage.
Folders for architectures your site does not support.
If you do not have any x86-64 hosts to support, trimming these
folders eliminates several gigabytes of extra files. If you
support x86-64 hosts later, though, you must restore mirroring of
these branches.
The development folder (formerly
rawhide).
This folder contains all the latest bleeding-edge packages from
the &FP;. If you participate in active &FED; development, you
should not trim this branch. &FED; development moves at a rapid
pace and requires frequent updates to the latest development
package versions. However, the frequent updates cause your mirror
to download significant amounts of material during the regular
update cycle.
The testing folders.
These branches contain updates that are being subjected to quality
assurance through public testing, as well as the test or
pre-release versions of the &FC;
distribution. The testing folder under the
main core tree is where test versions of the
distribution, such as &FC; &FCTESTVER;, are kept. (Users of &FC;
test distributions are often directed to use the
development branch to update packages.) The
testing folder, under
updates, contains package updates that have
not yet passed the public testing phase.
The debug folders.
These folders contain packages that enable developers and skilled
users to interpret data created when a program crashes or
encounters a bug. If you participate actively in &FED;
development, you should not trim these folders. If you trim this
branch, you may still download individual packages on an
basis from a nearby public mirror site.
The SRPMS folders (and links
thereto).
These folders contain the original source for all the binary RPM
packages in the distribution. You may download these packages on
an ad hoc basis if you need to save space on your local mirror.
Unless your site closely manages workstation configuration, you should
probably not trim any of the updates branches for
the distributions you support. These locations contain packages handling
bug fixes, security patches, and errata updates which your users
probably want.
Downloading the Files
Locate a public mirror site for &FC; by referring to the main project
site's mirror page, &FDP-URL;. Once you have selected a nearby mirror
site, note what services it offers (FTP, HTTP, and/or rsync). A mirror
is usually servicing a large number of users. Choose off-peak hours,
when possible, to download a large set of files. Be aware of any
timezone differences when estimating off-peak hours.
Download Using HTTP or FTP
To download via HTTP or FTP, use the wget command.
wget recurses subdirectories automatically and
pulls down entire trees of data with a single command. If you are not
careful, however, it is possible to pull down much more data than you
intended. The following commands mirror the entire current &FC;
distribution:
cd /var/ftp/pub/mirror
wget --mirror -np -nH --cut-dirs=2 http://mirror.example.com/pub/mirror/fedora/linux/core/&FCVER;/
Note the options used above:
turns on recursion (descends into all
subdirectories), and duplicates file timestamps;
prevents wget from
ascending into the parent directory;
prevents wget from
writing a directory named after the host (in this case,
mirror.example.com);
truncates the first n directories in
the path. In the example above, --cut-dirs=2
prevents wget from writing the
/pub/mirror
portion of the path into your mirror.
The same syntax works for both HTTP and FTP mirrors. It is possible
that you may download some extraneous files if the HTTP site formats
its pages for browser viewing. These files can be safely deleted, but
return each time the mirror updates unless you exclude them using
special options. See the wget man pages for more
information.
The rsync Command
Use the rsync command to synchronize a set of files
and/or directories with a remote host. It operates in much the same
way as rcp, but it is usually faster. One reason
for the speed is that rsync has a special protocol
that evaluates and skips files (or portions of files) that are already
downloaded.
Begin by identifying the modules available on the upstream mirror site
you have chosen. Note that the double colon
:: is always used after the host name
to separate it from the rest of the rsync path. The
following command generates a list of modules
on the upstream mirror.
rsync mirror.example.org::
These modules are roughly equivalent to top-level directories, and
they follow the same rules. To list any subdirectory of the upstream
mirror, add the directory path to the command above. For example, on
many mirrors, the fedora-linux-core module is
equivalent to the fedora/linux/core path found at
the &FP; main download server. To list the contents of the &FC;
&FCVER; distribution folder on the upstream server, issue the
following command. Do not forget the trailing slash
/. Without it, you only receive a
listing of a folder name that matches the last component of the remote
path.
rsync mirror.example.org::fedora-linux-core/&FCVER;/Downloading Using rsync
To download via rsync, add a destination path on
your system to the end of the command line. The resulting tree of
files from the listing you perform are downloaded to the local path
you specify. Remember, if you leave off the trailing slash on the
remote path, then the last component of that path is created as a new
folder inside the target directory, and its contents are copied.
rsync filehouse.example.org::files/misc/ /var/ftp/pub/misc/
When downloading using rsync for mirror purposes,
use some of the command line switches to improve performance and
feedback. The switches enable the following
rsync features:
-P — recover partially-downloaded files,
and show a progress meter
-H — preserve hard links
-a — recurse all directories, and preserve
as much file information as possible, including timestamps,
ownership, permissions, device files (if you are running as root),
and soft links
-v — give verbose feedback to the screen
Remove the -v switch if you run this mirroring
process as part of a script, or have no need to monitor progress. The
following example mirrors all available versions of &FC; from an
upstream site.
Example command downloads many gigabytes of files
This command downloads many gigabytes of files, and is intended for
use as an example only. Do not run this command if you do not
understand the consequences.
rsync -PHav mirror.example.org::fedora-linux-core/&FCVER;/ /var/ftp/pub/mirror/fedora/core/&FCVER;
The -n switch performs a dry run
using the other given parameters. Use this switch to test any
rsync command if you are unsure what files you will
receive. See also .
The -z switch enables compression during the
rsync process. The server compresses data before
transmission, and the client decompresses the data before writing it
to disk.
Compression using rsync
The vast majority of the &FC; distribution consists of RPM files,
which are already compressed data. Therefore, additional compression
does not save time, and instead induces an unnecessary load on the
upstream mirror CPU. As a courtesy, do not use the
-z switch for this purpose.
The next section features some additional switches that can be used to
automatically trim branches from the tree of downloaded folders. With
proper usage, they result in a mirror that is exactly as organized and
full-featured as any high-volume public upstream site.
Possible data loss
If you are not exceedingly careful in using these switches, it is
possible to delete large portions of your mirrored data. Fixing this
problem might simply require performing the copying steps outlined
in above. On the
other hand, if you are also careless about your destination path,
and you are running as root, you could put your entire system at
risk. Know your environment before using these switches:
What is your current working directory? Use
pwd to find out, if you are unsure.
Are you logged in as root? If you are using SELinux extensions,
what is your current security context?
Have you tested this command using the -n
switch (see )?
Use the --exclude switch, along with a simple
pattern, to disallow download of certain files and/or folders. For
instance, --exclude "*.iso" excludes the download
of any file that has the string x86_64 in its filename.
Use the --delete switch, again with a pattern, to
remove any file from the local system which does not have a match on
the upstream mirror. This switch prevents unwanted file
debris from cropping up in your mirror. You can also use
it to retroactively trim branches of the tree which you no longer wish
to maintain or download.
Wildcards are permitted with rsync commands,
including the asterisk *, question
mark ?, and brackets
[ ]. The question mark and brackets
work as in the shell; the former matches any single character, while
the brackets define a set of characters to be matched. Asterisks are
especially powerful when combined with a portion of a file name. The
double asterisk ** pattern matches
any character, including slashes; a single
asterisk * matches any character, but
stops at a slash. Therefore, be judicious about using either. The
double asterisk is very useful for mirroring a tree that includes
multiple instances of directories and files that contain a pattern. A
good example is mirroring several versions of &FC;, where certain
folder names appear in every version.
Pattern matching wildcards
Use double asterisks to trim out directories that repeat throughout
a mirrored tree. For example, when mirroring for a site that
only uses i386 architecture machines, you may trim all files and
folders marked for x86_64 architecture, using the switch
--exclude "**x86_64**". This matches not only
folders marked x86_64, but also files such as
ISO images for x86_64, which are indicated by file names such as
FC&FCVER;-x86_64-disc1.iso.
Process a long list of exclusions and deletions with the
--exclude-from and --delete-from
options. Follow each tag with a file name that includes a list of
patterns, one per line, to be matched by the appropriate option.
These syntax hints only scratch the surface of
rsync, but suffice to make your first mirror. Once
you have selected your site and formulated your excludes and deletes,
run your rsync command with the
-n option. Redirect output to a file so you can
examine the resulting list of files in the editor or pager of your
choice.
The following example mirrors the entire &FC; &FCVER; distribution,
with --exclude options that avoid downloading:
Any information for x86_64 architecture;
Any yum headers (see );
Any debuginfo packages; and,
CD or DVD images.
The -n switch is included for testing purposes.
Backslashes at the ends of lines indicate this example is a single
command line.
rsync -Pan --delete --exclude "**x86_64**" --exclude "**headers**" \
--exclude "**debug**" --exclude "**iso**" \
mirror.example.com::fedora-linux-core/&FCVER;/ \
/var/ftp/pub/mirror/fedora/core/&FCVER;Maintaining Your Mirror
&FED; mirrors are even more useful when they are more than just a
snapshot of the distribution at release time. Most mirror administrators
also choose to carry updates and errata packages. Repositories of
updates or development trees change daily, and your mirror should
reflect these changes.
rsync etiquette
If you plan to do regular updates of your mirror that include large
amounts of data, you should ask permission from the administrator of
the upstream mirror. Downloading nightly package updates for the
official releases of &FC; &FCVER; should not require notification, as
they are rarely more than a few megabytes. However, the
development tree routinely turns over several
hundred megabytes nightly. Take these factors into consideration
before putting any maintenance scripts into effect.
Once your rsync command is working as desire, you may
want to place it in a nightly cron script. The
cron system allows you to schedule
regularly-occurring jobs on your system. The intervals are highly
configurable, but a nightly run keeps your mirror synchronized with
updates and errata. Make sure your nightly cron job
follows some simple guidelines:
If your upstream mirror only synchronizes once or twice daily, run
your job after the upstream mirror completes
its update. This insures your mirror not only gets the freshest
material, but also does not interfere with the upstream server's
bandwidth while it runs its job. If you do not know this time, it is
usually safe to plan your downloads for pre-dawn hours.
Be sure you have sufficient disk space for additional packages. The
updates tree in particular grows over time as
more errata packages are released.
Always test your script thoroughly before allowing it to run
automatically. Use a -n or -v
switch in the rsync command line for testing, and
then remove it once you have completed testing. Remember that the
results are e-mailed to your account on your system unless you
specify differently. Read the crontab(5) man
pages for additional information, with the command man 5
crontab.
Server Configuration Planning
Decide what services your mirror will offer to clients. There are at least
three services useful for providing &FED; installation and update
services: HTTP, FTP, and NFS. Some or all of these services can be used
for offering post-installation functions such as updates or installing
additional packages.
Install the vsftpd package for FTP services. Install
the httpd package to use the Apache HTTP server. Most
&FC; systems already have the nfs-utils package
installed, which contains the NFS server.
To start a service, use the /sbin/service
service start command. To enable that
server by default at boot time, use the chkconfig
service on command.
One recommended method is to download all mirrored files into
/var/ftp/pub, add a link in
/var/www/html that points to
/var/ftp/pub, and share out
/var/ftp/pub via NFS as well. FTP and HTTP services
do not require any further configuration to work properly.
However, you should evaluate your site's security needs before
enabling them. NFS service configuration is explained below
in .
To share out the public FTP area via HTTP, issue the following
command:
ln -s /var/ftp/pub /var/www/html/pub
Your clients may now visit any area of your mirror by using the URL
http://server.mydomain.org/pub/path. To create
an NFS share, add a line to /etc/exports. This
example shares out the &FC; &FCVER; i386 stock distribution with read-only
access for any host in the mydomain.org
domain.
/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os *.mydomain.org(ro,sync,root_squash)
To reread the NFS server configuration files and export the new share, use
the following command:
exportfs -ar
Refer to for a list of commands for
starting services both on demand and at boot time.
How to Solve Dependencies
Every RPM package has a header that contains all
the vital information about that package. This information includes
name, version and release, contents, the capabilities provided by the
package, and any prerequisites. These prerequisites may include
dependenciesdependencies. A dependency is a requirement for one or more additional
packages.
Packages installed without satisfying their dependencies may not work
correctly. Dependencies may create a problem for users who are trying to
install a single package. Manually determining and resolving
dependencies is difficult. &FC; has several methods for solving these
dependencies automatically, providing an improved user experience.
Red Hat NetworkRed Hat NetworkRed Hat Network, or RHNRHNRed Hat Network, is a systems management and deployment tool that was
introduced in Red Hat Linux, and continues to be used with Red Hat
Enterprise Linux. RHN makes updates available to registered users, and
allows them to remotely schedule and manage their systems using a
single Web-based console. The client systems run the
up2date application to communicate with
RHN.
Although &FC; systems do not inter-operate with RHN, they still include
an up2date client. This client is
enhanced to support non-RHN update services. These services, like RHN,
solve RPM package dependencies automatically.
yum
The Yellow Dog Updater Modified, or
yumyum, is a Python-based system for computing and solving RPM
dependencies. A yum client retrieves a cache of
headers from its repository server, as well as a list of available RPM
packages and their exact locations on the server. It can do this via
HTTP or FTP, as well as using standard file system calls (either local
or remote via NFS). The client computes solutions to any package
dependencies using the downloaded header information, and simply
requests all necessary RPM packages once it has finished. The
yum command relies on rpm to
perform all computation involved in the process.
A drawback to yum is that the first time it is run,
it must download a header for every package installed on the system in
order to determine available updates. However, running a local mirror
nullifies this drawback. The yum command can, of
course, download many megabytes of headers almost instantly on a
standard Ethernet LAN. yum is the most popular
update method for &FC;.
Configuring Repositories
A yumrepositoryrepositoryyum is a collection of packages on a server which supports
yum clients. Repositories can serve both types of
clients if desired.
To set up a yum repository, you must write a
directory of header information from which the clients pull the data
they require. The directory is named headers. It is
created by using the command yum-arch, which is run
against the directory under which you want the
headers directory to appear. The
yum-arch program searches recursively through that
directory and any subdirectories for RPM packages, and includes them in
the header data.
yum-arch -l -s /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os
The -l switch follows symbolic links. This is useful
in the first case below. The -s switch includes SRPMS
(source RPM packages) in the header list. The command above creates the
yum header cache in the directory
/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers.
Typically yum-arch is run against at least the
following locations:
The stock distribution; for example,
/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/.
Use the -l and -s options to
follow the linked directory SRPMS and include
the source packages therein.
Official updates to the distribution; for example,
/var/ftp/pub/linux/fedora/core/updates/&FCVER;/.
Once again use -l and/or -s if
appropriate.
Configuring NFS
Some client-side utilities also resolve dependencies automatically.
These utilities require more detailed configuration of the client
workstation. For more information, see below. These utilities, however, require
standard file system access to package collections. For this reason, you
may require NFS on your mirror. Configuration of the client depends
in large part on how you decide to implement NFS sharing on the mirror.
It is difficult to share subdirectories of other shared directories.
Therefore, think of your mirror as offering many services, each one to
be considered for NFS sharing. For example, share both the stock
distribution of &FC; 2 and the stock distribution of &FC; 3.
The client side tools discussed later can use a directory of ISO images
or an exploded tree of package data (see ). You may share out any or
all of these, provided your shares do not clash as described above.
To share via NFS, edit the /etc/exports file. A
typical share, exported with read-only access for any host on any
network, looks like this:
/mnt/media *(ro,all_squash,async)
The all_squash option ensures that no users accessing
the share using their local root account receive equivalent access on
the share. This feature keeps some small measure of security even on a
public share, since a file readable only by root on the server is not
readable by an NFS client. The async option allows
asynchronous read/writes, which is not dangerous in this case because
the share is read-only. The * is a host designator,
in this case matching any host name or IP address. You may wish to
restrict this share to your internal network. You may declare either a
matching name or IP address specification. You can find more detailed
information by reading the man pages for the
/etc/exports file by using the command man
5 exports.
Access control format
Be certain that you do not have a space between the host specification
and the option listing in parentheses (
). A space causes the NFS daemon to consider that
entry as two separate access controls. In the
example above, a space causes the first access control to match all
hosts and allow write access, which is the default! The second access
control is never reached because the first matches any host first.
To share the proper directories from your mirror, use one of the
following forms. To share your exploded tree, export the directory that
contains the &FED; folder (note the capitalization). For i386
architectures:
/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os *(ro,all_squash,async)
To share a directory full of ISO images, export that directory:
/var/ftp/pub/linux/fedora/core/&FCVER;/i386/iso *(ro,all_squash,async)
Once you have edited the /etc/exports file, make
sure that the NFS server is installed and started properly on the
mirror. The portmap and
nfs-utils packages must be installed. Configure
them to be turned on at boot time by default.
/sbin/chkconfig portmap on
/sbin/chkconfig nfslock on
/sbin/chkconfig nfs on
To check if any of these services are currently running, use the
/sbin/service service_name
status command:
/sbin/service portmap status
/sbin/service nfslock status
/sbin/service nfs status
To restart a service, use the /sbin/service
service_name restart command:
/sbin/service portmap restart
/sbin/service nfslock restart
/sbin/service nfs restart
If any service is not started, use the command /sbin/service
service_name start to start it, as
in the following examples:
/sbin/service portmap start
/sbin/service nfslock start
/sbin/service nfs start
To change your exports when the NFS service is already running, use the
command /usr/sbin/exportfs -ar. The command
/usr/sbin/showmount -e displays a list of the
current NFS exports on the local host machine.
Client Configuration
You must also correctly configure the client workstations that use your
mirror. Using the mirror as a source for RPM packages, clients may have
seamless access for installing basic software through
system-config-packages, solving RPM package
installations at the command line, and pulling bug fix and security errata
updates.
Configuring system-config-packages
Users typically run the
system-config-packages application from the
GUI menu, by choosing System Settings,
Add/Remove Applications. This program allows
the user to change the stock installation, provided no updates have
taken place yet that interfere.
Often, system-config-packages stops
functioning optimally after certain updates are installed. This is
because system-config-packages solves
dependencies based on the stock distribution. It is impossible for
system-config-packages to predict version
numbers of updates. If you intend to carry updates on your mirror, you
should be aware that installing certain updates causes
system-config-packages to lose its
effectiveness. Some sites do not mirror all updates due to configuration
management concerns. The guidance in this section is especially useful
in those scenarios.
up2date and
system-config-packages
If you plan to carry updates on your mirror, as most administrators
do, you will probably not use
system-config-packages much. Once the
installed package versions become out of sync with the stock
distribution versions, up2date becomes much
more useful. The preferred method for installing a package in that
case would be up2date --install
package_name. See for more information.
Setting Up autofs
The autofsautofs facility allows a &FC; system to mount file systems on
demand. The /etc/auto.master file contains an
automounter mapautomounter mapmapautomounterautomounter map. On &FC;, the automounter map is a list of additional
definition files that should be loaded, one for each directory in the
map. An example line from /etc/auto.master is
shown below:
/misc /etc/auto.misc --timeout=60
The first term in the line is the directory which is reserved for
automounting. The second term is the automount file which should be
consulted to determine any maps for that directory. The third term in
the example indicates that if a map under /misc is not busy for 60
seconds, it is unmounted.
The /etc/auto.misc file contains entries similar
to the following example.
remote -ro,soft,intr host.foobar.org:/pub
This line is contained in the automounter map file for the
/misc directory. The first term is a key which is
the name of a directory that appears upon demand. The second term is
actually a list of options, identical to those that would be used for
a real mount command. The final term is the file
system (local or remote) to mount. In the above example, if the user
of this station accesses the directory
/misc/remote, an NFS mount is automatically
performed. The user's command appears to hesitate, depending on how
fast the NFS server responds. Then /misc/remote
appears to be full of whatever content is on host.foobar.org in the
/pub NFS share.
You can use this function to provide NFS access to the stock
distribution for &FC;. Choose a directory to map in the
/etc/auto.master file, and match it to a
corresponding automounter map file. The easiest way to do this is to
simply remove the comment # from the
front of the line attaching /misc to
/etc/auto.misc. The default timeout should be
sufficient.
Make an entry in /etc/auto.misc similar to
this. You can have multiple entries, each one with a different
key. For instance, each key could be mapped to a different version of
&FC; that you have available on the local mirror.
fc&FCVER; -ro,soft,intr mirror.mydomain.org:/var/ftp/pub/linux/fedora/core/&FCVER;
Now restart the autofs service:
/sbin/service autofs restart
To access the stock distribution for &FC; &FCVER; the user can simply
type cd /misc/fc&FCVER;. The share is automatically
mounted and the files simply appear in that local directory.
/usr/share/applications/system-config-packages
Now that autofs has been configured, your client
workstations need to be configured so that
system-config-packages points to the
mirror's NFS share. Edit the
/usr/share/applications/system-config-packages
file's Exec= line to add a switch pointing to the
share:
Exec=/usr/bin/system-config-packages --tree=/misc/fc&FCVER;/i386/os
When users choose System Settings,
Add/Remove Applications from the GUI main
menu, the system now automatically resolves package dependencies from
the mirror. The restrictions stated above in apply.
The rpm --aid Switch
The --aid switch for the rpm
command also automatically solves dependencies. It performs this
function based on the rpmdb-fedora package. That
package is a preset database for a system that has every RPM package
in the &FC; distribution installed. Even if a system does not
itself have every package installed, it can
consult the rpmdb-fedora package database to see
what such a system would look like. By using the
--aid switch, clients can issue a single
rpm --install --aid command against an original
&FC; package, and have all dependencies automatically installed as
well.
Two steps are required for this process. First, install the
rpmdb-fedora package:
rpm --install /misc/fc&FCVER;/i386/os/&FED;/RPMS/rpmdb-fedora-*.rpm
Then, edit the file /etc/rpm/macros.solve, which
is part of the rpmdb-fedora package. Change the
following lines to enable package resolution:
%_solve_pkgsdir /misc/fc&FCVER;/i386/os/&FED;/RPMS/
%_solve_name_fmt %{?_solve_pkgsdir}%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm
Users now issue a single command to install any package from
the stock distribution, and all dependencies are solved for
them. For example:
rpm --install --aid /misc/fc&FCVER;/i386/os/&FED;/RPMS/kdeutils-*.rpm
If a user forgets the --aid switch, they
still receive hints. Normally rpm
displays a slightly cryptic list of capability requirements,
instead of straightforward package names. If you edit
/etc/rpm/macros.solve as shown,
rpm displays a list of required package
names instead.
Package dependency solutions using --aid
are also restricted as shown above in .
Configuring up2date
The up2date application in &FC; now
allows use of yum and
apt repositories. The client must have a
configuration that points at the desired repositories.
/etc/sysconfig/rhn/up2date
The /etc/sysconfig/rhn/up2date file
controls the global configuration of the
up2date application. This file is
well commented and is not explained in great detail
here. Here are some points to keep in mind, however:
By default, the user must intervene to update
kernel packages. See the
pkgSkipList variable. At the command
line, use the -f option to force an
override. At the GUI interface,
up2date allows the user to
override.
By default, up2date does not remove
old kernel packages. See the
pkgsToInstallNotUpdate variable. When
up2date installs a new kernel
package, the old version remains in place until removed
explicitly.
The configuration file also allows use of an HTTP proxy
if desired. A number of variables pertain to this
function.
By default, up2date sends
mail to root at localhost when packages are
updated in batch mode. (Running up2date
-u starts up2date
in batch mode.) See the adminAddress
option. If you support multiple clients and intend to
use batch mode at your site, you should set a new
address here.
/etc/sysconfig/rhn/sources
The /etc/sysconfig/rhn/sources file is used to
declare the repositories that are used with
up2date. A repository is declared in any of
the following ways:
apt labelservice:serverpathrepository_name
yum labelURL
dir labellocal_path
For apt repositories,
service:server is the standard Internet protocol
and host name — for example, http://mirror.example.com. For
yum repositories, the URL points to the directory
on a server which contains the
headers folder. A dir
repository simply points to a folder that contains RPM packages. The
folder may contain the RPM packages in subdirectories.
The yum-mirror syntax points to a file that is a
list of alternative sources for the same repository:
yum-mirror labelURL
Edit /etc/sysconfig/rhn/sources for the clients
at your site to point to your repository. For any repository, point to
the URL for the directory containing the headers
folder. You created this folder using yum-arch in
. You will likely have two
repositories, one for the stock distribution and one for updates.
Examples are shown below; you may wish to point to an internal address
rather than an outward-facing server. Use a URL appropriate to your
network and Apache configuration.
yum fedora-core-2 http://www.mydomain.org/pub/linux/fedora/core/2/i386/os
yum fc2-updates http://www.mydomain.org/pub/linux/fedora/core/updates/2/i386
From fedora-docs-commits at redhat.com Thu May 5 21:15:32 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Thu, 5 May 2005 17:15:32 -0400
Subject: fedora-docs/install-guide fedora-install-guide-firstboot-en.xml, 1.3,
1.4
Message-ID: <200505052115.j45LFWlS011071@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10951
Modified Files:
fedora-install-guide-firstboot-en.xml
Log Message:
Amendments for compliance with style guidelines.
Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-firstboot-en.xml 3 May 2005 12:19:44 -0000 1.3
+++ fedora-install-guide-firstboot-en.xml 5 May 2005 21:15:30 -0000 1.4
@@ -1,12 +1,12 @@
- The Setup Agent
+ On First Boot
- The first time that you load a new installation of &FC; the Setup
- Agent will run, enabling you to configure the basic elements of the
- system.
+ The Setup Agent will run the first time that you load a new
+ installation of &FC;, enabling you to configure the basic elements
+ of the system.
@@ -33,10 +33,8 @@
The Setup Agent requires a graphical interface
- The Setup Agent cannot run if you chose to install a system with
- no graphical interface. In this case you must manually configure
- a user account for yourself, and if necessary, adjust the system
- date and time.
+ If your system does not have a graphical interface you must
+ manually carry out these configuration tasks.
@@ -80,8 +78,8 @@
Date and Time
- You can either set the date and time of your system, or use
- network time servers (NTP). If possible you should use NTP
+ You can either set the date and time of your system, or use NTP
+ (network time protocol). If possible you should use NTP
servers so that your system clock will automatically be kept
accurate.
@@ -131,9 +129,8 @@
To configure your system to use network time servers you must
Enable Network Time Protocol. This
- disables thesettings on the Date and Time
- tab and allows you to access to the other settings on this
- display.
+ disables the settings on the Date and Time
+ tab and allows you to access to the other settings on this screen.
@@ -161,17 +158,6 @@
becomes unavailable.
-
- You do not need to edit the list of NTP servers
-
- The three server clusters provide a highly reliable method of
- setting your system clock. You only need change the list of
- NTP Servers if your system does not have
- full access to the Internet. In this case replace the listed
- servers with the time servers on your network.
-
-
-
To use an additional time server either select it from the
Server drop-down box, or type the DNS name
in the box, and Add. To remove a server or
@@ -295,8 +281,8 @@
manufacturer to view the models of monitor. Select the correct
model from the list and click OK. If none
of the listed models match your monitor, select the closest match
- from the Generic CRT Display or
- Generic LCD Display, as appropriate.
+ from either the Generic CRT Display list or
+ the Generic LCD Display list.
@@ -367,11 +353,11 @@
Changing the sound card
- If you have to reconfigure the sound card later, use the
- system-config-soundcard utility.
- From the main menu, choose System
- SettingsSoundcard
- Detection.
+ Use the system-config-soundcard utility
+ to redetect your current sound card, if it is not automatically
+ configured after a change of hardware. From the main menu, choose
+ System
+ SettingsSoundcard Detection.
@@ -404,8 +390,9 @@
- Click Next to move on to the final
- screen.
+
+ Click Next to move on to the final screen.
+ Finish Setup Screen
From fedora-docs-commits at redhat.com Sun May 8 23:33:15 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 8 May 2005 19:33:15 -0400
Subject: fedora-docs/install-guide
fedora-install-guide-other-instmethods-en.xml, 1.4, 1.5
Message-ID: <200505082333.j48NXF5M005305@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5297
Modified Files:
fedora-install-guide-other-instmethods-en.xml
Log Message:
Adhere (mostly) to style guidelines
Index: fedora-install-guide-other-instmethods-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-other-instmethods-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-other-instmethods-en.xml 3 May 2005 22:09:21 -0000 1.4
+++ fedora-install-guide-other-instmethods-en.xml 8 May 2005 23:33:13 -0000 1.5
@@ -4,12 +4,21 @@
Other Installation Methods
- If you have booted from removable media or PXE then you will see
- some additional screens. The first of these screens enables you to
- specify where the main installation program and packages are held.
- This screen will also appear if you started the boot process with
- the linux askmethod option.
+ The following screen appears if one of the following is true:
+
+
+
+ You booted using PXE, or USB media.
+
+
+
+
+ You entered the option at the
+ boot: prompt.
+
+
+ Installation Method Screen
@@ -34,39 +43,42 @@
- Discs override manual selection
+ CD/DVD Activity
- If a &FED; disc is detected in the drive of your computer then it
- will automatically be used to perform the installation. This will
- override any installation method that you configure manually.
+ If a &FED; disc is in your computer's CD or DVD drive, the
+ installation program loads its next stage from that disc. The
+ installation program downloads package data from the source you
+ choose.
- Installing from a Network Server with FTP, HTTP or
- NFS
+ Installation from a Network Server
- These installation methods require a server to be configured
- first. Setting up an installation server is detailed in a separate
- tutorial.
+ You may install &FC; from a network server using FTP, HTTP, or NFS
+ protocols.
- Configuring TCP/IP
+ TCP/IP Configuration
- The default option is to use DHCP to automatically provide the
- network settings. If this is incorrect, click Use
- dynamic IP configuration to empty the checkbox and
- fill in the settingsmanually. Select OK
- to move to the next screen.
+ By default, the installation program uses DHCP to automatically
+ provide the network settings. If your network has no DHCP
+ server, clear the checkbox labeled Use dynamic IP
+ configuration and enter the settings manually.
+ Select OK to continue.
- Configure TCP/IP Screen
+ Configure TCP/IP Dialog
@@ -76,16 +88,16 @@
- TCP/IP configuration screen.
+ TCP/IP configuration dialog.
- This settings on this screen only apply during the installation
- process. You configure the network settings for the final system
- on a later screen.
+ These settings apply only during the installation process. The
+ installation program allows you to configure the final network
+ configuration later.
@@ -95,22 +107,13 @@
Network Service Setup
- The FTP Setup screen is shown below. The
- NFS image and HTTP
- screens have the same layout, but do not have a checkbox for
- non-anonymous FTP.
-
-
-
- The site name is the name or IP address of
- the server. The &FC; directory is the name
- that the installation tree is shared as. Selecting
- non-anonymous FTP means that you will use a
- named account with a password to access the server.
+ The FTP, HTTP, and NFS service setup dialogs are very similar.
+ Each requires the name or IP address of the server, and a
+ directory where the installation tree resides.
- FTP Setup Screen
+ FTP Setup Dialog
@@ -120,7 +123,7 @@
- FTP setup screen.
+ FTP setup dialog.
@@ -133,14 +136,15 @@
Further FTP Setup
- If you selected the option for non-anonymous FTP, then you will
- be presented with this screen. Fill in the account name and
- password for the server, and then select
+ The FTP service setup dialog also has an option for
+ non-anonymous FTP. If your FTP server does
+ not provide anonymous access, select this check box, and provide
+ an account name and password in the following dialog. Select
OK to continue.
- Further FTP Setup Screen
+ Non-anonymous FTP Account Dialog
@@ -150,7 +154,7 @@
- Further FTP setup screen.
+ Non-anonymous FTP account dialog.
@@ -162,20 +166,19 @@
- Installing from a Hard Drive
+ Installation from a Hard Drive
- You will need a hard drive containing the ISO image files for the
- &FED; discs. The hard drive can be either internal to the
+ You may install from a hard drive containing the ISO image files
+ for the &FED; discs. The hard drive can be either internal to the
computer, or attached by USB. The partition on the hard drive
holding the ISO files must be formatted with either ext2, ext3 or
- the FAT file system. External hard drives are supplied formatted
- as FAT.
+ the FAT file system. Most external hard drives are supplied
+ formatted as FAT.
- If you chose the option to install from a hard drive, this screen
- will appear:
+ If you choose this option, the following screen appears:
@@ -198,14 +201,15 @@
Select the partition containing the ISO files from the list of
available partitions. Each drive is assigned a unique letter.
- Each partition on a drive is numbered sequentially. Internal IDE
- drives are prefixed with /dev/hd. SCSI or
- USB drives are prefixed with /dev/sd.
+ Each partition on a drive is numbered. Internal IDE drive device
+ names begin with /dev/hd. SCSI or USB drive
+ device names begin with /dev/sd.
You must also specify the Directory holding
- images.
+ images. Enter the full directory path on the drive
+ that contains the ISO image files.
From fedora-docs-commits at redhat.com Mon May 9 16:13:19 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 9 May 2005 12:13:19 -0400
Subject: fedora-docs/install-guide fedora-install-guide-locale-en.xml, 1.1,
1.2
Message-ID: <200505091613.j49GDJQj026497@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26489/install-guide
Modified Files:
fedora-install-guide-locale-en.xml
Log Message:
Style changes
Index: fedora-install-guide-locale-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-locale-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-locale-en.xml 2 May 2005 22:18:42 -0000 1.1
+++ fedora-install-guide-locale-en.xml 9 May 2005 16:13:17 -0000 1.2
@@ -4,7 +4,7 @@
If the installation system fails to identify the display hardware on
- your computer, it will display text screens rather than the default
+ your computer, it displays text screens rather than the default
graphical interface. The text screens provide the same functions as
the standard screens. Later in the installation process you can
manually specify your display hardware.
@@ -12,8 +12,8 @@
- Network installations with HTTP and FTP will always use text
- screens on systems with less than 128Mb of memory.
+ Network installations with HTTP and FTP always use text screens on
+ systems with less than 128Mb of memory.
@@ -22,10 +22,7 @@
The installation program displays a list of languages supported by
- &FED;. The installation process continues in this language. This
- language also becomes the default language for your system. The
- installation program provides additional language support at a
- later stage.
+ &FED;.
@@ -80,7 +77,10 @@
Highlight the correct layout on the list, and select
- Next.
+ Next. The installation process continues
+ in this language. This language also becomes the default language
+ for your system. The installation program provides additional
+ language support at a later stage.
From fedora-docs-commits at redhat.com Mon May 9 17:00:00 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 9 May 2005 13:00:00 -0400
Subject: fedora-docs/install-guide fedora-install-guide-locale-en.xml, 1.2,
1.3
Message-ID: <200505091700.j49H00Bx026841@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26833
Modified Files:
fedora-install-guide-locale-en.xml
Log Message:
Minor cosmetic fixes
Index: fedora-install-guide-locale-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-locale-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-locale-en.xml 9 May 2005 16:13:17 -0000 1.2
+++ fedora-install-guide-locale-en.xml 9 May 2005 16:59:58 -0000 1.3
@@ -6,7 +6,7 @@
If the installation system fails to identify the display hardware on
your computer, it displays text screens rather than the default
graphical interface. The text screens provide the same functions as
- the standard screens. Later in the installation process you can
+ the standard screens. Later in the installation process you can
manually specify your display hardware.
@@ -78,8 +78,8 @@
Highlight the correct layout on the list, and select
Next. The installation process continues
- in this language. This language also becomes the default language
- for your system. The installation program provides additional
+ in this language. This language also becomes the default language
+ for your system. The installation program provides additional
language support at a later stage.
From fedora-docs-commits at redhat.com Mon May 9 17:01:44 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 9 May 2005 13:01:44 -0400
Subject: fedora-docs/install-guide fedora-install-guide-upgrading-en.xml, 1.2,
1.3
Message-ID: <200505091701.j49H1i1q027792@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/fedora-docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27784
Modified Files:
fedora-install-guide-upgrading-en.xml
Log Message:
Applied standard cosmetic fixes, began style edits
Index: fedora-install-guide-upgrading-en.xml
===================================================================
RCS file: /cvs/docs/fedora-docs/install-guide/fedora-install-guide-upgrading-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-upgrading-en.xml 2 May 2005 22:24:28 -0000 1.2
+++ fedora-install-guide-upgrading-en.xml 9 May 2005 17:01:42 -0000 1.3
@@ -1,137 +1,135 @@
- Upgrading Over An Existing System
+ Upgrading an Existing System
- The installation system will automatically detect any existing
- installation of &FC;. If there is a copy of &FC; then you will be
- presented with this screen:
+ The installation system will automatically detect any existing
+ installation of &FC;. If there is a copy of &FC; then you will be
+ presented with this screen:
-
- Upgrade Examine Screen
-
-
+
+ Upgrade Examine Screen
+
+
-
-
+
+
-
-
+
+
- Upgrade examine screen.
+ Upgrade examine screen.
-
-
-
-
+
+
+
-
- Upgrading an Existing System
-
- To perform an upgrade of an existing system, select the appropriate
- installation from the drop-down list before selecting Next.
-
+
+ To perform an upgrade of an existing system, select the appropriate
+ installation from the drop-down list and then select
+ Next.
+
-
- An upgrade will update the existing &FC; installation using the software
- packages for the new version. Your data and the configuration of your
- system will not be changed or lost. The upgrade process
- does not delete any files in the /home/ and
- the /usr/local/ directories.
-
+
+ An upgrade consists of updating the existing &FC; or &RHL;
+ installation with the software packages for the new version. Your
+ data is not lost, and the existing partition structure on your hard
+ drives does not change. Your system configuration changes only if a
+ package upgrade demands it. The upgrade process does not delete any
+ files in the /home/ and the
+ /usr/local/ directories.
+
+
+ Manually Installed Software
- The existing partition structure on the hard drives of your machine is
- also not altered by an upgrade.
+ Software which you installed manually on your existing &FC; or
+ &RHL; system may behave differently after an upgrade. You may
+ manually recompile this software after an upgrade to ensure it
+ performs correctly on the updated system.
-
-
- Upgrades may affect manually installed software
-
- Software may behave differently after an upgrade. Manually compiled
- software should be recompiled after an upgrade to ensure that it
- performs correctly on the updated system.
-
-
+
-
- Upgrading Boot Loader Configuration
+
+ Upgrading Boot Loader Configuration
-
- Your completed &FC; installation must be registered in the
- boot loader in order for it to start. The boot
- loader is the software on your machine that boots the main operating
- system. If you have multiple operating systems then the boot loader
- determines which operating system to boot, usually by offering a menu of
- options to the user. Operating systems install their own preferred
- boot loader, but you may have chosen to use a third-party boot loader.
-
+
+ Your completed &FC; installation must be registered in the
+ boot loader to boot properly. The boot
+ loader is software on your machine that locates and starts the
+ operating system. If you have multiple operating systems, the
+ boot loader determines which one to boot, usually by offering a
+ menu. An operating system may install its own preferred boot
+ loader, or you may have installed a third-party boot loader.
+
- Upgrade Bootloader Screen
+ Upgrade Bootloader Screen
-
-
-
-
-
-
-
-
- Upgrade bootloader screen.
-
-
+
+
+
+
+
+
+
+
+ Upgrade bootloader screen.
+
+
-
- If the existing boot loader has been installed by a Linux distribution
- then the installation system can modify it to load the new &FC; system.
- To amend a Linux boot loader, select Update boot loader configuration.
- This is default option for upgrading from one version of &FC; to another.
-
-
-
- GRUB is the default boot loader
-
- GRUB is the default boot loader installed by &FC;, recent &RH; operating
- systems and some other Linux distributions. &FC; also supports LILO,
- the boot loader provided by older Linux distributions.
+
+ If the existing boot loader has been installed by a Linux
+ distribution then the installation system can modify it to load
+ the new &FC; system. To amend a Linux boot loader, select
+ Update boot loader configuration. This is
+ default option for upgrading from one version of &FC; to another.
+
+
+
+ GRUB is the default boot loader
+
+ GRUB is the default boot loader installed by &FC;, recent &RH;
+ operating systems and some other Linux distributions. &FC; also
+ supports LILO, the boot loader provided by older Linux
+ distributions.
-
+
-
- If your machine is using another boot loader, such as
- BootMagic or the loader installed
- by MicrosoftWindows, then the &FED; installation
- system cannot update it. You must manually add the settings for loading
- &FC; after completing the installation process. To leave the existing
- boot loader unmodified, select Skip boot loader updating.
-
-
-
- You should only install a new boot loader as part of an upgrade process
- if you are certain that you wish to replace the existing boot loader.
- This may prevent other operating systems on the same machine from being
- loaded until you have reconfigured the new boot loader. Select
- Create new boot loader configuration to remove the
- existing boot loader and install GRUB as part of the installation process.
-
+
+ If your machine is using another boot loader, such as
+ BootMagic or the loader installed by
+ MicrosoftWindows, then the &FED;
+ installation system cannot update it. You must manually add the
+ settings for loading &FC; after completing the installation
+ process. To leave the existing boot loader unmodified, select
+ Skip boot loader updating.
+
-
- Click Next once you have made a selection.
-
+
+ You should only install a new boot loader as part of an upgrade
+ process if you are certain that you wish to replace the existing
+ boot loader. This may prevent other operating systems on the same
+ machine from being loaded until you have reconfigured the new boot
+ loader. Select Create new boot loader
+ configuration to remove the existing boot loader and
+ install GRUB as part of the installation process.
+
-
+
+ Click Next once you have made a selection.
+
+
-
+
-
+
+
+
+
@@ -36,7 +39,7 @@
- &FC; &IG;
+ &FC; &LOCALVER; &IG;2005&FORMAL-RHI;
@@ -67,6 +70,17 @@
+
+ 0.6.3
+ 2005-05-10
+ PaulWFrields
+ StuartEllis
+
+
+ Style editing, removed "nextsteps" from build
+
+
+
@@ -102,8 +116,6 @@
&FIRSTBOOT;
- &NEXTSTEPS;
-
&ACKNOWLEDGEMENTS;
Index: fedora-install-guide-rootpassword-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-rootpassword-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-rootpassword-en.xml 9 May 2005 22:17:46 -0000 1.3
+++ fedora-install-guide-rootpassword-en.xml 10 May 2005 21:25:56 -0000 1.4
@@ -47,7 +47,7 @@
the Confirm field.
-
+ Set Root Password Screen
From fedora-docs-commits at redhat.com Tue May 10 21:33:53 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 10 May 2005 17:33:53 -0400
Subject: install-guide fedora-install-guide-en.xml,1.9,1.10
Message-ID: <200505102133.j4ALXrDO003811@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3803
Modified Files:
fedora-install-guide-en.xml
Log Message:
LOCALVER change
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-en.xml 10 May 2005 21:25:56 -0000 1.9
+++ fedora-install-guide-en.xml 10 May 2005 21:33:51 -0000 1.10
@@ -12,7 +12,8 @@
-
+
+
@@ -39,7 +40,7 @@
- &FC; &LOCALVER; &IG;
+ &FC; &FCLOCALVER; &IG; &DOCLOCALVER;2005&FORMAL-RHI;
From fedora-docs-commits at redhat.com Wed May 11 16:08:59 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 11 May 2005 12:08:59 -0400
Subject: README,1.8,1.9
Message-ID: <200505111608.j4BG8xXw028372@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28365
Modified Files:
README
Log Message:
Updated to reflect current CVS usage strategy.
From fedora-docs-commits at redhat.com Wed May 11 16:50:28 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 11 May 2005 12:50:28 -0400
Subject: sudo-tutorial - Imported sources
Message-ID: <200505111650.j4BGoSlZ028566@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/sudo-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28560
Log Message:
Mini-tutorial about setting up and using the sudo(8) tool.
Status:
Vendor Tag: TommyReynolds
Release Tags: initial
N sudo-tutorial/Makefile
N sudo-tutorial/sudo-tutorial-en.xml
No conflicts created by this import
From fedora-docs-commits at redhat.com Wed May 11 23:38:06 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 11 May 2005 19:38:06 -0400
Subject: install-guide fedora-install-guide-firstboot-en.xml,1.4,1.5
Message-ID: <200505112338.j4BNc6tp005465@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5457
Modified Files:
fedora-install-guide-firstboot-en.xml
Log Message:
Hopefully fixed passive voice.
Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-firstboot-en.xml 5 May 2005 21:15:30 -0000 1.4
+++ fedora-install-guide-firstboot-en.xml 11 May 2005 23:38:04 -0000 1.5
@@ -4,9 +4,9 @@
On First Boot
- The Setup Agent will run the first time that you load a new
- installation of &FC;, enabling you to configure the basic elements
- of the system.
+ The first time that you load a new installation of &FC; the Setup
+ Agent is launched, enabling you to configure the basic elements of the
+ system.
@@ -33,8 +33,8 @@
The Setup Agent requires a graphical interface
- If your system does not have a graphical interface you must
- manually carry out these configuration tasks.
+ You must manually carry out these configuration tasks if the Setup
+ Agent cannot run.
@@ -78,10 +78,9 @@
Date and Time
- You can either set the date and time of your system, or use NTP
- (network time protocol). If possible you should use NTP
- servers so that your system clock will automatically be kept
- accurate.
+ You can either manually set the date and time for your system, or
+ configure your system to use NTP (Network Time Protocol) servers
+ to maintain the clock. NTP ensures that the time is always accurate.
@@ -250,9 +249,9 @@
Display
- The Setup Agent will automatically attempt to identify the
- graphics hardware and monitor for your computer. These are used
- to determine the Resolution and
+ The Setup Agent attempts to identify the graphics hardware and
+ monitor for your computer. It also uses this information to
+ calculate the correct Resolution and
Color Depth settings.
@@ -275,8 +274,8 @@
To change the selected monitor, click
- Configure. A list of manufacturers will then
- be displayed. Find the manufacturer of your monitor on the list
+ Configure. This displays a list of
+ manufacturers. Find the manufacturer of your monitor on the list
and click the disclosure triangle next to the name of the
manufacturer to view the models of monitor. Select the correct
model from the list and click OK. If none
@@ -306,7 +305,7 @@
You also can select different Resolution and
Color Depth settings by choosing them from
the drop-down lists. Only the settings that are valid for the
- detected hardware will be displayed.
+ hardware are displayed.
@@ -326,11 +325,10 @@
Sound Card
- The Setup Agent will attempt to automatically identify the sound
- card in your computer. To confirm that the sound card is
- configured correctly, click Play Test
- Sound. You should then hear a series of three
- sounds.
+ The Setup Agent automatically identifies the sound card in your
+ computer. To confirm that the sound card is configured
+ correctly, click Play Test Sound. You
+ should then hear a series of three sounds.
From fedora-docs-commits at redhat.com Wed May 11 23:48:38 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 11 May 2005 19:48:38 -0400
Subject: install-guide fedora-install-guide-installingpackages-en.xml, 1.4,
1.5
Message-ID: <200505112348.j4BNmcZF005505@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5497
Modified Files:
fedora-install-guide-installingpackages-en.xml
Log Message:
Passive voice fixes.
Index: fedora-install-guide-installingpackages-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-installingpackages-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-installingpackages-en.xml 9 May 2005 20:18:17 -0000 1.4
+++ fedora-install-guide-installingpackages-en.xml 11 May 2005 23:48:36 -0000 1.5
@@ -4,8 +4,8 @@
Installing Packages
- The installation process will now take place. You will see the
- progress reported on screen.
+ The progress of the installation is reported on screen. Network and
+ DVD installations do not require any action.
@@ -33,15 +33,15 @@
- Once the installation has completed you will be prompted to
- Reboot your computer. Any disc in the CD or
- DVD drive will automatically be ejected before your computer reboots.
+ Click Reboot to restart your computer once
+ the installation has completed. Discs are automatically ejected
+ before the computer reboots.
- The first time that your computer loads &FC; you will be presented
- with a Welcome screen, and given the opportunity
- to configure various aspects of your new system. This process is
+ The first time that your computer loads &FC;, you are presented with
+ a Welcome screen and given the opportunity to
+ configure various aspects of your new system. This process is
explained in the next section.
From fedora-docs-commits at redhat.com Thu May 12 00:43:50 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 11 May 2005 20:43:50 -0400
Subject: install-guide fedora-install-guide-packageselection-en.xml,1.4,1.5
Message-ID: <200505120043.j4C0hodv006521@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6513
Modified Files:
fedora-install-guide-packageselection-en.xml
Log Message:
Style edits.
Index: fedora-install-guide-packageselection-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-packageselection-en.xml 9 May 2005 20:51:31 -0000 1.4
+++ fedora-install-guide-packageselection-en.xml 12 May 2005 00:43:48 -0000 1.5
@@ -11,19 +11,24 @@
- Package selection does not impose any restrictions after the
- installation process has completed. You can use the management
- utilities supplied with &FC; to install or remove any available
- software from the system at any time.
+ If you chose the Custom installation type then the screen for
+ Package Group Selection is shown automatically.
+
+ Installation Choices Are Not Permanent
+
+ The installation type and packages that you select do not
+ impose any restrictions after the installation process has completed.
+
+
+
Package Installation Defaults
- A summary of the default package selection will be displayed for
- your approval.
+ A summary of the default package selection is displayed.
@@ -50,21 +55,14 @@
To view or change the packages, select Customize
- software packages to be installed. This option will
- take you to the Package Group Selection
- screen.
+ software packages to be installed. This option takes
+ you to the Package Group Selection screen.
Click Next to proceed.
-
- If you chose the Custom installation type then the screen for
- Package Group Selection will automatically be
- shown at this point instead.
-
-
@@ -72,13 +70,9 @@
Package Group Selection
- Software is managed in groups. Each group includes packages for a
- particular system or function.
-
-
-
- These package groups are listed under headings to increase the
- readability of the screen.
+ The software included with &FC; is divided into package
+ groups, enabling you to specify the systems and
+ functions that you require.
@@ -99,32 +93,31 @@
- Against each group is listed the number of packages within the
- group that will be installed, and the total number of packages in
- that group.
-
-
-
- The groups required for the installation type that you chose are
+ The default groups for the installation type that you chose are
ticked. You can select or remove any group of packages at this
point, including those for the installation type.
No packages from a group will be installed unless the checkbox
- next to the group is ticked.
+ next to the group is ticked.
-
+
To change which packages within a selected group will be installed,
click the Details link next to the name of
- the group. The Base Packages of a group will
- automatically be installed if the group has been selected.
+ the group. The Base Packages of a group are
+ automatically installed if the group is selected.
Optional Packages can be selected or
deselected by clicking the checkbox next to the name of the
individual package.
+
+ Listed against each group is the number of packages are currently
+ slected for installation, and the total number of packages within that group.
+
+
Package Group Details Dialog
@@ -149,7 +142,7 @@
Selecting Support for Additional Languages
- Your &FED; system will automatically support the language that you
+ Your &FED; system automatically supports the language that you
selected at the start of the installation process. To include
support for additional languages, select the packages for those
languages from the Language Support package
@@ -170,8 +163,8 @@
Two of the groups under the heading of
Miscellaneous are not compatible with the
- others. For this reason, selecting either of these groups will
- prevent you from using all of the other groups on the list.
+ others. For this reason, selecting either of these groups
+ prevents you from using the other groups on the list.
@@ -201,10 +194,9 @@
When you are satisfied with the packages selected for
installation, click Next. The installation
- system will then check your selection and automatically resolve
- inconsistencies by adding any other packages needed to support the
- software that you have chosen. You will then move on to the next
- screen.
+ system checks your selection, and automatically adds any extra
+ packages required for the software that you have selected, before
+ moving on to the next screen.
From fedora-docs-commits at redhat.com Thu May 12 14:05:38 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 12 May 2005 10:05:38 -0400
Subject: install-guide fedora-install-guide-intro-en.xml,1.3,1.4
Message-ID: <200505121405.j4CE5cQB023703@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23695/install-guide
Modified Files:
fedora-install-guide-intro-en.xml
Log Message:
Cleaned up admonition in intro
Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-intro-en.xml 1 May 2005 17:59:44 -0000 1.3
+++ fedora-install-guide-intro-en.xml 12 May 2005 14:05:36 -0000 1.4
@@ -10,9 +10,9 @@
- &FED; is not intended for critical systems
+ &FC; Lifecycle
- &FC; is a rapidly evolving system that follows the latest
+ &FC; is a rapidly evolving system which follows the latest
technical developments. It may not be appropriate to use &FC; in
critical applications in your organization.
From fedora-docs-commits at redhat.com Thu May 12 22:27:33 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 12 May 2005 18:27:33 -0400
Subject: install-guide fedora-install-guide-diskpartitioning-en.xml, 1.3,
1.4 fedora-install-guide-en.xml, 1.10,
1.11 fedora-install-guide-installtypes-en.xml, 1.3,
1.4 fedora-install-guide-other-instmethods-en.xml, 1.5,
1.6 fedora-install-guide-upgrading-en.xml, 1.4, 1.5
Message-ID: <200505122227.j4CMRXXv002443@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2435
Modified Files:
fedora-install-guide-diskpartitioning-en.xml
fedora-install-guide-en.xml
fedora-install-guide-installtypes-en.xml
fedora-install-guide-other-instmethods-en.xml
fedora-install-guide-upgrading-en.xml
Log Message:
Style editing continues, started indexing
Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-diskpartitioning-en.xml 3 May 2005 12:19:44 -0000 1.3
+++ fedora-install-guide-diskpartitioning-en.xml 12 May 2005 22:27:31 -0000 1.4
@@ -3,56 +3,92 @@
Disk Partitioning
- This section describes how to use the installation program to
- partition disks attached to your &FED; system. If you are new to
- Linux, you may want to simply use the automatic partitioning method.
- If you are a more experienced Linux user, you can use the manual
- partitioning method to have more control over your system
+ If you are new to Linux, you may want to use the automatic
+ partitioning method. If you are a more experienced Linux user, use
+ the manual partitioning method for more control over your system
configuration.
Choosing a Partitioning Method
-
+
Setting Up Partitions Automatically
Choose Automatic partitioning at the
- partitioning menu to have a partition scheme set up for you.
+ partitioning menu to use a preset partitioning layout.
Disk Druid then displays additional
- options. Select Remove all Linux partitions on this
- system to remove all ext2,
- ext3, or Linux
- swap partitions from all hard disks. Select
- Remove all partitions on this system to
- remove all partitions from all hard disks. Select
- Keep all partitions and use only existing free
- space to use only the unpartitioned space on the
- hard disk(s) to install &FC;.
+ options:
+
+
+
+ Remove all Linux partitions on this
+ system
+
+
+ Removes all ext2,
+ ext3, and Linux
+ swap partitions from all hard disks
+
+
+
+
+ Remove all partitions on this
+ system
+
+
+ Removes all partitions from all hard
+ disks
+
+
+
+
+ Keep all partitions and use only existing free
+ space
+
+
+ Uses only the unpartitioned space on the hard disk(s) to
+ install &FC;
+
+
+
+
+
+
+ Select the desired option.
+
+
Next, select the drive(s) you wish to use for Linux partitions.
- If your system contains only one disk, that disk will
- automatically be selected. If you are confused about the device
- names used in this box, consult the Linux Partition-HOWTO at
- http://www.tldp.org/HOWTO/Partition/partition-2.html.
- Any drives you select will be used for Linux partitions
- according to the option selected above. The option selection is
- global, and you may not select a different option for each disk.
+ If your system contains only one disk, that disk is
+ automatically selected. Any drives you select are used for
+ Linux partitions according to the option selected above. The
+ option selection is global, and you may not select a different
+ option for each disk.
+
+
+ Device Names
+
+ If you are confused about the device names used in this box,
+ consult the Linux Partition-HOWTO at http://www.tldp.org/HOWTO/Partition/partition-2.html.
+
+
+
- If you wish to review the automatic partition configuration,
- select the Review checkbox.
+ To review the automatic partition configuration, select the
+ Review checkbox.
- If you chose to remove any existing partitions, the
- installation program will ask you to confirm this choice. Once
- you have reviewed and approve of the partition configuration,
- select Next to continue to the next
- installation step. Proceed with .
+ If you remove any existing partitions, the installation program
+ asks you to confirm this choice. Once you have reviewed and
+ approve of the partition configuration, select
+ Next to continue to the next installation
+ step. Proceed with .
@@ -61,13 +97,12 @@
Setting Up Partitions Manually
- If you wish to manually set up all disk partitions, choose
- Manually partition with Disk Druid. You
- should choose this method if you require a special partition
- configuration. If you are familiar with how disk partitions and
- the Linux file system work, move on to . Otherwise, read .
+ To manually set up all disk partitions, choose
+ Manually partition with Disk Druid. Choose
+ this method if you require a special partition configuration. If
+ you are familiar with how disk partitions and the Linux file
+ system work, move on to .
+ Otherwise, read .
@@ -78,7 +113,7 @@
General Information
- A &FC; system should have at least three partitions installed:
+ A &FC; system has at least three partitions:
@@ -98,27 +133,44 @@
- Most systems have more partitions than the minimum listed above.
+ Most systems have more partitions than the minimum listed above.
Choose partitions based on your particular system needs. If you
are not sure what to choose, use the "Automatic partitioning"
method shown in .
- Every partition must have a partition type.
- The partition type indicates the file system expected on that
- partition. The most common partition type for &FED; is
- ext3 or ext2. The
- ext3 file system provides more robust features for preventing data
- loss. Most &FED; administrators choose this type for data
- partitions.
+ Every partition has a
+ partition
+ type
+ file system
+ partition type. The partition
+ type indicates the
+ file system
+ file system expected on that
+ partition. A file system allows a Linux system to more
+ effectively organize, search, and retrieve files. The most common
+ partition type for &FED; is
+ ext3
+ file system
+
+ file system
+ ext3
+ ext3. The ext3 file system
+ provides more robust features for preventing data loss. Most
+ &FED; administrators choose this type for data partitions.
- Most partitions have a mount point. The
- mount point indicates the directory whose contents will reside on
- that partition. Data that does not reside on any other partition
- will be in the / (or
- "root") partition. In the minimum
- configuration shown above:
+ Most partitions have a
+ mount point
+ mount point. The mount point
+ indicates the directory whose contents reside on that partition. A
+ partition with no mount point is not accessible by users. Data
+ not located on any other partition resides in the
+ / (or
+ partition
+ root
+ "root") partition. In the
+ minimum configuration shown above:
@@ -149,9 +201,9 @@
/usr partition.
- When you create partitions in this manner, as opposed to using one
- large / partition, upgrades may be easier.
- See the description of Disk Druid's
+ When you create many partitions instead of one large
+ / partition, upgrades become easier. Refer
+ to the description of Disk Druid's
Edit option for more
information.
@@ -183,10 +235,10 @@
Disk Druid
- Disk Druid
-
+ Disk Druid
+ Disk Druid
- is an interactive program for editing disk
+ is an interactive program for editing disk
partitions. It is only available within the &FC; installation
system. Disk Druid supports advanced technologies such as
RAID and LVM, which
@@ -206,7 +258,7 @@
to the disk. In the Add partition
dialog, choose a mount point and a partition type. If you
have more than one disk on the system, choose which disks
- the partition may inhabit. Indicate a size in megabytes for
+ the partition may inhabit. Indicate a size in megabytes for
the partition.
@@ -224,10 +276,16 @@
Root and /root
- The / (or "root") partition is the
- top of the file system. The /root
- (or "slash-root") directory is the home directory of the
- administrator.
+ The / (or
+ partition
+ root
+ "root") partition is the top of the file
+ system. The
+ partition
+ /root
+ /root (sometimes
+ pronounced "slash-root") directory is the home directory
+ of the administrator.
@@ -314,9 +372,16 @@
Windows Partitions
You may not label Windows partitions that use the NTFS
- file system with a mount point in the &FC; installer. You
- may label vfat (FAT-16 or FAT-32)
- partitions with a mount point.
+ file system with a mount point in the &FC; installer. You
+ may label
+ vfat
+ file system
+
+
+ file system
+ vfat
+ vfat (FAT-16 or
+ FAT-32) partitions with a mount point.
@@ -329,7 +394,7 @@
If you have many separate partitions for system and user
- data, it will be easier for you to upgrade your system. The
+ data, it will be easier for you to upgrade your system. The
installation program allows you to erase or retain data on
specific partitions. If your user data is on a separate
/home partition, you may retain that
@@ -423,7 +488,7 @@
In LVM, one or more physical volumes are combined to form
a volume group. Each volume group's total storage may be
- apportioned for one or more logical volumes. Logical
+ apportioned for one or more logical volumes. Logical
volumes function much like standard data partitions. They
have a file system type, such as ext3, and a mount point.
An administrator may grow or shrink logical volumes
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fedora-install-guide-en.xml 10 May 2005 21:33:51 -0000 1.10
+++ fedora-install-guide-en.xml 12 May 2005 22:27:31 -0000 1.11
@@ -119,7 +119,9 @@
&ACKNOWLEDGEMENTS;
-
+
+
+
- First Step: Installation Type
+ Installation Types
- Installation types enable you to ensure that your &FED; system is
- loaded with the correct software without needing to specify
- individual packages. The installation type that you choose
- determines the suggested software later on in the installation
- process. You can customize the package selection at that point if
- you wish to do so.
-
-
-
- Installation Type Screen
-
-
-
-
-
-
-
-
-
- Installation type screen.
-
-
-
-
+ An installation type is a label that roughly
+ describes how you will use your &FED; system. Several installation
+ types are already defined in the &FC; installation program. Choose
+ the appropriate installation type to streamline the installation
+ process if you are a beginner. The installation program makes some
+ choices for you based on the type you select. These choices include
+ partitioning of your hard disks, and software packages to be
+ installed. All installation types allow you to customize these
+ selections.
+
+
+
+ Choosing an Installation Type
+
+
+ Installation Type Screen
+
+
+
+
+
+
+
+
+
+ Installation type screen.
+
+
+
+
-
- A Personal Desktop installation is the default.
- It provides a graphical working environment with an office suite,
- Internet applications and multimedia software.
-
+
+ The default installation type is a Personal
+ Desktop. It provides a graphical working environment
+ with an office suite, Internet applications and multimedia
+ software.
+
-
- A Workstation installation includes the same
- software as a Personal Desktop. Extra software
- will also be installed for development and systems administration.
- Choose this installation type if you will be compiling software from
- source code.
-
+
+ A Workstation installation includes the
+ software installed on a Personal Desktop, and
+ adds software for development and systems administration. Choose
+ this installation type if you plan to compile software from source
+ code.
+
-
- A Server installation automatically provides
- the Apache Web server and the Samba suite of services, along with
- administration tools. By default, no graphical environment is
- included.
-
+
+ A Server installation provides network
+ servers such as the Apache Web server and the Samba suite of
+ services, and administration tools. The
+ Server installation type provides no
+ graphical environment by default.
+
-
- If you choose to perform a Custom installation
- then you will automatically be presented with the Package
- Group Selection screen later on in the installation
- process.
-
+
+ The Custom installation type does not provide
+ any disk partitioning layout for you. It also does not include
+ any additional software beyond a Personal
+ Desktop. If you perform a Custom
+ installation, the installation program will present dialogs for
+ these selections during the installation process.
+
-
- Default network services
- All &FC; installations include e-mail (SMTP), file sharing (NFS),
- printing (CUPS) and remote login (SSH) services. Various
- automated processes on your &FED; system use the e-mail service to
- send reports and messages to the system administrator. By default
- the e-mail and printing services do not accept connections from
- other systems.
+ Click Next once you have made a selection.
-
-
- Click Next once you have made a selection.
-
+
+
+
+ Special Considerations
-
- Minimal installations
- To install a system with the minimum of software choose the
- Custom installation type. On the
- Package Group Selection screen select the
- Minimal package group. A small command-line
- only system will then be installed. The only services that are
- included in a Minimal installation are CUPS,
- NFS, SMTP and SSH. This type of installation is useful as a basis
- for preparing specialized systems.
+ All &FC; installations include email (SMTP), file sharing (NFS),
+ printing (CUPS) and remote login (SSH) services. Some automated
+ processes on your &FED; system use the email service to send
+ reports and messages to the system administrator. By default, the
+ email and printing services do not accept connections from other
+ systems. If you want your &FED; system to function as an email or
+ print server, you may configure it after installation.
-
+
+
+ Minimal installations
+
+ To install a minimum of software, choose the
+ Custom installation type. On the
+ Package Group Selection screen, select the
+ Minimal package group. The only services
+ included in a Minimal installation are
+ printing, email (SMTP), secure remote login (SSH), and network
+ file access (NFS). This type of installation may be useful for
+ firewalls or other specialized systems on which limited service
+ is an advantage.
+
+
+
+
Index: fedora-install-guide-other-instmethods-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-other-instmethods-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-other-instmethods-en.xml 8 May 2005 23:33:13 -0000 1.5
+++ fedora-install-guide-other-instmethods-en.xml 12 May 2005 22:27:31 -0000 1.6
@@ -169,7 +169,7 @@
Installation from a Hard Drive
- You may install from a hard drive containing the ISO image files
+ You can install from a hard drive containing the ISO image files
for the &FED; discs. The hard drive can be either internal to the
computer, or attached by USB. The partition on the hard drive
holding the ISO files must be formatted with either ext2, ext3 or
@@ -200,16 +200,18 @@
Select the partition containing the ISO files from the list of
- available partitions. Each drive is assigned a unique letter.
- Each partition on a drive is numbered. Internal IDE drive device
- names begin with /dev/hd. SCSI or USB drive
- device names begin with /dev/sd.
+ available partitions. Internal IDE drive device names begin with
+ /dev/hd. SCSI or USB drive device names
+ begin with /dev/sd. Each individual drive
+ has its own letter, for example /dev/hda.
+ Each partition on a drive is numbered, for example
+ /dev/sda1.
- You must also specify the Directory holding
- images. Enter the full directory path on the drive
- that contains the ISO image files.
+ Also specify the Directory holding images.
+ Enter the full directory path on the drive that contains the ISO
+ image files.
Index: fedora-install-guide-upgrading-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-upgrading-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-upgrading-en.xml 9 May 2005 21:28:28 -0000 1.4
+++ fedora-install-guide-upgrading-en.xml 12 May 2005 22:27:31 -0000 1.5
@@ -34,20 +34,20 @@
- An upgrade consists of updating the existing &FC; or &RHL;
- installation with the software packages for the new version. Your
- data is not lost, and the existing partition structure on your hard
- drives does not change. Your system configuration changes only if a
- package upgrade demands it. The upgrade process does not delete any
- files in the /home/ and the
- /usr/local/ directories.
+ The upgrade process updates the existing &FC; or &RHL; software with
+ new versions. The process does not remove any data from users' home
+ directories. The existing partition structure on your hard drives
+ does not change. Your system configuration changes only if a
+ package upgrade demands it. Most package upgrades do not change
+ system configuration, but rather install an additional configuration
+ file for you to examine later.
Manually Installed Software
- Software which you installed manually on your existing &FC; or
- &RHL; system may behave differently after an upgrade. You may
+ Software which you have installed manually on your existing &FC;
+ or &RHL; system may behave differently after an upgrade. You may
manually recompile this software after an upgrade to ensure it
performs correctly on the updated system.
From fedora-docs-commits at redhat.com Thu May 12 23:56:00 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 12 May 2005 19:56:00 -0400
Subject: install-guide fedora-install-guide-abouttoinstall-en.xml, 1.4,
1.5 fedora-install-guide-bootloader-en.xml, 1.5,
1.6 fedora-install-guide-diskpartitioning-en.xml, 1.4,
1.5 fedora-install-guide-firewallconfig-en.xml, 1.4,
1.5 fedora-install-guide-networkconfig-en.xml, 1.4,
1.5 fedora-install-guide-packageselection-en.xml, 1.5,
1.6 fedora-install-guide-rootpassword-en.xml, 1.4,
1.5 fedora-install-guide-timezone-en.xml, 1.3, 1.4
Message-ID: <200505122356.j4CNu1ih003948@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3936/install-guide
Modified Files:
fedora-install-guide-abouttoinstall-en.xml
fedora-install-guide-bootloader-en.xml
fedora-install-guide-diskpartitioning-en.xml
fedora-install-guide-firewallconfig-en.xml
fedora-install-guide-networkconfig-en.xml
fedora-install-guide-packageselection-en.xml
fedora-install-guide-rootpassword-en.xml
fedora-install-guide-timezone-en.xml
Log Message:
Removed "step" counters; additional style editing in Disk Partitioning chapter
Index: fedora-install-guide-abouttoinstall-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-abouttoinstall-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-abouttoinstall-en.xml 9 May 2005 20:29:35 -0000 1.4
+++ fedora-install-guide-abouttoinstall-en.xml 12 May 2005 23:55:56 -0000 1.5
@@ -1,7 +1,7 @@
- Ninth Step: About to Install
+ About to InstallThis is the last point at which you can decide to stop the
Index: fedora-install-guide-bootloader-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-bootloader-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-bootloader-en.xml 9 May 2005 22:33:18 -0000 1.5
+++ fedora-install-guide-bootloader-en.xml 12 May 2005 23:55:56 -0000 1.6
@@ -1,6 +1,6 @@
- Third Step: Boot Loader
+ Boot Loader
A boot loader is a small program that reads
Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-diskpartitioning-en.xml 12 May 2005 22:27:31 -0000 1.4
+++ fedora-install-guide-diskpartitioning-en.xml 12 May 2005 23:55:57 -0000 1.5
@@ -196,8 +196,8 @@
under /usr/local, such as
/usr/local/bin/foo, will be on the
/usr/local partition. Any other files in
- /usr, such as the
- /usr/bin directory, will be in the
+ /usr, such as
+ /usr/bin/foo, will be in the
/usr partition.
@@ -239,11 +239,10 @@
Disk Druid is an interactive program for editing disk
- partitions. It is only available within the &FC; installation
+ partitions. Users run it only within the &FC; installation
system. Disk Druid supports advanced technologies such as
RAID and LVM, which
- provide more extensible and reliable data storage for servers and
- workstations.
+ provide more extensible and reliable data storage.
Disk Druid displays the following
@@ -270,7 +269,10 @@
and /sbin directories may not be used
for separate partitions in Disk
Druid. These directories reside on the
- / (root) partition.
+
+ partition
+ root
+ / (root) partition.
@@ -341,10 +343,15 @@
Select this option to edit an existing partition, LVM volume
group, or a LVM physical volume that is not yet part of a
volume group. If you need to change the size of a LVM
- physical volume partition, you will need to remove it from
- any volume groups, which will erase any logical volumes it
- contains.
+ physical volume partition, remove it from any volume groups.
+
+ Removing LVM Physical Volumes
+
+ If you remove a LVM physical volume from a volume group,
+ you will erase any logical volumes it contains.
+
+
Edit a partition to change its size, mount point, or file
system type. Use this function to:
@@ -371,9 +378,16 @@
Windows Partitions
- You may not label Windows partitions that use the NTFS
- file system with a mount point in the &FC; installer. You
- may label
+ You may not label Windows partitions that use the
+
+ NTFS
+ file system
+
+
+ file system
+ NTFS
+ NTFS file system with a mount point in the
+ &FC; installer. You may label vfatfile system
@@ -388,17 +402,19 @@
If you need to make sweeping changes to your partition
configuration, consider starting over. If your disk
contains data that you need to keep, back it up before you
- edit your partitions. If you edit the sizes of your
- partitions, you will likely lose all data on those
- partitions.
+ edit any partitions. If you edit the size of a partition,
+ you may lose all data on it.
- If you have many separate partitions for system and user
- data, it will be easier for you to upgrade your system. The
+ If your system contains many separate partitions for system
+ and user data, it is easier to upgrade your system. The
installation program allows you to erase or retain data on
specific partitions. If your user data is on a separate
- /home partition, you may retain that
- data while erasing system partitions like
+
+ partition
+ /home
+ /home partition, you may
+ retain that data while erasing system partitions such as
/boot.
@@ -453,7 +469,7 @@
Choose this option to construct a RAID device from two
or more existing software RAID partitions. This
- option is only available if two or more software RAID
+ option is available if two or more software RAID
partitions have been configured.
@@ -465,7 +481,7 @@
Choose this option to set up a RAID
mirror of an existing disk.
- This option is only available if two or more disks are
+ This option is available if two or more disks are
attached to the system.
@@ -477,11 +493,11 @@
LVM
- Select this button to set up LVM on your &FED; system. You
- must first create at least one partition or software RAID
- device as a LVM physical volume, using the
- Add option in the main
- Disk Druid dialog.
+ Select this button to set up LVM on your &FED; system.
+ First create at least one partition or software RAID device
+ as a LVM physical volume, using the Add
+ option in the main Disk Druid
+ dialog.
Understanding LVM Components
@@ -491,9 +507,8 @@
apportioned for one or more logical volumes. Logical
volumes function much like standard data partitions. They
have a file system type, such as ext3, and a mount point.
- An administrator may grow or shrink logical volumes
- without disturbing any data, unlike standard disk
- partitions.
+ An administrator can grow or shrink logical volumes
+ without destroying data, unlike standard disk partitions.
@@ -507,20 +522,20 @@
You may not remove a physical volume from a volume group if
doing so would leave insufficient space for that group's
- logical volumes. For example, imagine a volume group made
- up of two 5 GB LVM physical volume partitions, which houses
- a logical volume that is 8 GB in size. The installer will
- not allow you to remove either of the component physical
- volumes, since that would leave only 5 GB in the group for
- an 8 GB logical volume. If you reduce the total size of any
- logical volumes appropriately, you may then remove a
- physical volume from the volume group.
+ logical volumes. Take for example a volume group made up of
+ two 5 GB LVM physical volume partitions, which houses an 8
+ GB logical volume. The installer would not allow you to
+ remove either of the component physical volumes, since that
+ would leave only 5 GB in the group for an 8 GB logical
+ volume. If you reduce the total size of any logical volumes
+ appropriately, you may then remove a physical volume from
+ the volume group.
- When you have finished setting up and reviewing your partition
+ After you finish setting up and reviewing your partition
configuration, select Next to continue the
installation process.
Index: fedora-install-guide-firewallconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firewallconfig-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-firewallconfig-en.xml 9 May 2005 22:22:12 -0000 1.4
+++ fedora-install-guide-firewallconfig-en.xml 12 May 2005 23:55:57 -0000 1.5
@@ -1,7 +1,7 @@
- Fifth Step: Firewall Configuration
+ Firewall Configuration
The default security configuration for &FC; will protect your system
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-networkconfig-en.xml 9 May 2005 22:39:03 -0000 1.4
+++ fedora-install-guide-networkconfig-en.xml 12 May 2005 23:55:58 -0000 1.5
@@ -1,7 +1,7 @@
- Fourth Step: Network Configuration
+ Network Configuration
This screen enables you to customize the network settings of the
Index: fedora-install-guide-packageselection-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-packageselection-en.xml 12 May 2005 00:43:48 -0000 1.5
+++ fedora-install-guide-packageselection-en.xml 12 May 2005 23:55:58 -0000 1.6
@@ -1,7 +1,7 @@
- Eighth Step: Package Selection
+ Package Selection
The installation type that you chose earlier in the process is used
Index: fedora-install-guide-rootpassword-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-rootpassword-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-rootpassword-en.xml 10 May 2005 21:25:56 -0000 1.4
+++ fedora-install-guide-rootpassword-en.xml 12 May 2005 23:55:58 -0000 1.5
@@ -1,7 +1,7 @@
- Seventh Step: Set the Root Password
+ Set the Root Password
The root account on every Linux system is
Index: fedora-install-guide-timezone-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-timezone-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-timezone-en.xml 9 May 2005 22:47:14 -0000 1.3
+++ fedora-install-guide-timezone-en.xml 12 May 2005 23:55:58 -0000 1.4
@@ -1,7 +1,7 @@
- Sixth Step: Time Zone Selection
+ Time Zone Selection
You must specify the correct time zone for the location of your
From fedora-docs-commits at redhat.com Fri May 13 00:04:04 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 12 May 2005 20:04:04 -0400
Subject: install-guide fedora-install-guide-upgrading-en.xml,1.5,1.6
Message-ID: <200505130004.j4D044Ji004959@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4951
Modified Files:
fedora-install-guide-upgrading-en.xml
Log Message:
Fixed Upgrade chapter for better information flow
Index: fedora-install-guide-upgrading-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-upgrading-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-upgrading-en.xml 12 May 2005 22:27:31 -0000 1.5
+++ fedora-install-guide-upgrading-en.xml 13 May 2005 00:04:02 -0000 1.6
@@ -4,55 +4,58 @@
Upgrading an Existing System
- The installation system will automatically detect any existing
- installation of &FC;. If there is a copy of &FC; then you will be
- presented with this screen:
+ The installation system automatically detects any existing
+ installation of &FC;. The upgrade process updates the existing &FC;
+ or &RHL; software with new versions. The process does not remove
+ any data from users' home directories. The existing partition
+ structure on your hard drives does not change. Your system
+ configuration changes only if a package upgrade demands it. Most
+ package upgrades do not change system configuration, but rather
+ install an additional configuration file for you to examine later.
-
- Upgrade Examine Screen
-
-
-
-
-
-
-
-
-
- Upgrade examine screen.
-
-
-
-
-
-
-
- To perform an upgrade of an existing system, select the appropriate
- installation from the drop-down list and then select
- Next.
-
+
+ Upgrade Examine
-
- The upgrade process updates the existing &FC; or &RHL; software with
- new versions. The process does not remove any data from users' home
- directories. The existing partition structure on your hard drives
- does not change. Your system configuration changes only if a
- package upgrade demands it. Most package upgrades do not change
- system configuration, but rather install an additional configuration
- file for you to examine later.
-
+
+ If your system contains a &FC; or &RHL; installation, the
+ following screen appears:
+
+
+
+ Upgrade Examine Screen
+
+
+
+
+
+
+
+
+
+ Upgrade examine screen.
+
+
+
+
-
- Manually Installed Software
- Software which you have installed manually on your existing &FC;
- or &RHL; system may behave differently after an upgrade. You may
- manually recompile this software after an upgrade to ensure it
- performs correctly on the updated system.
+ To perform an upgrade of an existing system, choose the
+ appropriate installation from the drop-down list and select
+ Next.
-
+
+ Manually Installed Software
+
+ Software which you have installed manually on your existing &FC;
+ or &RHL; system may behave differently after an upgrade. You
+ may manually recompile this software after an upgrade to ensure
+ it performs correctly on the updated system.
+
+
+
+ Upgrading Boot Loader Configuration
@@ -108,8 +111,7 @@
installation system cannot update it. In this case, select
Skip boot loader updating. When the
installation process completes, refer to the documentation for
- your product for help adding &FC; to your boot loader
- configuration.
+ your product for assistance.
From fedora-docs-commits at redhat.com Fri May 13 22:03:34 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Fri, 13 May 2005 18:03:34 -0400
Subject: install-guide fedora-install-guide-diskpartitioning-en.xml,1.5,1.6
Message-ID: <200505132203.j4DM3YUW032023@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32015/install-guide
Modified Files:
fedora-install-guide-diskpartitioning-en.xml
Log Message:
Style editing and additional indexing of Disk Partitioning chapter
Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-diskpartitioning-en.xml 12 May 2005 23:55:57 -0000 1.5
+++ fedora-install-guide-diskpartitioning-en.xml 13 May 2005 22:03:32 -0000 1.6
@@ -201,7 +201,7 @@
/usr partition.
- When you create many partitions instead of one large
+ If you create many partitions instead of one large
/ partition, upgrades become easier. Refer
to the description of Disk Druid's
Edit option for more
@@ -241,8 +241,12 @@
is an interactive program for editing disk
partitions. Users run it only within the &FC; installation
system. Disk Druid supports advanced technologies such as
- RAID and LVM, which
- provide more extensible and reliable data storage.
+ RAID
+ RAID
+ and LVM,
+ LVM
+ which provide more extensible and reliable data
+ storage.
Disk Druid displays the following
@@ -253,12 +257,14 @@
New
- Select this option to add a partition or LVM physical volume
- to the disk. In the Add partition
- dialog, choose a mount point and a partition type. If you
- have more than one disk on the system, choose which disks
- the partition may inhabit. Indicate a size in megabytes for
- the partition.
+ Select this option to add a partition
+ partition
+ adding
+ or LVM physical volume to the disk. In the
+ Add partition dialog, choose a mount
+ point and a partition type. If you have more than one disk
+ on the system, choose which disks the partition may inhabit.
+ Indicate a size in megabytes for the partition.
Some Partitions Not Allowed
@@ -340,10 +346,14 @@
Edit
- Select this option to edit an existing partition, LVM volume
- group, or a LVM physical volume that is not yet part of a
- volume group. If you need to change the size of a LVM
- physical volume partition, remove it from any volume groups.
+ Select this option to edit an existing partition,
+
+ partition
+ editing
+ LVM volume group, or a LVM physical volume that
+ is not yet part of a volume group. To change the size of a
+ LVM physical volume partition, first remove it from any
+ volume groups.
Removing LVM Physical Volumes
@@ -359,19 +369,19 @@
- correct a mistake in setting up your partitions;
+ correct a mistake in setting up your partitions
migrate Linux partitions if you are upgrading or
- reinstalling &FC;; or
+ reinstalling &FC;
provide a mount point for non-Linux partitions such as
- those used on some Windows operating systems.
+ those used on some Windows operating systems
@@ -399,11 +409,12 @@
- If you need to make sweeping changes to your partition
- configuration, consider starting over. If your disk
- contains data that you need to keep, back it up before you
- edit any partitions. If you edit the size of a partition,
- you may lose all data on it.
+ If you need to make drastic changes to
+ your partition configuration, you may want to delete
+ partitions and start over. If your disk contains data that
+ you need to keep, back it up before you edit any partitions.
+ If you edit the size of a partition, you may lose all data
+ on it.
If your system contains many separate partitions for system
@@ -423,9 +434,12 @@
Delete
- Select a partition and then this option to erase an existing
- partition or LVM physical volume. To delete a LVM physical
- volume, you must first delete any volume groups of which
+ Select this option to erase an existing partition
+
+ partition
+ deleting
+ or LVM physical volume. To delete a LVM
+ physical volume, first delete any volume groups of which
that physical volume is a member.
@@ -448,8 +462,9 @@
RAID
- Select this button to set up software RAID on your &FED;
- system.
+ Select this button to set up software RAID
+ RAID
+ on your &FED; system.
@@ -493,22 +508,27 @@
LVM
- Select this button to set up LVM on your &FED; system.
- First create at least one partition or software RAID device
- as a LVM physical volume, using the Add
- option in the main Disk Druid
- dialog.
+ Select this button to set up LVM
+ LVM
+ on your &FED; system. First create at least one
+ partition or software RAID device as a LVM physical volume,
+ using the Add option in the main
+ Disk Druid dialog.
Understanding LVM Components
- In LVM, one or more physical volumes are combined to form
- a volume group. Each volume group's total storage may be
- apportioned for one or more logical volumes. Logical
- volumes function much like standard data partitions. They
- have a file system type, such as ext3, and a mount point.
- An administrator can grow or shrink logical volumes
- without destroying data, unlike standard disk partitions.
+ In LVM,
+ LVM
+ understanding
+ one or more physical volumes are combined to
+ form a volume group. Each volume group's total storage
+ may be apportioned for one or more logical volumes.
+ Logical volumes function much like standard data
+ partitions. They have a file system type, such as ext3,
+ and a mount point. An administrator can grow or shrink
+ logical volumes without destroying data, unlike standard
+ disk partitions.
@@ -522,9 +542,9 @@
You may not remove a physical volume from a volume group if
doing so would leave insufficient space for that group's
- logical volumes. Take for example a volume group made up of
- two 5 GB LVM physical volume partitions, which houses an 8
- GB logical volume. The installer would not allow you to
+ logical volumes. Take, for example, a volume group made up
+ of two 5 GB LVM physical volume partitions, which contains an
+ 8 GB logical volume. The installer would not allow you to
remove either of the component physical volumes, since that
would leave only 5 GB in the group for an 8 GB logical
volume. If you reduce the total size of any logical volumes
From fedora-docs-commits at redhat.com Fri May 13 22:44:00 2005
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Fri, 13 May 2005 18:44:00 -0400
Subject: install-guide fedora-install-guide-firstboot-en.xml,1.5,1.6
Message-ID: <200505132244.j4DMi0Up032137@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32124
Modified Files:
fedora-install-guide-firstboot-en.xml
Log Message:
Style edit fixes.
Also fixed spelling of licence/license within text to match US.
Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-firstboot-en.xml 11 May 2005 23:38:04 -0000 1.5
+++ fedora-install-guide-firstboot-en.xml 13 May 2005 22:43:58 -0000 1.6
@@ -4,9 +4,9 @@
On First Boot
- The first time that you load a new installation of &FC; the Setup
- Agent is launched, enabling you to configure the basic elements of the
- system.
+ The Setup Agent launches the first time
+ that you start a new &FED; system. This enables you to configure
+ the system for use before logging in.
@@ -27,11 +27,11 @@
- Click Next to start the Setup Agent.
+ Click Next to start the Setup Agent.
- The Setup Agent requires a graphical interface
+ The Setup Agent requires a graphical interface
You must manually carry out these configuration tasks if the Setup
Agent cannot run.
@@ -40,12 +40,12 @@
- Licence Agreement
+ License Agreement
- This screen displays the overall licencing terms for &FC;.
- Individual software packages are covered by their own licences.
- Every software product included in &FC; uses a licence that has
+ This screen displays the overall licensing terms for &FC;.
+ Individual software packages are covered by their own licenses.
+ Every software product included in &FC; uses a license that has
been approved by the Open Source Initiative (OSI).
@@ -60,14 +60,14 @@
- Licence agreement screen.
+ License agreement screen.
- To proceed, select Yes, I agree to the Licence
+ To proceed, select Yes, I agree to the License
Agreement and click Next.
@@ -78,14 +78,15 @@
Date and Time
- You can either manually set the date and time for your system, or
- configure your system to use NTP (Network Time Protocol) servers
- to maintain the clock. NTP ensures that the time is always accurate.
+ To configure a system that does not have Internet access, manually
+ set the date and time for your system at this screen. If your
+ system has network access, use NTP (Network Time Protocol) servers
+ to maintain the accuracy of the clock.
The initial display enables you to set the date and time of your
- system manually:
+ system manually.
@@ -107,7 +108,7 @@
Select the Network Time Protocol tab to
- configure your system to use network time servers instead.
+ configure your system to use NTP servers instead.
@@ -249,10 +250,10 @@
Display
- The Setup Agent attempts to identify the graphics hardware and
- monitor for your computer. It also uses this information to
- calculate the correct Resolution and
- Color Depth settings.
+ The Setup Agent automatically attempts
+ to identify the graphics card and monitor for your computer. It also uses
+ this information to calculate the correct
+ Resolution and Color Depth settings.
@@ -302,10 +303,11 @@
- You also can select different Resolution and
- Color Depth settings by choosing them from
- the drop-down lists. Only the settings that are valid for the
- hardware are displayed.
+ To change a display setting, click
+ Resolution or Color
+ Depth, and select a new value from the drop-down list. The
+ Setup Agent only shows the settings
+ that are valid for your hardware.
@@ -314,7 +316,7 @@
To reconfigure your system after the installation has completed,
use the system-config-display
utility. From the main menu, choose System
- SettingsDisplay.
+ SettingsDisplay.
@@ -325,10 +327,8 @@
Sound Card
- The Setup Agent automatically identifies the sound card in your
- computer. To confirm that the sound card is configured
- correctly, click Play Test Sound. You
- should then hear a series of three sounds.
+ The Setup Agent automatically
+ identifies the sound card in your computer.
@@ -347,7 +347,20 @@
-
+
+
+ Click Play Test Sound. If you hear a
+ series of three sounds then your system has been configured
+ successfully. If your sound card is identified but you do not
+ hear these sounds, check your speakers and try again.
+
+
+
+ You can manually configure a &FED; system to use unsupported sound
+ cards after the installation process is complete. Manual hardware
+ configuration is beyond the scope of this document.
+
+
Changing the sound card
@@ -410,8 +423,8 @@
- After you click Next, the login screen will
- appear. Your &FC; system is now ready for use.
+ Click Next to proceed to the login
+ screen. Your &FC; system is now ready for use.
From fedora-docs-commits at redhat.com Sat May 14 15:20:05 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 14 May 2005 11:20:05 -0400
Subject: install-guide fedora-install-guide-networkconfig-en.xml,1.5,1.6
Message-ID: <200505141520.j4EFK5mi019707@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19699
Modified Files:
fedora-install-guide-networkconfig-en.xml
Log Message:
Turned all sect[0-9] into section; started style edits and indexing
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-networkconfig-en.xml 12 May 2005 23:55:58 -0000 1.5
+++ fedora-install-guide-networkconfig-en.xml 14 May 2005 15:20:02 -0000 1.6
@@ -4,29 +4,45 @@
Network Configuration
- This screen enables you to customize the network settings of the
- final system.
+ This screen enables you to customize the network settings of your
+ &FED; system. Networking is a complex subject which is currently
+ beyond the scope of this document. For more information on basic
+ networking concepts, refer to one or more of the following
+ documents. To find a specific title online, search for the title
+ using an Internet search engine such as Google (http://www.google.com/).
+
+
+
+ Chapters 1 and 2 of the Linux Network Administrators
+ Guide
+
+
+
+
+ The Linux Networking-HOWTO
+
+
+
+
- It is not necessary to manually configure these settings if your
- computer will be part of an existing network, or if it is a laptop
- that will move between networks. By default, &FC; will activate
- all of the network interfaces on your computer and configure them to
- use DHCP. Most networks have a DHCP service that can automatically
- supply your system with connection information.
+ You may not need to manually configure these settings if your
+ computer is part of an existing network, or if it is a laptop that
+ moves between networks. By default, &FC; activates all of the
+ network interfaces on your computer and configures them to use
+
+ DHCP (Dynamic Host Control Protocol)
+ DHCP, or Dynamic Host Control
+ Protocol. Most networks have a DHCP service that automatically
+ supplies connected systems with configuration data.
Wireless interfaces using DHCP will join an open wireless network
once it is in range. Many wireless networks are restricted, and
- will only accept systems which also have the correct security
- credentials.
-
-
-
- Click Next once you are satisfied with the
- network settings for your system.
+ only accept systems which have the correct security credentials.
@@ -47,14 +63,16 @@
-
+ Network Devices
- The list on the screen shows the network interfaces that the
- installation system has detected on your computer. Each interface
- will have a unique address on the network that it is attached to.
- This IP address can be assigned by the network DHCP service.
+ The installation program displays a list of network interfaces
+ detected on your computer. Each interface must have a unique
+ IP address
+ IP address
+ on the network to which it is attached. This address
+ may be assigned by the network DHCP service.
@@ -89,10 +107,10 @@
-
+
-
+ Computer Hostname
@@ -114,10 +132,10 @@
-
+
-
+ Miscellaneous Settings
@@ -143,7 +161,17 @@
to three DNS servers.
-
+
+ Click Next once you are satisfied with the
+ network settings for your system.
+
+
+
+ Click Next once you are satisfied with the
+ network settings for your system.
+
+
+
+
+
+ CVS
+
+
+ The Concurrent Versions System (CVS) provides a framework where multiple users can edit the same files.
+ As you can imagine, if a group of users edits the files in a single directory, chaos would reign.
+ Using CVS, however, a group of people can safely work on the same set of files.
+ CVS keeps the master copy of the files, and it records who changed what and when in a central repository.
+ If conflicts arise, CVS lets you know.
+ CVS is often used so that programmers can share code, but it also works well for documentation.
+
+
+
+ cvs
+
+
+
+ How CVS Works
+
+
+ cvs
+ how it works
+
+
+
+ cvs
+ overview
+
+
+
+ In most cases, each set of files that make up a package or project is stored as a module on the CVS server.
+
+
+
+ When working with files from CVS, you checkout a copy of the module on your local file system.
+ After modifying one or more files, you commit them back to the central CVS repository server.
+
+
- CVS, or Concurrent Versions System, provides a framework for multiple
- users to edit the same files. As you can imagine, if a group of users
- edits the files in a single directory, chaos would reign. Using CVS,
- however, a group of people can safely work on the same set of files. CVS
- keeps the master copy of the files, and it records who changed what and
- when in a central repository. If conflicts arise, CVS lets you know. CVS
- is usually used so that programmers can share code, but it also works well
- for documentation.
+ With CVS you may edit a file without first getting permission or locking the file.
+ The concurrent part of the CVS name comes from its ability to allow several different people to edit different parts of the same file.
+ As long as none of the changes overlap, CVS can correctly record their changes.
+ In case of duplicate changes, they are clearly marked in the files and the authors must resolve the issue among themselves.
-
+
+
+ When you commit changes, only changes to files the server knows about are committed.
+ In other words, if you created a file in your local checkout of a module, the new file is not automatically uploaded to the server.
+ You must add the file to the repository and then commit it.
+ If you remove a file from your local checkout of a module, you must specify that you want to remove it from the repository on the CVS server and then commit the removal of the file.
+
+
+
+ The specific commands to perform these actions are discussed in .
+
+
+
+ If someone has modified the file between the last time you grabbed the file from CVS and when you try to commit a change, CVS will try to merge the changes into the master copy of the CVS server.
+ If the content you changed is in a different location in the file than the content changed by someone else, chances are, the commit action will go through without a conflict.
+ If someone modified the same content as the content you just changed and tried to commit, you will see a message that a file conflict has occurred.
+ Thus, you need to update your files frequently.
+ It is a good practice to update them right before you start modifying a file.
+ Refer to for instructions on resolving conflicts.
+
+
+
+
+
+ Preparing For CVS Use
+
cvs
+ preparing for use
-
- How CVS Works
+
+ Before using CVS, you need to establish an account with the CVS server.
+ After getting an account, you do not need to perform these actions again.
+
-
- cvs
- how it works
-
+
+ Is CVS Installed On Your System
- cvs
- overview
+ cvs
+ RPM installation
- In most cases, each set of files that make up a package or project is
- stored as a module on the CVS server.
+ You must have the CVS
+ RPM package installed.
+ Verify its presence by typing the command:
-
- When working with files from CVS, you checkout a
- copy of the module on your local file system. After modifying one or
- more files, you commit them back to the central
- CVS repository server.
-
+ $ rpm -q cvs
- When you commit changes, only changes to files the server knows about
- are committed. In other words, if you created a file in your local
- checkout of a module, the new file is not automatically uploaded to the
- server. You must add the file to the repository
- and then commit it. If you remove a file from your local checkout of a
- module, you must specify that you want to remove it from the repository
- on the CVS server and then commit the removal of the file.
+ If you see output similar to cvs-1.11.19-1, then the package is installed.
+ A message similar to package cvs is not installed means you must install the cvs package before continuing.
+ If you do not know how to do this, consult your system administrator who can install it for you.
+
+
+
+ Generating SSH Keys
+
+ OpenSSH
+ authorization keys
+
+
- The specific commands to perform these actions are discussed in .
+ The CVS server uses SSH Protocol 2 keys to authenticate users.
+ Thus, you need to generate a pair of keys before applying for a CVS account.
+ If you already have an SSH
+ DSA key, you may skip this step.
+
+ Tip
+
+ You already have a DSA key if you have the file ~/.ssh/id_dsa.pub on the system.
+
+
+ If your existing DSA key does not require a passphrase, you are strongly urged to generate one that does require a passphrase.
+
+
+
- If someone has modified the file between the last time you grabbed the
- file from CVS and when you try to commit a change, it tried to merge the
- changes into the master copy of the CVS server. If the content you
- changed is in a different location in the file than the content changed
- by someone else, chances are, the commit action will go through without
- a conflict. If someone modified the same content
- as the content you just changed and tried to commit, you will see a
- message that a file conflict has occurred. Thus, you need to
- update your files frequently. It is a good
- practice to update them right before you start modifying a file. Refer
- to for instructions
- on resolving conflicts.
+ Use the following steps to generate a DSA key used by SSH Protocol 2.
+ It is required for an cvs.fedora.redhat.com
+ CVS account.
+
+
+
+ OpenSSH
+
+ ssh-keygen
+
+
+
+
+ ssh-keygen
+
+
+
+
+ To generate a DSA key to work with version 2.0 protocol, at a shell prompt, type the command:
+
+ $ ssh-keygen -t dsa
+
+ Accept the default file location of ~/.ssh/id_dsa.
+ You are strongly urged to define and use a passphrase to enhance the security of your key.
+ Enter a passphrase different than your account password and confirm it by entering it again.
+
+
+
+
+ Copy your new key to the correct file by typing the following at a shell prompt.
+
+ $ cat ~/.ssh/id_dsa.pub>>~/.ssh/authorized_keys
+
+
+ Check this command carefully before you press the ENTER key.
+ If ~/.ssh/authorized_keys already exists, the contents of ~/.ssh/id_dsa.pub will be appended to the end of the ~/.ssh/authorized_keys file.
+
+
+
+
+
+ Change the permissions of your ~/.ssh directory and your keys with the commands:
+ $ chmod 755 ~/.ssh
+$ chmod 644 ~/.ssh/authorized_keys
+
+
-
-
+
+ cvs
+ CVS_RSH
+
+
+
+ CVSROOT
+
+
+
+ CVS_RSH
+
-
- Configuring CVS on Your System
+
+ cvs
+
+ .cvsrc
+
+
+
+
+ .cvsrc
+
+
+
+
+ Avoiding Repetitive Typing
- cvs
- configuring your system for
+ cvs
+ avoiding repetitive typing
- You need to have the RPM package cvs installed to
- use CVS.
+ Many CVS commands need certain command line switches to operate consistently.
+ Rather than typing them every time that command is used, you can save the switches in a file that CVS will read before executing your command line.
-
- cvs
- CVSROOT
-
+
+ Create a file named ~/.cvsrc in your home directory.
+ It should contain the following commands, one per line:
+cvs -z3
+diff -uNp
+rdiff -uNp
+update -dP
+
+
+
+
+
+ Configuring for Read-Only CVS Access
- cvs
- CVS_RSH
-
-
-
- CVSROOT
+ cvs
+ configuring read-only access
- CVS_RSH
+ cvs
+ anonymous access
+
+ If your goal is to download the various &FC; documents and to render them on your system, you only need read-only access to the CVS repository.
+ Follow the instructions in this section and then skip directly to .
+
+
+
+ Change directories to where you want your files from CVS to be located, and execute the following commands:
+
+ $ export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs
+$ cvs login
+$ cvs checkout docs-setupmodule-name
+$ cvs checkoutmodule-name
+$ cdmodule-name
+
+
+ Once you have checked the module out, it doesn't matter what your CVSROOT is set to because it is stored in the file CVS/Root for each directory in your local repository.
+ As long as your current working directory has a CVS/ directory, the CVS program will automatically locate the &FC; repository.
+
+
+
+
+
+ Configuring Read/Write CVS Access
+
- cvs
- .cvsrc
+ cvs
+ configuring read/write access
+
- .cvsrc
+ cvs
+ configuring access for authors
- Follow these steps to configure your CVS environment:
-
-
-
- In your favorite Linux editor, add the following lines to your
- ~/.bashrc:
-
-
-export CVSROOT=:pserver:anonymous at rhlinux.redhat.com:/usr/local/CVS
-
-
-
- Note
- Only anonymous CVS access is available at this time. Anonymous
- access does not allow write priviledges.
-
-
-
- Use the command source ~/.bashrc to have the
- changes take effect.
-
-
-
- Create a file named .cvsrc in your home
- directory. It should contain the following:
-
-cvs -z3
-diff -uN
-rdiff -uN
-update -dP
-
-
-
-
- Change directories to where you want your files from CVS to be
- located, and execute the following commands:
-
-
-cvs login
-cvs checkout <module-name>
-
+ To author a new document or to change an existing one, you must obtain full read/write access to the &FC; Docs CVS repository.
+ For the full details on this process, refer to the http://fedoraproject.org/wiki/DocsProject/NewWriters
+ web site.
+ Below is a summary:
+
- Refer to if you need help
- using CVS.
-
-
-
+
+
+
+ Subscribe to the fedora-docs-list
+ , which is the main forum for the project.
+
+
+
+
+ Generate a GNU Privacy Guard (GPG) key to identify yourself to the project.
+
+
+
+
+ Register for a Bugzilla
+ account, if you do not have one already.
+ Bugzilla is how we keep track of bugs, changes and projects.
+
+
+
+
+ Post a self introduction to the list.
+
+
+
+
+
+ After your self introduction has been approved your CVS access will be granted.
+
+
+
+ Every author, and that includes you once your self introduction has been received, has a unique $CVSROOT to access the CVS repository:
+
+
+ $ export CVSROOT=:ext:yourname@cvs.fedora.redhat.com:/cvs/docs
+$ export CVS_RSH=/usr/bin/ssh
+
+
+ With the $CVSROOT and $CVS_RSH environment variables in place, you can access the repository:
+
+
+ $ cvs co -c
- Once you have checked it out, it doesn't matter what your
- CVSROOT is set to because it is stored in the file
- CVS/Root for each directory in your local
- repository.
+ You will be asked for the passphrase for your SSH key.
+ Press ENTER and you should receive a list of modules already in the repository.
-
-
+
-
+
+
+ Basic CVS Commands
- cvs
- commands
+ cvs
+ commands
- After configuring your system to work with CVS, checkout the modules you
- will be working on.
-
+ After configuring your system to work with CVS, checkout the modules you will be working on.
+
-
- Checking Out Modules
+
+ Tip
+
+ To see if you need a correctly-set $CVSROOT variable, or the
+ repository command line switch, see if you have a CVS/ subdirectory in your working directory.
+
+
+ If you have a CVS/ directory, CVS ignores any $CVSROOT or command line switch.
+
+
-
- cvs
- checking out modules
-
+
+ Checking Out Modules
-
- You only need to checkout a module once. After a local copy of the
- module is on your system, it is on your system.
-
+
+ cvs
+ checking out modules
+
-
- To checkout a module, use the following command:
-
+
+ You only need to checkout a module once. After a local copy of the module is on your system, it is on your system.
+
-
-cvs co <module-name>
-
+
+ To checkout a module, use the following command:
+
-
- For example, to checkout the
- redhat-logviewer module, change to
- your work directory, and execute the following command:
-
+ $ cvs co<module-name>
-
-cvs co redhat-logviewer
-
+
+ For example, to checkout the example-tutorial module, change to your work directory, and execute the following command:
+
-
- A directory called redhat-logviewer/ is created
- in the current directory.
-
-
-
- If a branch name is not specified when checking out a module, it is
- referred to as the HEAD of the CVS module.
-
-
-
- Checking Out Branches of Modules
-
-
- cvs
- check out modules
- checking out branches
-
-
-
- Think of a CVS branch as a version of the files for a particular
- version of a manual or package.
-
-
-
- To checkout a branch of a module, use the following command:
-
+ $ cvs co example-tutorial
-
-cvs co -d <directory> -r <branchname><module-name>
-
+
+ A directory called example-tutorial/ is created in the current directory.
+
-
- A directory named <directory> is created,
- and the files for the <branchname> branch
- of the <module-name> module are copied in
- the directory.
-
-
-
- For example, to checkout a branch named BRANCH-VERSION-1.2 from the
- mymodule module, use the command:
-
+
+ If a branch name is not specified when checking out a module, it is referred to as the HEAD of the CVS module.
+
-
-cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule
-
+
+ Checking Out Branches of Modules
-
- The BRANCH-VERSION-1.2 branch of the module is checked out in the
- mymodule-1.2 directory on your system.
-
-
-
- To determine which branches and tags exist for a file, use the command:
-
-
-cvs status -v <filename>
-
+
+ cvs
+ check out modules
+ checking out branches
+
+
+
+ Think of a CVS branch as a version of the files for a particular version of a manual or package.
+
+
+
+ To checkout a branch of a module, use the following command:
+
+
+ $ cvs co<directory><branchname><module-name>
+
+
+ A directory named <directory> is created, and the files for the <branchname> branch of the <module-name> module are copied in the directory.
+
+
+
+ For example, to checkout a branch named BRANCH-VERSION-1.2 from the mymodule module, use the command:
+
+
+ $ cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule
+
+
+ The BRANCH-VERSION-1.2 branch of the module is checked out in the mymodule-1.2 directory on your system.
+
+
+
+ To determine which branches and tags exist for a file, use the command:
+
+ $ cvs status<filename>
-
- For example, the status of the file foo.sgml is
- as follows:
-
-
+
+ For example, the status of the file foo.sgml is as follows:
+
+
===================================================================
File: foo.sgml Status: Up-to-date
-
+
Working revision: 1.47
- Repository revision: 1.47 /usr/local/CVS/docs/custom-guide/rhl-cg-en.sg
-ml,v
+ Repository revision: 1.47 /cvs/docs/custom-guide/rhl-cg-en.sgml,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
-
+
Existing Tags:
BRANCH-VERSION-1.2 (branch: 1.25.2)
-
- Only tags marked as branches in the second column under the
- Existing Tags section can be
- checked out as a branch.
-
-
-
-
-
-
-
- Updating Files
-
-
- cvs
- updating files
-
-
-
- To retrieve the latest versions of the files in a module, change to
- the directory that contains the files for the module and execute the
- command:
-
-
-cvs up
-
+
+ Only tags marked as branches in the second column under the Existing Tags section can be checked out as a branch.
+
-
- The latest versions of all the files in the module are downloaded into
- your local copy. If you notice a file conflict, refer to .
-
-
-
-
-
- Committing Files
-
-
- cvs
- committing files
-
-
-
- After modifying files in your local version of a module, commit them
- to save the changes on the CVS server:
-
-
-cvs commit -m "some log message" <filename>
-
+
-
- The log message should be as descriptive as possible so that you and
- anyone else working on the module understands what changed. Using a
- log message such as updated some files does not
- accurately describe what has changed and will not help you in the
- future.
-
-
-
- <filename> can
- be one filename, a series of filenames separated by spaces, or a group
- of filenames specified using wildcards such as
- *.png or foo-*.sgml.
-
-
-
- If no filename or group of filenames is specified in the commit
- command, all files that have been changed in the module, added to the
- module with the cvs add command, and removed with
- the cvs rm command are committed to the server. All
- files in the module means that the command is recursive. It is not
- good practice to issue the commit command without a filename or group
- of filenames specified because you might not remember exactly what
- files changed.
-
-
-
- If you notice a file conflict, refer to .
-
-
-
-
-
-
- Adding Files
-
-
- cvs
- adding files
-
-
-
- To add a file to a module, create the file in your local copy, and
- execute the following command:
-
-
-cvs add <file-to-add>
-
+
-
- After adding the file, you must commit the add to copy it to the
- server:
-
+
+ Updating Files
-
-cvs commit -m "some log message" <file-to-add>
-
+
+ cvs
+ updating files
+
-
+
+ To retrieve the latest versions of the files in a module, change to the directory that contains the files for the module and execute the command:
+
+ cvs update
-
- Removing Files
+
+ The latest versions of all the files in the module are downloaded into your local copy.
+ If you notice a file conflict, refer to .
+
-
- cvs
- removing files
-
-
-
- If a file is no longer needed in the module, use the following command
- to remove it from your local version and commit the removal to the
- server. Even though the file is removed from current version of the
- module, an archived copy is still kept on the server and can be
- retrieved at any time.
-
-
-cvs rm -f <file-to-remove>
-
+
-
- After removing the file, you must commit the removal:
-
+
+ Committing Files
-
-cvs commit -m "some log message" <file-to-remove>
-
+
+ cvs
+ committing files
+
+
+
+ After modifying files in your local version of a module, commit them to save the changes on the CVS server:
+
+ $ cvs commit "some log message" filename
+
+
+
+ If you would prefer to write your log message with your favorite text editor, as defined by the $VISUAL or the $EDITOR environment variable, just omit the -m "some log message".
+ The buffer will already contain comments describing the change; you do not need to delete them as you enter your own text.
+
+
+
+
+ The log message should be as descriptive as possible so that you and anyone else working on the module understands what changed.
+ Using a log message such as updated some files does not accurately describe what has changed and will not help you in the future.
+ If you are correcting a bug, use the Bugzilla reference.
+
-
- You can not use wildcards in the commit command to commit removed
- files. They must be specified with the complete filenames.
-
-
-
- If you need to rename a file, it is best to rename the file on the CVS
- server so that the history of the file is preserved. If you need to
- rename a file, contact Tammy (or whoever is the technical lead).
-
-
-
-
-
- Status of Files
-
-
- cvs
- status of files
-
-
-
- Sometimes it is necessary to view the status of
- a file in a CVS module. To view the status of a file, use the command:
-
+
+ The <filename> can be one filename, a series of filenames separated by spaces, or a group of filenames specified using wildcards such as *.png or foo-*.sgml.
+
-
-cvs status <filename>
-
+
+ If no filename or group of filenames is specified in the commit command, all outstanding changes of any kind are committed to the server.
+ The command is recursive and will include changes in any subdirectories of the module.
+ Use caution when issuing the commit command without any filenames because you might not remember exactly what files changed.
+
+
+
+ If you notice a file conflict, refer to .
+
+
+
+
+
+
+ Adding Files
+
+
+ cvs
+ adding files
+
+
+
+ To add a file to a module, create the file in your local copy then execute the following command:
+
+ $ cvs addfile-to-add
+
+
+ After adding the file, you must commit the add to copy it to the server:
+
+
+ $ cvs commit "some log message" file-to-add
-
- The statuses of a file in the repository are as follows:
-
-
-
- Up-to-date
-
- Your revision of the file is identical to the latest
- revision on the CVS server.
-
-
-
- Locally Modified
-
- You have update to the latest revision from the server, but
- then you modified the file in your checkout.
-
-
-
- Locally Added
-
- You added the file with the cvs add
- command but have not yet committed the addition of the
- file.
-
-
-
- Locally Removed
-
- You removed the file with the cvs remove
- command but have not yet committed the removal.
-
-
-
- Needs Checkout
-
- A newer version of the file is on the server and needs to be
- retrieved. Even though the status includes the word checkout, it
- really means that you need to update your files with the
- cvs update command.
-
-
-
- Needs Patch
-
- The revision in your local checkout needs a patch to be the
- latest revision from the server. Issue the cvs
- update command to resolve.
-
-
-
- Needs Merge
-
- A newer revision exists on the server and your local version
- contains modification not yet committed. This status usually
- occurs if you don't have the latest revision of the file and
- edit it anyway.
-
-
-
- File had conflicts on merge
-
- Similar to Needs Merge,
- except when you tried to issue the cvs update
- command, the differences could not be resolved
- automatically. Refer to
- for more information on resolving conflicts.
-
-
-
- Unknown
-
- The CVS server does not know anything about this file. It
- has not been added or removed locally and has never been
- committed to the server. This status usually occurs for files
- you should not commit to CVS such as
- generated-index.sgml or for files that you
- want to add to the repository but have not issued the
- cvs add command for yet.
-
-
-
-
-
-
-
- Resolving Conflicts
-
-
- cvs
- resolving conflicts
-
-
-
- If you modify a file and the same content is modified by someone else
- and committed first, you will probably see a message similar to the
- following when committing the file or updating your local copy of the
- module:
-
+
-
+
+ Removing Files
+
+
+ cvs
+ removing files
+
+
+
+ If a file is no longer needed in the module, use the remove command to remove it from your local copy and then commit the removal to the server.
+ Even though the file is removed from current version of the module, an archived copy is still kept on the server and can be retrieved at any time with the add command.
+
+ $ cvs rm -ffile-to-remove
+
+
+ After removing the file, you must commit the removal:
+
+
+ $ cvs commit "some log message" file-to-remove
+
+
+ You can not use wildcards in the commit command to identify removed files.
+ They must be specified with a exact filename.
+
+
+
+ If you need to rename a file, it is best to rename the file on the CVS server so that the history of the file is preserved.
+ If you need to rename a file, send an email to
+ cvsdocs-administrator at fedora.redhat.com
+ asking to have the file renamed.
+
+
+
+
+
+ Status of Files
+
+
+ cvs
+ status of files
+
+
+
+ Sometimes it is necessary to view the status of a file in a CVS module.
+ To view the status of a file, use the command:
+
+
+ $ cvs statusfilename
+
+
+ The status report of a repository file is as follows:
+
+
+
+
+ Up-to-date
+
+
+
+ Your revision of the file is identical to the latest revision on the CVS server.
+
+
+
+
+
+ Locally Modified
+
+
+
+ You have updated to the latest revision from the server, but then you modified the file on your system.
+
+
+
+
+
+ Locally Added
+
+
+
+ You added the file with the cvs add command but have not yet committed the addition of the file.
+
+
+
+
+
+ Locally Removed
+
+
+
+ You removed the file with the cvs remove command but have not yet committed the removal.
+
+
+
+
+
+ Needs Checkout
+
+
+
+ A newer version of the file is on the server and needs to be retrieved.
+ Even though the status includes the word checkout, it really means that you need to update your files with the cvs update command.
+
+
+
+
+
+ Needs Patch
+
+
+
+ The revision in your local checkout needs a patch to be the latest revision from the server.
+ Issue the cvs update command to resolve.
+
+
+
+
+
+ Needs Merge
+
+
+
+ A newer revision exists on the server and your local version contains modification not yet committed.
+ This status usually occurs if you don't have the latest revision of the file and edit it anyway.
+
+
+
+
+
+ File had conflicts on merge
+
+
+
+ Similar to Needs Merge, except when you tried to issue the cvs update command, the differences could not be resolved automatically.
+ Refer to for more information on resolving conflicts.
+
+
+
+
+
+ Unknown
+
+
+
+ The CVS server does not know anything about this file.
+ It has neither been added nor removed locally and has never been committed to the server.
+ This status usually occurs for files you should not commit to CVS such as generated-index.sgml or for files that you want to add to the repository but have not yet issued the cvs add command.
+
+
+
+
+
+
+
+ Resolving Conflicts
+
+
+ cvs
+ resolving conflicts
+
+
+
+ If you modify a file and the same region is modified by someone else and committed first, you will probably see a message similar to the following when committing the file or updating your local copy of the module:
+
+
+
-RCS file: /usr/local/CVS/docs/module-name/filename.sgml,v
+RCS file: /cvs/docs/module-name/filename.sgml,v
retrieving revision 1.12
retrieving revision 1.13
Merging differences between 1.12 and 1.13 into filename.sgml
@@ -664,13 +744,11 @@
-
- To resolve the conflict, open the file, search for
- <<<<<<< and determine which version
- of the content should be in the latest revision of the file in
- CVS. For example:
-
-
+
+ To resolve the conflict, open the file, search for <<<<<<< and determine which version of the content is correct.
+ For example:
+
+
<para>
Some sentence.
@@ -683,133 +761,149 @@
-
- The content between the
- <<<<<<<, the
- ======= is the content in your
- working copy. The content between the
- ======= and the
- >>>>>>> is
- the content from the latest revision (or the latest revision
- for the branch) on the server.
-
-
-
- Resolve the conflict, and commit the file.
-
-
-
-
-
-
- Summary
-
-
- cvs
- commands
- summary of
-
-
-
- All commands assume you are in the proper directory for the CVS module.
-
-
-
- Basic CVS Commands
-
-
-
-
-
- Command
- Description
-
-
-
-
- cvs checkout
- <module-name>
- or cvs co <module-name>
- Creates a directory called
- <module-name> with the contents of the
- module in the directory
-
-
- cvs co -d <directory> -r <branchname><module-name>
- Creates the <directory> directory
- with the contents of the <branchname>
- branch of the <module-name> module
-
-
- cvs update or cvs up
- Update your files with the latest files from the CVS server
-
-
- cvs add <filename>
- Add a new file "filename" to the CVS server
-
-
- cvs commit -m "My message"
- <filename>
- Update file <filename> with the
- latest copy from your computer
-
-
- cvs log <filename>
- View the commit messages for the file <filename>
-
-
- cvs status <filename>
- View status of the file, such as Locally
- Modified
-
-
- cvs status -v <filename>
- View existing tags and branches for file
-
-
- cvs diff <filename>
- Show diff of the working copy of the file and the latest
- version of the file for the branch
-
-
- cvs diff -r1.1 -r1.2 <filename>
- Show diff of version 1.1 and 1.2 for file
-
-
-
-
-
-
- For more information, read the CVS manual available on your system at
- /usr/share/doc/cvs-<version-number>/cvs.ps
- (the CVS version might vary) and visit the CVS webpage available at
- http://www.cvshome.org/.
-
+
+ The content between the <<<<<<<, and the ======= is the content from your
+ working copy.
+ The content between the ======= and the >>>>>>> is the content from the server.
+
-
- Tip
-
- Since CVS is using ssh to connect to the CVS server, it will prompt
- you for your password before allowing you to performing your CVS
- request. If you want to configure your machine so that you do not
- have to enter a password, refer to the &RH; Linux
- 9 Customization Guide for details about using
- ssh-agent.
-
-
-
-
-
-
-
-
+
+ Resolve the conflict by editing your copy, and commit the file.
+
+
+
+ Summary
+
+ cvs
+ commands
+ summary of
+
+
+ All commands assume you are in the proper directory for the CVS module.
+
+
+ Basic CVS Commands
+
+
+
+
+
+ Command
+ Description
+
+
+
+
+
+ cvs checkout
+ <module-name>
+
+ or cvs co <module-name>
+
+
+ Creates a directory called
+ <module-name> with the contents of the
+ module in the directory
+
+
+
+ cvs co -d <directory> -r <branchname>
+ <module-name>
+
+
+ Creates the <directory> directory
+ with the contents of the <branchname>
+ branch of the <module-name> module
+
+
+
+ cvs update or cvs up
+
+ Update your files with the latest files from the CVS server
+
+
+
+ cvs add <filename>
+
+
+ Add a new file "filename" to the CVS server
+
+
+
+ cvs commit -m "My message"
+ <filename>
+
+
+ Update file <filename> with the
+ latest copy from your computer
+
+
+
+ cvs log <filename>
+
+
+ View the commit messages for the file <filename>
+
+
+
+
+ cvs status <filename>
+
+
+ View status of the file, such as Locally
+ Modified
+
+
+
+
+ cvs status -v <filename>
+
+
+ View existing tags and branches for file
+
+
+
+ cvs diff <filename>
+
+
+ Show diff of the working copy of the file and the latest
+ version of the file for the branch
+
+
+
+ cvs diff -r1.1 -r1.2 <filename>
+
+
+ Show diff of version 1.1 and 1.2 for file
+
+
+
+
+
+ For more information, read the CVS manual available on your system at /usr/share/doc/cvs-<version-number>/cvs.ps (the CVS version might vary) and visit the CVS webpage available at http://www.cvshome.org/.
+
+
+
+ Tip
+
+ Since CVS is using ssh to connect to the CVS server, you will be prompted your password before performing your CVS request.
+ If you want to configure your machine so that you do not have to enter a password, refer to the
+ &RH; Linux 9 Customization Guide
+
+ for details about using
+ ssh-agent.
+
+
+
+
+
+
+
From fedora-docs-commits at redhat.com Sat May 14 20:00:17 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 14 May 2005 16:00:17 -0400
Subject: documentation-guide docs-getting-files-en.xml,1.2,1.3
Message-ID: <200505142000.j4EK0Hg7024358@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/documentation-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24343/documentation-guide
Modified Files:
docs-getting-files-en.xml
Log Message:
1) Changed to reflect the updated CVS arrangement with modules as "top-level"
objects.
2) Changed URL for :pserver: CVS access.
3) Added short section on :ext: CVS access with reference to the WIKI doc.
Index: docs-getting-files-en.xml
===================================================================
RCS file: /cvs/docs/documentation-guide/docs-getting-files-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- docs-getting-files-en.xml 3 May 2005 18:45:19 -0000 1.2
+++ docs-getting-files-en.xml 14 May 2005 20:00:15 -0000 1.3
@@ -1,6 +1,13 @@
-
-
-
+
+
+Getting the Files
@@ -11,20 +18,20 @@
- xmlto — for producing HTML and PDF outputs
+ xmlto — for producing HTML and PDF outputs
- docbook-style-xsl — for the default XSLT stylesheets we
- build on
+ docbook-style-xsl — for the default XSLT stylesheets we
+ build on
- docbook-dtds — XML versions of the DocBook DTD
+ docbook-dtds — XML versions of the DocBook DTD
The custom scripts and stylesheets used are all stored in CVS on the
- rhlinux.redhat.com CVS server.
+ cvs.fedora.redhat.com CVS server.
@@ -33,29 +40,46 @@
- To check out the scripts anonymously:
+ Get started by following these once-only steps.
+ When asked for a CVS password, just press the ENTER key.
-export CVSROOT=:pserver:anonymous at cvs.fedora.redhat.com:/cvs/docs
-cvs -z3 login
-cvs -z3 co fedora-docs
+$ mkdir my-fedora-docs
+$ cd my-fedora-docs
+$ export CVSROOT=:pserver:anonymous at cvs.fedora.redhat.com:/cvs/docs
+$ cvs login
+<enter>
+$ cvs co docs-setup
Checking the files out anonymously means that you can view them and
retreive the latest versions, but you can not add (commit) any updates or
new files back to the repository.
+ You need CVS write access for that; check with the
+ http://fedoraproject.org/wiki/DocsProject/NewWriters
+ site to learn about getting write access to CVS.
+ To see a list of the available documents:
+
+
+$ cvs co -c
+
+
+ Pick your document of interest and then download it to your working directory:
+
+
+$ cvs co example-tutorial
+
+
Except for the &IG;, all docs must be tutorials
written in DocBook XML article format using the template in the
example-tutorial directory. Each tutorial
must be in its own directory. No XML files should be
- in the root directory except for files shared by all documents such
- legalnotice.xml, which must be included in all docs
- so that the FDL is used for all docs.
+ in the root directory.
From fedora-docs-commits at redhat.com Sat May 14 20:54:37 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 14 May 2005 16:54:37 -0400
Subject: install-guide fedora-install-guide-networkconfig-en.xml,1.6,1.7
Message-ID: <200505142054.j4EKsbd9025524@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25516
Modified Files:
fedora-install-guide-networkconfig-en.xml
Log Message:
1. Additional style edits
2. Removed superfluous note about networking issues (thanks Stuart)
3. Cleaned some tags - use instead of for
lists of definitions; use more and to provide
new terms; don't use as a substitute for defining a term
that would otherwise be jargon
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-networkconfig-en.xml 14 May 2005 15:20:02 -0000 1.6
+++ fedora-install-guide-networkconfig-en.xml 14 May 2005 20:54:35 -0000 1.7
@@ -5,12 +5,7 @@
This screen enables you to customize the network settings of your
- &FED; system. Networking is a complex subject which is currently
- beyond the scope of this document. For more information on basic
- networking concepts, refer to one or more of the following
- documents. To find a specific title online, search for the title
- using an Internet search engine such as Google (http://www.google.com/).
+ &FED; system.
@@ -71,39 +66,39 @@
detected on your computer. Each interface must have a unique
IP addressIP address
- on the network to which it is attached. This address
- may be assigned by the network DHCP service.
+ on the network to which it is attached. The interface
+ may receive this address from the network DHCP service.
- To set an IP address yourself, highlight the interface on the
- Network Device list and then click
- Edit. This will open a dialog box. Click
- the Configure using DHCP checkbox, so that it
- is empty. Type the correct numbers of the IP
- Address in the boxes. You must also set the
- appropriate Netmask for the interface. Then
- click OK.
+ To manually assign an IP address, highlight the interface on the
+ Network Device list and select
+ Edit. The installation program then
+ displays a network configuration dialog.
+ Deselect the Configure using
+ DHCP checkbox, so that it is empty. Enter the
+ IP Address and the appropriate
+ Netmask for the interface. Then select
+ OK.
- You can specify that an interface should not be automatically
- activated by clicking the Active on Boot
- checkbox next to the name of the interface. Network interfaces
- can be manually activated at any time after the system has booted.
+ Specify whether an interface should be automatically activated at
+ boot time with the Active on Boot checkbox
+ for that device. You may manually activate a network interfaces at
+ any time after the system has booted.
- Modems are configured after the installation
- process
+ Modem Configuration
- Modems are not listed on the Network
- Configuration screen. Use either
- Internet Connection Wizard or
- system-config-network to set up
- Internet access on your &FED; system. The settings for your
- modem are specific to your particular Internet Service Provider
- (ISP).
+ The Network Configuration screen does not
+ list modems. Configure these devices after installation with
+ either the Internet Configuration
+ Wizard or Network
+ Cnfiguration utility to set up Internet access
+ on your &FED; system. The settings for your modem are specific
+ to your particular Internet Service Provider (ISP).
@@ -114,21 +109,27 @@
Computer Hostname
- On some networks the DHCP provider will also set the name of the
- computer itself. To specify the name of your computer select
- manual and type the complete name in the box.
- A full computer hostname includes both the name of the machine and
- the name of the DNS domain that it is a member of, e.g.
- machine1.example.com.
+ On some networks, the DHCP provider also provides the name of the
+ computer, or
+ hostname
+ hostname. To specify the
+ hostname select Manual and type the complete
+ name in the box. The complete hostname includes both the name of
+ the machine and the name of the domain of which it is a member,
+ such as machine1.example.com. The
+ machine name (or "short hostname") is
+ machine1, and the
+ domain name
+ domain name is
+ example.com.
Valid Hostnames
- You can give your system any name that you wish, provided that
- the full hostname is unique. The system name may include
- letters, numbers and hyphens. You can change the name of your
- system at any time.
+ You may give your system any name provided that the full
+ hostname is unique. The hostname may include letters, numbers
+ and hyphens.
@@ -139,37 +140,41 @@
Miscellaneous Settings
- If you have chosen to manually configure a network interface then
- you may also wish to determine the other network settings for your
- computer. All of these settings are the IP addresses of other
- systems on the network.
+ To manually configure a network interface, you may also provide
+ other network settings for your computer. All of these settings
+ are the IP addresses of other systems on the network.
- The Gateway is the device that provides
- access to other networks. Gateways are also referred to as
- routers.
+ A gateway
+ gateway
+ is the device that provides access to other networks.
+ Gateways are also referred to as
+ router
+ gateway
+ routers. If your system
+ connects to other networks through a gateway, enter its IP address
+ in the Gateway box.
- Most software relies on the DNS (Domain Name Service) provider to
- locate machines and services on the network. A &FC; system may
- use more than one DNS server. If the Primary
- DNS server does not respond then the query is
- resubmitted to the Secondary DNS server, and
- so on. This screen enables you to specify the IP addresses of up
- to three DNS servers.
+ Most software relies on the
+ DNS (Domain Name Service)
+ DNS (Domain Name Service)
+ provider to locate machines and services on the network. DNS
+ converts hostnames to IP addresses and vice versa. A &FC; system
+ may use more than one DNS server. If the primary DNS server does
+ not respond, the computer sends any query to the secondary DNS
+ server, and so on. To assign DNS servers, type their IP addresses
+ into the Primary,
+ Secondary, or Tertiary DNS
+ Server boxes.
-
- Click Next once you are satisfied with the
- network settings for your system.
-
-
-
- Click Next once you are satisfied with the
- network settings for your system.
-
+
+ Click Next once you are satisfied with the
+ network settings for your system.
+
From fedora-docs-commits at redhat.com Sat May 14 21:49:46 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 14 May 2005 17:49:46 -0400
Subject: install-guide fedora-install-guide-bootloader-en.xml,1.7,1.8
Message-ID: <200505142149.j4ELnkbr026999@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26991
Modified Files:
fedora-install-guide-bootloader-en.xml
Log Message:
1. More style edits
2. Made section on GRUB passwords more procedure-oriented
3. Reset id attributes to reflect DocGuide standards (2.1)
Index: fedora-install-guide-bootloader-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-bootloader-en.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-bootloader-en.xml 14 May 2005 15:22:52 -0000 1.7
+++ fedora-install-guide-bootloader-en.xml 14 May 2005 21:49:44 -0000 1.8
@@ -25,10 +25,9 @@
- shows the boot loader
- configuration choices.
+ The following screen displays boot loader configuration options.
-
+
Boot Loader Configuration Screen
@@ -45,10 +44,8 @@
-
-
- Keeping Your Existing Boot Loader Settings
-
+
+ Keeping Your Existing Boot Loader Settings
By default, the installation program installs GRUB in the
master boot record,
@@ -56,11 +53,11 @@
or MBR, of the device for the root
file system. To change or decline installation of a new boot
loader, select the Change boot loader
- button. The pop-up shown in
- allows you to avoid
+ button. The dialog shown in
+ allows you to avoid
installing or changing your existing boot loader settings.
-
+ Change Boot Loader
@@ -76,74 +73,72 @@
- If you decline to install any boot loader, you will not be able
- to boot Linux after the installation unless you choose to
- generate a startup disk. Refer to
+ If you do not install any boot loader, you will not be able to
+ boot Linux after the installation unless you generate a startup
+ disk.
-
+
Booting Additional Operating Systems
If you have other operating systems already installed, &FED;
attempts to automatically detect and configure
- GRUB so that any installed
- OS can be booted. You can also manually configure
- any additional operating systems if
- GRUB does not detect them. To the right
- of the partition display there are three buttons that allow you to
- add, remove, or change the detected operating system settings.
-
-
-
-
+ GRUB to boot them. You may manually
+ configure any additional operating systems if
+ GRUB does not detect them. To
+ add, remove, or change the detected operating system settings,
+ use the options provided.
+
+
+
+ Add
-
-
+
+
- Pressing the Add button displays
- the pop-up shown in .
+ Press the Add button to include an
+ additional operating system in GRUB. &FED; displays the
+ dialog shown in .
- You must know the disk partition holding the bootable
- operating system. Select the disk partition holding the
- bootable operating system from the drop-down list and give
- the entry a label. The label is shown at boot-time when
- GRUB presents its boot menu.
+ Select the disk partition which contains the bootable
+ operating system from the drop-down list and give the entry
+ a label. GRUB displays this
+ label in its boot menu.
-
-
-
-
+
+
+
+ Edit
-
-
-
- You can change an entry shown in the partition list by
- clicking on the item with the mouse and then pressing the
- Edit button.
+
+
+
+ To change an entry in the GRUB boot menu, select the entry
+ and then select Edit.
-
-
-
-
+
+
+
+ Delete
-
-
+
+
- If you want to remove an entry from the partition list, just
- click it with the mouse and then press the
- Delete button.
+ To remove an entry from the GRUB boot menu, select the entry
+ and then select Delete.
-
-
-
-
- Adding Other Operating Systems To The Boot Menu
+
+
+
+
+ Adding Operating Systems to the Boot Menu
@@ -158,48 +153,37 @@
-
+
- Setting A Boot loader Password
+ Setting a Boot Loader Password
- A useful GRUB feature is that it can
- browse disk files itself on many file system layouts, not relying
- on any active OS. An operator can interrupt the
- booting sequence to choose a different image file to boot, or to
- change the command line arguments passed to the kernel. A system
- administrator can use the features to recover a system that will
- not boot.
-
-
- Alas, allowing whom ever happens to be near the system console to
- type arbitrary commands or to change system parameters during the
- boot sequence can be a security issue.
- GRUB can be configured to require that
- a password be typed before the start parameters can be changed.
- Any operator with console access can boot the system but only if
- the correct password is given can the boot settings be changed.
-
-
- You do not have to set a GRUB password.
- If you have trusted operators, or a physically secured system with
- controlled console access, you probably do not need a boot
- password. Likewise if you have a single-user system and you do not
- worry about passers-by rebooting your system and fiddling with it,
- you can probably dispense with a boot password.
+ GRUB reads many file systems without
+ the help of an operating system. An operator can interrupt the
+ booting sequence to choose a different operating system to boot,
+ change boot options, or recover from a system error. These
+ functions, however, may introduce serious security risks in some
+ environments. You can add a password to
+ GRUB so that the operator must enter
+ the password to interrupt the normal boot sequence.
+
+ GRUB Passwords Not Required
+
+ You may not require a GRUB password
+ if your system only has trusted operators, or is physically
+ secured with controlled console access.
+
+
- If you decide to use a boot password, mark the checkbox beside the
- Use a boot loader password legend. The
- Change password button will become
- un-grayed and selectable. Press the Change
- password button to display the pop-up shown in
- . Carefully type in your
- desired password and then confirm its correctness by typing it
- again in the space provided.
+ To set a boot password, select the Use a boot loader
+ password checkbox. The Change
+ password button will become active. Select
+ Change password to display the dialog
+ below. Type the desired password, and then confirm it by typing
+ it again in the spaces provided.
-
+ Entering A Boot Password
@@ -213,48 +197,59 @@
-
+
+ Choose a Good Password
Choose a password that is easy for you to remember but hard for
- others to guess. The password is stored in encrypted form and
- cannot be recovered.
+ others to guess.
+
+
+ Forgotten GRUB Passwords
- If you forget the boot password, "Don't Panic!".
- All you need do is boot the system normally and then change the
- password entry in the /etc/grub.conf file.
+ GRUB stores the password in encrypted
+ form, so it cannot be read or recovered. If
+ you forget the boot password, boot the system normally and then
+ change the password entry in the
+ /boot/grub/grub.conf file. If you cannot
+ boot, you may be able to use the "rescue" mode on the first &FC;
+ installation disc to reset the GRUB password.
-
+
Advanced Boot loader Options
The default boot options are adequate for most situations. The
- GRUB boot loader will be stored in the
- MBR, overwriting any existing boot loader.
+ installation program writes the GRUB
+ boot loader in the
+
+ master boot record
+ master boot record (MBR),
+ overwriting any existing boot loader.
- If you want to keep your current boot loader in the
- MBR, you must use the advanced settings to place
- GRUB in the first sector of the
- partition holding the Linux root file system.
+ Tto keep your current boot loader in the MBR, use
+ the advanced settings to place GRUB in
+ the first sector of the partition holding the Linux root file
+ system.
You may also need the advanced options if your
- BIOS has numbered your disk devices differently
- than Linux expects. On some systems, Linux may not configure the
+ BIOS enumerates your disk devices differently
+ than &FED; expects. On a few systems, &FED; may not configure the
disk drive geometry for large disks correctly because of a broken
- BIOS. As a work around, mark the Force
- LBA32 checkbox.
+ BIOS. To work around this problem, mark the
+ Force LBA32 checkbox.
The Linux kernel usually auto-detects its environment correctly,
- and no additional kernel parameters are needed. However, it is
- possible to provide any needed kernel parameter using the advanced
- boot loader options.
+ and no additional kernel parameters are needed. You may provide
+ any needed kernel parameter, however, using the advanced boot
+ loader options.
@@ -265,20 +260,19 @@
- If you need to alter any of these settings, mark the
- Configure advanced boot loader options
- checkbox. Then, when you press Next, the
- menu shown in will
- appear.
+ To alter any of these settings, mark the Configure
+ advanced boot loader options checkbox. Select
+ Next and the menu shown in appears.
- The following advanced boot options menu will be displayed
- only if the advanced configuration
- checkbox, just described, has been selected.
+ &FED; displays the following advanced boot options menu
+ only if the advanced configuration checkbox
+ described above has been selected.
-
+ Advanced Boot Options
@@ -288,8 +282,7 @@
- Menu displayed if advanced boot settings are
- desired
+ Advanced boot settings menu
From fedora-docs-commits at redhat.com Sat May 14 21:52:01 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 14 May 2005 17:52:01 -0400
Subject: install-guide fedora-install-guide-networkconfig-en.xml,1.7,1.8
Message-ID: <200505142152.j4ELq1l4027022@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27014
Modified Files:
fedora-install-guide-networkconfig-en.xml
Log Message:
Whoops, needed to remove pesky references list
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-networkconfig-en.xml 14 May 2005 20:54:35 -0000 1.7
+++ fedora-install-guide-networkconfig-en.xml 14 May 2005 21:51:58 -0000 1.8
@@ -4,24 +4,10 @@
Network Configuration
- This screen enables you to customize the network settings of your
- &FED; system.
+ Use this screen to customize the network settings of your &FED;
+ system.
-
-
-
- Chapters 1 and 2 of the Linux Network Administrators
- Guide
-
-
-
-
- The Linux Networking-HOWTO
-
-
-
-
You may not need to manually configure these settings if your
computer is part of an existing network, or if it is a laptop that
From fedora-docs-commits at redhat.com Sat May 14 21:57:40 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 14 May 2005 17:57:40 -0400
Subject: install-guide fedora-install-guide-networkconfig-en.xml,1.8,1.9
Message-ID: <200505142157.j4ELvefU027049@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27041
Modified Files:
fedora-install-guide-networkconfig-en.xml
Log Message:
Remove wordiness, emphasize Fedora
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-networkconfig-en.xml 14 May 2005 21:51:58 -0000 1.8
+++ fedora-install-guide-networkconfig-en.xml 14 May 2005 21:57:38 -0000 1.9
@@ -48,9 +48,9 @@
Network Devices
- The installation program displays a list of network interfaces
- detected on your computer. Each interface must have a unique
- IP address
+ &FED; displays a list of network interfaces detected on your
+ computer. Each interface must have a unique IP
+ addressIP address on the network to which it is attached. The interface
may receive this address from the network DHCP service.
@@ -59,13 +59,12 @@
To manually assign an IP address, highlight the interface on the
Network Device list and select
- Edit. The installation program then
- displays a network configuration dialog.
- Deselect the Configure using
- DHCP checkbox, so that it is empty. Enter the
- IP Address and the appropriate
- Netmask for the interface. Then select
- OK.
+ Edit. &FED; then displays a network
+ configuration dialog. Deselect the
+ Configure using DHCP checkbox, so that it is
+ empty. Enter the IP Address and the
+ appropriate Netmask for the interface. Then
+ select OK.
From fedora-docs-commits at redhat.com Sat May 14 22:35:29 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 14 May 2005 18:35:29 -0400
Subject: install-guide fedora-install-guide-firewallconfig-en.xml,1.5,1.6
Message-ID: <200505142235.j4EMZTuk028230@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28222
Modified Files:
fedora-install-guide-firewallconfig-en.xml
Log Message:
1. A few style edits - best first-draft work yet!
2. Reminder: the GUI main menu now has both user preferences and
system settings under a "Desktop" menu
Index: fedora-install-guide-firewallconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firewallconfig-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-firewallconfig-en.xml 12 May 2005 23:55:57 -0000 1.5
+++ fedora-install-guide-firewallconfig-en.xml 14 May 2005 22:35:27 -0000 1.6
@@ -1,66 +1,66 @@
-
- Firewall Configuration
+
+ Security Configuration
- The default security configuration for &FC; will protect your system
+ The default security configuration for &FC; protects your system
without restricting any of the functions of a desktop or laptop
- computer. If you are installing a server then you will need to
- alter these settings in order to enable others to access the system.
+ computer. If you are installing a server, you may need to alter
+ these settings so others can access the system.
+
+ Security Configuration Screen
+
+
+
+
+
+
+
+
+
+ Security configuration screen.
+
+
+
+
+
- Click Next to proceed after you have reviewed
- the security configuration and made any necessary changes.
+ Select Next to proceed after you review the
+ security configuration and make any necessary changes.
-
-
+ Firewall
- The firewall built into Linux checks every incoming and outgoing
- network connection between your machine and another against a set
- of rules. These rules specify which types of connections are
- permitted and which are denied.
+ The
+ firewall
+ firewall built into &FC;
+ checks every incoming and outgoing network connection on your
+ machine against a set of rules. These rules specify which types of
+ connections are permitted and which are denied.
By default the firewall is enabled, with a simple set of rules
that allow connections to be made from your system to others, but
- block incoming connections from other systems. You can then
- choose to allow access to specific network services on your &FC;
- system.
+ block incoming connections from other systems. By making changes
+ on this screen, you can allow access to specific network services
+ on your &FED; system.
To enable access to services listed on this screen, click the
- checkbox next to the name of the service. After the installation
- is complete you can enable access to other services as well.
+ checkbox next to the service name. After installation is
+ complete, you can enable access to other services as well.
-
-
- Firewall Configuration Screen
-
-
-
-
-
-
-
-
-
- Firewall configuration screen.
-
-
-
-
-
- Avoid disabling the firewall. If you believe that it is necessary
- to do so, then select No firewall.
+ Avoid disabling the firewall. If you believe it is necessary to
+ do so, however, select No firewall.
@@ -68,51 +68,62 @@
To change these settings later, use the
system-config-securitylevel utility.
- From the main menu, choose System
- SettingsSecurity Level and
- Firewall.
+ From the main menu, choose
+ Desktop
+ System SettingsSecurity
+ Level and Firewall.
-
+
-
+ &SEL;
- The &SEL; (Security Enhanced Linux) framework that is part of &FC;
- limits the actions of both users and programs by enforcing defined
- security policies throughout the operating system. Software bugs
- or configuration changes can render a system vulnerable, and the
- restrictions imposed by the &SEL; policies provide an extra line
- of defense.
+ The
+ &SEL;
+ &SEL; (Security Enhanced
+ Linux) framework is part of &FC;. &SEL; limits the actions of both
+ users and programs by enforcing security policies throughout the
+ operating system. Without &SEL; software bugs or configuration
+ changes can render a system more vulnerable. The restrictions
+ imposed by &SEL; policies provide an extra line of defense.
- An inflexible set of &SEL; policies could also inhibit many normal
- activities. For this reason &FC; uses targeted policies, which
- only affect specific network services. These services cannot
- perform actions that are not part of their normal functions. This
- means that &SEL; can be Active without
- causing users any inconvenience.
+ Inflexible &SEL; policies might inhibit many normal activities on
+ a &FED; system. For this reason, &FC; uses targeted policies,
+ which only affect specific network services. These services
+ cannot perform actions that are not part of their normal
+ functions. This means that &SEL; can be active without causing
+ users any inconvenience.
+
+
+ To use the targeted &SEL; policy on your &FED; system, set the
+ &SEL; mode to Active. This is the default
+ mode for &FED; installations.
- As &SEL; is a new technology, a diagnostic mode is provided. If
- you set &SEL; to Warn then the system is
- configured, but any breach of security policies will merely cause
- an error message to appear. No activities are actually prohibited
- when &SEL; is installed in this mode. You can make &SEL; fully
- active at a later time.
+ Because &SEL; is a new technology, a diagnostic mode is provided.
+ If you set &SEL; to Warn, the system is
+ configured, but any breach of security policies only causes an
+ error message to appear. No activities are actually prohibited
+ when &SEL; is installed in this mode. You may change the &SEL;
+ mode to active at any time after booting.
- If you choose to have &SEL; Disabled then the
- access control system will not be configured at all. To make
- &SEL; active later you should use the
- system-config-securitylevel utility.
+ If you choose the Disabled mode for &SEL;,
+ &FED; does not configure the access control system at all. To
+ make &SEL; active later, from the main menu, select
+ Desktop
+ System Settings
+ Security Level and Firewall
+ .
@@ -121,13 +132,18 @@
&SEL; is unique in that it cannot be bypassed, even by the
system administrators. You can configure the behavior of &SEL;
with the system-config-securitylevel
- utility. From the main menu, choose System
- SettingsSecurity Level and
- Firewall.
+ utility. From the main menu, choose
+ Desktop
+ System Settings
+ Security Level and Firewall
+ .
-
+
+
+
+
- On First Boot
+ First Boot
The Setup Agent launches the first time
- that you start a new &FED; system. This enables you to configure
- the system for use before logging in.
+ that you start a new &FED; system. Use Setup
+ Agent to configure the system for use before logging
+ in.
@@ -27,30 +28,35 @@
- Click Next to start the Setup Agent.
+ Select Next to start the Setup
+ Agent.
- The Setup Agent requires a graphical interface
+ GUI Required
- You must manually carry out these configuration tasks if the Setup
- Agent cannot run.
+ Setup Agent requires a graphical
+ interface. If none is available, configure these options manually
+ after you log in.
-
+ License Agreement
- This screen displays the overall licensing terms for &FC;.
- Individual software packages are covered by their own licenses.
- Every software product included in &FC; uses a license that has
- been approved by the Open Source Initiative (OSI).
+ This screen displays the overall licensing terms for &FC;. Each
+ software package in &FC; is covered by its own license which has
+ been approved by the
+ OSI (Open Source Initiative)
+ Open Source Initiative (OSI). For more information
+ about the OSI, refer to http://www.opensource.org/.
- Licence Agreement Screen
+ License Agreement Screen
@@ -68,20 +74,25 @@
To proceed, select Yes, I agree to the License
- Agreement and click Next.
+ Agreement and then select
+ Next.
-
+
-
+ Date and Time
- To configure a system that does not have Internet access, manually
- set the date and time for your system at this screen. If your
- system has network access, use NTP (Network Time Protocol) servers
- to maintain the accuracy of the clock.
+ If your system does not have Internet access or a network time
+ server, manually set the date and time for your system on this
+ screen. Otherwise, use
+ NTP (Network Time Protocol)
+ NTP (Network Time Protocol)
+ servers to maintain the accuracy of the clock. NTP provides time
+ synchronization service to computers on the same network. The
+ Internet contains many computers that offer public NTP services.
@@ -112,25 +123,28 @@
- Changing the clock
+ Setting the Clock
- To change these settings later, use the
- system-config-date utility. From the
- main menu, choose System
- SettingsDate &
- Time.
+ To change these settings later, use the Date/Time
+ Properties utility. From the main menu, choose
+
+ Desktop
+ System Settings
+ Date & Time
+ .
-
+ Network Time Protocol
- To configure your system to use network time servers you must
- Enable Network Time Protocol. This
- disables the settings on the Date and Time
- tab and allows you to access to the other settings on this screen.
+ To configure your system to use network time servers, select the
+ Enable Network Time Protocol option. This
+ option disables the settings on the Date and
+ Time tab and enables the other settings on this
+ screen.
@@ -151,47 +165,49 @@
- By default &FC; is configured to use three separate clusters, or
- pools, of time servers. Having more than one NTP provider
- enables your system to choose the most accurate, or switch to
- using another server for time synchronization if the first
- becomes unavailable.
+ By default &FC; is configured to use three separate groups, or
+ pools, of time servers. Time server
+ pools create redundancy, so if one time server is unavailable,
+ your system will synchronize with another server.
- To use an additional time server either select it from the
+
+ To use an additional time server, either select it from the
Server drop-down box, or type the DNS name
- in the box, and Add. To remove a server or
- server pool from the list, select the name and click
+ in the box, and select Add. To remove a
+ server or server pool from the list, select the name and click
Delete. The drop-down box already has two
listings as examples, which are servers provided by &RH;.
- If the hardware clock in your computer is highly inaccurate you
- may also wish to remove the option to Use Local Time
- Source, under Show advanced
- options. This ensures that the NTP servers take
- priority over the internal clock.
+ If the hardware clock in your computer is highly inaccurate, you
+ may turn off your local time source entirely. To turn off the
+ local time source, select Show advanced
+ options and then deselect the Use Local
+ Time Source option. If you turn off your local
+ time source, the NTP servers take priority over the internal
+ clock.
- The Enable NTP Broadcast advanced option
- causes your system to attempt to automatically locate time
- servers available on the network.
+ If you enable the Enable NTP Broadcast
+ advanced option, &FED; will attempt to automatically locate time
+ servers on the network.
-
+
-
+
-
+ System User
- You create a user account for yourself with this screen. Always
- use this account to log in to your &FC; system, rather than using
- the root account.
+ Create a user account for yourself with this screen. Always use
+ this account to log in to your &FC; system, rather than using the
+ root account.
@@ -212,11 +228,11 @@
- Enter a Username and your Full
- Name, then enter your chosen
- Password and type it once more in the
- Confirm Password box to ensure that it is
- correct.
+ Enter a user name and your full name, and then enter your chosen
+ password. Type your password once more in the Confirm
+ Password box to ensure that it is correct. Refer to
+ for guidelines on selecting a
+ secure password.
@@ -224,17 +240,19 @@
To add additional user accounts to your system after the
installation is complete, use the
- system-config-users utility. From
- the main menu, choose System
- SettingsUsers &
- Groups.
+ User Manager utility. From
+ the main menu, chose
+ Desktop
+ System Settings
+ Users & Groups
+ .
- To configure your system to use network services for
- authentication or user information, click Use Network
- Login.... Network authentication is explained in a
+ To configure &FED; to use network services for authentication or
+ user information, select Use Network
+ Login.... Network authentication is explained in a
separate tutorial.
@@ -243,17 +261,18 @@
Next.
-
+
-
+ Display
The Setup Agent automatically attempts
- to identify the graphics card and monitor for your computer. It also uses
- this information to calculate the correct
- Resolution and Color Depth settings.
+ to identify the graphics card and monitor for your computer. It
+ also uses this information to calculate the correct
+ Resolution and Color
+ Depth settings.
@@ -274,15 +293,15 @@
- To change the selected monitor, click
- Configure. This displays a list of
- manufacturers. Find the manufacturer of your monitor on the list
- and click the disclosure triangle next to the name of the
- manufacturer to view the models of monitor. Select the correct
- model from the list and click OK. If none
- of the listed models match your monitor, select the closest match
- from either the Generic CRT Display list or
- the Generic LCD Display list.
+ If you need to change the monitor, select
+ Configure to display a list of manufacturers.
+ Select the manufacturer of your monitor on the list and hit
+ + or select the triangle next to the name to view
+ supported models. Select the correct model from the list and
+ click OK. If none of the listed models
+ match your monitor, select the closest match from either the
+ Generic CRT Display list or the
+ Generic LCD Display list.
@@ -303,27 +322,30 @@
- To change a display setting, click
+ To change a display setting, select
Resolution or Color
- Depth, and select a new value from the drop-down list. The
- Setup Agent only shows the settings
- that are valid for your hardware.
+ Depth, and select a new value from the drop-down
+ list. The Setup Agent only shows the
+ settings that are valid for your hardware.
Resetting the display
To reconfigure your system after the installation has completed,
- use the system-config-display
- utility. From the main menu, choose System
- SettingsDisplay.
+ use the Display Settings
+ utility. From the main menu, choose
+ Desktop
+ System Settings
+ Display
+ .
-
+
-
+ Sound Card
@@ -349,41 +371,58 @@
- Click Play Test Sound. If you hear a
- series of three sounds then your system has been configured
- successfully. If your sound card is identified but you do not
- hear these sounds, check your speakers and try again.
+ Click Play Test Sound to check the sound
+ card configuration. If the configuration is correct, &FED; plays
+ a sound sequence. If your sound card is identified, but you do
+ not hear the sound, check your speakers and try again.
You can manually configure a &FED; system to use unsupported sound
- cards after the installation process is complete. Manual hardware
- configuration is beyond the scope of this document.
+ cards after the installation process is complete. Manual sound
+ hardware configuration, however, is beyond the scope of this
+ document.
- Changing the sound card
+ Changing the Sound Card
- Use the system-config-soundcard utility
- to redetect your current sound card, if it is not automatically
- configured after a change of hardware. From the main menu, choose
- System
- SettingsSoundcard Detection.
+ Use the Audio Devices utility to
+ redetect your current sound card, if it is not automatically
+ configured after a change of hardware. From the main menu,
+ choose
+ Desktop
+ System Settings
+ Soundcard Detection
+ .
-
+
-
+ Additional CDs
- This screen enables you to load prepared discs for installing
- third-party software. It cannot be used for installing additional
- packages from the &FC; discs.
+ This screen allows you to load prepared discs for installing
+ third-party software. You cannot use it, however, to install
+ additional packages from the &FC; discs.
+
+ Adding Software
+
+ To add software packages from the &FC; discs, use the
+ Package Manager utility after you log
+ in. From the main menu, select
+ Desktop
+ System Settings
+ Add/Remove Applications
+ .
+
+
+
Additional CDs Screen
@@ -402,7 +441,7 @@
- Click Next to move on to the final screen.
+ Click Next to proceed to the final screen.
@@ -423,11 +462,11 @@
- Click Next to proceed to the login
- screen. Your &FC; system is now ready for use.
+ Click Next to proceed to the login screen.
+ Your &FC; system is now ready for use.
-
+
From fedora-docs-commits at redhat.com Sun May 15 18:39:11 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 15 May 2005 14:39:11 -0400
Subject: install-guide fedora-install-guide-acknowledgements-en.xml,1.3,1.4
Message-ID: <200505151839.j4FIdBFG021543@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21535
Modified Files:
fedora-install-guide-acknowledgements-en.xml
Log Message:
Removed authors' names since they are on the front page and need not
acknowledge themselves :-)
Index: fedora-install-guide-acknowledgements-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-acknowledgements-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-acknowledgements-en.xml 3 May 2005 12:19:44 -0000 1.3
+++ fedora-install-guide-acknowledgements-en.xml 15 May 2005 18:39:09 -0000 1.4
@@ -4,13 +4,8 @@
Acknowledgements
- This version of the &IG; was written by Stuart Ellis, with the
- sections on Disk Partitioning contributed by Paul W. Frields.
-
-
-
Many useful comments and suggestions were provided by Rahul
- Sundaram.
+ Sundaram and the Anaconda team.
From fedora-docs-commits at redhat.com Sun May 15 18:41:31 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 15 May 2005 14:41:31 -0400
Subject: install-guide fedora-install-guide-firstboot-en.xml,1.7,1.8
Message-ID: <200505151841.j4FIfVlE021723@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21715
Modified Files:
fedora-install-guide-firstboot-en.xml
Log Message:
Removed superfluous section tags and fixed indentation
Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-firstboot-en.xml 15 May 2005 18:37:46 -0000 1.7
+++ fedora-install-guide-firstboot-en.xml 15 May 2005 18:41:29 -0000 1.8
@@ -136,67 +136,61 @@
-
- Network Time Protocol
-
-
- To configure your system to use network time servers, select the
- Enable Network Time Protocol option. This
- option disables the settings on the Date and
- Time tab and enables the other settings on this
- screen.
-
-
-
- Date and Time Screen
-
-
-
-
-
-
-
-
-
- Date and time screen.
-
-
-
-
+
+ To configure your system to use network time servers, select the
+ Enable Network Time Protocol option. This
+ option disables the settings on the Date and
+ Time tab and enables the other settings on this
+ screen.
+
-
- By default &FC; is configured to use three separate groups, or
- pools, of time servers. Time server
- pools create redundancy, so if one time server is unavailable,
- your system will synchronize with another server.
-
+
+ Date and Time Screen
+
+
+
+
+
+
+
+
+
+ Date and time screen.
+
+
+
+
-
- To use an additional time server, either select it from the
- Server drop-down box, or type the DNS name
- in the box, and select Add. To remove a
- server or server pool from the list, select the name and click
- Delete. The drop-down box already has two
- listings as examples, which are servers provided by &RH;.
-
+
+ By default &FC; is configured to use three separate groups, or
+ pools, of time servers. Time server pools
+ create redundancy, so if one time server is unavailable, your
+ system will synchronize with another server.
+
-
- If the hardware clock in your computer is highly inaccurate, you
- may turn off your local time source entirely. To turn off the
- local time source, select Show advanced
- options and then deselect the Use Local
- Time Source option. If you turn off your local
- time source, the NTP servers take priority over the internal
- clock.
-
+
+ To use an additional time server, either select it from the
+ Server drop-down box, or type the DNS name in
+ the box, and select Add. To remove a server
+ or server pool from the list, select the name and click
+ Delete. The drop-down box already has two
+ listings as examples, which are servers provided by &RH;.
+
-
- If you enable the Enable NTP Broadcast
- advanced option, &FED; will attempt to automatically locate time
- servers on the network.
-
+
+ If the hardware clock in your computer is highly inaccurate, you
+ may turn off your local time source entirely. To turn off the
+ local time source, select Show advanced
+ options and then deselect the Use Local
+ Time Source option. If you turn off your local time
+ source, the NTP servers take priority over the internal clock.
+
-
+
+ If you enable the Enable NTP Broadcast
+ advanced option, &FED; will attempt to automatically locate time
+ servers on the network.
+
From fedora-docs-commits at redhat.com Sun May 15 18:44:41 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 15 May 2005 14:44:41 -0400
Subject: install-guide fedora-install-guide-en.xml,1.11,1.12
Message-ID: <200505151844.j4FIifQf021737@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21729
Modified Files:
fedora-install-guide-en.xml
Log Message:
Moved to version 0.7 to reflect style editing and indexing
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- fedora-install-guide-en.xml 12 May 2005 22:27:31 -0000 1.11
+++ fedora-install-guide-en.xml 15 May 2005 18:44:39 -0000 1.12
@@ -4,9 +4,9 @@
%FEDORA-ENTITIES-EN;
-
+
-
+
@@ -82,6 +82,17 @@
+
+ 0.7
+ 2005-05-15
+ StuartEllis
+ PaulWFrields
+
+
+ Additional style editing and indexing
+
+
+
From fedora-docs-commits at redhat.com Mon May 16 20:51:43 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 16 May 2005 16:51:43 -0400
Subject: install-guide fedora-install-guide-intro-en.xml,1.4,1.5
Message-ID: <200505162051.j4GKph6O017951@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17943
Modified Files:
fedora-install-guide-intro-en.xml
Log Message:
Start 2nd style pass of intro; defined architectures
Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-intro-en.xml 12 May 2005 14:05:36 -0000 1.4
+++ fedora-install-guide-intro-en.xml 16 May 2005 20:51:41 -0000 1.5
@@ -5,28 +5,50 @@
&DRAFTNOTICE;
- &FC; is a complete desktop and server operating system that is
- created entirely with Open Source software.
+ &FC; is a complete desktop and server operating system created
+ entirely with Open Source software.
&FC; Lifecycle
&FC; is a rapidly evolving system which follows the latest
- technical developments. It may not be appropriate to use &FC; in
+ technical developments. &FC; may not be appropriate for use in
critical applications in your organization.
-
+
This manual helps you to install &FC; on desktops, laptops and
- servers. The installation system is extremely flexible, but you do
- not need any previous knowledge of Linux or computer networks in
- order to use &FC;. You can have a desktop operating system with
- applications installed on your computer simply by accepting the
- default options.
+ servers. The installation system is flexible enough to use even if
+ you have no previous knowledge of Linux or computer networks. Even
+ if you only select default options, &FC; provides a complete desktop
+ operating system, including:
+
+
+
+ full-featured productivity applications such as a word
+ processor, spreadsheet manager, and presentation manager
+
+
+
+
+ Internet utilities such as a Web browser, email client, Internet
+ Relay Chat client, and instant messaging client
+
+
+
+
+ desktop tools to catalog and edit digital photographs, create
+ sophisticated computer graphics, create and copy compact discs,
+ and play media files
+
+
+
+
+
This document does not detail all of the features of the
installation system.
]>
Fedora Core 3 Hardening Guide2005&FORMAL-RHI;Charles HeseltonHeseltonCharles
&LEGALNOTICE;
Introduction
&DRAFTNOTICE;
This tutorial is a basic walk-through of how to harden a basic install
of &FC;. Many of the actions and principles discussed here will apply
to many different linux distributions. However, for the purpose of this
tutorial we will be regarding &FC;, specifically.
Document Scope
While describing the techniques and tools used in this tutorial, it is
the goal of the author to present both the Graphical User Interface (GUI) tools, and the
more traditional command line (CLI) tools that are available in
FC3.
Many users will have customized the appearance of their desktop (if running
one), panels, menus, etc. This guide makes direction based on the default
install and configuration of &FC;. The locations of items, menus,
commands, etc. may differ from your actual experience.
Intended Audience
This document is intended for use by all &FC; users. However, there is a
focus for home or small-business users. Enterprise deployments of Fedora
will want to make some different considerations such as centralized syslog
storage, unified (central) user authentication, etc. Most of the
principles discussed will apply, however there are some enterprise
applications which are outside the scope of this document.
Initial Steps
&DRAFTNOTICE;
Package Installation Considerations
This section will not go into the actual process of installing packages,
that falls under the scope of the Installation Guide. However, there
are some important things to consider, in regards to security, when you are installing &FC;
and selecting your packages for installation, and when you are
installing new packages on an already built system.
Package Selections During Install
When you are first installing your &FC; system, take careful
consideration of the packages that you are installing. Know what type
of system you are building before you build it. Fedora offers a
"system role" method of choosing packages, which can be customized to
remove or not install certain packages, and install others that may not be
designated as part of that particular role. A good approach would be to,
first, draw out a plan of what your system is to be used for, and what
services you will want to offer (if any). You can then make an
educated decision about what installation type you want to start
with. Fedora offers the following in terms of installation types:
Personal DesktopWorkstationServerCustomYou can then check the "Select specific packages" to modify your
installation, or use the Add
and Remove Progams GUI utility, or the
yum command line utility, to install any additional
packages required for your needs.
Package Considerations for Installation of New Software
If you are updating, or adding to, a system that is already
installed with &FC;, then there are some other considerations that
need to be made.
When installing a new package, you should check the integrity of the
package. Most reliable sources will provide a signed checksum file
for a package file. You can use gpg or
md5sum to verify the checksum provided,
depending on the digital signature provided.
gpg is a utility which allows you to manage digital
signatures. These signatures allow you to digitally sign or encrypt
data (including text messages or files). For more details on
gpg visit the GNU gpg website at http://www.gnupg.org.
md5sum is a utility which is based off of the MD5
algorithm. This utility can be used to create a digital signature of
a file, which can then be compared to the MD5 checksum downloaded with
the software package. For more details on the MD5 hashing algorithm,
and associated utilities, you can visit the MD5 website at http://www.fourmilab.ch/md5/.
The actual source of the package must come into consideration as
well. If you are downloading new packages from fedora.redhat.com, the
package and checksum should be fairly trustworthy. However, if you
are downloading the package from www.myanonymoussoftwaresite.com, you
may want to try to find another source for the package, or further verify the
integrity of the site. You can find a brief description of how to
verify a downloaded file with the provided checksum in the following
two sections.
gpg usage example
Verifying a file with gpg is a method of verifying
a file's integrity with a digital signature. In porder for this to
work, you must have the signer's public key, or digital signature, on
your local keyring. If you are totally lost at this point, you
should go back and read the documentation on the GNUpg site, linked
above. For this example, we're going to download and test a kernel
image from ftp://ftp.kernel.org. As just stated, we need to get the key for
the Linux Kernel Archives. However, first we need to make sure that
our gpg comfiguration is complete.
Start by issuing the following command to see if our home
configuration directory exists or not. (If you have never used gpg,
this directory will not exist.)
ls -d ~/.gnupg
If your directory exists, you will see something along the lines of
the following:
/home/charlie/.gnupg
Of course, unless your username happens to be "charlie", this part
of the path will be something different. If your directory does
not exist, then you will see something like
this:
ls: /home/charlie/.gnupg: No such file or directory
... and you will need to create that directory ...
mkdir ~/.gnupg
Next, you will need to create your own keys, which will also
initialize your gpg public and private keyrings.
gpg --gen-keyYou will be prompted with the following:gpg (GnuPG) 1.2.6; Copyright (C) 2004 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.
Please select what kind of key you want:
(1) DSA and ElGamal (default)
(2) DSA (sign only)
(4) RSA (sign only)
Your selection?
Option one (1) is the option you should choose if you ever might
want to encrypt anything. The other two options only allow you to
sign. After you make your selection, you will be asked a series of
questions about yourself (name, email, etc.), and you will be asked
for a passphrase. Once the key has been created, you will be
prompted with your new gpg fingerprint:
public and secret key created and signed.
key marked as ultimately trusted.
pub 1024D/834AA506 2005-04-08 Bogus (Bogus key) <bogus at foo.com>
Key fingerprint = 8F0F CDA0 1682 58B2 F38D 31AF CD8A 6FD5 834A A506
sub 1024g/0F43BE0D 2005-04-08
If you have never used gpg before, you may also
receive messages regarding the creation of your public and private
keyrings. Now that you have your keyrings in place, you need to add
the Linux Kernel Archive public key to your key ring. This process
is described in detail at the following URL:
http://www.kernel.org/signature.html
However, the process is summarized in one simple step for you below:
gpg --keyserver wwwkeys.pgp.net --recv-keys 0x517D0F0E
When you downloaded the kernel file, you should have also downloaded
a linux-2.x.x.x.tar.gz.sign file. This file
contains the signature of the file you downloaded that was created
with the Archive public key. In order to get that warm and fuzzy
when we verify the file. We will also want to sign the key we just
downloaded.
gpg --lsign-key 517D0F0E
pub 1024D/517D0F0E created: 2000-10-10 expires: never trust: -/-
sub 4096g/E50A8F2A created: 2000-10-10 expires: never
(1). Linux Kernel Archives Verification Key <ftpadmin at kernel.org>
pub 1024D/517D0F0E created: 2000-10-10 expires: never trust: -/-
Primary key fingerprint: C75D C40A 11D7 AF88 9981 ED5B C86B A06A 517D 0F0E
Linux Kernel Archives Verification Key <ftpadmin at kernel.org>
How carefully have you verified the key you are about to sign actually belongs
to the person named above? If you don't know what to answer, enter "0".
(0) I will not answer. (default)
(1) I have not checked at all.
(2) I have done casual checking.
(3) I have done very careful checking.
Your selection? (enter '?' for more information): 2
Are you really sure that you want to sign this key
with your key: "Tuxxer (Tuxxer) <tuxxer at cox.net>" (F1E11EA1)
I have checked this key casually.
Really sign? y
Option two (2) in the dialog described above is a good selection if
you are somewhat familiar with the person or group owning the key.
Now on to the downloading and verifying. The download process is
outlined below:
ftp ftp.kernel.org
Connected to ftp.kernel.org (204.152.191.37).
220 Welcome to ftp.kernel.org.
Name (ftp.kernel.org:charlie): anonymous
331 Please specify the password.
Password:
230- Welcome to the
230- LINUX KERNEL ARCHIVES
230- ftp.kernel.org
230-
< ... snip kernel.org banner stuff ... >
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd /pub/linux/kernel/v2.6
250 Directory successfully changed.
ftp>ls linux-2.6.11*
227 Entering Passive Mode (204,152,191,37,71,78)
150 Here comes the directory listing.
< ... snip older versions listing ... >
-rw-r--r-- 1 536 536 37099602 Apr 07 19:21 linux-2.6.11.7.tar.bz2
-rw-r--r-- 1 536 536 248 Apr 07 19:21 linux-2.6.11.7.tar.bz2.sign
-rw-r--r-- 1 536 536 46585077 Apr 07 19:21 linux-2.6.11.7.tar.gz
-rw-r--r-- 1 536 536 248 Apr 07 19:21 linux-2.6.11.7.tar.gz.sign
-rw-r--r-- 1 536 536 248 Apr 07 19:21 linux-2.6.11.7.tar.sign
226 Directory send OK.
ftp> prompt
Interactive mode off.At the time of this writing, the 2.6.11.7 kernel was the most
recent. There may be a more recent version when you read this
document.
ftp> mget linux-2.6.11.7.tar.gz linux-2.6.11.7.tar.gz.signlocal: linux-2.6.11.7.tar.gz remote: linux-2.6.11.7.tar.gz
227 Entering Passive Mode (204,152,191,37,170,43)
150 Opening BINARY mode data connection for linux-2.6.11.7.tar.gz (46585077 bytes).
226 File send OK.
46585077 bytes received in 89.7 secs (5.1e+02 Kbytes/sec)
local: linux-2.6.11.7.tar.gz.sign remote: linux-2.6.11.7.tar.gz.sign
227 Entering Passive Mode (204,152,191,37,84,119)
150 Opening BINARY mode data connection for linux-2.6.11.7.tar.gz.sign (248 bytes).
226 File send OK.
248 bytes received in 0.00102 secs (2.4e+02 Kbytes/sec)
ftp> bye
221 Goodbye.
Now that we have all that ftp stuff out of the
way, we can verify the file that has just been downloaded. Since
you have already gone through the trouble of creating your
keyring, and signing the Linux Kernel Archive's key, this
is a easy as the single command below.
gpg --verify linux-2.6.11.7.tar.gz.sign linux-2.6.11.7.tar.gzgpg: Signature made Thu 07 Apr 2005 12:30:06 PM PDT using DSA key ID 517D0F0E
gpg: Good signature from "Linux Kernel Archives Verification Key <ftpadmin at kernel.org>"
gpg: checking the trustdb
gpg: checking at depth 0 signed=7 ot(-/q/n/m/f/u)=0/0/0/0/0/2
gpg: checking at depth 1 signed=16 ot(-/q/n/m/f/u)=7/0/0/0/0/0
gpg: next trustdb check due at 2005-09-29
The line "gpg: Good signature from ... " indicates that the
signatures is valid, and the file is verified.
md5sum usage example
The md5sum command is used to get an MD5 checksum
from a file, or line/section of text, which can then be compared to
a supplied checksum to verify the integrity of the file you are
downloading.
Start by downloading the file. For this example, we are using the
first disk image of the Fedora Core 3 install.
ftp download.fedora.redhat.comTrying 66.187.224.20...
Connected to download.fedora.redhat.com (66.187.224.20).
220 Fedora FTP server ready. All transfers are logged.
Name (download.fedora.redhat.com:charlie): anonymous
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd /pub/fedora/linux/core/3/i386/iso/
250 Directory successfully changed.
ftp> ls
227 Entering Passive Mode (66,187,224,20,49,191)
150 Here comes the directory listing.
-rw-r--r-- 1 ftp ftp 2466410496 Nov 03 22:18 FC3-i386-DVD.iso
-rw-r--r-- 1 ftp ftp 589832192 Nov 03 22:11 FC3-i386-SRPMS-disc1.iso
-rw-r--r-- 1 ftp ftp 589844480 Nov 03 22:12 FC3-i386-SRPMS-disc2.iso
-rw-r--r-- 1 ftp ftp 589815808 Nov 03 22:13 FC3-i386-SRPMS-disc3.iso
-rw-r--r-- 1 ftp ftp 589817856 Nov 03 22:15 FC3-i386-SRPMS-disc4.iso
-rw-r--r-- 1 ftp ftp 646987776 Nov 03 22:05 FC3-i386-disc1.iso
-rw-r--r-- 1 ftp ftp 668520448 Nov 03 22:07 FC3-i386-disc2.iso
-rw-r--r-- 1 ftp ftp 667498496 Nov 03 22:08 FC3-i386-disc3.iso
-rw-r--r-- 1 ftp ftp 404764672 Nov 03 22:10 FC3-i386-disc4.iso
-rw-r--r-- 2 ftp ftp 79908864 Nov 03 21:59 FC3-i386-rescuecd.iso
-rw-r--r-- 1 ftp ftp 791 Nov 03 23:00 MD5SUM
226 Directory send OK.
ftp> get FC3-i386-disc1.iso
ftp> get MD5SUM
After you have the file downloaded, verify the checksum by issuing
the following command:
md5sum FC3-i386-disc1.isoThis will output something similar to the following:db8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso
You can then grep the
MD5SUM file you should have downloaded for the
correct checksum:
grep 'FC3-i386-disc1.iso' MD5SUMdb8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso
If the hexadecimal number in the first column matches the
hexadecimal number output by the md5sum command,
then you can be assured that the file you downloaded is an
unmodified version of the file that was posted.
Configuring and Using sudo
Using the sudo utility allows a user to run another
command or tool as if they were logged on as root. If you're doing
something that requires the access of the root user, this is the best method
for elevating your privileges.
The file that sudo uses as its configuration file is
/etc/sudoers. This file allows you to set up
command, host, and user aliases that are allowed through sudo, and
which users are allowed to run them, from which host, etc. For more information on the details
of the sudoers file and how to configure it, take a
look at the sudoers man page.
If you add the lines below to the /etc/sudoers
file, it will allow your user account access to command(s) specified by
the 'Cmnd_Alias' when you use the sudo command. You will
have to type your password for each command.
Cmnd_Alias HARD = "gpg", "md5sum", "sudo", "yum", "rpm", "find", "pkill",
"iptables", "umask", "chkconfig", "grep"
yourusername ALL = HARD
The commands selected for this example should
provide all of the appropriate priveleges required by the instructions
in this guide. If you would like a more complete configuration for your
implementation of sudo, please consult the
man page or the online documentation.
For more information on how to configure sudo, you can view the manpage
and other documentation at the link below.
http://www.courtesan.com/sudo/man/sudo.htmlhttp://www.linuxhelp.net/guides/sudo/Identifying system role and usage
&DRAFTNOTICE;
As we have already mentioned, one important thing to do initially is to identify what
your system will be used for, what services you will need, and how many
users will be using your system. Here are some things to consider:
Will you be using your new &FC; system for Internet and email only?Will you be serving web/email/ftp content?Will your system act as a firewall for your home or office
network which will do Network Address Translation (NAT'ing)?
Once you have considered all of these things in regards to your new &FC;
system, you can make intelligent decisions about to secure your system.
For the scope of this guide, it is assumed that you will be securing a
workstation which will be used for web surfing, email, office documents,
and the like. It is also assumed that there will be one primary user for
this system.
GUI: Updates with up2date
Make sure that you have all of the most current updates. There are many
times that a package will be released with a distribution release and then a
vulnerability with that version will be posted after the release of the
distribution. While there is a lag between notification, and patching, the
distribution "owner" will usually release a patch or updated version
shortly. This means that if you are installing a system after it's initial
release, it may be outdated.
&FC; provides a couple of different ways of accomplishing this.
The GUI utility is called up2date. After
you've first installed your new &FC; system, it should automatically
try to connect to the &RHN; to determine if it's applications are up
to date or not. Most likely, they will not be up to date. This is
indicated by the red exclamation point icon in the upper right hand
corner of the screen, on the Gnome panel.
Clicking on the icon will bring up the &RHN;
Alert Notification Tool dialog. This will show you any products
that are currently installed on your system that need to be updated. Click
the "Launch up2date" button to launch the actual update application. Follow
the instructions in the subsequent dialogs to update your system. If your
system is up to date, you will receive a notification that indicates this.
Otherwise, the up2date program will download the
necessary packages and install them for you.CLI: Updates with yum
&DRAFTNOTICE;
The most convenient CLI tool that comes with &FC; is
yum. Yum will not automatically check to see
if your applications and packages are up to date, since the default
functionality relies on the GUI tools. It can, however, be configured to
do so. By issuing the following command:
sudo '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'
you will start the service, and configure it to start at runlevels
3, 4, and 5. If you are running a
"headless" system, or if you are running in command line only mode,
one of the first things that you will want to do will be to run
yum. Use the following command to check for
any available updates:
sudo 'yum check-update'
This will check for any package updates, and dependencies. Ultimately,
this is not a necessary step, but I like to run it to see what updates are
available, if any, before actually updating. Then, to install any
updates found, you will need to run the following command:
sudo 'yum update'
This will automatically download any pending package or application updates,
including kernel updates. Then once all of the updates packages have been
downloaded, you will be prompted to continue with the transaction (or
installation process).
The first time you run yum, you will be asked to
install the gpg key, unless you have already disabled file signature
checking in yum.conf. The simplest way to do this
is to use the key installed when installing the operating system. Issue
the following command to accomplish this:
sudo "rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora"
Once you have the key installed, you will be able to verify the packages
you download and install by using yum.
NoteIf there are any unresolved dependencies, you will be asked if you want
to download and install the dependencies. Most of the time, you should do this.
Tip
If you have received any critical updates, like a kernel update, you will want
to reboot your system after the update is complete.
You can find more information on keeping your system up to date at
following link:
http://fedora.redhat.com/docs/updates/index.htmlDisabling unnecessary services
&DRAFTNOTICE;
GUI: Service Configuration
To get to the GUI tool to edit the default services, select
Menu->System Settings->Server Settings->Services.
This will bring up the Service configuration dialog.
Access Note
You should run this utility (and all other GUI utilities) as a normal user,
unless otherwise specified. When doing so, you will be prompted for the
root password. Type it in the dialog to continue.
For each service listed, the Service
Configuration utility will display a short description
about the service you have highlighted in the upper-right pane, and the
current status and process ID (PID) of the service, if it is running.
The services that you can safely disable will depend upon the role of
your system. For example, if you are planning to run a web server, you
will not want to disable the httpd service.
The list below is a good starting place. These services can be disabled
for the role we have chosen, that of a home workstation:
aep1000 - load and unload AEP1000/AEP2000 coprocessor driver.bcm5820 - Hardware cryptographic accelerator support - BCM5820 Cryptonet driver.chargen - An xinetd internal service which generates characters.chargen-udp - This is the udp version.daytime - An internal xinetd service which gets the current system time.daytime-udp - This is the udp version.echo - An xinetd internal service which echo's characters back to clients.echo-udp - This is the udp version.httpd - Apache is a World Wide Web server. It is used to serve HTML files and CGI.irda - Infrared data link (for PDAs and such)ktalk - KDE version of the talk server.lisa - Provides information about hosts on your network.mysqld - MySQL database server.named - named (BIND) is a Domain Name Server (DNS) that is used to resolve host names to IP addresses.netplugd - netplugd is a daemon for managing non-static network interfaces.nfs - This service provides NFS server functionality.nfslock - This service provides NFS file locking functionality.nscd - This is a daemon which handles passwd and group lookups for running programs and cache the results for the next query. ntpd - ntpd is the NTPv4 daemon.pcmcia - PCMCIA support is usually to support things like ethernet and modems in laptops. rsync - allows remote file synchronizationsaslauthd - saslauthd is a server process which handles plaintext authentication requests on behalf of the cyrus-sasl library.services - An internal xinetd service, listing active services.sgi_fam - FAM is a file monitoring daemon.smartd - Self Monitoring and Reporting Technology (SMART) Daemon.snmpd - Simple Network Management Protocol (SNMP) Daemon.snmptrapd - Simple Network Management Protocol (SNMP)
Trap Daemon.squid - Squid - Internet Object Cache.time - An RFC 868 time server. time-udp - This is the udp version.tux - The TUX threaded kernel-based http server.vncserver - Starts and stops vncserver. used to provide remote X administration services.winbind - Starts and stops the Samba winbind daemon.ypbind - This is a daemon which runs on NIS/YP clients and binds them to a NIS domain.yppasswdd - yppasswdd is the RPC server that lets users change their passwords in the presence of NIS (a.k.a. YP).ypserv - ypserv is an implementation of the standard NIS/YP networking protocol.ypxfrd - ypxfrd should be started in addition to ypserv to accelerate transferring yp maps.yum - Enable daily run of yum, a program updater. (This will
depend on your environment.)
If you include yum in your list of services to
disable here, then you will be disabling the automated updates you
would have configured in earlier sections of this overview. Certain
users may have specific reasons for not wanting to run
automated updates every night. Most users will want to leave this
enabled, if you are disabling it, you should know exactly why.
Once you have chosen the services that you want to disable for your
application, you can do so by unchecking the check box next to the name
of the service you are disabling. Once you have deselected all of the
services you want to disable, be sure to click the
Save button, so that your changes are committed.
The process needs to be done for all 3 multi user runlevels (3, 4, 5).
The GUI utility defaults to runlevel 5, so you will have to manually
select runlevels 3 and 4 to enable/disable service there. You may also
want to check runlevel 2, as there are certain services that may be
considered "critical" that will be started at that runlevel.
Important
Be sure to stop the service you are disabling, if it is running.
This will both prevent you from having to reboot your system, as well as
give you an immediate indication of what effect
not having that particular service running will
have on your system.
CLI: Service ConfigurationNote:
The following commands will need to be run as root.
There are a number of ways to tackle service control from the command
line. One of the simplest is to use chkconfig. The
following command will show you the all of the services that are enabled
to run at runlevel 5:
sudo '/sbin/chkconfig --list | awk '/5:on/ { print $1 }' | sort'
If you are running in command line only mode (runlevel 3),
theoretically, you could disable all of these services. However, this
could cause problems if you were to ever run in GUI mode. So, focus on
the ones that I have listed above in the GUI section. Take this list of
services, and put it into a series of commands that can be run
either from the command line directly, or in a script. The easiest way
will be to put the list of services in a file, however you could list
all of the services individually in the for loop. This might be the
better option if you were running it directly from the command line.
To put the list of services in a file, issue the command above, and
redirect the output to a file:
sudo '/sbin/chkconfig --list | awk '/[35]:on/ { print $1 }' | sort >> serviceslist.txt'
This will capture all of the services that are designated to start at
either runlevel 3 or runlevel 5. Then, edit the
serviceslist.txt file to only disable
the services you want to disable. An example serviceslist.txt file
might look like this:
acpid
anacron
apmd
autofs
cpuspeed
crond
cups
cups-config-daemon
gpm
haldaemon
httpd
iptables
irqbalance
kudzu
lm_sensors
mDNSResponder
messagebus
microcode_ctl
netfs
network
nfslock
nifd
portmap
readahead
readahead_early
rhnsd
rpcgssd
rpcidmapd
rpcsvcgssd
smartd
smb
vncserver
xfs
xinetd
Once you've edited the
serviceslist.txt file, put the following into a text file:
for SERVICE in `cat serviceslist.txt` ;do
/sbin/chkconfig --level 35 ${SERVICE} off
done
...and give it executable permissions:
sudo chmod u+x script.sh
Execute the script by issuing the following command:
sudo ./script.sh
This will disable the services you have selected for runlevels 3 and 5,
which are multi-user runlevels: level 3 for command line only, and
level 5 for X, or GUI, mode.
Disabling or Deleting Unnecessary Users and Groups
&DRAFTNOTICE;
Once you've disabled all of the services you have determined to be
unnecessary for your implementation, you will need to do the same thing
for your users and groups.
Warning!Unmanaged users (unused users, users without passwords, etc.) can be a
vector for attack. Without proper management of all of these "system" and
"service" accounts, they could be easily compromised, and used to bring
further harm to your system.
Remember the list of services that you disabled? Most of those services
will have their own user. This is a good thing if you are intending to
use those services, because that means that there is some chroot, or
"jail environment", that is built into the application for that service.
However, if you're not going to use those services, there is no reason
to have those users lying around. For the most part, the user accounts
that are associated with a service should be removed when the service is
removed. However, the following steps will be necessary if a service or
package is simply disabled, as described above, as opposed to completely
removed.
GUI: Disabling unnecessary users
Start by selecting Menu->System Setting->Users and Groups. This will bring up the User
Manager.
AuthorizationIf you are running this as a normal user (as you
should be), then you will have to type in the root password in the
administrative privilege dialog box.
By default, the User Manager will filter
all of the "default" and/or "system" users. These are the user
account that need to be scrutinized. To view the users you
want to disable, select Preferences->Filter System users and
Groups. This will disable the default filter and you will
be able to view the system users you want to disable. In order to
disable a user, you will need to select the user, then click
Properties. This will show you the details of
the user's account. The first tab in the User Properties
dialog will be the User Data tab. Here you will be presented with options
such as "username", "user full name", etc. At the bottom of the tab will be
the user's default shell. If this is not already
/sbin/nologin, change it to that shell. Next, select the
"Account Info" tab. You will be presented with two (2) check boxes here.
The first is for account expiration period, the second is for "locking" the
user account's password. Click both of these boxes so that they are
checked. In the "Account Expiration" section, put today's date. Click the
OK button, and move on to the next user.
The following are some of the service related user accounts that you
might want to disable, depending on your requirements:
news - news server useroperatorgophergamessquid - squid proxy cache daemon user.named - BIND (DNS Server) user.mysql - MySQLd user.ncsd - NCSD daemon user.ntp - ntp client user.apache - Apache/HTTPD user.smmsp - Sendmail mail queue user.
Your usage will vary. If you are using certain publicly available
services (such as a web server), you may not want to disable some of the
user accounts mentioned here (like apache). A good rule of thumb is, that if you are disabling
a service, and there is a user associated with that service, you will
want to disable the user as well.
Securing the File System
&DRAFTNOTICE;
Securing the file system basically translates to securing files. Some
might consider selection of the file system type to be important, but for the
scope of this document, it is assumed that you will be dealing with a base
installation of &FC;. Given that assumption, most files will have
"reasonable" permission already set. However, it never hurts to be sure.
Searching for insecure filesBasic File Permissions Introduction&FC; (and most other Unices) separates access control on
files and directories according to three characteristics: user, group,
and other. There is always exactly one owner, any number of members of the
group, and everyone else.
A quick explanation of Unix permissions:
Ownership - Which user(s) and group(s) retain(s) control of the
permission settings of the node and parent of the node
Permissions - Bits capable of being set or reset to allow certain types
of access to it. Permissions for directories may have a different
meaning than the same set of permissions on files.
Read:
To be able to view contents of a fileTo be able to read a directory
Write:
To be able to add to or change a fileTo be able to delete or move files in a directory
Execute:
To be able to run a binary program or shell scriptTo be able to search in a directory, combined with read
permission
Save Text Attribute: (For directories)
The "sticky bit" also has a different meaning when applied to
directories than when applied to files. If the sticky bit is set on a
directory, then a user may only delete files that the he owns or for which
he has explicit write permission granted, even when he has write access to
the directory. This is designed for directories like /tmp, which are
world-writable, but where it may not be desirable to allow any user to
delete files at will. The sticky bit is seen as a t in a long directory
listing.
SUID Attribute: (For Files)
This describes set-user-id permissions on the file. When the set user ID
access mode is set in the owner permissions, and the file is executable,
processes which run it are granted access to system resources based on the
user who owns the file, as opposed to the user who created the
process. This is the cause of many "buffer overflow" exploits.
SGID Attribute: (For Files)
If set in the group permissions, this bit controls the "set group id"
status of a file. This behaves the same way as SUID, except the group is
affected instead. The file must be executable for this to have any
effect.
SGID Attribute: (For directories)
If you set the SGID bit on a directory (with chmod g+s directory), files created in that directory will have their group set to the directory's group.
You - The owner of the file
Group - The group you belong to
Everyone - Anyone on the system that is not the owner or a member of the
group
This is a fairly high level discussion of linux file permissions. A
slightly more indepth discussion can be found here:
http://www.tldp.org/LDP/intro-linux/html/sect_03_04.htmlFinding world-writable files
Unfortunately, there is no Fedora-specific tool (or GUI tool, for that
matter) which raises the "Big Red Flag" and says:
/THIS/FILE/IN/THIS/PATH has world writable permissions. ANYONE can write to this file!!!
There is, however, a very simple (although not very timely) way of doing
this with the *NIX find command. The lines below can
be copied to a command line and then executed to find any world writable
files and directories.
sudo 'find / \( -type d -o -type f \) -perm +002 | tee world-writable-files.txt'
You may be surprised at how many files are world-writable "out of the
box". But you'll have to examine the list carefully, making sure that
files that are listed are not links, or devices, or other special files.
The command line above will only return normal directories and files. So
if you have device (i.e. /dev/foo) files in your list, they are most
likely marker files for devices that don't exist, or aren't in use on your
system.
Finding SetUID/SetGID files
You should also check for setUID/setGID files and directories.
SetUID/setGID files are files that can be executed with permissions
greater than that of the user running the program. Often, this can be
exploited, and may still leave backdoors into your system, even after patching.
Again, there is no Fedora-specific tool which will help us identify these
files, however find can also solve this problem. Use
the find command line string below to pipe all of the
setUID/setGID files into a file.
find / -type f \( -perm -04000 -o -perm -02000 \) | tee -a setuid-files.txt
You are likely to see many normal programs in this list, however, if you
have just installed your system, and have not yet connected it to a
network, it would be safe to consider this entire list of files as
trusted. If you have connected this system to a network and/or have not
just installed your system, you will want to carefully review the list
of files, to make sure that there is nothing "odd" in the list.
Insecure files summary
Once you have obtained the list(s) of world-writable files and
directories, you will want to save those lists in a secure place. Make
a copy of the lists on a floppy, or other secure location, so you have
them to reference, if needed. If you are using gpg, or have installed
the md5 utility, you will want to run a
checksum of your file, or digitally sign it, so that in the event you
need to reference that file, you are able to verify that it has not been
tampered with.
You will also want to periodically re-check your file system to make sure
that no new files with the above permissions issues have been introduced
into your system, that you are unaware of. To accomplish this, you can
copy the following script, which combines the above commands, and run it
from the cron tab on a regular basis.
#!/bin/bash
#simple script to check for world writable files and setUID/setGID files.
# baseline world-writable files list
BL_WWF='/SCRIPTS/security/harden/world-writable-files.txt'
#baseline setuid files list
BL_SUID='/SCRIPTS/security/harden/setuid-files.txt'
TODAY=`date +%y%m%d`
printf "Checking the file system for world-writable files ..... "
find / \( -type d -o -type f \) -perm +002 > /tmp/${TODAY}-wwf.txt
printf " done.\n"
printf "Checking the file system for setUID/GID files ..... "
find / -type f \( -perm -04000 -o -perm -02000 \) > /tmp/${TODAY}-suid.txt
printf " done.\n"
diff ${BL_WWF} /tmp/${TODAY}-wwf.txt > /tmp/${TODAY}-wwf.diff
diff ${BL_SUID} /tmp/${TODAY}-suid.txt > /tmp/${TODAY}-suid.diff
printf "Changed world-writable files:\n"
cat /tmp/${TODAY}-wwf.diff | mail -s "World Writable Files for ${TODAY}" charlie at localhost
printf "Changed setUID/GID files:\n"
cat /tmp/${TODAY}-suid.diff | mail -s "setU/GID Files for ${TODAY}" charlie at localhost
This may take a few minutes depending upon the size of your file
system. For example, on a file system spanning multiple drives, and
totaling approximately 160GB, it could take as long as 10 minutes.
To run the script from the crontab, enter a line like the following into
the cron:
0 0 * * * /SCRIPTS/security/harden/check_files.sh
This will run the script every night at midnight. You will want to make
adjustments for your own application.
Verifying packages with rpm
The rpm command can be used to verify the packages
that you have installed. This should be done regularly. Verifying a
package compares information about the installed files in the package
with information about the files taken from the package metadata
stored in the rpm database. Among other things, verifying compares the
size, MD5 sum, permissions, type, owner and group of each file. Any
discrepancies are displayed. Files that were not installed from the
package will be silently ignored. There are a number of options that
you can implement at the command line, however, they are mostly to
disable features that you would most likely want. You can do this type
of verification by issuing the following command:
rpm -Va
This will verify each installed package as described above, and output
something similar to the following:
.....UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/lxdialog/msgbox.c
.....UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/lxdialog/yesno.c
.M...UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/mkuboot.sh
.....UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/mkversion
S.5....T c /etc/pam.d/system-auth
S.5....T /usr/share/texmf/web2c/amstex.fmt
S.5....T /usr/share/texmf/web2c/bamstex.fmt
There may be file identifiers, like the 'c' in the middle of the line
for the /etc/pam.d/system-auth. This index can
indicate any of the following:
c - configuration file.
d - documentation file.
g - the file contents are not included in the package payload
l - license file.
r - readme file.
The indicators in the left column indicate the test success or failure,
and if the test failed, the reason for the failure. The alphanumeric
indicator can indicate any of the following:
S - file Size differs
M - Mode differs (includes permissions and file type)
5 - MD5 sum differs
D - Device major/minor number mismatch
L - readLink(2) path mismatch
U - User ownership differs
G - Group ownership differs
T - mTime differs
Most of the time the errors seen here will be relatively benign,
especially if you have yum configured to update packages automatically.
However you should verify changes that you don't recognize.
Configuration File Verification
If you are running any types of network services, i.e. web, mail, ftp,
etc., you should periodically verify your configuration files. It is a
good idea to have an external backup (floppy, CD, etc.) in case something happens to your working
config. Once you have completed either the base configuration, or an
update to an existing configuration, save your files to your chosen secure
location. You may even consider running the tool
md5sum against each configuration file as an extra
measure. This will help to ensure that your configuration files haven't
been tampered with.
md5sum examplemd5sum /etc/httpd/conf/httpd.conf >> /dev/fd0/conf_files_checksums.md5
The above example makes the assumption that you will be saving your md5
checksum list to a floppy, and the your floppy is already mounted. If
you don't know how to mount a floppy, the following command should work:
mount -t vfat /dev/fd0 /mnt/floppy
You can also find more information on md5sum, and a more complete
example in the previous section: .
Setting the default umask
The default UMASK is the file permissions mask that establishes the
level of permissions used for creating the default permissions on files.
The mask is the "mirror image" of the actual permissions that you
want. For example, if you want files created with permissions of 755, or
-rwxr-xr-x, you would want your umask to be 022. In order to set this
globally, you will need to edit this parameter in the
/etc/bashrc file. However, the default
implementation with &FC; is fairly secure, employing the idea of what
RedHat calls "User Private Groups". So, if you want to change this
parameter, you should know exactly what you are doing and why.
To change the umask for a single session, you can use the
umask utility as shown below.
umask 0022
The above command will change the default umask to 022. (This should
already be the default and you can test this by issuing the command
umask at the command line as root.)
File System Security Summary: Where to go from here?
The actions discussed here will put you on the road to file system
security. However, you may find that there are some other things which
are handy to have to help ensure the security of your files.
One type of tool that you may want to look into is called a System
Integrity Verifier (SIV). This is a program which will scan your system
and keep track of any changes to your files, or file system, based on a
security policy that you design. Some examples of this might be Tripwire
or AIDE. You can find out more about these products at the links below.
http://sourceforge.net/projects/tripwire/http://www.cs.tut.fi/~rammer/aide.htmlSecuring User Accounts
&DRAFTNOTICE;
Disabling Unnecessary UsersDisabling unnecessary users can stop possible attacks by
limiting the avenues that an attacker can use to penetrate your system. The
procedure has already been discussed in .
Limiting root logins
There are a number of ways to limit how root can login to
your system. When making changes to your system, you must be mindful of how
root could access your system. The most secure practice is to limit root to
su logins only.
GUI: Limiting root
As alluded to in earlier sections, where GUI configurations were
discussed, as long as you are logged in as a normal user, you will be
prompted for the root password if you are attempting to administer any
system-wide services that require root access. From time to time, there
will be an application or program that does not ask for root
authentication when attempting to run. If you believe that an
application should run as root, and it does not ask for the root
password, you may be better off running it from a terminal with the
su.
CLI: Limiting root
Unfortunately, the command line isn't so forgiving. Unless you are
starting a GUI application that requires root permissions, you will not be
prompted for the root password if attempting to execute a command that
requires root permissions. You will just get a "Permission Denied"
error.
One of the easiest ways to utilize the su capability, is with the
utility called sudo.
Aside from enabling and using sudo, one of the first
things to disable is root's direct access via SSH. If
you plan not to use SSH for remote access to your system, then you can
disable SSH completely as described in . However, if you ARE planning to
use SSH, then you will want to limit direct access as root. "Direct
access" means that you login to the system as root, instead of SSH'ing as
a normal user, then su'ing to root (or using sudo, which will be discussed
later).
Unfortunately, there isn't yet a Fedora GUI tool for editing SSH
configuration. So choose your favorite editor (this may actually be a GUI
editor, but there is no specific tool for ssh configuration). Go to the
line that reads:
PermitRoot yesAnd change it to read:PermitRoot noApplication Security Note
While you are editing the sshd_config file, you
may want to disable the SSH1 protocol by changing the line that
reads:
Protocol 2,1to read:Protocol 2
This forces the client to use the SSH2 protocol, which can help to
discourage attacks that SSH1 is vulnerable to.
Then, either reboot your system, or issue the command pkill
-1 sshd. The pkill command will force
sshd to re-read it's configuration file, it will
also kill any existing connections, including your own if you're
making these changes through an ssh session. A more graceful way to
simply make sshd reread it's config file would be with the following
command:
sudo '/sbin/service sshd reload'
This will force users to login as a normal user account and then
su to root, or utilize sudo.
Verifying and Correcting System user shells
System users, such as bin, sys, nobody, lp, etc. should not have valid
shells &FC; offers the /bin/false and the
/bin/nologin shell for these users.
To verify the shells in use by your system accounts, you can use the
User Manager utility. Select System Settings->Users and
Groups. You will be prompted for the root password, if you are logged in
as a normal user. Then the utility will open. If you do not see any of
the systems users, make sure that you do not have them filtered (this is
the default behavior). Select Preferences->Filter System Users
and Groups from the menu and ensure that it is NOT checked.
Then, you can scroll through the list of users to make sure that all of
your system users have the /bin/false or
/bin/nologin shells.
There are some users which will have a special shell, like the shutdown or
halt users. These special shells can be left alone.
Password Security and PAM Configuration
Password strength and security is one of the weakest points in a
system's security posture. This is mainly because password strength
depends on us humans. One way that you can help to enforce more secure
passwords is by editing the PAM configuration. PAM stands for Pluggable
Authentication Modules, and is a good way of setting password and
authentication settings for many different services on your &FC; system.
All or most of the files that configure PAM settings for different
services are located in the /etc/pam.d/ directory.
The one that we want to focus on for increasing password strength is the
system-auth file. This file contains configuration
information for your general system authentication.
The file
/usr/share/doc/pam-0.77/txts/README.pam_cracklib
contains some information regarding the configuration options for this
file.
One option described in this file is the
minlen= option. This is the option
that specifies the minimum number of characters in a password. A
password with 7 characters, even a "strong" password, yeilds only a
maximum of [still figuring this number] character combinations, which can be cracked rather
easily by today's brute force methods. Increasing the minimum length to
8 characters ups the number of combinations to [still figuring this
number too]. Most security guides will advise a password of at least 8
characters, however, 12-16 characters is considered ",very
secure.
Other important options are the
dcredit=,
ucredit=,
lcredit=, and
ocredit= options. These options
specify how many characters should be digits, uppercase, lowercase, and
special characters, respectively. In order to ensure a strong password,
all of these options should be set to at least one.
The difok= option specifies how many
characters can be the same between the "old" password and the "new"
password when changing passwords. For example, if your old password was
password, and you had the difok=
setting set to 4, the "new" password passways would fail, whereas
pastels would succeed.
tcp_wrappers and Firewall Configurationtcp_wrappers Configurationtcp_wrappers is a method of limiting the
connections that can be made to your system - sort of like the "poor
man's firewall". tcp_wrappers will allow or
deny a connection based on the source IP address and the service that
that IP address is attempting to connect to. The version of
tcp_wrappers that comes with &FC; does not
support the "enhanced" functionality, however with a proper
implementation of iptables you can get a lot
more granular in your network defense.
The hosts.deny file.
The basic tcp_wrappers configuration consists
of two files: /etc/hosts.allow and
/etc/hosts.deny. The
hosts.deny is the easier of the two to configure.
An example is below.
# Example hosts.deny file configuration
# Deny all hosts unless specified in the allow file
ALL:ALL
As indicated by the example, the best practice is to deny all hosts
attempting to make a connection to your system, unless they are
specifically allowed in the hosts.allow file.
The hosts.allow file.
The hosts.allow file is only slightly more
complex in this implementation, than the
hosts.deny file. Let's assume for example, that
you were running a web server on your workstation and you wanted every
system in your local network to be able to connect to it, but you only
wanted to be able to manage the web server from one other
workstation. You hosts.allow file might look
something like the following:
# Example hosts.allow file configuration
# Allow every system in the local network to connect to
# the web server
httpd:10.0.0.
# Only allow the administration workstation to ssh to the
# server for configuration and administration
sshd:10.0.0.192
This would satisfy the requirements as specified above. If there was
a service that you wanted anyone and everyone to be able to connect
to, you might include a line like the following:
# Allow any system to make DNS queries
named:all
There is more information on tcp_wrappers
at the links below. They may mention features which are not
implemented in the &FC; implementation, but they will give you an idea
of how tcp_wrappers can be configured, and
its purpose.
http://www.cert.org/security-improvement/implementations/i041.07.htmlhttp://www.stanford.edu/group/itss-ccs/security/unix/tcpwrappers.htmlFirewall/IPTables Configuration
The default &FC; firewall configuration utility is
somewhat limited at this point in time. However, it should
function well enough for most home or small office users.
During the install you will be asked if you want to enable the firewall,
and what services you will want enabled (if any). If you disabled the
firewall during the install, or if you are working with a previously
installed system and are not sure whether the firewall was enabled, you
can check the security level by selecting Applications->System
Settings->Security Level. This will bring up the
system-config-securitylevel utility. This
utility will allow you to view or change the firewall settings. It will
also allow you to change the SELinux settings, however that
discussion is currently outside of the scope of this document.
If you are familiar enough with the applications that you need to allow
to your system, then you can specify specific ports in the text area
provided in the utility's dialog. The format for adding ports should
match the following:
445:tcp, 135:tcp, 137:udp, 138:udp, 139:udp
The example above would allow NetBIOS communications to your system.
The utility currently does not support entry of port ranges. So, if
your are going to use the default Fedora utility, you will need to
specify each port specifically as exemplified above.
If you have need for more granular control over your firewall, you may
consider a utility such as Firestarter. Or do some reading on the
configuration of iptables.
Conclusion
As stated in the introduction and the scope of this document, this is not
meant to be the end-all-be-all document for security, or even Fedora
security. However, it can be a guide to specific tasks that will help to
accomplish a couple of things. One, it gives you guidance on how to
accomplish specific tasks to make your Fedora system more secure. It also
can act as a guide to get you thinking about security.
To stay as secure as possible, explore tools and opportunities outside of
the Fedora utilities. This will help you to see the breadth of things
that are out there to help you secure your system. Learn, learn, learn.
As threats become more mature, so must the user. The more you read and
learn about your system and your chosen operating system, the more savvy,
and more secure as a user you will become.
Bibliography and Referenceshttp://www.tldp.org/LDP/intro-linux/html/sect_03_04.htmlhttp://www.linuxhelp.net/guides/sudo/http://www.brandonhutchinson.com/Hardening_Fedora.htmlhttp://www.linuxsecurity.com/docs/LDP/Security-HOWTO/file-security.htmlhttp://security.linux.com/security/04/09/20/1555239.shtml?tid=35http://lists.samba.org/archive/samba-technical/2002-November/025702.htmlhttp://www.puschitz.com/SecuringLinux.shtmlhttp://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam-6.html#ss6.3http://openskills.info/infobox.php?IDbox=1092&boxtype=distro
From fedora-docs-commits at redhat.com Tue May 17 01:29:54 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Mon, 16 May 2005 21:29:54 -0400
Subject: hardening/fedora-hardening-guide-whole-en.xml/hardening
fedora-hardening-guide-whole-en.xml, 1.2, NONE
Message-ID: <200505170129.j4H1TsOK023934@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/hardening/fedora-hardening-guide-whole-en.xml/hardening
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23918/fedora-hardening-guide-whole-en.xml/hardening
Removed Files:
fedora-hardening-guide-whole-en.xml
Log Message:
Brought all the files up to a top-level directory. Will reconstruct
why this happened ASAP.
--- fedora-hardening-guide-whole-en.xml DELETED ---
From fedora-docs-commits at redhat.com Tue May 17 02:02:15 2005
From: fedora-docs-commits at redhat.com (Charles Heselton (cheselto))
Date: Mon, 16 May 2005 22:02:15 -0400
Subject: hardening Makefile,NONE,1.1
Message-ID: <200505170202.j4H22FIx024946@cvs-int.fedora.redhat.com>
Author: cheselto
Update of /cvs/docs/hardening
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24936
Added Files:
Makefile
Log Message:
Added Makefile. Cleanup of local filesystem.
--- NEW FILE Makefile ---
###############################################################################
# Makefile for RHLP docs project
# Created by: Tammy Fox
# Last edited by: Tammy Fox
# WARNING: need passivetex 1.24 for pdf generation to work
# License: GPL
# Copyright 2003 Tammy Fox, Red Hat, Inc.
###############################################################################
XSLPDF = ../xsl/main-pdf.xsl
XSLHTML = ../xsl/main-html.xsl
LANG = en
#DOCNAME = fedora-hardening-guide-$(LANG)
DOCNAME = fedora-hardening-guide-$(LANG)
XMLFILE = $(DOCNAME).xml
######################################################
html:
@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
@mkdir -p $(DOCNAME)/stylesheet-images
@cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images
@cp ../css/fedora.css $(DOCNAME)
pdf-%:
@xmlto pdf -x $(XSLPDF) $(XMLFILE)
######################################################
clean:
@rm -rfv *.html *.pdf *.tex $(DOCNAME)
From fedora-docs-commits at redhat.com Tue May 17 15:51:19 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 17 May 2005 11:51:19 -0400
Subject: xsl html-common.xsl,1.5,1.6
Message-ID: <200505171551.j4HFpJZS008126@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/xsl
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8112/xsl
Modified Files:
html-common.xsl
Log Message:
Added FDP-style callout images and a usage example.
Index: html-common.xsl
===================================================================
RCS file: /cvs/docs/xsl/html-common.xsl,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- html-common.xsl 2 Oct 2003 16:33:54 -0000 1.5
+++ html-common.xsl 17 May 2005 15:51:17 -0000 1.6
@@ -11,6 +11,7 @@
./stylesheet-images/
+./stylesheet-images/
From fedora-docs-commits at redhat.com Tue May 17 15:51:19 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 17 May 2005 11:51:19 -0400
Subject: example-tutorial example-tutorial-en.xml,1.11,1.12
Message-ID: <200505171551.j4HFpJPh008133@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8112/example-tutorial
Modified Files:
example-tutorial-en.xml
Log Message:
Added FDP-style callout images and a usage example.
Index: example-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- example-tutorial-en.xml 22 Apr 2005 16:35:32 -0000 1.11
+++ example-tutorial-en.xml 17 May 2005 15:51:17 -0000 1.12
@@ -21,13 +21,13 @@
- Fox
- Tammy
+ Fox
+ Tammy
- Frields
- Paul
- W.
+ Frields
+ Paul
+ W.
&LEGALNOTICE;
@@ -88,12 +88,34 @@
Fill modes and screen tags
- Using automatic or manual fill commands in Emacs/PSGML will sometimes
- mangle screen sections. Use care when performing fill
- operations, and check the results.
+ Using automatic or manual fill commands in Emacs/PSGML will sometimes
+ mangle screen sections. Use care when performing fill
+ operations, and check the results.
+
+ Callout Example
+
+Line 1
+Line 2
+Line 3
+Line 4
+
+
+
+
+ Here is a callout.
+
+
+
+
+ The second callout.
+
+
+
+
+
From fedora-docs-commits at redhat.com Tue May 17 15:51:19 2005
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 17 May 2005 11:51:19 -0400
Subject: stylesheet-images 1.eps, NONE, 1.1 1.png, NONE, 1.1 1.svg, NONE,
1.1 10.eps, NONE, 1.1 10.png, NONE, 1.1 10.svg, NONE,
1.1 11.eps, NONE, 1.1 11.png, NONE, 1.1 11.svg, NONE,
1.1 12.eps, NONE, 1.1 12.png, NONE, 1.1 12.svg, NONE,
1.1 13.eps, NONE, 1.1 13.png, NONE, 1.1 13.svg, NONE,
1.1 14.eps, NONE, 1.1 14.png, NONE, 1.1 14.svg, NONE,
1.1 15.eps, NONE, 1.1 15.png, NONE, 1.1 15.svg, NONE,
1.1 2.eps, NONE, 1.1 2.png, NONE, 1.1 2.svg, NONE, 1.1 3.eps,
NONE, 1.1 3.png, NONE, 1.1 3.svg, NONE, 1.1 4.eps, NONE,
1.1 4.png, NONE, 1.1 4.svg, NONE, 1.1 5.eps, NONE, 1.1 5.png,
NONE, 1.1 5.svg, NONE, 1.1 6.eps, NONE, 1.1 6.png, NONE,
1.1 6.svg, NONE, 1.1 7.eps, NONE, 1.1 7.png, NONE, 1.1 7.svg,
NONE, 1.1 8.eps, NONE, 1.1 8.png, NONE, 1.1 8.svg, NONE,
1.1 9.eps, NONE, 1.1 9.png, NONE, 1.1 9.svg, NONE,
1.1 callout.svg, NONE, 1.1 LICENSE, 1.2, 1.3
Message-ID: <200505171551.j4HFpJ2l008129@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/stylesheet-images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8112/stylesheet-images
Modified Files:
LICENSE
Added Files:
1.eps 1.png 1.svg 10.eps 10.png 10.svg 11.eps 11.png 11.svg
12.eps 12.png 12.svg 13.eps 13.png 13.svg 14.eps 14.png 14.svg
15.eps 15.png 15.svg 2.eps 2.png 2.svg 3.eps 3.png 3.svg 4.eps
4.png 4.svg 5.eps 5.png 5.svg 6.eps 6.png 6.svg 7.eps 7.png
7.svg 8.eps 8.png 8.svg 9.eps 9.png 9.svg callout.svg
Log Message:
Added FDP-style callout images and a usage example.
--- NEW FILE 1.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoKf)5 at D#e?S.XK&2"\(po]$g*nZXf\\)Vkp,Zd/EucR&d?k^[nJ&US+0I
mJm3pW3!)&f^Yu=U7RjAXoJmWqE6aSsbk-NlJr0
USO``VY$XUR[0+uNP<9$TV8'RU at b%HQBRAhN4mB%S"-%?SF`,5P)bN]N6'VNQBml'
rpgP[NJrgSVU5 at LPEM)kOH9C#'8qd+[I!qJRu`ShNK/sUMi*Fpa8Z)If:%\YN/NXQ
Mi+XJr;HX&n#M\1MMm at g[)`+ at rs%l1]Y);4m/?q
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 1.svg ---
--- NEW FILE 10.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoJebo7C#e?S.X/`)"\D7#^$g!hYXf\\)Vkp)Xd/EtgR(`*nXfSP+hqFlq
mJm3qW7CF?XfSP]`5:)mXoJN6'YOQi?S)
Q'IN!c-)3,VU>FLPEM&jOH,<[MiuBf9qSWMi3Jl
MZU#nr;HX&n#V\0Mi*@e[)`+ at rs%i/]Y)83m/?q
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 10.svg ---
--- NEW FILE 11.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoKebo7C#e?S.XK&2#\D7#^$g*nZXf\\)Vkp)Yd/EtgR(`*oXfSP5n"?5@
mJm3pW7CF?XfSPMl^jT5XoJ7Qg2niVPj+dW_0.`oU1u-NlJr/
U87FYVl$5]o9GK#NP<<$StP_MTqJ!Gnrf&nN4mE%S"'#>S=5h1nrA]hN6'YOQh0e=
Q'@I&naVQrVU5 at KPQ$^^OH,
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 11.svg ---
--- NEW FILE 12.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoKf)5 at D#e?S.XK&2"\(po]$g*nZXf\\)Vkp,Zd/EtgR(`*oXfSP;g#0<.
mJm3pW7CF?XfSPUV6KQXXoJS=5i.SW<].$-:c!Qh0e=
Q'IO3nHSK at V:#=KPQ$^HOcPM$N"V&+[-[hHRZEJgN/`aSMMd=oa8Z)Cf9qSVMi3Jl
MZU#nr;HX&n#V\0Mi3Fg[)`+ at rs%i/]Y);4m/?q
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 12.svg ---
--- NEW FILE 13.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)ElJebo7C#e?S.XK&2"\D@)_$g*nZXf\\)Vk]rVd/EtgR(`*oXfSPqo^/uS
mJm3qW7CF?XfSP"U8RUMXoJFLrK75DNfF$s#`FSHm/Ph0O,j4!!Kr=crVl
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 13.svg ---
--- NEW FILE 14.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoKf)5 at D#e?P,X/`)"\(po]$g!hYXf\\)Vkp&Wd/EtgR(`*nXfSP"Z1OTV
mJm3pWRgUAXfSP#o^nW?XoJFMPEM&iNfK*ZMi]Z8FdrVl
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 14.svg ---
--- NEW FILE 15.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)FLP*1riOH,<\N/W[PZg at _HRu`ShN/`epMZKs"rr32RRZ*2`Mi.Ll
!j0-5rVm5nXHJI!MM\.9a8Gf6#40=A]Z8FdrVl
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 15.svg ---
--- NEW FILE 2.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoKf)5 at D#e?S.XK&2"\)$u^$g*nZXf\\)Vkp,Yd/EtgR&dhNP3K&S"#q=lDBr6P)bN^N6'YOrg!PL
rUKrJreq2\dJpP;PEM&iNfF$s%?$+Nm/Ph0O,f3ZN/`bpM?0j"rr32RRZ3;cMi at Xm
!j0-5rVm5nX-AL"MMe7<`r,]5#49FA]#N+`rVl
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 2.svg ---
--- NEW FILE 3.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)mWqH"`T:(t-NlJr0
U8.[aR^;1 at NfK*WaOdGWQ'R^+
o'E-3Nf/gmdJpP:P*1rhNfB!WN/EM"m/Ph0O,f3ZNf/gSMMeLUrr32SRZ3;cMi7Rl
!j0'3rVm5nX-AL"Mi+=
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 3.svg ---
--- NEW FILE 4.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)XoJ
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 4.svg ---
--- NEW FILE 5.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)FMP`q8mOH,
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 5.svg ---
--- NEW FILE 6.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)mo"ae-T:(t-NlJr/
U8+T_oWkjrS!K4tN5!0#T:hmPoUqfIQBR>gNP3K&S"#qDKZ]pZ:P)t]`reqJIMR;aMgR=1`NK&mVMi3IMXN1>?%+^l,NJi^R
Mi3Ip]);O,$Lb$[Mi*FLUp\8 at qYpcd`4Wb'dHpi3
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 6.svg ---
--- NEW FILE 7.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoJf)5 at D#e?S.XK&2"\(po]$g*nZXf\\)Vkp,Zd/EtIR&d?lpAX_FUS+0I
mJm3pW2m#%XfSnpU7RjAXoJmWjgr^T:(t.NlJr/
USIgc.dO4/S!K5!NP<9#T:_dMZfn!LQBRAhN4mB%S=?"
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 7.svg ---
--- NEW FILE 8.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoKebo7C#e?S.XK&2#\(po]$g*nZXf\\)Vkp&Xd/EunR&d"kK-%NJibp
MZ\j=]DVX-$Lb$[Mi3ILUp\8 at qYpcd`4Wb'dHpi3
~>
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 8.svg ---
--- NEW FILE 9.eps ---
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 16 16
%
% created by bmeps 1.0.9 (SCCS=1.70)
%
/pstr
16 string
def
/inputf
currentfile
/ASCII85Decode filter
/RunLengthDecode filter
def
gsave
0 16 translate
16 16 scale
16 16 8 [16 0 0 -16 0 0]
{ inputf pstr readstring pop }
image
r;R!"d)EoKebo7C#e?S.XK&5$\D@)_$g*nZXf\\)W2-,Xd/EuQR&d?l]]A(VUS+0I
mJm3qW2m#%otA9)URmp at XoJ
grestore
currentdict /inputf undef
currentdict /pstr undef
--- NEW FILE 9.svg ---
--- NEW FILE callout.svg ---
Index: LICENSE
===================================================================
RCS file: /cvs/docs/stylesheet-images/LICENSE,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LICENSE 1 Oct 2003 19:03:33 -0000 1.2
+++ LICENSE 17 May 2005 15:51:17 -0000 1.3
@@ -2,3 +2,6 @@
caution, and warning). They may be freely redistributed with Red Hat
and Fedora Project documentation.
+Tommy Reynolds created the callout
+digit graphics. They may be freely redistributed with the Fedora
+Project documentation.
From fedora-docs-commits at redhat.com Tue May 17 22:32:28 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 17 May 2005 18:32:28 -0400
Subject: install-guide fedora-install-guide-intro-en.xml, 1.7,
1.8 fedora-install-guide-networkconfig-en.xml, 1.9, 1.10
Message-ID: <200505172232.j4HMWS8S016944@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16935
Modified Files:
fedora-install-guide-intro-en.xml
fedora-install-guide-networkconfig-en.xml
Log Message:
Remove/reduce unnecessary text; move network stuff to logical place
Index: fedora-install-guide-intro-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-intro-en.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-intro-en.xml 16 May 2005 20:57:32 -0000 1.7
+++ fedora-install-guide-intro-en.xml 17 May 2005 22:32:26 -0000 1.8
@@ -21,33 +21,12 @@
This manual helps you to install &FC; on desktops, laptops and
servers. The installation system is flexible enough to use even if
- you have no previous knowledge of Linux or computer networks. Even
- if you only select default options, &FC; provides a complete desktop
- operating system, including:
+ you have no previous knowledge of Linux or computer networks. If
+ you select default options, &FC; provides a complete desktop
+ operating system, including productivity applications, Internet
+ utilities, and desktop tools.
-
-
-
- full-featured productivity applications such as a word
- processor, spreadsheet manager, and presentation manager
-
-
-
-
- Internet utilities such as a Web browser, email client, Internet
- Relay Chat client, and instant messaging client
-
-
-
-
- desktop tools to catalog and edit digital photographs, create
- sophisticated computer graphics, create and copy compact discs,
- and play media files
-
-
-
-
This document does not detail all of the features of the
installation system.
-
@@ -248,16 +224,16 @@
PXE (also referred to as netboot) is a
standard that enables PCs to use files on a server as a boot
device. &FC; includes utilities that allow it to function as a
- PXE server for other computers.
+ PXE server for other computers.
- Booting your computer is explained in the next section, .
+ Booting your computer is explained in the next section, .
-
+
Installing &FC; on a Managed Network
Index: fedora-install-guide-networkconfig-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-networkconfig-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-networkconfig-en.xml 14 May 2005 21:57:38 -0000 1.9
+++ fedora-install-guide-networkconfig-en.xml 17 May 2005 22:32:26 -0000 1.10
@@ -68,6 +68,13 @@
+ If your computer will be acting as a server, do not use DHCP.
+ Manually configure networking instead. A manual network
+ configuration assures that your server will join the local network
+ even if the DHCP provider is down.
+
+
+
Specify whether an interface should be automatically activated at
boot time with the Active on Boot checkbox
for that device. You may manually activate a network interfaces at
From fedora-docs-commits at redhat.com Wed May 18 02:00:42 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 17 May 2005 22:00:42 -0400
Subject: mirror-tutorial mirror-tutorial-en.xml,1.1,1.2
Message-ID: <200505180200.j4I20gUx020005@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19997
Modified Files:
mirror-tutorial-en.xml
Log Message:
Doesn't look like I did anything, but I actually removed a control character breaking the build
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mirror-tutorial-en.xml 5 May 2005 19:04:44 -0000 1.1
+++ mirror-tutorial-en.xml 18 May 2005 02:00:40 -0000 1.2
@@ -450,7 +450,7 @@
users to interpret data created when a program crashes or
encounters a bug. If you participate actively in &FED;
development, you should not trim these folders. If you trim this
- branch, you may still download individual packages on an
+ branch, you may still download individual packages on an ad hoc
basis from a nearby public mirror site.
+ To boot with
+ PXE (Pre-boot eXecution Environment)
+ PXE, you need a properly configured server, and a
+ network interface in your computer that supports PXE.
Configure the computer to boot from the network interface. This
option is in the BIOS, and may be labeled or . Once you
- properly configure PXE booting, the computer can boot into the
- &FED; installation system without any other media.
+ properly configure PXE booting, the computer can boot the &FED;
+ installation system without any other media.
-
- PXE Troubleshooting
-
- If your PC does not boot from the netboot server, ensure that
- the BIOS is configured to boot first from the correct network
- interface. Some BIOS systems specify the network interface as a
- possible boot device, but do not support the PXE standard.
- Refer to your hardware documentation for more information.
-
-
-
To boot a computer from a PXE server:
@@ -433,6 +424,13 @@
+ Ensure that the network cable is attached. The link indicator
+ light on the network socket should be lit, even if the
+ computer is not switched on.
+
+
+
+
Switch on the computer.
@@ -465,6 +463,17 @@
Choose a network installation option to continue.
+
+ PXE Troubleshooting
+
+ If your PC does not boot from the netboot server, ensure that
+ the BIOS is configured to boot first from the correct network
+ interface. Some BIOS systems specify the network interface as a
+ possible boot device, but do not support the PXE standard.
+ Refer to your hardware documentation for more information.
+
+
+
From fedora-docs-commits at redhat.com Wed May 18 22:02:25 2005
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 18 May 2005 18:02:25 -0400
Subject: release-notes fc4-relnotes,NONE,1.1
Message-ID: <200505182202.j4IM2PrZ011538@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11531
Added Files:
fc4-relnotes
Log Message:
Plain text version of FC4 notes-in-progress, being posted on f.r.c/docs/beta for developer perusal.
--- NEW FILE fc4-relnotes ---
= Fedora Core 4 Release Notes =
Copyright (c) 2005 Red Hat, Inc.
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
[1]http://www.gnu.org/licenses/fdl.html.
This document may be copied and distributed in any medium, either
commercially or non-commercially, 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.
Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum
RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based
trademarks and logos are trademarks or registered trademarks of Red
Hat, Inc. in the United States and other countries.
The Fedora trademark is a trademark of Red Hat, Inc. in the United
States and other countries.
Linux is a registered trademark of Linus Torvalds.
All other trademarks and copyrights referred to are the property of
their respective owners.
The GPG fingerprint of the "Fedora Project " key is:
CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
---------------------------------------------------------------------------
1. Fedora Core 4 Release Notes
2. Introduction
3. Hardware Requirements
1. CPU Requirements
2. Hard Disk Space Requirements
3. Memory Requirements
4. Overview of This Release
5. Installation-Related Notes
6. Installation-Related Issues
7. Package-Specific Notes
1. Base
2. Core
3. Language Support
4. Server Configuration Tools
5. Sound and Video
6. Web Server
7. Windows File Server
8. Macintosh File Server
9. X Window System
10. Miscellaneous Notes
8. Packages Added, Moved From Core, Changed, or Deprecated/Nuked
1. Packages Added
2. Packages Moved Out Of Core
9. An Overview of the Fedora Project
10. References
== Introduction ==
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, a complete, general-purpose operating system built
exclusively from open source software.
NOTE: Fedora Core is not a supported product of Red Hat, Inc.
For more information, refer to the Fedora Project overview later in
this document.
The following topics related to Fedora Core 4 are covered in this
document:
* Introduction (this section)
* Hardware requirements
* Overview of this release
* Installation-related notes
* Package-specific notes
* Packages added/removed/deprecated
* An overview of the Fedora Project
== Hardware Requirements ==
The following information represents the minimum hardware requirements
necessary to successfully install Fedora Core 4.
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.
=== CPU Requirements ===
This section lists the CPU specifications required by Fedora Core
4.
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.
* Minimum: Pentium-class
Fedora Core 4 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.
* Recommended for text-mode: 200 MHz Pentium-class or better
* Recommended for graphical: 400 MHz Pentium II or better
=== Hard Disk Space Requirements ===
This section lists the disk space required to install Fedora Core 4.
Note
The disk space requirements listed below represent the disk space
taken up by Fedora Core 4 after the installation is
complete. However, additional disk space is required during the
installation to support the installation environment. This
additional disk space corresponds to the size of
/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.
* Custom Installation (Minimal): 620MB
* Server: 1.1GB
* Personal Desktop: 2.3GB
* Workstation: 3.0GB
* Custom Installation (Everything): 6.9GB
=== Memory Requirements ===
This section lists the memory required to install Fedora Core 4.
* Minimum for text-mode: 64MB
* Minimum for graphical: 192MB
* Recommended for graphical: 256MB
== Overview of This Release ==
The following list highlights certain new features of Fedora Core 4:
* GCC 4.0
* GNOME 2.10
* KDE 3.4
* Native Eclipse 3.1M6 - Part of free Java stack
* MySQL 4.1
* PHP 5.0
* Xen 2 - Virtualization to run multiple versions of an OS
* GFS 6.1-0.pre22 - Cluster file system
* Evince 0.2.1 - Universal document viewer
* GDM 2.6 - Includes early login capability
* SELinux -- New daemons have been added to the targeted policy.
http://fedora.redhat.com/docs/selinux-faq/ . This is a list of
daemons protected by the targeted policy:
* NetworkManager
* amanda
* apache
* apmd
* arpwatch
* auditd
* bluetooth
* canna
* cardmgr
* checkpolicy
* chkpwd
* compat
* comsat
* consoletype
* cpucontrol
* cpuspeed
* crond
* cups
* cvs
* cyrus
* dbskkd
* dbusd
* dhcpc
* dhcpd
* dictd
* dmidecode
* dovecot
* fingerd
* fsadm
* ftpd
* getty
* hald
* hostname
* hotplug
* howl
* hwclock
* i18n_input
* ifconfig
* inetd
* init
* initrc
* innd
* kerberos
* klogd
* ktalkd
* kudzu
* ldconfig
* load_policy
* login
* lpd
* mailman
* modutil
* mta
* mysqld
* named
* netutils
* nscd
* ntpd
* portmap
* postgresql
* pppd
* privoxy
* radius
* radvd
* restorecon
* rlogind
* rpcd
* rpm
* rshd
* rsync
* samba
* saslauthd
* sendmail
* setfiles
* slapd
* snmpd
* squid
* ssh
* stunnel
* syslogd
* telnetd
* tftpd
* udev
* updfstab
* uucpd
* webalizer
* winbind
* xdm
* ypbind
* ypserv
* zebra
== Installation-Related Notes ==
This section outlines anything noteworthy that is related to Anaconda
(the Fedora Core installation program) and installing Fedora Core
4 in general.
Note
If you intend to download the Fedora Core 4 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.
Anaconda Notes
* 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.
* 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.
* Fedora Core 4 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.
== Installation-Related Issues ==
* 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.
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.
* 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.
* 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:
[6]http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
* There have been issues observed when upgrading Red Hat Linux
7., 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The
issue 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 issue:
1) You may remove Ximian GNOME from your system prior to upgrading
to Fedora Core.
2) You may upgrade your system, and then immediately reinstall
Ximian GNOME.
3) 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.
== Package-Specific Notes ==
The following sections contain information regarding packages that
have undergone significant changes for Fedora Core 4. For easier
access, they are organized using the same groups used in Anaconda.
=== Base ===
This section contains information related to basic system components.
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'
LinuxThreads v. NPTL
As the next step in removing support for the obsolete LinuxThreads
library, code compiled and linked on FC4 now automatically uses the NPTL
headers and libraries.
In previous releases, since Red Hat Linux 9, the default was to use
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 FC4 it is still possible to create code using the LinuxThreads
definitions. For this the linuxthreads-devel package must be
installed and
-I/usr/include/linuxthreads -L/usr/lib{,64}/linuxthreads
must be passed to the compiler.
At runtime, it used to be possible to use the LD_ASSUME_KERNEL
environment variable to select the appropriate version of glibc and the
libpthread DSO. Now it is additionally necessary to specify
LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads
in the environment. This is because the runtime libraries have also
been moved out of the way. There might 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.
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.
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.
openssh
The version of OpenSSH in Fedora Core 4 contains OpenSSH 3.9
includes strict permission and ownership checks for the ~/.ssh/config
file. These checks mean that ssh will exit if this file does not have
appropriate ownership and permissions.
Therefore, make sure that ~/.ssh/config is owned by the owner of ~/,
and that its permissions are set to mode 600.
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 flag 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 flag instead of the -X flag,
or set ForwardX11Trusted in the ~/.ssh/config file.
=== Core ===
This section contains the most elemental components of Fedora Core,
including the kernel.
yum
The sqllite database is now used by yum, and makes performance
noticeably faster.
The Fedora Extras repository is now enabled by default.
kernel source
In order to eliminate the redundancy inherent in providing a separate
package for the kernel source code when that source code already
exists in the kernel's .src.rpm file, Fedora Core 4 no longer
includes the kernel-source package. Users that require access to the
kernel sources can find them in the kernel .src.rpm file. To create an
exploded source tree from this file, perform the following steps (note
that refers to the version specification for your
currently-running kernel):
1. Obtain the kernel-.src.rpm file from one of the
following sources:
* The SRPMS directory on the appropriate "SRPMS" CD iso image
* The FTP site where you got the kernel package
* By running the following command:
up2date --get-source kernel
2. Install kernel-.src.rpm (given the default RPM
configuration, the files this package contains will be written to
/usr/src/redhat/)
rpm -ivh kernel-.src.rpm
3. Change directory to /usr/src/redhat/SPECS/, and issue the
following command:
rpmbuild -bp --target= kernel.spec
(Where is the desired target architecture.)
On a default RPM configuration, the kernel tree will be located
in /usr/src/redhat/BUILD/.
4. In resulting tree, the configurations for the specific kernels
shipped in Fedora Core 4 are in the /configs/
directory. For example, the i686 SMP configuration file is named
/configs/kernel--i686-smp.config. Issue the following
command to place the desired configuration file in the proper
place for building:
cp ./.config
5. Issue the following command:
make oldconfig
You can then proceed as usual.
Note
An exploded source tree is not required to build kernel modules
against the currently in-use kernel.
For example, to build the foo.ko module, create the following file
(named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
Issue the make command to build the foo.ko module.
=== Language Support ===
This section includes information related to the support of various
languages under Fedora Core.
=== Server Configuration Tools ===
This section contains information related to various server
configuration tools.
=== Sound and Video ===
This section contains information related to multimedia applications.
=== Web Server ===
This section contains information related to Web-related tools.
mod_perl
The "RC5" release of mod_perl 2.0 is now included; the API provided by
this release is incompatible with previous 1.99_xx releases. Please
refer to the following document for discussion of how to adapt code to
use the new API:
http://perl.apache.org/docs/2.0/rename.html
php
Version 5.0 of PHP is now included, which includes a number of changes
to the language along with significant performance improvements.
Please refer to the PHP documentation for more information on
migrating from PHP 4.3 to PHP 5.0:
http://www.php.net/manual/en/migration5.php
The /usr/bin/php binary is now built using the "CLI" command-line
SAPI, rather than the CGI SAPI. The CGI SAPI is now available as
/usr/bin/php-cgi; this binary also includes FastCGI support.
The following extensions have been added:
* the "mysqli" extension, the newly MySQL interface designed
specifically for MySQL 4; included in the php-mysql
* the "soap" extension, which can be used to implement a SOAP server
or client
The following extensions are now available as optional loadable
extensions, rather than being built in to the php binaries:
* dba, now available in the php-dba package
* bcmath, now available in the php-bcmath package
=== Windows File Server ===
This section contains information related to Samba, software that
makes it possible to share files between Linux and Windows systems.
samba
Browsing of Windows shares (also known as SMB browsing) fails on
Fedora Core 4 systems that have the standard firewall
configured. This is most easily noticed in the failure of Nautilus to
display shares. The failure is due to the firewall disrupting the
broadcast mode of SMB browsing, which is Samba's default
setting. There are two workarounds:
* Configure a WINS server on the network, and set the "wins server"
option in smb.conf to the address of the WINS server.
* Disable the firewall
Warning
Depending on your system and network configurations, disabling the
firewall can greatly increase the chance of your system being attacked
and compromised. Make sure you fully understand the risks before
undertaking this step.
For additional information, refer to the following bug report:
[8]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
=== Macintosh File Server ===
This section contains information related to netatalk, software that
makes it possible to share files between Linux and Macintosh systems.
netatalk
The 2.x version of netatalk uses a different method to store resource
forks, and may use a different file name encoding scheme. Upgrading to
Fedora Core 4 may result in data loss. Please read the documentation of
the netatalk 1.x to 2.x upgrade before upgrading to Fedora Core 4.
The netatalk upgrade information is available directly from the
netatalk site:
http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html
It is also included in the netatalk installation for Fedora Core 4, the
files are at:
/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf - numbered page
25, document page 33.
or
/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html
=== X Window System ===
This section contains information related to the X Window System
implementation provided with Fedora Core.
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 Red Hat operating systems. In
particular, the names of some files have changed:
X Server Binary:
* XFree86 X11: XFree86
* X.org X11: Xorg
X Server Configuration File:
* XFree86 X11: /etc/X11/XF86Config
* X.org X11: /etc/X11/xorg.conf
X Server Log File
* XFree86 X11: /var/log/XFree86.$DISPLAY.log
* 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:
- 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 like:
-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 like:
Luxi Sans-10
* Over time, fontconfig/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.
NOTE: An exception to the font subsystem usage outlined above is
OpenOffice.org (which uses its own font rendering technology).
If you wish to add new fonts to your Fedora Core 4 system, you
must be aware that the steps necessary depend on which font subsystem
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 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/fonts.scale
mkfontdir /usr/share/fonts/local/
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
(Where 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 = ""
}
widget_class " *" style "user-font"
(Where represents a font specification in the
style used by traditional X applications, such as
"-adobe-helvetica-medium-r-normal-- *-120- *- *- *- *- *- *".)
=== Miscellaneous Notes ===
This section contains information related to packages that do not fit
in any of the proceeding categories.
OpenOffice and upgrading test releases
If you choose to go counter to the recommendation to *not* upgrade
from a previous test release, you may encounter a problem with
OpenOffice following the upgrade.
To resolve this, you must do the following command *before* doing the
upgrade:
rm -rf /usr/lib/openoffice.org*/share/template/*/wizard/bitmap
== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
For an overview of orphaned packages, visit
[:Extras/OrphanedPackages:this list].
This section contains lists of packages that fit into the following
categories:
* Packages that have been added to Fedora Core 4
* Packages that have been moved out of Fedora Core 4
* Packages that have a changed version since Fedora Core 3
* Packages that have been deprecated, and may be removed from a
future release of Fedora Core
=== Packages Added ===
The following packages have been added to Fedora Core 4. This is
based on a treediff of dist-fc3 and dist-fc4 on 04-MAY-2005:
* ant-1.6.2-3jpp_5fc
* antlr-2.7.4-2jpp_1fc
* aqbanking-1.0.4beta-2
* aqhbci-1.0.2beta-2
* aspell-is-0.51.1-1
* avalon-framework-4.1.4-2jpp_5fc
* avalon-logkit-1.2-2jpp_4fc
* bcel-5.1-1jpp_4fc
* ccs-0.25-0.1
* classpathx-jaf-1.0-2jpp_3fc
* classpathx-mail-1.0-3jpp_1fc
* cman-1.0-0.pre33.2
* cman-kernel-2.6.11.3-20050425.154843.FC4.5
* compat-gcc-296-2.96-132.fc4
* compat-gcc-32-3.2.3-47.fc4
* compat-readline43-4.3-2
* cpufreq-utils-0.2-1.1.14
* cpuspeed-1.2.1-1.20
* cryptix-3.2.0-4jpp_1fc
* cryptix-asn1-20011119-4jpp_1fc
* cryptsetup-luks-1.0-1
* dcraw-0.0.20050227-1
* device-mapper-multipath-0.4.4-2.0
* dlm-1.0-0.pre21.2
* dlm-kernel-2.6.11.3-20050425.154843.FC4.6
* dmidecode-2.6-1.14
* eclipse-3.1.0_fc-0.M6.14
* eclipse-bugzilla-0.1.0_fc-14
* eclipse-cdt-3.0.0_fc-0.M6.5
* eclipse-changelog-2.0.1_fc-21
* eclipse-pydev-0.9.3_fc-7
* evince-0.2.1-1
* fence-1.27-1
* fonts-chinese-2.15-2
* fonts-indic-1.9-2
* fonts-japanese-0.20050222-3
* fonts-korean-1.0.11-4
* GFS-6.1-0.pre22.1
* GFS-kernel-2.6.11.4-20050503.144108.FC4.1
* gjdoc-0.7.4-4
* gnbd-1.0-0.pre13.1
* gnbd-kernel-2.6.11.2-20050420.133124.FC4.10
* gnome-doc-utils-0.2.0-2
* gnome-menus-2.10.1-3
* gnome-python2-extras-2.10.0-2.1
* gnu-crypto-2.0.1-1jpp_3fc
* gnu.getopt-1.0.9-4jpp_1fc
* gulm-1.0-0.pre28.3
* gwenhywfar-1.7.2-2
* hardlink-1.0-1.13
* iddev-1.9-19
* iiimf-12.2-0.7.svn2578
* ipv6calc-0.48-5
* irqbalance-1.12-1.18
* jakarta-commons-beanutils-1.7.0-1jpp_1fc
* jakarta-commons-collections-3.1-1jpp_1fc
* jakarta-commons-daemon-1.0-2jpp_1fc
* jakarta-commons-dbcp-1.2.1-3jpp_1fc
* jakarta-commons-digester-1.6-2jpp_1fc
* jakarta-commons-el-1.0-2jpp_1fc
* jakarta-commons-fileupload-1.0-3jpp_1fc
* jakarta-commons-lang-2.0-2jpp_1fc
* jakarta-commons-launcher-0.9-3jpp_1fc
* jakarta-commons-logging-1.0.4-2jpp_1fc
* jakarta-commons-modeler-1.1-3jpp_1fc
* jakarta-commons-pool-1.2-2jpp_1fc
* jakarta-commons-validator-1.1.3-1jpp_1fc
* jakarta-taglibs-standard-1.1.1-4jpp_1fc
* java_cup-0.10-0.k.1jpp_2fc
* jdepend-2.6-2jpp_3fc
* jessie-1.0.0-6
* jlex-1.2.6-1jpp_2fc
* jsch-0.1.18-1jpp_1fc
* junit-3.8.1-3jpp_4fc
* jzlib-1.0.5-2jpp_1fc
* kdeaccessibility-3.4.0-1
* ksh-20050202-1
* latex2html-2002.2.1-1
* ldapjdk-4.17-1jpp_2fc
* libdbi-drivers-0.7.1-3
* libgconf-java-2.10.1-1
* libglade-java-2.10.1-3
* libgnome-java-2.10.1-1
* libgtk-java-2.6.2-1
* linux-atm-2.5.0-0.20050118.2
* lksctp-tools-1.0.2-5
* log4j-1.2.8-7jpp_3fc
* longrun-0.9-1.9
* lvm2-cluster-2.01.09-2.1
* magma-1.0-0.pre21.4
* magma-plugins-1.0-0.pre16.11
* mcelog-0.4-1.8
* microcode_ctl-1.11-1.21
* mod_jk-1.2.6-3jpp_2fc
* mx4j-2.1.0-1jpp_5fc
* mysqlclient10-3.23.58-6
* openhpi-2.0.3-2
* OpenIPMI-1.4.11-5
* openssl097a-0.9.7a-2
* oro-2.0.8-1jpp_2fc
* perl-Archive-Zip-1.14-1
* perl-Carp-Clan-5.3-1
* perl-IO-String-1.06-3
* perl-IO-Zlib-1.04-4
* perl-Net-Telnet-3.03-4
* pm-utils-0.01-1
* poppler-0.3.0-2
* puretls-0.9-0.b4.1jpp_2fc
* python-docs-2.4.1-1
* python-elementtree-1.2.6-4
* python-numeric-23.7-2
* python-sqlite-1.1.6-1
* python-twisted-1.3.0-4
* python-urlgrabber-2.9.6-1
* readahead-1.0-1.7
* regexp-1.3-1jpp_4fc
* rgmanager-1.9.31-0
* rng-utils-2.0-1.6
* salinfo-0.5-1.4
* slib-3a1-2
* smartmontools-5.33-1.5
* sqlite-3.1.2-3
* struts11-1.1-1jpp_4fc
* system-config-lvm-0.9.25-1.0
* texi2html-1.76-2
* tomcat5-5.0.30-5jpp_1fc
* x86info-1.13-1.10
* xalan-j2-2.6.0-2jpp_1fc
* xen-2-20050424
* xerces-j2-2.6.2-4jpp_4fc
* xml-commons-1.0-0.b2.6jpp_10fc
* xml-commons-resolver-1.1-1jpp_4fc
=== Packages Moved Out Of Core ===
This is a new section to the release notes. This is based on a
treediff of dist-fc3 and dist-fc4 on 04-MAY-2005. The following
packages have been moved out of core from Fedora Core 4:
* abiword-2.0.12-3
* aiksaurus-1.2.1-2
* ash-0.3.8-20
* asp2php-0.76.18-3
* aspell-ia-0.50-1
* aumix-2.8-9
* balsa-2.2.4-1.FC3.1
* bluez-bluefw-1.0-6
* bonobo-1.0.22-9
* bzflag-1.10.6-2
* cdecl-2.5-30
* cdlabelgen-3.0.0-1
* cdp-0.33-32
* compat-gcc-8-3.3.4.2
* compat-pwdb-0.62-9
* comsat-0.17-11
* cproto-4.7c-3
* cryptsetup-0.1-4
* cyrus-imapd-2.2.6-2.FC3.6
* dbh-1.0.18-5
* dbskkd-cdb-1.01-21
* ddskk-12.2.0-4
* dietlibc-0.27-4
* diskcheck-1.6-2
* dmalloc-5.3.0-3
* exim-4.43-1
* flim-1.14.7-1
* fonts-bengali-0.1-3
* fonts-ja-8.0-16
* freeciv-1.14.2-1
* FreeWnn-1.10pl020-5
* fsh-1.2-5
* ftpcopy-0.6.2-7
* gcc4-4.0.0-0.8
* ggv-2.8.0-1
* giftrans-1.12.2-20
* Glide3-20010520-33
* gnome-vfs-1.0.5-21
* gnome-vfs-extras-0.2.0-9
* gnuchess-5.07-4
* gnumeric-1.2.13-6
* gpdf-2.8.0-5
* grip-3.2.0-3
* gv-3.5.8-29
* im-sdk-12.1-4
* jcode.pl-2.13-11
* jed-0.99.16-6
* jisksp14-0.1-16
* jisksp16-1990-0.1-16
* kappa20-0.3-15
* katana-2.0.0-1
* kdetoys-3.3.0-1
* kernel-utils-2.4-13.1.39
* kinput2-v3.1-23
* knm_new-1.1-16
* koffice-1.3.3-1
* lapack-3.0-25
* lesstif-0.93.36-6
* libesmtp-1.0.3r1-2
* libgda-1.0.4-3
* libgnomedb-1.0.4-3
* libtool-libs13-1.3.5-10
* libxfce4mcs-4.0.6-1
* libxfce4util-4.0.6-1
* libxfcegui4-4.0.6-1
* lilo-21.4.4-26
* Maelstrom-3.0.6-6
* MagicPoint-1.11b-1
* memprof-0.5.1-5
* mew-3.3-4
* miniChinput-0.0.3-58
* nabi-0.14-3
* namazu-2.0.13-3
* nautilus-media-0.8.1-3
* ncftp-3.1.8-2
* nedit-5.4-3
* octave-2.1.57-7
* Omni-0.9.1-7
* openhbci-0.9.17-1
* openssl096b-0.9.6b-19
* ots-0.4.2-2
* pan-0.14.2-8
* pccts-1.33mr33-11
* pdksh-5.2.14-30
* qmkbootdisk-1.0.2-3
* Regina-2.3-1
* routed-0.17-18
* skkinput-2.06.4-7
* splint-3.1.1-4
* sylpheed-0.9.12-1
* system-logviewer-0.9.11-1
* system-switch-im-0.1.2-3
* THE-3.1-2
* tora-1.3.14.1-2
* ttfonts-indic-1.6-1
* ttfonts-ja-1.2-36
* ttfonts-ko-1.0.11-32.2
* ttfonts-zh_CN-2.14-10
* ttfonts-zh_TW-2.11-28
* ttfprint-0.9-13
* tuxracer-0.61-28
* w3m-el-1.4.3-2
* wl-2.10.1-4
* x3270-3.3.2.p1-6
* xboard-4.2.7-6
* xcin-2.5.3.pre3-24
* xemacs-21.4.15-9
* xemacs-sumo-20040818-2
* xfce4-iconbox-4.0.6-2
* xfce4-panel-4.0.6-1
* xfce4-systray-4.0.6-2
* xfce-mcs-manager-4.0.6-2
* xfce-mcs-plugins-4.0.6-2
* xfce-utils-4.0.6-1
* xfdesktop-4.0.6-2
* xffm-4.0.6-1
* xffm-icons-4.0.6-2
* xfprint-4.0.6-2
* xfwm4-4.0.6-1
* xfwm4-themes-4.0.6-2
* xloadimage-4.1-32
* xmms-1.2.10-9
* xosview-1.8.2-1
* xsnow-1.42-15
* ytalk-3.1.2-1
== An Overview of the Fedora Project ==
The goal of the Fedora Project is to work with the Linux community to
build a complete, general purpose operating system exclusively from
open source software. Development will be done in a public forum. The
project will produce time-based releases of Fedora Core about 2-3
times a year, with a public release schedule. The Red Hat engineering
team will continue to participate in building Fedora Core and will
invite and encourage more outside participation than was possible in
the past. By using this more open process, we hope to provide an
operating system more in line with the ideals of free software and
more appealing to the open source community.
For more information, refer to the Fedora Project website:
[10]http://fedora.redhat.com/
In addition to the website, the following mailing lists are available:
* fedora-list at redhat.com -- For users of Fedora Core releases
* fedora-test-list at redhat.com -- For testers of Fedora Core test releases
* fedora-devel-list at redhat.com -- For developers, developers, developers
* fedora-docs-list at redhat.com -- For participants of the docs project
To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to -request (where is
one of the above list names.)
NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
rhl-devel-list, or rhl-docs-list, your subscriptions have been
retained.
The Fedora Project also includes an IRC (Internet Relay Chat)
channel. IRC is a real-time, text-based form of communication. With
it, you can have conversations with multiple people in an open channel
or chat with someone privately one-on-one.
To talk with other Fedora Project participants via IRC, access
freenode IRC network. Initially, you can use irc.freenode.net as the
IRC server, although you may decide to select a server that is
geographically closer to you. Refer to the freenode website
([11]http://www.freenode.net/) for more information. Fedora Project
participants frequent the #fedora channel, while Fedora Project
developers can often be found on the #fedora-devel channel. Some of
the larger projects may have their own channels as well; this
information can be found on the project pages.
NOTE: Red Hat has no control over the Fedora IRC channels or their
content.
( x86 )
== References ==
Visible links
1. http://www.gnu.org/licenses/fdl.html
2. http://fedora.redhat.com/docs/selinux-faq/
3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
5. http://platan.vc.cvut.cz/ftp/pub/vmware/
6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
7. http://i2o.shadowconnect.com/
8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
9. http://people.redhat.com/~harald/udev.html
10. http://fedora.redhat.com/
11. http://www.freenode.net/
From fedora-docs-commits at redhat.com Wed May 18 22:39:56 2005
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Wed, 18 May 2005 18:39:56 -0400
Subject: install-guide fedora-install-guide-other-instmethods-en.xml, 1.6,
1.7
Message-ID: <200505182239.j4IMdu2H012587@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12567
Modified Files:
fedora-install-guide-other-instmethods-en.xml
Log Message:
Started 2nd edit of other install methods; consolidated section and added a small clarification for newbies
Index: fedora-install-guide-other-instmethods-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-other-instmethods-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-other-instmethods-en.xml 12 May 2005 22:27:31 -0000 1.6
+++ fedora-install-guide-other-instmethods-en.xml 18 May 2005 22:39:54 -0000 1.7
@@ -4,18 +4,19 @@
Other Installation Methods
- The following screen appears if one of the following is true:
+ The installation method screen below appears if one of the following
+ is true:
- You booted using PXE, or USB media.
+ You booted with PXE, or USB media.
You entered the option at the
- boot: prompt.
+ boot: prompt.
@@ -48,8 +49,7 @@
If a &FED; disc is in your computer's CD or DVD drive, the
installation program loads its next stage from that disc. The
installation program downloads package data from the source you
- choose.
+ choose.
@@ -129,12 +129,6 @@