docs-commits January 2006

docs-commits@lists.fedoraproject.org

1 participants
215 discussions

release-notes RELEASE-NOTES-en.xml,1.19,1.20
by fedora-docs-commits＠redhat.com 30 Jan '06

30 Jan '06

Author: kwade Update of /cvs/docs/release-notes In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16814 Modified Files: RELEASE-NOTES-en.xml Log Message: Typo fixed. Index: RELEASE-NOTES-en.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- RELEASE-NOTES-en.xml 30 Jan 2006 00:36:05 -0000 1.19 +++ RELEASE-NOTES-en.xml 30 Jan 2006 14:57:22 -0000 1.20 @@ -8,7 +8,7 @@ <!ENTITY ARCH-SPECIFIC-PPC SYSTEM "./ArchSpecificPPC-en.xml"> <!ENTITY ARCH-SPECIFIC-x86 SYSTEM "./ArchSpecificx86-en.xml"> <!ENTITY ARCH-SPECIFIC-x86-64 SYSTEM "./ArchSpecificx86_64-en.xml"> -<!ENTITY BACKWARDS-COMPATIBILITY SYSTEM "./BackwardsCompatbility"> +<!ENTITY BACKWARDS-COMPATIBILITY SYSTEM "./BackwardsCompatibility"> <!ENTITY COLOPHON SYSTEM "./Colophon-en.xml"> <!ENTITY DATABASE-SERVERS SYSTEM "./DatabaseServers-en.xml"> <!ENTITY DESKTOP SYSTEM "./Desktop-en.xml">

1 0

docs-common Makefile.common,1.35,1.36
by fedora-docs-commits＠redhat.com 30 Jan '06

30 Jan '06

Author: jtr Update of /cvs/docs/docs-common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8398 Modified Files: Makefile.common Log Message: Remove harmless debugging cruft. Index: Makefile.common =================================================================== RCS file: /cvs/docs/docs-common/Makefile.common,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- Makefile.common 30 Jan 2006 10:31:48 -0000 1.35 +++ Makefile.common 30 Jan 2006 10:32:17 -0000 1.36 @@ -343,7 +343,7 @@ -o -name '*.tar.gz' \ -o -name '*.tmp' \ -o -name '${DOCBASE}-${VERSION}' \ - ')' -prune -o -print | tee /tmp/log.files | cpio -pamdv $(DOCBASE)-$(VERSION) + ')' -prune -o -print | cpio -pamdv $(DOCBASE)-$(VERSION) tar -zcvf $@ $(DOCBASE)-$(VERSION)/ ${RM} -r $(DOCBASE)-$(VERSION)

1 0

docs-common Makefile.common,1.34,1.35
by fedora-docs-commits＠redhat.com 30 Jan '06

30 Jan '06

Author: jtr Update of /cvs/docs/docs-common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8374 Modified Files: Makefile.common Log Message: When using find(1) to generate the list of candidate files for the tarball, do not expand the filenames onto the command line, using "find *" because a filename with an embedded '#" will bork the remainder of the command line, seriously breaking the build process. Thanks again, Emacs! Index: Makefile.common =================================================================== RCS file: /cvs/docs/docs-common/Makefile.common,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- Makefile.common 20 Jan 2006 01:05:14 -0000 1.34 +++ Makefile.common 30 Jan 2006 10:31:48 -0000 1.35 @@ -332,18 +332,18 @@ ${MAKE} kde.desktop ${MAKE} khelp.desktop ${MAKE} omf - mkdir $(DOCBASE)-$(VERSION) - find * '(' \ - -name '.*' \ - -o -name 'CVS' \ - -o -name 'rpm' \ - -o -name '*.rpm' \ - -o -name '#*' \ - -o -name '*~' \ - -o -name '*.tar.gz' \ - -o -name '*.tmp' \ - -o -name '${DOCBASE}-${VERSION}' \ - ')' -prune -o -print | cpio -pamdv $(DOCBASE)-$(VERSION) + ${RM} -r $(DOCBASE)-$(VERSION) + mkdir -p $(DOCBASE)-$(VERSION) + find . '(' \ + -name '*#*' \ + -o -name 'CVS' \ + -o -name 'rpm' \ + -o -name '*.rpm' \ + -o -name '*~' \ + -o -name '*.tar.gz' \ + -o -name '*.tmp' \ + -o -name '${DOCBASE}-${VERSION}' \ + ')' -prune -o -print | tee /tmp/log.files | cpio -pamdv $(DOCBASE)-$(VERSION) tar -zcvf $@ $(DOCBASE)-$(VERSION)/ ${RM} -r $(DOCBASE)-$(VERSION)

1 0

release-notes files-map.txt,NONE,1.1
by fedora-docs-commits＠redhat.com 30 Jan '06

30 Jan '06

Author: kwade Update of /cvs/docs/release-notes In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3633 Added Files: files-map.txt Log Message: A map of where all the XML files go in relation to each other. --- NEW FILE files-map.txt --- # map of how XML files in the release-notes module interact RELEASE-NOTES-*.xml fdp-info-*.xml ../docs-common/common/legalnotice-relnotes-*.xml Welcome-*.xml OverView-*.xml ../docs-common/common/legalnotice-*.xml Feedback-*.xml Introduction-*.xml Installer-*.xml ArchSpecific-*.xml ArchSpecificPPC-*.xml ArchSpecificx86-*.xml ArchSpecificx86_64-*.xml Networking-*.xml PackageNotes-*.xml ServerTools-*.xml PackageNotesJava-*.xml Kernel-*.xml Security-*.xml SecuritySELinux-*.xml DevelopmentTools-*.xml DevelopmentToolsJava-*.xml DevelopmentToolsGCC-*.xml I18n-*.xml Printing-*.xml DatabaseServers-*.xml Multimedia-*.xml WebServers-*.xml Samba-*.xml Xorg-*.xml Entertainment-*.xml Legacy-*.xml PackageChanges-*.xml ProjectOverview-*.xml Colophon-*.xml # Unused, but maybe we should use/ BackwardsCompatibility-*.xml Desktop-*.xml FileSystems-*.xml FileServers-*.xml SystemDaemons-*.xml

1 0

release-notes/xmlbeats steps-to-convert-v-1.txt,NONE,1.1
by fedora-docs-commits＠redhat.com 30 Jan '06

30 Jan '06

Author: kwade Update of /cvs/docs/release-notes/xmlbeats In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30934 Added Files: steps-to-convert-v-1.txt Log Message: This was one of the procedures for converting the Wiki XML into DB XML, put here for reference. --- NEW FILE steps-to-convert-v-1.txt --- 1. Use xmlbeats to get the content local 2. Convert filenames that need it to match the WikiName GCC.xml => DevelopmentToolsGCC.xml ... 3. Run xmlformat on all the Beats cd release-notes/xmlbeats/Beats for i in *.xml; do # Run xmlformat with the nifty config file xmlformat -f /path/to/xmlformat-fdp.conf $i > tmpfile; mv tmpfile $i; done 4. Remove the <?xml>, <DOCTYPE>, <article />, and <articleinfo /> contents from each file. 5. Run xmldiff to get a diff; do not use -p (default) as the colored output is icky when piped to a file. cd release-notes/xmlbeats/Beats mkdir ../diffs for i in *.xml; do # Get a mirror of the file name without extension echo $i | sed 's/\.xml//' > tmpname; # Format "oldfile newfile" # oldfile == XML in CVS # newfile == XML from Wiki xmldiff -u ../../`cat tmpname`-en.xml $i > ../diffs/`cat tmpname`.diff; done

1 0

release-notes RELEASE-NOTES-en.xml, 1.18, 1.19 RELEASE-NOTES-it.xml, 1.9, 1.10 RELEASE-NOTES-ja_JP.xml, 1.5, 1.6 RELEASE-NOTES-pa.xml, 1.2, 1.3 RELEASE-NOTES-ru.xml, 1.5, 1.6 RELEASE-NOTES-zh_CN.xml, 1.7, 1.8
by fedora-docs-commits＠redhat.com 29 Jan '06

29 Jan '06

Author: kwade Update of /cvs/docs/release-notes In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19553 Modified Files: RELEASE-NOTES-en.xml RELEASE-NOTES-it.xml RELEASE-NOTES-ja_JP.xml RELEASE-NOTES-pa.xml RELEASE-NOTES-ru.xml RELEASE-NOTES-zh_CN.xml Log Message: Adding colophon for all languages. Very sorry that this did not happen for test2, it was a mistake. This is included now forevermore. A big personal thanks to all release notes contributors. Index: RELEASE-NOTES-en.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- RELEASE-NOTES-en.xml 24 Jan 2006 22:10:39 -0000 1.18 +++ RELEASE-NOTES-en.xml 30 Jan 2006 00:36:05 -0000 1.19 @@ -82,4 +82,5 @@ &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW; + &COLOPHON; </article> Index: RELEASE-NOTES-it.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- RELEASE-NOTES-it.xml 24 Jan 2006 22:10:39 -0000 1.9 +++ RELEASE-NOTES-it.xml 30 Jan 2006 00:36:05 -0000 1.10 @@ -82,4 +82,5 @@ &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW; + &COLOPHON; </article> Index: RELEASE-NOTES-ja_JP.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-ja_JP.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- RELEASE-NOTES-ja_JP.xml 24 Jan 2006 22:10:39 -0000 1.5 +++ RELEASE-NOTES-ja_JP.xml 30 Jan 2006 00:36:05 -0000 1.6 @@ -81,6 +81,7 @@ &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW; + &COLOPHON; </article> <!-- Local variables: Index: RELEASE-NOTES-pa.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-pa.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- RELEASE-NOTES-pa.xml 24 Jan 2006 22:10:39 -0000 1.2 +++ RELEASE-NOTES-pa.xml 30 Jan 2006 00:36:05 -0000 1.3 @@ -88,4 +88,6 @@ &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW; + &COLOPHON; </article> + Index: RELEASE-NOTES-ru.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-ru.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- RELEASE-NOTES-ru.xml 24 Jan 2006 22:10:39 -0000 1.5 +++ RELEASE-NOTES-ru.xml 30 Jan 2006 00:36:05 -0000 1.6 @@ -82,4 +82,5 @@ &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW; + &COLOPHON; </article> Index: RELEASE-NOTES-zh_CN.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-zh_CN.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- RELEASE-NOTES-zh_CN.xml 24 Jan 2006 22:10:39 -0000 1.7 +++ RELEASE-NOTES-zh_CN.xml 30 Jan 2006 00:36:05 -0000 1.8 @@ -64,4 +64,4 @@ &FDP-INFO; - &WELCOME; &OVERVIEW; &LEGALNOTICE-SECTION; &FEEDBACK; &INTRO; &INSTALLER; &ARCH-SPECIFIC; &NETWORKING; &PACKAGE-NOTES; &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW;</article> + &WELCOME; &OVERVIEW; &LEGALNOTICE-SECTION; &FEEDBACK; &INTRO; &INSTALLER; &ARCH-SPECIFIC; &NETWORKING; &PACKAGE-NOTES; &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW; &COLOPHON;</article>

1 0

release-notes/xmlbeats wikixml2fdpxml,NONE,1.1
by fedora-docs-commits＠redhat.com 29 Jan '06

29 Jan '06

Author: kwade Update of /cvs/docs/release-notes/xmlbeats In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19460 Added Files: wikixml2fdpxml Log Message: This script does some of what is needed, but not all, it needs a language such as perl or python to do some kung-fu. It is also not a modular script or otherwise well written, it's just a hack to get started. --- NEW FILE wikixml2fdpxml --- #!/bin/bash # # This file can be completely replaced with a better tool written in # $LANGUAGE of someone's choice # # Original shell script - 29-Jan-2005 # kwade(a)redhat.com # Manually rename some files to include their wiki namespace mv Beats/x86_64.xml Beats/ArchSpecificx86_64.xml mv Beats/x86.xml Beats/ArchSpecificx86.xml mv Beats/GCC.xml Beats/DevelToolsGCC.xml mv Beats/SELinux.xml Beats/SecuritySELinux.xml # Add the base language extension to the files ls Beats/ > xmlfiles for i in `cat xmlfiles`; do echo $i | sed 's/.xml/-en.xml/g' > newfilename; mv Beats/$i Beats/`cat newfilename`; done rm xmlfiles newfilename echo "done" # Right here is where we want to call perl-fu or python-fu # to follow this pseudo-code # # for each(<section>); # do # get(contents of <title></title>) == $title; # replace(" " with "-") == $idattrib; # insert($idattrib) -> <section id="$idattrib">; # done

1 0

install-guide fedora-install-guide-adminoptions-en.xml, 1.8, 1.9 fedora-install-guide-bootloader-en.xml, 1.13, 1.14 fedora-install-guide-en.xml, 1.40, 1.41 fedora-install-guide-firstboot-en.xml, 1.18, 1.19 fedora-install-guide-packageselection-en.xml, 1.17, 1.18 fedora-install-guide-techref-en.xml, 1.5, 1.6 rpm-info.xml, 1.5, 1.6
by fedora-docs-commits＠redhat.com 29 Jan '06

29 Jan '06

Author: elliss Update of /cvs/docs/install-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8184 Modified Files: fedora-install-guide-adminoptions-en.xml fedora-install-guide-bootloader-en.xml fedora-install-guide-en.xml fedora-install-guide-firstboot-en.xml fedora-install-guide-packageselection-en.xml fedora-install-guide-techref-en.xml rpm-info.xml Log Message: - Updated indexing. - Added SSH to Tech Ref section. - Package Selection is still subject to change at this point. Index: fedora-install-guide-adminoptions-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- fedora-install-guide-adminoptions-en.xml 26 Jan 2006 00:15:39 -0000 1.8 +++ fedora-install-guide-adminoptions-en.xml 29 Jan 2006 20:37:55 -0000 1.9 @@ -22,17 +22,18 @@ <para> The &FED; installation and <firstterm>rescue discs</firstterm> may - either boot with <firstterm>rescue mode</firstterm> , or load the + either boot with <firstterm>rescue mode</firstterm>, or load the installation system. For more information on rescue discs and rescue mode, refer to <xref linkend="sn-mode-rescue"/>. </para> </note> <section id="sn-bootoptions-installer"> - <title>Configuring the Installation System</title> + <title>Configuring the Installation System at the + <prompt>boot:</prompt> + Prompt</title> <para> - You may configure the installation system without affecting the - final &FED; system. The + The <prompt>boot:</prompt> prompt enables you to specify a number of settings for the installation system. These include: @@ -70,8 +71,8 @@ <title>Specifying the Language</title> <para> - To set the language for the installation process screens, - specify the ISO code for that language with the + To set the language for both the installation process and the + final system, specify the ISO code for that language with the <option>lang</option> option. For example, the ISO code <userinput>fr</userinput> identifies the French language: </para> @@ -95,16 +96,35 @@ <userinput>linux resolution=<replaceable>1024x768</replaceable></userinput> </screen> <para> - To run the installation process in <option>text</option> mode, - enter: + To run the installation process in + <indexterm> + <primary>text interface</primary> + </indexterm> + <option>text</option> mode, enter: </para> <screen> <userinput>linux text</userinput> </screen> <para> - To enable support for a serial console, enter - <option>serial</option> as an additional option. + To enable support for a + <indexterm> + <primary>serial console</primary> + </indexterm> + serial console, enter <option>serial</option> as an additional + option. </para> + + <note> + <title>Configuring the Installed System</title> + + <para> + The installed system runs the Setup Agent the first time that + it boots. Use the Setup Agent to configure the display + settings for the new system. Refer to + <xref linkend="sn-firstboot-display"/> for more information on + configuring the display with the Setup Agent. + </para> + </note> </section> <section id="sn-boot-options-installmethod"> @@ -230,6 +250,16 @@ <screen> <userinput>linux ip=<replaceable>192.168.1.10</replaceable> netmask=<replaceable>255.255.255.0</replaceable> gateway=<replaceable>192.168.1.1</replaceable> dns=<replaceable>192.168.1.2,192.168.1.3</replaceable></userinput> </screen> + <note> + <title>Configuring the Installed System</title> + + <para> + Use the Network Configuration screen to specify the network + settings for the new system. Refer to + <xref linkend="ch-networkconfig"/> for more information on + configuring the network settings for the installed system. + </para> + </note> </section> </section> <section id="sn-remote-installation"> @@ -241,6 +271,9 @@ display requires <command>telnet</command>, which is installed by default on &FED; systems. To remotely access the graphical display of an installation system, use client software that supports the + <indexterm> + <primary>VNC (Virtual Network Computing)</primary> + </indexterm> VNC (Virtual Network Computing) display protocol. A number of providers offer VNC clients for Microsoft Windows and Mac OS, as well as UNIX-based systems. @@ -248,6 +281,10 @@ <tip> <title>Installing a VNC Client on &FED;</title> <para> + <indexterm> + <primary>VNC (Virtual Network Computing)</primary> + <secondary>installing client</secondary> + </indexterm> &FED; includes <application>vncviewer</application>, the client provided by the developers of VNC. To obtain <application>vncviewer</application>, install the @@ -259,11 +296,15 @@ may either start the installation and manually login to the graphical display with a VNC client on another system, or configure the installation system to automatically connect to a - VNC client on the network that is running in - <emphasis>listening</emphasis> mode. + VNC client on the network that is running in <firstterm>listening + mode</firstterm>. </para> <para> + <indexterm> + <primary>VNC (Virtual Network Computing)</primary> + <secondary>enabling</secondary> + </indexterm> To enable remote graphical access to the installation system, enter two options at the prompt: </para> @@ -314,10 +355,14 @@ <para> To have the installation system automatically connect to a VNC - client, first start the client in listening mode. On &FED; - systems, use the <option>-listen</option> option to run - <application>vncviewer</application> as a listener. In a terminal - window, enter the command: + client, first start the client in + <indexterm> + <primary>VNC (Virtual Network Computing)</primary> + <secondary>listening mode</secondary> + </indexterm> + listening mode. On &FED; systems, use the <option>-listen</option> + option to run <application>vncviewer</application> as a listener. + In a terminal window, enter the command: </para> <screen> <userinput>vncviewer -listen</userinput> @@ -364,6 +409,9 @@ </screen> <para> To enable remote access to a text mode installation, use the + <indexterm> + <primary>Telnet</primary> + </indexterm> <option>telnet</option> option at the <prompt>boot:</prompt> prompt: @@ -396,7 +444,11 @@ <title>Automating the Installation with Kickstart</title> <para> - A <firstterm>Kickstart</firstterm> file specifies settings for an + A + <indexterm> + <primary>Kickstart</primary> + </indexterm> + <firstterm>Kickstart</firstterm> file specifies settings for an installation. Once booted, the installation system may read a Kickstart file and carry out the installation process without requiring any further input from a user. @@ -568,10 +620,13 @@ </para> <para> - Hardware manufacturers may supply driver disks for &FED; with - the device, or provide image files to prepare the disks. To - obtain the latest drivers, download the correct file from the - website of the manufacturer. + Hardware manufacturers may supply + <indexterm> + <primary>driver disks</primary> + </indexterm> + driver disks for &FED; with the device, or provide image files + to prepare the disks. To obtain the latest drivers, download the + correct file from the website of the manufacturer. </para> <note> @@ -618,7 +673,7 @@ The installation system may also read drivers from disk images that are held on network servers. Refer to <xref linkend="tb-driversources"/> for the supported sources of - driver image files. + driver disk image files. </para> <table id="tb-driversources"> <title>Driver Disk Image Sources</title> @@ -907,8 +962,12 @@ </para> <para> - To boot your computer in memory testing mode, enter - <userinput>memtest86</userinput> at the + To boot your computer in + <indexterm> + <primary>memory testing mode</primary> + </indexterm> + memory testing mode, enter <userinput>memtest86</userinput> at + the <prompt>boot:</prompt> prompt. The first test starts immediately. By default, <command>memtest86</command> carries out a total of ten tests. @@ -922,11 +981,16 @@ <section id="sn-mode-rescue"> <title>Booting Your Computer with the Rescue Mode</title> - - <para> - You may boot a command-line Linux system from either a rescue - disc or the first installation disc, without installing &FED; on - the computer. This enables you to use the utilities and + <indexterm> + <primary>rescue mode</primary> + </indexterm> + <para> + You may boot a command-line Linux system from either a + <indexterm> + <primary>rescue discs</primary> + </indexterm> + rescue disc or the first installation disc, without installing + &FED; on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair an installed system. </para> Index: fedora-install-guide-bootloader-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-bootloader-en.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- fedora-install-guide-bootloader-en.xml 9 Jun 2005 22:36:07 -0000 1.13 +++ fedora-install-guide-bootloader-en.xml 29 Jan 2006 20:37:55 -0000 1.14 @@ -1,39 +1,40 @@  + <chapter id="ch-bootloader"> <title>Boot Loader</title> - <para> A <firstterm>boot loader</firstterm> is a small program that reads and launches the operating system. &FC; uses the - <application>GRUB</application> boot loader by default. If you have + <indexterm> + <primary>GRUB</primary> + <secondary>configuring</secondary> + <seealso>boot loader</seealso> + </indexterm> + <application>GRUB</application> boot loader by default. If you have multiple operating systems, the boot loader determines which one to boot, usually by offering a menu. </para> - <para> - You may have a boot loader installed on your system already. An + You may have a boot loader installed on your system already. An operating system may install its own preferred boot loader, or you may have installed a third-party boot loader.If your boot loader does not recognize Linux partitions, you may not be able to boot - &FC;. Use <application>GRUB</application> as your boot loader to - boot Linux and most other operating systems. Follow the directions + &FC;. Use <application>GRUB</application> as your boot loader to + boot Linux and most other operating systems. Follow the directions in this section to install <application>GRUB</application>. </para> - <warning> <title>Installing GRUB</title> + <para> If you install GRUB, it may overwrite your existing boot loader. </para> </warning> - <para> The following screen displays boot loader configuration options. </para> <figure id="fig-bootloader-config"> - <title> - Boot Loader Configuration Screen - </title> + <title>Boot Loader Configuration Screen</title> <mediaobject> <imageobject> <imagedata align="center" fileref="figs/bootloader-config.eps" format="EPS"/> @@ -46,18 +47,19 @@ </textobject> </mediaobject> </figure> - <section id="sn-bootloader-config-change"> <title>Keeping Your Existing Boot Loader Settings</title> + <para> By default, the installation program installs GRUB in the - <firstterm>master boot record</firstterm>, <indexterm> - <primary>master boot record</primary> - </indexterm> or <abbrev>MBR</abbrev>, of the device for the root - file system. To change or decline installation of a new boot - loader, select the <guibutton>Change boot loader</guibutton> - button. The dialog shown in - <xref linkend="fig-bootloader-change"/> allows you to avoid + <firstterm>master boot record</firstterm>, + <indexterm> + <primary>master boot record</primary> + </indexterm> + or <abbrev>MBR</abbrev>, of the device for the root file system. + To change or decline installation of a new boot loader, select the + <guibutton>Change boot loader</guibutton> button. The dialog shown + in <xref linkend="fig-bootloader-change"/> allows you to avoid installing or changing your existing boot loader settings. </para> <figure id="fig-bootloader-change"> @@ -75,69 +77,67 @@ </mediaobject> </figure> <important> - <title>Boot Loader Required</title> + <title>Boot Loader Required</title> + <para> - Your computer must have <application>GRUB</application> or another boot loader installed - in order to start, unless you create a separate startup - disk to boot from.  </para> </important> </section> - <section id="sn-bootloader-others"> - <title> - Booting Additional Operating Systems - </title> + <title>Booting Additional Operating Systems</title> + <para> If you have other operating systems already installed, &FC; attempts to automatically detect and configure - <application>GRUB</application> to boot them. You may manually + <application>GRUB</application> to boot them. You may manually configure any additional operating systems if - <application>GRUB</application> does not detect them. To - add, remove, or change the detected operating system settings, - use the options provided. + <application>GRUB</application> does not detect them. To add, + remove, or change the detected operating system settings, use the + options provided. </para> + <variablelist> <varlistentry> - <term> - <guibutton>Add</guibutton> - </term> + <term><guibutton>Add</guibutton></term> <listitem> <para> - Press the <guibutton>Add</guibutton> button to include an - additional operating system in GRUB. &FC; displays the - dialog shown in <xref + Press the <guibutton>Add</guibutton> button to include an + additional operating system in GRUB. &FC; displays the + dialog shown in + <xref linkend="fig-bootloader-others-popup"/>. - </para> + </para> <para> - Select the disk partition which contains the bootable - operating system from the drop-down list and give the entry - a label. <application>GRUB</application> displays this - label in its boot menu. - </para> + Select the disk partition which contains the bootable + operating system from the drop-down list and give the entry + a label. <application>GRUB</application> displays this label + in its boot menu. + </para> </listitem> </varlistentry> + <varlistentry> - <term> - <guibutton>Edit</guibutton> - </term> - <listitem> - <para> - To change an entry in the GRUB boot menu, select the entry - and then select <guibutton>Edit</guibutton>. - </para> + <term><guibutton>Edit</guibutton></term> + <listitem> + <para> + To change an entry in the GRUB boot menu, select the entry + and then select <guibutton>Edit</guibutton>. + </para> </listitem> </varlistentry> + <varlistentry> - <term> - <guibutton>Delete</guibutton> - </term> + <term><guibutton>Delete</guibutton></term> <listitem> <para> - To remove an entry from the GRUB boot menu, select the entry - and then select <guibutton>Delete</guibutton>. - </para> + To remove an entry from the GRUB boot menu, select the entry + and then select <guibutton>Delete</guibutton>. + </para> </listitem> </varlistentry> </variablelist> @@ -156,42 +156,40 @@ </mediaobject> </figure> </section> - <section id="sn-bootloader-password"> - <title> - Setting a Boot Loader Password - </title> + <title>Setting a Boot Loader Password</title> + <para> <application>GRUB</application> reads many file systems without - the help of an operating system. An operator can interrupt the + 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. However, these - functions may introduce serious security risks in some - environments. You can add a password to + change boot options, or recover from a system error. However, + these functions may introduce serious security risks in some + environments. You can add a password to <application>GRUB</application> so that the operator must enter the password to interrupt the normal boot sequence. </para> <tip> <title>GRUB Passwords Not Required</title> <para> - You may not require a <application>GRUB</application> password - if your system only has trusted operators, or is physically - secured with controlled console access. + You may not require a <application>GRUB</application> password + if your system only has trusted operators, or is physically + secured with controlled console access. </para> <para> - However, if there is a chance someone can get physical access to - the keyboard and monitor of your computer, that person can - reboot the system and access <application>GRUB</application>. - This is where a password is helpful. + However, if there is a chance someone can get physical access to + the keyboard and monitor of your computer, that person can + reboot the system and access <application>GRUB</application>. + This is where a password is helpful. </para> </tip> <para> To set a boot password, select the <guibutton>Use a boot loader - password</guibutton> checkbox. The <guibutton>Change - password</guibutton> button will become active. Select + password</guibutton> checkbox. The <guibutton>Change + password</guibutton> button will become active. Select <guibutton>Change password</guibutton> to display the dialog - below. Type the desired password, and then confirm it by typing - it again in the spaces provided. + below. Type the desired password, and then confirm it by typing it + again in the spaces provided. </para> <figure id="fig-bootloader-password"> <title>Entering A Boot Password</title> @@ -211,84 +209,94 @@ <title>Choose a Good Password</title> <para> Choose a password that is easy for you to remember but hard for - others to guess. + others to guess. </para> </tip> <warning> <title>Forgotten <application>GRUB</application> Passwords</title> + <para> <application>GRUB</application> stores the password in encrypted - form, so it <emphasis>cannot</emphasis> be read or recovered. If - you forget the boot password, boot the system normally and then - change the password entry in the - <filename>/boot/grub/grub.conf</filename> 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. + form, so it <emphasis>cannot</emphasis> be read or recovered. If + you forget the boot password, boot the system normally and then + change the password entry in the + <filename>/boot/grub/grub.conf</filename> 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. </para> </warning> + <para> If you do need to change the <application>GRUB</application> - password, use the <command>grub-md5-crypt</command> utility. For + password, use the <command>grub-md5-crypt</command> utility. For information on using this utility, use the command <command>man - grub-md5-crypt</command> in a terminal window to read the manual + grub-md5-crypt</command> in a terminal window to read the manual pages. </para> </section> - <section id="sn-bootloader-advanced"> - <title> - Advanced Boot loader Options - </title> + <title>Advanced Boot loader Options</title> + <para> - The default boot options are adequate for most situations. The + The default boot options are adequate for most situations. The installation program writes the <application>GRUB</application> boot loader in the <indexterm> - <primary>master boot record</primary> - </indexterm> master boot record (<abbrev>MBR</abbrev>), - overwriting any existing boot loader. + <primary>master boot record</primary> + </indexterm> + master boot record (<abbrev>MBR</abbrev>), overwriting any + existing boot loader. </para> + <para> Tto keep your current boot loader in the <abbrev>MBR</abbrev>, use the advanced settings to place <application>GRUB</application> in the first sector of the partition holding the Linux root file system. </para> + <para> You may also need the advanced options if your <abbrev>BIOS</abbrev> enumerates your disk devices differently - than &FC; expects. On a few systems, &FC; may not configure the + than &FC; expects. On a few systems, &FC; may not configure the disk drive geometry for large disks correctly because of a broken - <abbrev>BIOS</abbrev>. To work around this problem, mark the + <abbrev>BIOS</abbrev>. To work around this problem, mark the <guibutton>Force LBA32</guibutton> checkbox. </para> + <para> The Linux kernel usually auto-detects its environment correctly, - and no additional kernel parameters are needed. However, you may provide - any needed kernel parameter using the advanced boot - loader options. + and no additional kernel parameters are needed. However, you may + provide any needed kernel parameter using the advanced boot loader + options. </para> + <note> - <title>Kernel Parameters</title> + <title>Kernel Parameters</title> + <para> For a partial list of the kernel command line parameters, type - the following command in a terminal window: <userinput>man - bootparam</userinput>. For a comprehensive and authoritative - list, refer to the documentation provided in the kernel sources. + the following command in a terminal window: <userinput>man + bootparam</userinput>. For a comprehensive and authoritative + list, refer to the documentation provided in the kernel sources. </para> </note> + <para> To alter any of these settings, mark the <guibutton>Configure - advanced boot loader options</guibutton> checkbox. Select - <guibutton>Next</guibutton> and the menu shown in <xref + advanced boot loader options</guibutton> checkbox. Select + <guibutton>Next</guibutton> and the menu shown in + <xref linkend="fig-bootloader-advanced"/> appears. </para> + <note> - <title>Optional Menu</title> + <title>Optional Menu</title> + <para> &FC; displays the following advanced boot options menu - <emphasis>only</emphasis> if the advanced configuration checkbox - described above has been selected. + <emphasis>only</emphasis> if the advanced configuration checkbox + described above has been selected. </para> </note> <figure id="fig-bootloader-advanced"> @@ -305,9 +313,7 @@ </textobject> </mediaobject> </figure> - </section> - </chapter>  <!ENTITY BUG-NUM "129911"> <!ENTITY FCLOCALVER "5"> -<!ENTITY DOCLOCALVER "1.15">  +<!ENTITY DOCLOCALVER "1.16">  <!ENTITY FDP-INFO SYSTEM "fdp-info-en.xml" > <!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml"> Index: fedora-install-guide-firstboot-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- fedora-install-guide-firstboot-en.xml 26 Jan 2006 00:15:39 -0000 1.18 +++ fedora-install-guide-firstboot-en.xml 29 Jan 2006 20:37:55 -0000 1.19 @@ -3,8 +3,12 @@ <chapter id="ch-firstboot"> <title>First Boot</title> <para> - The <application>Setup Agent</application> launches the first time - that you start a new &FC; system. Use <application>Setup + The + <indexterm> + <primary>Setup Agent</primary> + </indexterm> + <application>Setup Agent</application> launches the first time that + you start a new &FC; system. Use <application>Setup Agent</application> to configure the system for use before you log in. </para> @@ -80,6 +84,7 @@ The <indexterm> <primary>firewall</primary> + <secondary>configuring</secondary> </indexterm> <firstterm>firewall</firstterm> built into &FC; checks every incoming and outgoing network connection on your machine against a @@ -90,9 +95,14 @@ <para> By default the firewall is enabled, with a simple set of rules that allow connections to be made from your system to others, but - permit only Secure SHell (SSH) connections from other systems. You - may make changes on this screen to allow access to specific - network services on your &FED; system. + permit only + <indexterm> + <primary>SSH (Secure SHell)</primary> + <secondary>firewall configuration</secondary> + </indexterm> + SSH (Secure SHell) connections from other systems. You may make + changes on this screen to allow access to specific network + services on your &FED; system. </para> <para> @@ -157,6 +167,7 @@ The <indexterm> <primary>&SEL;</primary> + <secondary>configuring</secondary> </indexterm> <firstterm>&SEL;</firstterm> (Security Enhanced Linux) framework is part of &FC;. &SEL; limits the actions of both users and @@ -195,7 +206,7 @@ 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 - <guilabel>Active</guilabel> at any time after booting. + <guilabel>Enforcing</guilabel> at any time after booting. </para> </listitem> </varlistentry> Index: fedora-install-guide-packageselection-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-en.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- fedora-install-guide-packageselection-en.xml 26 Jan 2006 00:15:39 -0000 1.17 +++ fedora-install-guide-packageselection-en.xml 29 Jan 2006 20:37:55 -0000 1.18 @@ -2,9 +2,10 @@ <chapter id="ch-packageselection"> <title>Package Selection</title> + <remark role="FIXME">TEXT SUBJECT TO CHANGE: The package selection screen is still being developed.</remark> <para> By default, the &FED; installation process loads a selection of - software that is suitable for a desktop system. This screen enables + software that is suitable for a desktop system. The package selection screen enables you to customize the set of software to match your requirements. </para> <para> @@ -80,6 +81,13 @@ </menuchoice>. </para> </tip> + <section id="sn-mandatory-packages"> + <title>Core Software</title> + <para> + <remark role="FIXME">Mention some base stuff that is part of every &FC; system: SMTP, SSH, CUPS, NFS, Python and <command>yum</command>...</remark> + </para> + </section> + <section id="sn-lang-packages"> <title>Additional Language Support</title> Index: fedora-install-guide-techref-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-techref-en.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- fedora-install-guide-techref-en.xml 23 Jan 2006 23:24:09 -0000 1.5 +++ fedora-install-guide-techref-en.xml 29 Jan 2006 20:37:55 -0000 1.6 @@ -5,6 +5,9 @@ <para> This document provides a reference for using the &FED; installation software, known as <command>anaconda</command>. To learn more about + <indexterm> + <primary>Anaconda</primary> + </indexterm> <command>anaconda</command>, visit the project webpage: <ulink url="http://www.fedoraproject.org/wiki/Anaconda"/>. </para> @@ -18,7 +21,12 @@ <term>Boot Loader</term> <listitem> <para> - &FED; uses the <command>GRUB</command> boot loader. Refer to + &FED; uses the + <indexterm> + <primary>GRUB</primary> + <secondary>documentation</secondary> + </indexterm> + <command>GRUB</command> boot loader. Refer to <ulink url="http://www.gnu.org/software/grub/"/> for more information. </para> @@ -40,9 +48,13 @@ <term>Audio Support</term> <listitem> <para> - The Linux kernel used by &FED; incorporates ALSA (Advanced - Linux Sound Architecture). For more information about ALSA, - refer to the project website: + The Linux kernel used by &FED; incorporates + <indexterm> + <primary>ALSA (Advanced + Linux Sound Architecture)</primary> + </indexterm> + ALSA (Advanced Linux Sound Architecture). For more information + about ALSA, refer to the project website: <ulink url="http://www.alsa-project.org/"/>. </para> </listitem> @@ -53,6 +65,9 @@ <listitem> <para> Both the installation system and &FED; itself use the + <indexterm> + <primary>Xorg</primary> + </indexterm> <command>Xorg</command> suite to provide graphical capabilities. Components of <command>Xorg</command> manage the display, keyboard and mouse for the desktop environments that @@ -66,9 +81,14 @@ <term>Remote Displays</term> <listitem> <para> - &FC; and <command>anaconda</command> include VNC to enable - remote access to graphical displays. For more information - about VNC, refer to the documentation on the RealVNC website: + &FC; and <command>anaconda</command> include + <indexterm> + <primary>VNC (Virtual Network Computing)</primary> + <secondary>documentation</secondary> + </indexterm> + VNC (Virtual Network Computing) software to enable remote + access to graphical displays. For more information about VNC, + refer to the documentation on the RealVNC website: <ulink url="http://www.realvnc.com/documentation/"/>. </para> </listitem> @@ -90,9 +110,42 @@ </varlistentry> <varlistentry> + <term>Remote System Access</term> + <listitem> + <para> + &FC; incorporates the + <indexterm> + <primary>OpenSSH</primary> + <seealso>SSH</seealso> + </indexterm> + OpenSSH suite to provide remote access to the system. The SSH + <indexterm> + <primary>SSH (Secure SHell)</primary> + <secondary>documentation</secondary> + </indexterm> + service enables a number of functions, which include access to + the command-line from other systems, remote command execution, + and network file transfers. During the installation process + <command>anaconda</command> may use the <command>scp</command> + <indexterm> + <primary>scp</primary> + <seealso>SSH</seealso> + </indexterm> + feature of OpenSSH to transfer crash reports to remote + systems. Refer to the OpenSSH website for more information: + <ulink url="http://www.openssh.com/"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term>Access Control</term> <listitem> <para> + <indexterm> + <primary>&SEL;</primary> + <secondary>documentation</secondary> + </indexterm> &SEL; provides Mandatory Access Control (MAC) capabilities that supplement the standard Linux security features. Refer to the &SEL; FAQ for more information: @@ -105,8 +158,14 @@ <term>Firewall</term> <listitem> <para> - &FED; uses the <command>netfilter</command> framework. The - Netfilter project website provides documentation for both <command>netfilter</command>, and the + The Linux kernel used by &FED; incorporates the + <command>netfilter</command> framework to provide + <indexterm> + <primary>firewall</primary> + <secondary>documentation</secondary> + </indexterm> + firewall features. The Netfilter project website provides + documentation for both <command>netfilter</command>, and the <command>iptables</command> administration facilities: <ulink url="http://netfilter.org/documentation/index.html"/>. </para> @@ -117,8 +176,13 @@ <term>Software Installation</term> <listitem> <para> - &FED; uses <command>yum</command> to manage the RPM packages - that make up the system. Refer to + &FED; uses + <indexterm> + <primary>yum</primary> + <secondary>documentation</secondary> + </indexterm> + <command>yum</command> to manage the RPM packages that make up + the system. Refer to <ulink url="http://fedora.redhat.com/docs/yum/"/> for more information. </para> Index: rpm-info.xml =================================================================== RCS file: /cvs/docs/install-guide/rpm-info.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- rpm-info.xml 26 Jan 2006 00:15:39 -0000 1.5 +++ rpm-info.xml 29 Jan 2006 20:37:55 -0000 1.6 @@ -28,10 +28,15 @@  </titles> <changelog order="newest-first"> + <revision date="2006-01-29" number="1.16" role="doc"> + <author worker="StuartEllis"/> + + <details>Updated indexing.</details> + </revision> <revision date="2006-01-26" number="1.15" role="doc"> <author worker="StuartEllis"/>  - <details>Updated Package Selection screen for test2.</details> + <details lang="en">Updated Package Selection screen for test2.</details> </revision> <revision date="2006-01-23" number="1.14" role="doc"> <author worker="StuartEllis"/>

1 0

docs-common/bin db2rpm-info,1.4,1.5
by fedora-docs-commits＠redhat.com 29 Jan '06

29 Jan '06

Author: jtr Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30650/bin Modified Files: db2rpm-info Log Message: Allow *any* modern shell. Index: db2rpm-info =================================================================== RCS file: /cvs/docs/docs-common/bin/db2rpm-info,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- db2rpm-info 28 Jan 2006 20:41:45 -0000 1.4 +++ db2rpm-info 29 Jan 2006 15:38:45 -0000 1.5 @@ -1,6 +1,6 @@ -#!/bin/bash -ME=$(basename $0) -BINDIR=$(dirname $0) +#!/bin/sh +ME=`basename $0` +BINDIR=`dirname $0` USAGE="usage: ${ME} [-o ofile] document.xml" ofile= while getopts o: c @@ -10,7 +10,7 @@ *) echo "${USAGE}" >&2; exit 1;; esac done -shift $(expr ${OPTIND} - 1) +shift `expr ${OPTIND} - 1` if [ $# -ne 1 ]; then echo "${USAGE}" >&2 exit 1

1 0

docs-common/bin db2rpm-info,1.3,1.4
by fedora-docs-commits＠redhat.com 28 Jan '06

28 Jan '06

Author: pfrields Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18544/docs-common/bin Modified Files: db2rpm-info Log Message: No presumed shell on contributors' machines but bash Index: db2rpm-info =================================================================== RCS file: /cvs/docs/docs-common/bin/db2rpm-info,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- db2rpm-info 19 Jan 2006 19:49:54 -0000 1.3 +++ db2rpm-info 28 Jan 2006 20:41:45 -0000 1.4 @@ -1,4 +1,4 @@ -#!/bin/zsh +#!/bin/bash ME=$(basename $0) BINDIR=$(dirname $0) USAGE="usage: ${ME} [-o ofile] document.xml"

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits January 2006