docs-commits January 2006

docs-commits@lists.fedoraproject.org

1 participants
215 discussions

owners owners.list,1.10,1.11
by fedora-docs-commits＠redhat.com 25 Jan '06

25 Jan '06

Author: kwade Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27397/owners Modified Files: owners.list Log Message: Adding new guide for bugzilla component. Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- owners.list 9 Nov 2005 21:17:45 -0000 1.10 +++ owners.list 25 Jan 2006 20:11:48 -0000 1.11 @@ -30,6 +30,8 @@ # fdr(a)eln.fastmail.fm # relnotes(a)fedoraproject.org # sarahs(a)redhat.com +# cchang(a)redhat.com +# aalam(a)redhat.com # # Global FDP components @@ -63,6 +65,7 @@ Fedora Documentation|toolchain-devel|For bugs and requests of the documentation tools.|kwade@redhat.com|mjohnson@redhat.com|Tommy.Reynolds@MegaCoder.com Fedora Documentation|translation-guide|The canonical reference for translating all aspects of the Fedora Project.|sarahs@redhat.com|tfox@redhat.com|kwade@redhat.com Fedora Documentation|translation-guide-windows|Tutorial for translators working in a Microsoft Windows environment.|sarahs@redhat.com|tfox@redhat.com| +Fedora Documentation|translation-quick-start-guide|Helping new translators get started quickly with Fedora translations.|mospina@redhat.com|aalam@redhat.com|stickster@gmail.com Fedora Documentation|updates|Tutorial for keeping a system up-to-date.|tfox@redhat.com|kwade@redhat.com| Fedora Documentation|usb-hotplug|Using USB and hotplug.|stickster@gmail.com|fdr@eln.fastmail.fm| Fedora Documentation|xml-normalize|Development of XML normalization tools.|Tommy.Reynolds@MegaCoder.com|stickster@gmail.com|

1 0

release-notes RELEASE-NOTES-en.xml, 1.17, 1.18 RELEASE-NOTES-it.xml, 1.8, 1.9 RELEASE-NOTES-ja_JP.xml, 1.4, 1.5 RELEASE-NOTES-pa.xml, 1.1, 1.2 RELEASE-NOTES-ru.xml, 1.4, 1.5 RELEASE-NOTES-zh_CN.xml, 1.6, 1.7
by fedora-docs-commits＠redhat.com 24 Jan '06

24 Jan '06

Author: jtr Update of /cvs/docs/release-notes In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10603 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: Changed to use information from "rpm-info.xml" instead of depricated in-line <bookinfo> or <articleinfo> elements. Index: RELEASE-NOTES-en.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- RELEASE-NOTES-en.xml 10 Jan 2006 21:51:56 -0000 1.17 +++ RELEASE-NOTES-en.xml 24 Jan 2006 22:10:39 -0000 1.18 @@ -47,6 +47,8 @@  + <!ENTITY FDP-INFO SYSTEM "fdp-info-en.xml" > + <!ENTITY LOCALVER "5 test2">   <!ENTITY DOCNAME "RELEASE-NOTES"> @@ -58,21 +60,15 @@ <!ENTITY PROJ "&FP;">  <!ENTITY DISTRO "&FC;">  <!ENTITY DISTROVER "&LOCALVER;">  - <!ENTITY BUG-NUM "151189">  + <!ENTITY BUG-NUM "151189">  <!ENTITY BUG-URL "https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&percnt;20…! ercnt;3A&percnt;0D&percnt;0A1.&percnt;0D&percnt;0A2.&percnt;0D&percnt;0A3.&percnt;0D&percnt;0A&percnt;20&percnt;20&percnt;0D&percnt;0AActual&percnt;20results&percnt;3A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0AExpected&percnt;20results&percnt;3A&percnt;0D&percnt;0A&percnt;0D&percnt;0A&percnt;0D&percnt;0AAdditional&percnt;20info&percnt;3A&status_whiteboard=&keywords=&issuetrackers=&dependson=&blocked=151189&percnt;2C&percnt;20168083&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text&percnt;2Fplain&contenttypeentry=&maketemplate=Remember&percnt;20values&percnt;20as&percnt;20bookmarkable&percnt;20template&form_name=enter_bug">  <!ENTITY TINY-BUG-URL "http://tinyurl.com/byvk2"> ]> <article id="index" lang="en"> - <articleinfo> - <title>&FC; &LOCALVER; Release Notes</title> - <copyright> - <year>2006</year> - <holder>&FORMAL-RHI;</holder> - </copyright> - &LEGALNOTICE-RELNOTES; - </articleinfo> + + &FDP-INFO; &WELCOME; &OVERVIEW; Index: RELEASE-NOTES-it.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- RELEASE-NOTES-it.xml 12 Jan 2006 06:16:24 -0000 1.8 +++ RELEASE-NOTES-it.xml 24 Jan 2006 22:10:39 -0000 1.9 @@ -47,6 +47,8 @@  + <!ENTITY FDP-INFO SYSTEM "fdp-info-it.xml" > + <!ENTITY LOCALVER "5 test2">   <!ENTITY DOCNAME "RELEASE-NOTES"> @@ -65,14 +67,8 @@ ]> <article id="index" lang="it"> - <articleinfo> - <title>Note di rilascio per &FC; &LOCALVER;</title> - <copyright> - <year>2006</year> - <holder>&FORMAL-RHI;</holder> - </copyright> - &LEGALNOTICE-RELNOTES; - </articleinfo> + + &FDP-INFO; &WELCOME; &OVERVIEW; Index: RELEASE-NOTES-ja_JP.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-ja_JP.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- RELEASE-NOTES-ja_JP.xml 11 Jan 2006 16:05:00 -0000 1.4 +++ RELEASE-NOTES-ja_JP.xml 24 Jan 2006 22:10:39 -0000 1.5 @@ -47,6 +47,8 @@  + <!ENTITY FDP-INFO SYSTEM "fdp-info-ja_JP.xml" > + <!ENTITY LOCALVER "5 test2">  <!ENTITY DOCNAME "RELEASE-NOTES"> <!ENTITY DOCVERSION "&FCX;&DISTROVER;"> @@ -64,15 +66,8 @@ ]> <article id="index" lang="ja"> - <articleinfo> - <title>&FC; &LOCALVER; ��</title> - <copyright> - <year>2006</year> - <holder>&FORMAL-RHI;</holder> - </copyright> - &LEGALNOTICE-RELNOTES; - </articleinfo> - + + &FDP-INFO; &WELCOME; &OVERVIEW; Index: RELEASE-NOTES-pa.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-pa.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- RELEASE-NOTES-pa.xml 9 Jan 2006 10:10:16 -0000 1.1 +++ RELEASE-NOTES-pa.xml 24 Jan 2006 22:10:39 -0000 1.2 @@ -47,6 +47,8 @@  + <!ENTITY FDP-INFO SYSTEM "fdp-info-pa.xml" > + <!ENTITY DOCNAME "RELEASE-NOTES"> <!ENTITY DOCVERSION "&FCX;&DISTROVER;"> <!ENTITY DOCDATE "2005-11-24-T23:10+0000"> @@ -71,18 +73,8 @@ ]> <article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final"> - <articleinfo> - <title ->&DISTRO; &DISTROVER; �� (��)</title> - <copyright> - <year ->2005</year> - <holder ->&FORMAL-RHI;</holder> - </copyright> - &LEGALNOTICE-RELNOTES; - </articleinfo> - + + &FDP-INFO; &WELCOME; &OVERVIEW; Index: RELEASE-NOTES-ru.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-ru.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- RELEASE-NOTES-ru.xml 15 Jan 2006 15:59:25 -0000 1.4 +++ RELEASE-NOTES-ru.xml 24 Jan 2006 22:10:39 -0000 1.5 @@ -47,6 +47,8 @@  + <!ENTITY FDP-INFO SYSTEM "fdp-info-ru.xml" > + <!ENTITY LOCALVER "5 test2">   <!ENTITY DOCNAME "RELEASE-NOTES"> @@ -65,14 +67,8 @@ ]> <article id="index" lang="en"> - <articleinfo> - <title>&FC; &LOCALVER; �� </title> - <copyright> - <year>2006</year> - <holder>&FORMAL-RHI;</holder> - </copyright> - &LEGALNOTICE-RELNOTES; - </articleinfo> + + &FDP-INFO; &WELCOME; &OVERVIEW; Index: RELEASE-NOTES-zh_CN.xml =================================================================== RCS file: /cvs/docs/release-notes/RELEASE-NOTES-zh_CN.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- RELEASE-NOTES-zh_CN.xml 13 Jan 2006 15:31:37 -0000 1.6 +++ RELEASE-NOTES-zh_CN.xml 24 Jan 2006 22:10:39 -0000 1.7 @@ -42,7 +42,11 @@ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-zh_CN.ent"> %FEDORA-ENTITIES-EN; -<!ENTITY LOCALVER "5 test2"> + + + <!ENTITY FDP-INFO SYSTEM "fdp-info-zh_CN.xml" > + +<!ENTITY LOCALVER "5 test2"> <!ENTITY DOCNAME "RELEASE-NOTES"> <!ENTITY DOCVERSION "&FCX;&DISTROVER;"> <!ENTITY DOCDATE "2005-01-10-T16:20+0800"> @@ -57,11 +61,7 @@ ]> <article id="index" lang="zh_CN"> - <articleinfo> - <title>&FC; &LOCALVER; ��</title> - <copyright> - <year>2006</year> - <holder>&FORMAL-RHI;</holder> - </copyright> - &LEGALNOTICE-RELNOTES; - </articleinfo> &WELCOME; &OVERVIEW; &LEGALNOTICE-SECTION; &FEEDBACK; &INTRO; &INSTALLER; &ARCH-SPECIFIC; &NETWORKING; &PACKAGE-NOTES; &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW;</article> + + &FDP-INFO; + + &WELCOME; &OVERVIEW; &LEGALNOTICE-SECTION; &FEEDBACK; &INTRO; &INSTALLER; &ARCH-SPECIFIC; &NETWORKING; &PACKAGE-NOTES; &LEGACY; &PACKAGE-CHANGES; &PROJECT-OVERVIEW;</article>

1 0

release-notes rpm-info.xml,1.1,1.2
by fedora-docs-commits＠redhat.com 24 Jan '06

24 Jan '06

Author: jtr Update of /cvs/docs/release-notes In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10575 Modified Files: rpm-info.xml Log Message: Fleshed out to allow RPM building to work. Index: rpm-info.xml =================================================================== RCS file: /cvs/docs/release-notes/rpm-info.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- rpm-info.xml 17 Jan 2006 02:12:20 -0000 1.1 +++ rpm-info.xml 24 Jan 2006 22:05:25 -0000 1.2 @@ -1,4 +1,4 @@ -<?xml version="1.0" encoding="UTF-8" standalone="yes"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd"> @@ -6,7 +6,9 @@ <colophon> <worker id="quaid" wholename="Karsten Wade" email="kwade(a)redhat.com" surname="Wade" firstname="Karsten" initials="quaid"/> + <worker email="Tommy.Reynolds(a)MegaCoder.com" firstname="Tommy" id="megacoder" initials="JTR" surname="Reynolds" wholename="Tommy Reynolds"/> </colophon> + <author worker="quaid"/> <license> <rights>GNU FDL</rights> <version>1.0</version> @@ -38,5 +40,14 @@ <desc></desc> </translation> </titles> - <changelog/> + <changelog order="newest-first"> + <revision date="Tue Jan 24 2006" number="0" role="rpm"> + <author worker="megacoder"/> + <details>Dummy entry to make rpm building work; please remove</details> + </revision> + <revision date="Tue Jan 24 2006" number="0.0.0" role="doc"> + <author worker="quaid"/> + <details>Dummy entry to make rpm building work; please remove</details> + </revision> + </changelog> </rpm-info>

1 0

release-notes Makefile,1.16,1.17
by fedora-docs-commits＠redhat.com 24 Jan '06

24 Jan '06

Author: jtr Update of /cvs/docs/release-notes In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10502 Modified Files: Makefile Log Message: Removed "make rpm" cruft. Index: Makefile =================================================================== RCS file: /cvs/docs/release-notes/Makefile,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- Makefile 16 Jan 2006 22:01:39 -0000 1.16 +++ Makefile 24 Jan 2006 22:01:51 -0000 1.17 @@ -12,19 +12,34 @@ # LANGUAGES = en it ja_JP zh_CN ru #ja_JP # uncomment languages when you have all the same - # fies localized as are listed in XMLEXTRAFILES + # files localized as are listed in XMLEXTRAFILES DOCBASE = RELEASE-NOTES define XMLEXTRAFILES_template -XMLEXTRAFILES-$(1)=ArchSpecific-$(1).xml ArchSpecificPPC-$(1).xml ArchSpecificx86_64-$(1).xml ArchSpecificx86-$(1).xml BackwardsCompatibility-$(1).xml Colophon-$(1).xml DatabaseServers-$(1).xml Desktop-$(1).xml DevelopmentTools-$(1).xml DevelopmentToolsGCC-$(1).xml DevelopmentToolsJava-$(1).xml Entertainment-$(1).xml Feedback-$(1).xml FileServers-$(1).xml FileSystems-$(1).xml I18n-$(1).xml Installer-$(1).xml Introduction-$(1).xml Kernel-$(1).xml Legacy-$(1).xml Multimedia-$(1).xml Networking-$(1).xml OverView-$(1).xml PackageChanges-$(1).xml PackageNotes-$(1).xml PackageNotesJava-$(1).xml Printing-$(1).xml ProjectOverview-$(1).xml RELEASE-NOTES-$(1).xml Samba-$(1).xml Security-$(1).xml SecuritySELinux-$(1).xml ServerTools-$(1).xml SystemDaemons-$(1).xml WebServers-$(1).xml Welcome-$(1).xml Xorg-$(1).xml +XMLEXTRAFILES-$(1)=ArchSpecific-$(1).xml ArchSpecificPPC-$(1).xml \ + ArchSpecificx86-$(1).xml ArchSpecificx86_64-$(1).xml \ + BackwardsCompatibility-$(1).xml Colophon-$(1).xml \ + DatabaseServers-$(1).xml Desktop-$(1).xml \ + DevelopmentTools-$(1).xml DevelopmentToolsGCC-$(1).xml \ + DevelopmentToolsJava-$(1).xml Entertainment-$(1).xml \ + Feedback-$(1).xml FileServers-$(1).xml FileSystems-$(1).xml \ + I18n-$(1).xml Installer-$(1).xml Introduction-$(1).xml \ + Kernel-$(1).xml Legacy-$(1).xml Multimedia-$(1).xml \ + Networking-$(1).xml OverView-$(1).xml PackageChanges-$(1).xml \ + PackageNotes-$(1).xml PackageNotesJava-$(1).xml \ + Printing-$(1).xml ProjectOverview-$(1).xml \ + RELEASE-NOTES-$(1).xml Samba-$(1).xml Security-$(1).xml \ + SecuritySELinux-$(1).xml ServerTools-$(1).xml \ + SystemDaemons-$(1).xml WebServers-$(1).xml Welcome-$(1).xml \ + Xorg-$(1).xml endef $(foreach LANG,${LANGUAGES},$(eval $(call XMLEXTRAFILES_template,${LANG}))) # -###################################################### +######################################################################## include ../docs-common/Makefile.common -###################################################### +######################################################################## # # If you want to add additional steps to any of the # targets defined in "Makefile.common", be sure to use @@ -34,68 +49,4 @@ # line: #${DOCBASE}-en/index.html:: # echo FINISHED AT LAST -###################################################### -# Some packaging specific vars -VERSION=$(shell grep BOOKID $(DOCBASE)-en.xml | sed 's/<!ENTITY BOOKID "[^0-9\.]\+//' | sed 's/ .\+//') -DATE=${shell grep BOOKID $(DOCBASE)-en.xml | sed 's/.\+(//' | sed 's/).\+//' } -NOW=$(shell date +"%a %b %e %Y") -SPECIN=../docs-common/packaging/fedora-doc.spec.in.common -OMFIN=../docs-common/packaging/fedora-doc.omf.in.common -DESKTOPIN=../docs-common/packaging/fedora-doc.desktop.in.common -DOCSPEC=$(PWD)/SPECS/$(DOCBASE).spec -DOCOMF=$(PWD)/SOURCES/fedora-doc-$(DOCBASE)-C.omf -DOCDESKTOP=$(PWD)/SOURCES/fedora-doc-$(DOCBASE).desktop -DOCSRCTAR=$(PWD)/SOURCES/$(DOCBASE)-$(VERSION).src.tar.gz -TITLE=$(shell ../docs-common/packaging/titlegrab.py $(DOCBASE)-en.xml | sed 's/^ \+//') -###################################################### -# Some RPM flags... -###################################################### -RPMFLAGS=--define "docbase $(DOCBASE)" --define "version $(VERSION)" --define "_topdir $(PWD)" -###################################################### - - -clean:: - rm -rf fedora-doc-$(DOCBASE)*.rpm - - -rpm: clean -# -# Make RPM-compliant tarball of source XML and other stuff - mkdir $(DOCBASE)-$(VERSION) - find . -maxdepth 1 -type f ! $ -name '*~' -o -name 'Makefile*' $ \ - | cpio -pamdv $(DOCBASE)-$(VERSION) - find . -maxdepth 1 -type d ! $ -name '$(DOCBASE)-$(VERSION)' \ - -o -name 'CVS' -o -name '*~' -o -name '$(DOCBASE)*' $ \ - | cpio -pamdv $(DOCBASE)-$(VERSION) -# -# Make RPM build tree; don't rely on local user's setup - mkdir -p {BUILD,RPMS/noarch,SOURCES,SPECS,SRPMS} - tar -zcvf $(DOCSRCTAR) $(DOCBASE)-$(VERSION) - rm -rf $(DOCBASE)-$(VERSION)/ -# -# Make rpmlint happy with a changelog entry -# FIXME: Maybe more magic would make this stickier; pity -# I'm no magician... - sed 's/$%changelog$/\1\n* $(NOW) Fedora Docs Project <fedora-docs-list(a)redhat.com> - $(VERSION)-1\n- Update to version $(VERSION)\n/' \ - $(SPECIN) > $(DOCSPEC) -# -# Fill in files -# FIXME: Needs to be multiplexed for LANGUAGES (see above) - cp $(OMFIN) $(DOCOMF) - cp $(DESKTOPIN) $(DOCDESKTOP) - sed -i 's/@VERSION@/$(VERSION)/g' $(DOCOMF) - sed -i 's/@DATE@/$(DATE)/g' $(DOCOMF) - sed -i 's/@TITLE@/$(TITLE)/g' $(DOCOMF) - sed -i 's/@DOCBASE@/$(DOCBASE)/g' $(DOCOMF) - sed -i 's/@VERSION@/$(VERSION)/g' $(DOCDESKTOP) - sed -i 's/@DATE@/$(DATE)/g' $(DOCDESKTOP) - sed -i 's/@TITLE@/$(TITLE)/g' $(DOCDESKTOP) - sed -i 's/@DOCBASE@/$(DOCBASE)/g' $(DOCDESKTOP) -# -# Do the build... -# - rpmbuild -bb $(RPMFLAGS) $(DOCSPEC) - mv RPMS/noarch/*.rpm . - rpmbuild --clean --rmsource $(RPMFLAGS) $(DOCSPEC) - rm -rf {BUILD,RPMS,SOURCES,SPECS,SRPMS} - rm -rf $(DOCBASE)-$(VERSION) +########################################################################

1 0

install-guide fedora-install-guide-zh_CN.xml,1.3,1.4
by fedora-docs-commits＠redhat.com 24 Jan '06

24 Jan '06

Author: pfrields Update of /cvs/docs/install-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8697 Modified Files: fedora-install-guide-zh_CN.xml Log Message: Fix bad entity Index: fedora-install-guide-zh_CN.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-zh_CN.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- fedora-install-guide-zh_CN.xml 17 Dec 2005 12:22:01 -0000 1.3 +++ fedora-install-guide-zh_CN.xml 24 Jan 2006 21:29:45 -0000 1.4 @@ -6,7 +6,7 @@ <!ENTITY DOCLANG "en"> <!ENTITY DOCVERSION "1.0.8"> <!ENTITY DOCDATE "2005-12-14"> -<!ENTITY BOOKID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)"> +<!ENTITY DOCID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)"> <!ENTITY BUG-NUM "129911"> <!ENTITY FCLOCALVER "5"> <!ENTITY DOCLOCALVER "1.0.8">

1 0

install-guide fedora-install-guide-adminoptions-en.xml, 1.6, 1.7 fedora-install-guide-en.xml, 1.38, 1.39 fedora-install-guide-firstboot-en.xml, 1.16, 1.17 fedora-install-guide-nextsteps-en.xml, 1.10, 1.11 fedora-install-guide-techref-en.xml, 1.4, 1.5 fedora-install-guide-timezone-en.xml, 1.10, 1.11 rpm-info.xml, 1.3, 1.4
by fedora-docs-commits＠redhat.com 23 Jan '06

23 Jan '06

Author: elliss Update of /cvs/docs/install-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24132 Modified Files: fedora-install-guide-adminoptions-en.xml fedora-install-guide-en.xml fedora-install-guide-firstboot-en.xml fedora-install-guide-nextsteps-en.xml fedora-install-guide-techref-en.xml fedora-install-guide-timezone-en.xml rpm-info.xml Log Message: - Amended Timezone section for new city selector map. - Added text on soundcard options to First Boot section. - Added SSH note and information on opening additional firewall ports to First Boot section. - Revised notes on procedure for software update. - Merged Documentation and Community support sections in Next Steps. - Restructured Management Options section. - Added more to Technical Reference section. Index: fedora-install-guide-adminoptions-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- fedora-install-guide-adminoptions-en.xml 16 Jan 2006 00:23:00 -0000 1.6 +++ fedora-install-guide-adminoptions-en.xml 23 Jan 2006 23:24:09 -0000 1.7 @@ -1,289 +1,254 @@  <chapter id="ch-admin-options"> - <title>Appendix: Management Options</title> + <title>Appendix: Boot Options</title> <para> The &FED; installation system includes a range of options and - functions for administrators. + functions for administrators. To use boot options, enter + <userinput>linux <replaceable>option</replaceable></userinput> at + the + <prompt>boot:</prompt> + prompt. </para> - <section id="sn-bootoptions"> - <title>Boot Options</title> + <para> + If you specify more than one option, separate each of the options by + a single space. For example: + </para> +<screen> +<userinput>linux <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</replaceable></userinput> +</screen> + <section id="sn-bootoptions-installer"> + <title>Configuring the Installation System</title> <para> - To use boot options, enter <userinput>linux - <replaceable>option</replaceable></userinput> at the + You may configure the installation system without affecting the + final &FED; system. The <prompt>boot:</prompt> - prompt. + prompt enables you to specify a number of settings for the + installation system. These include: </para> + <itemizedlist> + <listitem> + <para> + Display resolution + </para> + </listitem> + <listitem> + <para> + Interface type + </para> + </listitem> + <listitem> + <para> + Installation method + </para> + </listitem> + <listitem> + <para> + Network settings + </para> + </listitem> + </itemizedlist> + <para> - If you specify more than one option, separate each of the options - by a single space. For example: + You may force the installation system to use the lowest possible + screen resolution (640x480) with the <option>lowres</option> + option. To use a specific display resolution, enter + <option>resolution=<replaceable>setting</replaceable></option> as + a boot option. For example, to set the display resolution to + 1024x768, enter: </para> <screen> -<userinput>linux <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</replaceable></userinput> -</screen> - <section id="sn-mode-rescue"> - <title>Booting Your Computer with Rescue Mode</title> - - <para> - You may use the first installation disc to boot a command-line - Linux system, without installing &FED; on the computer. This - rescue system may access the drives on your computer. Rescue - mode enables you to use the utilities and functions of a running - system to modify or repair an installed system. - </para> - - <para> - To load the rescue mode, enter: - </para> -<screen> - <userinput>linux rescue</userinput> -</screen> - <para> - Specify the language, keyboard layout and network settings for - the rescue system with the screens that follow. - </para> - - <para> - <remark role="FIXME">Add a note that the boot and rescue CDs also have this facility. - </remark> - </para> - </section> - - <section id="sn-bootoptions-installer"> - <title>Configuring the Installation System</title> - - <para> - You may configure the installation system without affecting the - final &FED; system. The - <prompt>boot:</prompt> - prompt enables you to specify a number of settings for the - installation system. These include: - </para> - - <itemizedlist> - <listitem> - <para> - Display resolution - </para> - </listitem> - <listitem> - <para> - Interface type - </para> - </listitem> - <listitem> - <para> - Installation method - </para> - </listitem> - <listitem> - <para> - Network settings - </para> - </listitem> - </itemizedlist> - - <para> - You may force the installation system to use the lowest possible - screen resolution (640x480) with the <option>lowres</option> - option. To use a specific display resolution, enter - <option>resolution=<replaceable>setting</replaceable></option> - as a boot option. For example, to set the display resolution to - 1024x768, enter: - </para> -<screen> <userinput>linux resolution=<replaceable>1024x768</replaceable></userinput> </screen> - <para> - To run the installation process in <option>text</option> mode, - enter: - </para> + <para> + To run the installation process in <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. - </para> + <para> + To enable support for a serial console, enter + <option>serial</option> as an additional option. + </para> - <para> - Use the <option>askmethod</option> option to display additional - menus that enable you to specify the installation method network - settings. You may also configure the installation method and - network settings at the - <prompt>boot:</prompt> - prompt itself. - </para> + <para> + Use the <option>askmethod</option> option to display additional + menus that enable you to specify the installation method network + settings. You may also configure the installation method and + network settings at the + <prompt>boot:</prompt> + prompt itself. + </para> - <para> - To specify the installation method from the - <prompt>boot:</prompt> - prompt, use the <option>method</option> option. Refer to - <xref linkend="tb-installmethods"/> for the supported - installation methods. - </para> - <table id="tb-installmethods"> - <title>Installation Methods</title> - <tgroup cols="2"> - <colspec colnum="1" colname="Installation Method"/> - <colspec colnum="2" colname="Option Format"/> - <thead> - <row> - <entry>Installation Method</entry> - <entry>Option Format</entry> - </row> - </thead> - <tbody> - <row> - <entry> + <para> + To specify the installation method from the + <prompt>boot:</prompt> + prompt, use the <option>method</option> option. Refer to + <xref linkend="tb-installmethods"/> for the supported installation + methods. + </para> + <table id="tb-installmethods"> + <title>Installation Methods</title> + <tgroup cols="2"> + <colspec colnum="1" colname="Installation Method"/> + <colspec colnum="2" colname="Option Format"/> + <thead> + <row> +<entry>Installation Method</entry> +<entry>Option Format</entry> + </row> + </thead> + <tbody> + <row> +<entry> <para> CD or DVD drive </para> </entry> - <entry> +<entry> <para> <option>method=<replaceable>cdrom</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Hard Drive </para> </entry> - <entry> +<entry> <para> <option>method=<replaceable>hd://device/</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> HTTP Server </para> </entry> - <entry> +<entry> <para> <option>method=<replaceable>http://server.example.com/directory/</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> FTP Server </para> </entry> - <entry> +<entry> <para> <option>method=<replaceable>ftp://server.example.com/directory/</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> NFS Server </para> </entry> - <entry> +<entry> <para> <option>method=<replaceable>nfs:server.example.com:/directory/</replaceable></option> </para> </entry> - </row> - </tbody> - </tgroup> - </table> - <para> - By default, the installation system uses DHCP to automatically - obtain the correct network settings. To manually configure the - network settings yourself, either enter them in the - <guilabel>Configure TCP/IP</guilabel> screen, or at the - <prompt>boot:</prompt> - prompt. You may specify the <option>ip</option> address, - <option>netmask</option>, <option>gateway</option>, and - <option>dns</option> server settings for the installation system - at the prompt. If you specify the network configuration at the - <prompt>boot:</prompt> - prompt, these settings are used for the installation process, - and the <guilabel>Configure TCP/IP</guilabel> screen does not - appear. - </para> + </row> + </tbody> + </tgroup> + </table> + <para> + By default, the installation system uses DHCP to automatically + obtain the correct network settings. To manually configure the + network settings yourself, either enter them in the + <guilabel>Configure TCP/IP</guilabel> screen, or at the + <prompt>boot:</prompt> + prompt. You may specify the <option>ip</option> address, + <option>netmask</option>, <option>gateway</option>, and + <option>dns</option> server settings for the installation system + at the prompt. If you specify the network configuration at the + <prompt>boot:</prompt> + prompt, these settings are used for the installation process, and + the <guilabel>Configure TCP/IP</guilabel> screen does not appear. + </para> - <para> - This example configures the network settings for an installation - system that uses the IP address 192.168.1.10: - </para> + <para> + This example configures the network settings for an installation + system that uses the IP address + <systemitem class="ipaddress">192.168.1.10</systemitem>: + </para> <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> - </section> - - <section id="sn-remote-installation"> - <title>Enabling Remote Access to the Installation System</title> + </section> + <section id="sn-remote-installation"> + <title>Enabling Remote Access to the Installation System</title>  + <para> + You may access either graphical or text interfaces for the + installation system from any other system. Access to a text mode + 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 + 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. + </para> + <tip> + <title>Installing a VNC Client on &FED;</title> <para> - You may access either graphical or text interfaces for the - installation system from any other system. Access to a text mode - 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 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. - </para> - <tip> - <title>Installing a VNC Client on &FED;</title> - <para> - &FED; includes <application>vncviewer</application>, the - client provided by the developers of VNC. To obtain - <application>vncviewer</application>, install the - <filename>vnc</filename> package. - </para> - </tip> - <para> - The installation system supports two types of VNC connection. - You 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. + &FED; includes <application>vncviewer</application>, the client + provided by the developers of VNC. To obtain + <application>vncviewer</application>, install the + <filename>vnc</filename> package. </para> + </tip> + <para> + The installation system supports two types of VNC connection. You + 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. + </para> - <para> - To enable remote graphical access to the installation system, - enter two options at the prompt: - </para> + <para> + To enable remote graphical access to the installation system, + enter two options at the prompt: + </para> <screen> <userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable></userinput> </screen> - <para> - The <option>vnc</option> option enables the VNC service. The - <option>vncpassword</option> option sets a password for remote - access. The example shown above sets the password as - <systemitem>qwerty</systemitem>. - </para> - - <note> - <title>VNC Passwords</title> + <para> + The <option>vnc</option> option enables the VNC service. The + <option>vncpassword</option> option sets a password for remote + access. The example shown above sets the password as + <systemitem>qwerty</systemitem>. + </para> - <para> - The VNC password must be at least six characters long. - </para> - </note> + <note> + <title>VNC Passwords</title> <para> - Specify the language, keyboard layout and network settings for - the installation system with the screens that follow. You may - then access the graphical interface through a VNC client. The - installation system displays the correct connection setting for - the VNC client: + The VNC password must be at least six characters long. </para> + </note> + + <para> + Specify the language, keyboard layout and network settings for the + installation system with the screens that follow. You may then + access the graphical interface through a VNC client. The + installation system displays the correct connection setting for + the VNC client: + </para> <screen> <computeroutput><![CDATA[Starting VNC... The VNC server is now running. @@ -291,581 +256,646 @@ Starting graphical installation... Press <enter> for a shell]]></computeroutput> </screen> - <para> - You may then login to the installation system with a VNC client. - To run the <application>vncviewer</application> client on &FED;, - choose <menuchoice> <guimenu>Applications</guimenu> - <guisubmenu>Accessories</guisubmenu><guimenuitem>VNC - Viewer</guimenuitem></menuchoice>, or type the command - <application>vncviewer</application> in a terminal window. Enter - the server and display number in the <guilabel>VNC - Server</guilabel> dialog. For the example above, the - <guilabel>VNC Server</guilabel> is - <systemitem>computer.mydomain.com:1</systemitem>. - </para> + <para> + You may then login to the installation system with a VNC client. + To run the <application>vncviewer</application> client on &FED;, + choose <menuchoice> <guimenu>Applications</guimenu> + <guisubmenu>Accessories</guisubmenu><guimenuitem>VNC + Viewer</guimenuitem></menuchoice>, or type the command + <application>vncviewer</application> in a terminal window. Enter + the server and display number in the <guilabel>VNC + Server</guilabel> dialog. For the example above, the <guilabel>VNC + Server</guilabel> is + <systemitem>computer.mydomain.com:1</systemitem>. + </para> - <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: - </para> + <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: + </para> <screen> <userinput>vncviewer -listen</userinput> </screen> - <note> - <title>Firewall Reconfiguration Required</title> - - <para> - By default, the <application>vncviewer</application> utility - listens on TCP port <systemitem>5500</systemitem>. To update - the &FED; firewall configuration to permit connections to this - port from other systems, choose <menuchoice> - <guimenu>System</guimenu> - <guisubmenu>Administration</guisubmenu> <guimenuitem>Security - Level and Firewall</guimenuitem> </menuchoice>, enter - <userinput>5500:tcp</userinput> in the <guilabel>Other - ports:</guilabel> field, and select <guilabel>OK</guilabel>. - </para> - </note> + <note> + <title>Firewall Reconfiguration Required</title> <para> - Once the listening client is active, start the installation - system and set the VNC options at the - <prompt>boot:</prompt> - prompt. In addition to <option>vnc</option> and - <option>vncpassword</option> options, use the - <option>vncconnect</option> option to specify the name or IP - address of the system that has the listening client. To specify - the TCP port for the listener, add a colon and the port number - to the name of the system. + By default, the <application>vncviewer</application> utility + listens on TCP port <systemitem>5500</systemitem>. To update the + &FED; firewall configuration to permit connections to this port + from other systems, choose <menuchoice> + <guimenu>System</guimenu> + <guisubmenu>Administration</guisubmenu> <guimenuitem>Security + Level and Firewall</guimenuitem> </menuchoice>, enter + <userinput>5500:tcp</userinput> in the <guilabel>Other + ports:</guilabel> field, and select <guilabel>OK</guilabel>. </para> + </note> - <para> - For example, to connect to a VNC client on the system - <systemitem + <para> + Once the listening client is active, start the installation system + and set the VNC options at the + <prompt>boot:</prompt> + prompt. In addition to <option>vnc</option> and + <option>vncpassword</option> options, use the + <option>vncconnect</option> option to specify the name or IP + address of the system that has the listening client. To specify + the TCP port for the listener, add a colon and the port number to + the name of the system. + </para> + + <para> + For example, to connect to a VNC client on the system + <systemitem class="systemname">desktop.mydomain.com</systemitem> - on the port <systemitem>5500</systemitem>, enter the following - at the - <prompt>boot:</prompt> - prompt: - </para> + on the port <systemitem>5500</systemitem>, enter the following at + the + <prompt>boot:</prompt> + prompt: + </para> <screen> <userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput> </screen> - <para> - To enable remote access to a text mode installation, use the - <option>telnet</option> option at the - <prompt>boot:</prompt> - prompt: - </para> + <para> + To enable remote access to a text mode installation, use the + <option>telnet</option> option at the + <prompt>boot:</prompt> + prompt: + </para> <screen> <userinput>linux telnet</userinput> </screen> - <para> - You may then connect to the installation system with the - <command>telnet</command> utility. The <command>telnet</command> - command requires the name or IP address of the installation - system: - </para> + <para> + You may then connect to the installation system with the + <command>telnet</command> utility. The <command>telnet</command> + command requires the name or IP address of the installation + system: + </para> <screen> <userinput>telnet computer.mydomain.com</userinput> </screen> - <para> - <remark role="FIXME">No password option for telnet ? + <para> + <remark role="FIXME">No password option for telnet ? </remark> - </para> - </section> - - <section id="sn-automating-installation"> - <title>Automating the Installation with Kickstart</title> + </para> + </section> + <section id="sn-automating-installation"> + <title>Automating the Installation with Kickstart</title> + <para> + A <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. + </para> + <tip> + <title>Every Installation Produces a Kickstart File</title> <para> - A <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. - </para> - <tip> - <title>Every Installation Produces a Kickstart File</title> - <para> - The &FED; installation process automatically writes a - Kickstart file that contains the settings for the installed - system. This file is always saved as - <filename>/root/anaconda-ks.cfg</filename>. You may use this - file to repeat the installation with identical settings, or - modify copies to specify settings for other systems. - </para> - </tip> - <para> - &FED; includes a graphical application that enables you to - create and modify Kickstart files by selecting the options that - you require. Use the package - <filename>system-config-kickstart</filename> to install this - utility. To load the &FED; Kickstart editor, choose <menuchoice> - <guimenu>Applications</guimenu> <guisubmenu>System - Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>. + The &FED; installation process automatically writes a Kickstart + file that contains the settings for the installed system. This + file is always saved as + <filename>/root/anaconda-ks.cfg</filename>. You may use this + file to repeat the installation with identical settings, or + modify copies to specify settings for other systems. </para> + </tip> + <para> + &FED; includes a graphical application that enables you to create + and modify Kickstart files by selecting the options that you + require. Use the package + <filename>system-config-kickstart</filename> to install this + utility. To load the &FED; Kickstart editor, choose <menuchoice> + <guimenu>Applications</guimenu> <guisubmenu>System + Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>. + </para> - <para> - Kickstart files list installation settings in plain-text, with - one option per line. This format enables you to modify your - Kickstart files with any text editor, and write scripts or - applications that generate custom Kickstart files for your - systems. - </para> + <para> + Kickstart files list installation settings in plain-text, with one + option per line. This format enables you to modify your Kickstart + files with any text editor, and write scripts or applications that + generate custom Kickstart files for your systems. + </para> - <para> - To automate the installation process with a Kickstart file, use - the <option>ks</option> option to specify the name and location - of the file: - </para> + <para> + To automate the installation process with a Kickstart file, use + the <option>ks</option> option to specify the name and location of + the file: + </para> <screen> <userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput> </screen> - <para> - You may use Kickstart files that are held on either removable - storage, or a hard drive, or located on a network server. Refer - to <xref linkend="tb-kssources"/> for the supported Kickstart - sources. - </para> - <table id="tb-kssources"> - <title>Kickstart Sources</title> - <tgroup cols="2"> - <colspec colnum="1" colname="Kickstart Source"/> - <colspec colnum="2" colname="Option Format"/> - <thead> - <row> - <entry>Kickstart Source</entry> - <entry>Option Format</entry> - </row> - </thead> - <tbody> - <row> - <entry> + <para> + You may use Kickstart files that are held on either removable + storage, or a hard drive, or located on a network server. Refer to + <xref linkend="tb-kssources"/> for the supported Kickstart + sources. + </para> + <table id="tb-kssources"> + <title>Kickstart Sources</title> + <tgroup cols="2"> + <colspec colnum="1" colname="Kickstart Source"/> + <colspec colnum="2" colname="Option Format"/> + <thead> + <row> +<entry>Kickstart Source</entry> +<entry>Option Format</entry> + </row> + </thead> + <tbody> + <row> +<entry> <para> CD or DVD drive </para> </entry> - <entry> +<entry> <para> <option>ks=<replaceable>cdrom:/directory/ks.cfg</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Hard Drive </para> </entry> - <entry> +<entry> <para> <option>ks=<replaceable>hd:/device/directory/ks.cfg</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Other Device </para> </entry> - <entry> +<entry> <para> <option>ks=<replaceable>file:/device/directory/ks.cfg</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> HTTP Server </para> </entry> - <entry> +<entry> <para> <option>ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> FTP Server </para> </entry> - <entry> +<entry> <para> <option>ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> NFS Server </para> </entry> - <entry> +<entry> <para> <option>ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable></option> </para> </entry> - </row> - </tbody> - </tgroup> - </table> - <para> - To obtain a Kickstart file from a script or application on a Web - server, specify the URL of the application with the - <option>ks=</option> option. If you add the option - <option>kssendmac</option>, the request also sends HTTP headers - to the Web application. Your application may use these headers - to identify the computer. This line sends a request with headers - to the application - <wordasword>http://server.example.com/kickstart.cgi</wordasword>: - </para> + </row> + </tbody> + </tgroup> + </table> + <para> + To obtain a Kickstart file from a script or application on a Web + server, specify the URL of the application with the + <option>ks=</option> option. If you add the option + <option>kssendmac</option>, the request also sends HTTP headers to + the Web application. Your application may use these headers to + identify the computer. This line sends a request with headers to + the application + <wordasword>http://server.example.com/kickstart.cgi</wordasword>: + </para> <screen> <userinput>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</userinput> </screen> - </section> + </section> + <section id="sn-bootoptions-hardware"> + <title>Enhancing Hardware Support</title> - <section id="sn-bootoptions-hardware"> - <title>Hardware Support</title> + <para> + By default, &FED; attempts to automatically detect and configure + support for all of the components of your computer. &FED; supports + the majority of hardware in common use with the software + <firstterm>drivers</firstterm> that are included with the + operating system. To enable a &FED; system to support more devices + you may supply additional drivers during the installation process, + or at a later time. + </para> + <section id="sn-bootoptions-driverdisks"> + <title>Adding Hardware Support with Driver Disks</title> + <para> - By default, &FED; attempts to automatically detect and configure - support for all of the components of your computer. &FED; - supports the majority of hardware in common use with the - software <firstterm>drivers</firstterm> that are included with - the operating system. To enable a &FED; system to support more - devices you may supply additional drivers during the - installation process, or at a later time. + The installation system may load drivers from disks, pen drives, + or network servers to configure support for new devices. After + the installation is complete, remove any driver disks and store + them for later use. </para> - <section id="sn-bootoptions-driverdisks"> - <title>Adding Hardware Support with Driver Disks</title> - - <para> - The installation system may load drivers from disks, pen - drives, or network servers to configure support for new - devices. After the installation is complete, remove any driver - disks and store them for later use. - </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. - </para> - - <note> - <title>Driver Disks Supplied as Zipped Files</title> + <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. + </para> - <para> - Driver disk images may be distributed as compressed - archives, or zip files. For identification, the names of zip - files include the extensions <filename>.zip</filename>, or - <filename>.tar.gz</filename>. To extract the contents of a - zipped file with a &FED; system, choose <menuchoice> - <guimenu>Applications</guimenu> <guisubmenu>System - Tools</guisubmenu><guimenuitem>Archive - Manager</guimenuitem></menuchoice>. - </para> - </note> + <note> + <title>Driver Disks Supplied as Zipped Files</title> <para> - To format a disk or pen drive with an image file, use the - <command>dd</command> utility. For example, to prepare a - diskette with the image file <filename>drivers.img</filename>, - enter this command in a terminal window: + Driver disk images may be distributed as compressed archives, + or zip files. For identification, the names of zip files + include the extensions <filename>.zip</filename>, or + <filename>.tar.gz</filename>. To extract the contents of a + zipped file with a &FED; system, choose <menuchoice> + <guimenu>Applications</guimenu> <guisubmenu>System + Tools</guisubmenu><guimenuitem>Archive + Manager</guimenuitem></menuchoice>. </para> + </note> + + <para> + To format a disk or pen drive with an image file, use the + <command>dd</command> utility. For example, to prepare a + diskette with the image file <filename>drivers.img</filename>, + enter this command in a terminal window: + </para> <screen> <userinput>dd if=drivers.img of=/dev/fd0</userinput> </screen> - <para> - To use a driver disk in the installation process, specify the - <option>dd</option> option at the - <prompt>boot:</prompt> - prompt: - </para> + <para> + To use a driver disk in the installation process, specify the + <option>dd</option> option at the + <prompt>boot:</prompt> + prompt: + </para> <screen> <userinput>linux dd</userinput> </screen> - <para> - When prompted, select <guibutton>Yes</guibutton> to provide a - driver disk. Choose the drive that holds the driver disk from - the list on the <guilabel>Driver Disk Source</guilabel> text - screen. - </para> + <para> + When prompted, select <guibutton>Yes</guibutton> to provide a + driver disk. Choose the drive that holds the driver disk from + the list on the <guilabel>Driver Disk Source</guilabel> text + screen. + </para> - <para> - 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. - </para> - <table id="tb-driversources"> - <title>Driver Disk Image Sources</title> - <tgroup cols="2"> - <colspec colnum="1" colname="Image Source"/> - <colspec colnum="2" colname="Option Format"/> - <thead> - <row> - <entry>Image Source</entry> - <entry>Option Format</entry> - </row> - </thead> - <tbody> - <row> - <entry> + <para> + 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. + </para> + <table id="tb-driversources"> + <title>Driver Disk Image Sources</title> + <tgroup cols="2"> + <colspec colnum="1" colname="Image Source"/> + <colspec colnum="2" colname="Option Format"/> + <thead> + <row> +<entry>Image Source</entry> +<entry>Option Format</entry> + </row> + </thead> + <tbody> + <row> +<entry> <para> Select a drive or device </para> </entry> - <entry> +<entry> <para> <option>dd</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> HTTP Server </para> </entry> - <entry> +<entry> <para> <option>dd=<replaceable>http://server.mydomain.com/directory/drivers.img</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> FTP Server </para> </entry> - <entry> +<entry> <para> <option>dd=<replaceable>ftp://server.mydomain.com/directory/drivers.img</replaceable></option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> NFS Server </para> </entry> - <entry> +<entry> <para> <option>dd=<replaceable>nfs:server.mydomain.com:/directory/drivers.img</replaceable></option> </para> </entry> - </row> - </tbody> - </tgroup> - </table> - </section> + </row> + </tbody> + </tgroup> + </table> + </section> - <section id="sn-bootoptions-hwdetection"> - <title>Overriding Automatic Hardware Detection</title> + <section id="sn-bootoptions-hwdetection"> + <title>Overriding Automatic Hardware Detection</title> + <para> + For some models of device automatic hardware configuration may + fail, or cause instability. In these cases, you may need to + disable automatic configuration for that type of device, and + take additional steps to manually configure the device after the + installation process is complete. + </para> + <tip> + <title>Check the Release Notes</title> <para> - For some models of device automatic hardware configuration may - fail, or cause instability. In these cases, you may need to - disable automatic configuration for that type of device, and - take additional steps to manually configure the device after - the installation process is complete. - </para> - <tip> - <title>Check the Release Notes</title> - <para> - Refer to the Release Notes for information on known issues - with specific devices. - </para> - </tip> - <para> - To override the automatic hardware detection, use one or more - of the following options: + Refer to the Release Notes for information on known issues + with specific devices. </para> - <table id="tb-hwoptions"> - <title>Hardware Options</title> - <tgroup cols="2"> - <colspec colnum="1" colname="Compatibility Setting"/> - <colspec colnum="2" colname="Option"/> - <thead> - <row> - <entry>Compatibility Setting</entry> - <entry>Option</entry> - </row> - </thead> - <tbody> - <row> - <entry> + </tip> + <para> + To override the automatic hardware detection, use one or more of + the following options: + </para> + <table id="tb-hwoptions"> + <title>Hardware Options</title> + <tgroup cols="2"> + <colspec colnum="1" colname="Compatibility Setting"/> + <colspec colnum="2" colname="Option"/> + <thead> + <row> +<entry>Compatibility Setting</entry> +<entry>Option</entry> + </row> + </thead> + <tbody> + <row> +<entry> <para> Disable all hardware detection </para> </entry> - <entry> +<entry> <para> <option>noprobe</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Disable graphics, keyboard, and mouse detection </para> </entry> - <entry> +<entry> <para> <option>headless</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> + <para> + Disable automatic monitor detection (DDC) + </para> + </entry> +<entry> + <para> + <option>skipddc</option> + </para> + </entry> + </row> + <row> +<entry> <para> Disable mainboard APIC </para> </entry> - <entry> +<entry> <para> <option>noapic</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Disable power management (ACPI) </para> </entry> - <entry> +<entry> <para> <option>acpi=off</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> - Disable automatic monitor detection (DDC) + Disable Direct Memory Access (DMA) for storage </para> </entry> - <entry> +<entry> <para> - <option>skipddc</option> + <option>ide=nodma</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> + <para> + Disable BIOS-assisted RAID + </para> + </entry> +<entry> + <para> + <option>nodmraid</option> + </para> + </entry> + </row> + <row> +<entry> <para> Disable Firewire device detection </para> </entry> - <entry> +<entry> <para> <option>nofirewire</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Disable parallel port detection </para> </entry> - <entry> +<entry> <para> <option>noparport</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Disable PC Card (PCMCIA) device detection </para> </entry> - <entry> +<entry> <para> <option>nopcmcia</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Disable USB storage device detection </para> </entry> - <entry> +<entry> <para> <option>nousbstorage</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Disable all USB device detection </para> </entry> - <entry> +<entry> <para> <option>nousb</option> </para> </entry> - </row> - <row> - <entry> - <para> - Enable software RAID controller support - </para> - </entry> - <entry> - <para> - <option>dmraid</option> - </para> - </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Force Firewire device detection </para> </entry> - <entry> +<entry> <para> <option>firewire</option> </para> </entry> - </row> - <row> - <entry> + </row> + <row> +<entry> <para> Prompt user for ISA device configuration </para> </entry> - <entry> +<entry> <para> <option>isa</option> </para> </entry> - </row> - </tbody> - </tgroup> - </table> - </section> + </row> + </tbody> + </tgroup> + </table> + </section> + </section> + <section id="sn-boot-modes"> + <title>Using the Maintenance Boot Modes</title> + + <section id="sn-memtest"> + <title>Memory (RAM) Testing Mode</title> + + <para> + Faults in memory modules may cause your system to freeze or + crash unpredictably. In some cases, memory faults may only cause + errors with particular combinations of software. For this + reason, you should test the memory of a computer before you + install &FED; for the first time, even if it has previously run + other operating systems. + </para> + + <para> + To boot your computer in 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. + </para> + + <para> + To halt the tests and reboot your computer, enter + <keycap>Esc</keycap> at any time. + </para> + </section> + + <section id="sn-mode-rescue"> + <title>Booting Your Computer with Rescue Mode</title> + + <para> + You may use the first installation disc to boot a command-line + Linux system, without installing &FED; on the computer. This + rescue system may access the drives on your computer. Rescue + mode enables you to use the utilities and functions of a running + system to modify or repair an installed system. + </para> + + <para> + To load the rescue mode, enter: + </para> +<screen> + <userinput>linux rescue</userinput> +</screen> + <para> + Specify the language, keyboard layout and network settings for + the rescue system with the screens that follow. + </para> + + <para> + <remark role="FIXME">Add a note that the boot and rescue CDs also have this facility. + </remark> + </para> </section>  </section> - <section id="sn-memtest"> - <title>Performing a Memory (RAM) Test</title> - - <para> - Faults in memory modules may cause your system to freeze or crash - unpredictably. In some cases, memory faults may only cause errors - with particular combinations of software. For this reason, you - should test the memory of a computer before you install &FED; for - the first time, even if it has previously run other operating - systems. - </para> - - <para> - To load the <command>memtest86</command> memory test utility, - enter <userinput>memtest86</userinput> at the - <prompt>boot:</prompt> - prompt. The utility immediately starts the first test. By default, - <command>memtest86</command> carries out a total of ten tests. - </para> - - <para> - To halt testing and reboot your computer, enter - <keycap>Esc</keycap> at any time. - </para> - </section> - <section id="sn-consoles-installation"> - <title>Accessing the Consoles</title> - - <para> - In addition to the main interface, or - <firstterm>console</firstterm>, the installation process provides - three other consoles. The shell console enables you to access the - command-line of the installation system. The two other consoles - display events as the installation proceeds. You may find these - consoles useful for diagnosing errors in the installation process. - </para> - - <para> - To switch between the consoles of installation process, press the - key combinations shown below: - </para> - <table id="tb-consoles"> - <title>Installation Consoles</title> - <tgroup cols="2"> - <colspec colnum="1" colname="Console"/> - <colspec colnum="2" colname="Key Combination"/> - <thead> - <row> - <entry>Console</entry> - <entry>Key Combination</entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para> - Main Console - </para> - </entry> - <entry> - <para> - <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F7</keycap> - </keycombo> - </para> - </entry> - </row> - <row> - <entry> - <para> - Shell Console - </para> - </entry> - <entry> - <para> - <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap> - </keycombo> - </para> - </entry> - </row> - <row> - <entry> - <para> - Main Log Console - </para> - </entry> - <entry> - <para> - <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F3</keycap> - </keycombo> - </para> - </entry> - </row> - <row> - <entry> - <para> - Boot Log Console - </para> - </entry> - <entry> - <para> - <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F4</keycap> - </keycombo> - </para> - </entry> - </row> - </tbody> - </tgroup> - </table> - </section> - <section id="sn-aborting-installation"> - <title>Aborting the Installation</title> - - <para> - To abort the installation process at any time before the - <guilabel>Installing Packages</guilabel> screen, either press - <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap> - </keycombo> - or power off the computer with the power switch. &FED; makes no - changes to your computer until package installation begins. - </para> - </section> </chapter>  -  <!ENTITY BUG-NUM "129911"> <!ENTITY FCLOCALVER "5"> -<!ENTITY DOCLOCALVER "1.13">  +<!ENTITY DOCLOCALVER "1.14">  <!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.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- fedora-install-guide-firstboot-en.xml 8 Dec 2005 00:27:16 -0000 1.16 +++ fedora-install-guide-firstboot-en.xml 23 Jan 2006 23:24:09 -0000 1.17 @@ -43,10 +43,12 @@ <para> 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 <indexterm> - <primary>OSI (Open Source Initiative)</primary> - </indexterm> Open Source Initiative (OSI). For more information - about the OSI, refer to + been approved by the + <indexterm> + <primary>OSI (Open Source Initiative)</primary> + </indexterm> + Open Source Initiative (OSI). For more information about the OSI, + refer to <ulink url="http://www.opensource.org/">http://www.opensource.org/</ulink>. </para> @@ -75,20 +77,22 @@ <title>Firewall</title> <para> - The <indexterm> - <primary>firewall</primary> - </indexterm> <firstterm>firewall</firstterm> 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. + The + <indexterm> + <primary>firewall</primary> + </indexterm> + <firstterm>firewall</firstterm> 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. </para> <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 - block incoming connections from other systems. You may make - changes on this screen to allow access to specific network - services on your &FED; system. + 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. </para> <para> @@ -97,20 +101,46 @@ </para> <para> - To enable access to services listed on this screen, click the - check box next to the service name. After installation is - complete, you can enable access to other services as well. + To enable access to the services listed on this screen, click the + check box next to the service name. + </para> + + <important> + <title>SSH Remote Access</title> + + <para> + All &FED; systems automatically run the SSH remote access + service. The default firewall configuration allows connections + to this service, to ensure that administrators have immediate + remote access to new systems. + </para> + </important> + + <para> + To enable access to other services, enter the required ports in + the <guilabel>Other ports:</guilabel> field. For each port, + specify the port number followed by the connection type, in the + format + <userinput><replaceable>portnumber</replaceable>:<replaceable>type</replaceable></userinput>. + The majority of services use TCP ports. + </para> + + <para> + For example, to allow other systems to access mail with the + <systemitem class="protocol">IMAP</systemitem> protocol, which may + use both TCP port 143 and TCP port 993, enter <userinput>143:tcp, + 993:tcp</userinput>. </para> <para> - Avoid disabling the firewall. If you believe it is necessary to do - so, select <guilabel>No firewall</guilabel>. + Avoid disabling the firewall. If you believe that it is necessary + to do so, select <guilabel>No firewall</guilabel>. </para> <tip> <title>Changing the Firewall Settings</title> <para> - To change these settings later, choose - <menuchoice> <guimenu>System</guimenu> + To change these settings later, choose <menuchoice> + <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu><guimenuitem>Security Level and Firewall</guimenuitem></menuchoice>. </para> @@ -125,15 +155,16 @@ </para> <para> - The <indexterm> - <primary>&SEL;</primary> - </indexterm> <firstterm>&SEL;</firstterm> (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 may render a system more vulnerable. The restrictions - imposed by &SEL; policies provide extra security against - unauthorized access. + The + <indexterm> + <primary>&SEL;</primary> + </indexterm> + <firstterm>&SEL;</firstterm> (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 may + render a system more vulnerable. The restrictions imposed by &SEL; + policies provide extra security against unauthorized access. </para> <para> @@ -147,7 +178,7 @@ <variablelist> <varlistentry> - <term><guilabel>Active</guilabel></term> + <term><guilabel>Enforcing</guilabel></term> <listitem> <para> Select this mode to use the targeted &SEL; policy on your @@ -176,8 +207,7 @@ <para> If you choose this mode for &SEL;, &FED; does not configure the access control system at all. To make &SEL; active - later, select <menuchoice> - <guimenu>System</guimenu> + later, select <menuchoice> <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Security Level and Firewall</guimenuitem> </menuchoice>. @@ -185,18 +215,21 @@ </listitem> </varlistentry> </variablelist> - + <para> - To adjust &SEL;, choose <guilabel>Modify SELinux Policy</guilabel>. To exempt a service from &SEL;, select the service from the list, and choose the <guilabel>Remove SELinux protection</guilabel> option. + To adjust &SEL;, choose <guilabel>Modify SELinux + Policy</guilabel>. To exempt a key service from &SEL; + restrictions, select the service from the list, and choose the + <guilabel>Remove SELinux protection</guilabel> option. The + <guilabel>SELinux Service Protection</guilabel> item on the list + includes options for additional services. </para> - <tip> <title>Changing the &SEL; policy</title> <para> &SEL; is unique in that it cannot be bypassed, even by the system administrators. To change the behavior of &SEL; after - installation, choose <menuchoice> - <guimenu>System</guimenu> + installation, choose <menuchoice> <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Security Level and Firewall</guimenuitem> </menuchoice>. </para> @@ -208,10 +241,12 @@ <para> 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 <indexterm> - <primary>NTP (Network Time Protocol)</primary> - </indexterm> <firstterm>NTP</firstterm> (Network Time Protocol) - servers to maintain the accuracy of the clock. NTP provides time + screen. Otherwise, use + <indexterm> + <primary>NTP (Network Time Protocol)</primary> + </indexterm> + <firstterm>NTP</firstterm> (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. </para> @@ -243,8 +278,8 @@ <tip> <title>Setting the Clock</title> <para> - To change these settings later, choose - <menuchoice> <guimenu>System</guimenu> + To change these settings later, choose <menuchoice> + <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Date & Time</guimenuitem> </menuchoice>. </para> @@ -365,8 +400,8 @@ <tip> <title>Resetting the display</title> <para> - To reconfigure your system after the installation has completed, choose <menuchoice> - <guimenu>System</guimenu> + To reconfigure your system after the installation has completed, + choose <menuchoice> <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Display</guimenuitem> </menuchoice>. </para> @@ -407,8 +442,8 @@ <title>Creating extra user accounts</title> <para> To add additional user accounts to your system after the - installation is complete, choose - <menuchoice> <guimenu>System</guimenu> + installation is complete, choose <menuchoice> + <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Users & Groups</guimenuitem> </menuchoice>. </para> @@ -417,9 +452,6 @@ To configure &FC; to use network services for authentication or user information, select <guibutton>Use Network Login...</guibutton>. - </para> <para> @@ -452,14 +484,20 @@ </figure> <para> Click <guibutton>Play Test Sound</guibutton> to check the sound - card configuration. If the configuration is correct, &FC; plays a + 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. - </para> - - <para> - <remark role="FIXME">Explain the option to <guilabel>Use only the hardware device</guilabel> - </remark> + hear the sound, check your speakers and try again. In some cases, + you may need to alter the additional settings to obtain the best + sound quality. + </para> + + <para> + Sound cards may act as multiple audio devices. To change the + <guilabel>Default PCM device</guilabel>, select a new option from + the drop-down list. By default, audio applications connect to a + software mixer that manages the PCM devices. To enable + applications to bypass the software mixer, select the option to + <guilabel>Use only the hardware device</guilabel>. </para> <para> @@ -470,10 +508,9 @@ <tip> <title>Changing the Sound Card</title> <para> - &FC; will automatically attempt to detect a new sound card if + &FED; will automatically attempt to detect a new sound card if you add one to your system. If you need to launch the detection - process manually, choose <menuchoice> - <guimenu>System</guimenu> + process manually, choose <menuchoice> <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Soundcard Detection</guimenuitem> </menuchoice>. </para> Index: fedora-install-guide-nextsteps-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-nextsteps-en.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- fedora-install-guide-nextsteps-en.xml 12 Dec 2005 02:21:54 -0000 1.10 +++ fedora-install-guide-nextsteps-en.xml 23 Jan 2006 23:24:09 -0000 1.11 @@ -3,11 +3,11 @@ <chapter id="ch-next-steps"> <title>Your Next Steps</title> <para> - &FC; provides you with a complete operating system with a vast range - of capabilities, supported by a large community. + &FED; provides you with a complete operating system with a vast + range of capabilities, supported by a large community. </para> <section id="sn-system-updating"> - <title>Updating Your &FED; System</title> + <title>Updating Your System</title> <para> The &FP; releases updated software packages for &FC; throughout @@ -24,14 +24,15 @@ <para> To update your system with the latest packages, use the <indexterm> - <primary>Package Updater</primary> - </indexterm> <application>Package Updater</application>: + <primary>Package Updater</primary> + </indexterm> + <application>Package Updater</application>: </para> <orderedlist> <listitem> <para> - Choose <menuchoice><guimenu>System</guimenu> - <guisubmenu>Administration</guisubmenu> <guimenuitem>Package + Choose <menuchoice><guimenu>Applications</guimenu> + <guisubmenu>System Tools</guisubmenu> <guimenuitem>Package Updater</guimenuitem> </menuchoice>. </para> </listitem> @@ -43,10 +44,9 @@ </listitem> <listitem> <para> - Review the list of updated packages. If your system uses a - slow network connection the <application>Package - Updater</application> may require several seconds to download - the information for all of the updated packages. + Review the list of updated packages. The package list displays + a double arrow next to any updates that require a system + reboot to take effect. </para> </listitem> <listitem> @@ -57,22 +57,21 @@ </listitem> <listitem> <para> - Restart any active programs or network services listed in the - update window. If the updates include a - <filename>kernel</filename> package, restart your system as - soon as possible to load the new kernel. + If one or more updates require a system reboot, the update + process displays a dialog with the option to <guibutton>Reboot + Now</guibutton>. Either select this option to reboot the + system immediately, or <guibutton>Cancel</guibutton> it and + reboot the system at a more convenient time. </para> </listitem> </orderedlist> <para> - <remark role="FIXME">Check this procedure on test2</remark> - </para> - - <para> - To update packages from the command-line, use the <indexterm> - <primary>yum</primary> - </indexterm> <command>yum</command> utility. Type this command to - begin a full update of your system with <command>yum</command>: + To update packages from the command-line, use the + <indexterm> + <primary>yum</primary> + </indexterm> + <command>yum</command> utility. Type this command to begin a full + update of your system with <command>yum</command>: </para> <screen> <userinput>su -c 'yum update'</userinput> @@ -140,41 +139,81 @@ <para> Announcements with the keyword <wordasword>[SECURITY]</wordasword> in the title identify - package updates that remove security vulnerabilities. + package updates that resolve security vulnerabilities. </para> </important> </section> <section id="sn-web-help"> - <title>Finding Documentation on the Web</title> + <title>Finding Documentation and Support</title> <para> - Documentation for &FC; is available from the &FP; Website: - </para> - - <para> - <ulink - url="http://fedora.redhat.com/docs/"/> + Members of the &FED; community provides support through mailing + lists, web forums and Linux User Groups (LUGs) across the world. </para> <para> - The Linux Documentation Project (LDP) produces books and - tutorials: + The Website for the official forums is: </para> <para> <ulink - url="http://www.tldp.org/"/> + url="http://forums.fedoraforum.org/"/> </para> <para> - For many parts of &FC;, you may find the &RHEL; documentation - useful: + The following resources provide information on many aspects of + &FED;: </para> - <para> - <ulink + <variablelist> + <varlistentry> + <term> + The FAQ on the &FP; website + </term> + <listitem> + <para> + <ulink + url="http://fedoraproject.org/wiki/FAQ/"/> + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term> + The documents available from the &FDP; website + </term> + <listitem> + <para> + <ulink + url="http://fedora.redhat.com/docs/"/> + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term> + The Linux Documentation Project (LDP) + </term> + <listitem> + <para> + <ulink + url="http://www.tldp.org/"/> + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term> + The &RHEL; documentation, much of which also applies to &FED; + </term> + <listitem> + <para> + <ulink url="http://www.redhat.com/docs/manuals/enterprise/"/> - </para> + </para> + </listitem> + </varlistentry> + </variablelist> <para> Many other organizations and individuals also provide tutorials @@ -187,23 +226,6 @@ url="http://www.google.com/linux/"/> </para> </section> - <section id="sn-community-help"> - <title>Getting Community Support</title> - - <para> - Members of the &FED; community provides support through mailing - lists, web forums and Linux User Groups (LUGs) across the world. - </para> - - <para> - The Website for the official forums is: - </para> - - <para> - <ulink - url="http://forums.fedoraforum.org/"/> - </para> - </section> <section id="sn-community"> <title>Joining The &FED; Community</title> Index: fedora-install-guide-techref-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-techref-en.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- fedora-install-guide-techref-en.xml 9 Jan 2006 23:56:29 -0000 1.4 +++ fedora-install-guide-techref-en.xml 23 Jan 2006 23:24:09 -0000 1.5 @@ -106,8 +106,7 @@ <listitem> <para> &FED; uses the <command>netfilter</command> framework. The - Netfilter project website provides documentation for - <command>netfilter</command>, and 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> Index: fedora-install-guide-timezone-en.xml =================================================================== RCS file: /cvs/docs/install-guide/fedora-install-guide-timezone-en.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- fedora-install-guide-timezone-en.xml 27 May 2005 22:15:15 -0000 1.10 +++ fedora-install-guide-timezone-en.xml 23 Jan 2006 23:24:09 -0000 1.11 @@ -2,16 +2,14 @@ <chapter id="ch-timezone"> <title>Time Zone Selection</title> - <para> This screen allows you to specify the correct time zone for the - location of your computer. Specify a time zone even if you plan to + location of your computer. Specify a time zone even if you plan to use <indexterm> - <primary>NTP (Network Time Protocol)</primary> + <primary>NTP (Network Time Protocol)</primary> </indexterm> NTP (Network Time Protocol) to maintain the accuracy of the system clock. </para> - <section id="sn-selecting-timezone"> <title>Selecting a Time Zone</title> @@ -19,76 +17,72 @@ &FED; displays on the screen two methods for selecting the time zone. </para> - <figure id="fig-timezone"> <title>Time Zone Selection Screen</title> <mediaobject> - <imageobject> - <imagedata align="center" fileref="./figs/timezone.eps" format="EPS"/> - </imageobject> - <imageobject> - <imagedata align="center" fileref="./figs/timezone.png" format="PNG"/> - </imageobject> - <textobject> - <phrase> + <imageobject> + <imagedata align="center" fileref="./figs/timezone.eps" format="EPS"/> + </imageobject> + <imageobject> + <imagedata align="center" fileref="./figs/timezone.png" format="PNG"/> + </imageobject> + <textobject> + <phrase> Time zone selection screen. </phrase> - </textobject> + </textobject> </mediaobject> </figure> - <para> - To select a time zone using the map, select the yellow dot that - represents the city nearest to your location. When you place the - arrow on a dot, &FED; displays the name of the city below the map. - Once you select a dot, it becomes a red <guilabel>X</guilabel> to - indicate your selection. + To select a time zone using the map, first place your mouse + pointer over your region on the map. Click once to magnify that + region on the map. Next, select the yellow dot that represents the + city nearest to your location. Once you select a dot, it becomes a + red <guilabel>X</guilabel> to indicate your selection. </para> <para> To select a time zone using the list, select the name of the city - nearest to your location. The cities are listed in alphabetical + nearest to your location. The cities are listed in alphabetical order. </para> - </section> - <section id="sn-utc"> <title>Universal Co-ordinated Time (UTC)</title> <para> <indexterm> - <primary>UTC (Universal Co-ordinated time)</primary> + <primary>UTC (Universal Co-ordinated time)</primary> </indexterm> Universal Co-ordinated Time is also known as <indexterm> - <primary>GMT (Greenwich Mean Time)</primary> - <see>UTC</see> + <primary>GMT (Greenwich Mean Time)</primary> + <see>UTC</see> </indexterm> Greenwich Mean Time (GMT). </para> <para> If &FC; is the only operating system on your computer, select - <guilabel>System clock uses UTC</guilabel>. The system clock is a - piece of hardware on your computer system. &FC; uses the timezone + <guilabel>System clock uses UTC</guilabel>. The system clock is a + piece of hardware on your computer system. &FC; uses the timezone setting to determine the offset between the local time and UTC on - the system clock. This behavior is standard for UNIX-like + the system clock. This behavior is standard for UNIX-like operating systems. </para> <caution> <title>Windows and the System Clock</title> + <para> - Do not enable the <guilabel>System clock uses UTC</guilabel> - option if your machine also runs Microsoft Windows. Microsoft - operating systems change the BIOS clock to match local time - rather than UTC. This may cause unexpected behavior under &FC;. + Do not enable the <guilabel>System clock uses UTC</guilabel> + option if your machine also runs Microsoft Windows. Microsoft + operating systems change the BIOS clock to match local time + rather than UTC. This may cause unexpected behavior under &FC;. </para> </caution> <para> Select <guibutton>Next</guibutton> to proceed. </para> - </section> </chapter> Index: rpm-info.xml =================================================================== RCS file: /cvs/docs/install-guide/rpm-info.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- rpm-info.xml 17 Jan 2006 23:04:15 -0000 1.3 +++ rpm-info.xml 23 Jan 2006 23:24:09 -0000 1.4 @@ -1,6 +1,6 @@ -<?xml version="1.0" encoding="UTF-8"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> -<!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd" > +<!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd"> <rpm-info> <colophon> @@ -28,9 +28,14 @@  </titles> <changelog order="newest-first"> + <revision date="2006-01-23" number="1.14" role="doc"> + <author worker="StuartEllis"/> + + <details>Updated for FC5 test2.</details> + </revision> <revision date="Tue Jan 17 2006" number="0" role="rpm"> <author worker="megacoder"/> - <details>Added initial empty RPM revision to test packaging.</details> + <details lang="en">Added initial empty RPM revision to test packaging.</details> </revision> <revision date="2006-01-16" number="1.13" role="doc"> <author worker="StuartEllis"/>

1 0

release-notes ArchSpecificx86-it.xml, 1.3, 1.4 Desktop-it.xml, 1.2, 1.3 DevelopmentToolsGCC-it.xml, 1.3, 1.4 DevelopmentToolsJava-it.xml, 1.3, 1.4 I18n-it.xml, 1.2, 1.3 Kernel-it.xml, 1.2, 1.3 Multimedia-it.xml, 1.2, 1.3 Networking-it.xml, 1.3, 1.4 OverView-it.xml, 1.3, 1.4 PackageChanges-it.xml, 1.2, 1.3 PackageNotes-it.xml, 1.3, 1.4 ProjectOverview-it.xml, 1.2, 1.3 Samba-it.xml, 1.2, 1.3 Security-it.xml, 1.2, 1.3 WebServers-it.xml, 1.2, 1.3 Welcome-it.xml, 1.4, 1.5 Xorg-it.xml, 1.1, 1.2
by fedora-docs-commits＠redhat.com 23 Jan '06

23 Jan '06

Author: tombo Update of /cvs/docs/release-notes In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19405/release-notes Modified Files: ArchSpecificx86-it.xml Desktop-it.xml DevelopmentToolsGCC-it.xml DevelopmentToolsJava-it.xml I18n-it.xml Kernel-it.xml Multimedia-it.xml Networking-it.xml OverView-it.xml PackageChanges-it.xml PackageNotes-it.xml ProjectOverview-it.xml Samba-it.xml Security-it.xml WebServers-it.xml Welcome-it.xml Xorg-it.xml Log Message: Some minor bug corrections... Index: ArchSpecificx86-it.xml =================================================================== RCS file: /cvs/docs/release-notes/ArchSpecificx86-it.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- ArchSpecificx86-it.xml 11 Jan 2006 07:17:52 -0000 1.3 +++ ArchSpecificx86-it.xml 23 Jan 2006 21:30:15 -0000 1.4 @@ -70,7 +70,7 @@ <title>Note sull'installazione x86</title> <para>La schermata di selezione dell'installer �� stata ridisegnata nella versione di sviluppo di &FED;. &FC; &LOCALVER; - non fornisce un opzione per selezionare il modo d'istallazione tipo + non fornisce un opzione per selezionare il modo d'installazione tipo Desktop Personale, Workstation, Server e personalizzata. </para> </section> </section> Index: Desktop-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Desktop-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Desktop-it.xml 15 Jan 2006 00:07:01 -0000 1.2 +++ Desktop-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -81,7 +81,7 @@ <para> L'utilit�� di configurazione <application>system-config-mouse</application> �� stata scartata - da questa release poich�� synaptic e la configurazione del mouse a 3 bottoni + da questa release poich�� synaptic e la configurazione del mouse a 3 bottoni viene fatta automaticamente durante l'installazione. I mouse seriali sono formalmente non pi�� supportati da &FC;. </para> Index: DevelopmentToolsGCC-it.xml =================================================================== RCS file: /cvs/docs/release-notes/DevelopmentToolsGCC-it.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- DevelopmentToolsGCC-it.xml 11 Jan 2006 07:17:52 -0000 1.3 +++ DevelopmentToolsGCC-it.xml 23 Jan 2006 21:30:15 -0000 1.4 @@ -42,7 +42,7 @@ <listitem> <para> Il file <filename>specs</filename> non �� pi�� installato su - molti systems. Gli utenti comunit non lo noteranno, ma gli sviluppatori + molti systems. Gli utenti comuni non lo noteranno, ma gli sviluppatori che debbono alterare il file possono usare l'opzione <parameter class="option">-dumpspecs</parameter> per generare il file per l'editing. @@ -72,7 +72,7 @@ <listitem> <para> Un attributo <computeroutput>sentinel</computeroutput> �� stato aggiunto - affinch�� il compilatore possa inviare un messaggio di avvertimento se una + affinch�� il compilatore possa inviare un messaggio di avvertimento se una funzione tipo <function>execl(char *path, const char *arg, ...)</function>, che richiede un terminatore di lista <computeroutput>NULL</computeroutput> Index: DevelopmentToolsJava-it.xml =================================================================== RCS file: /cvs/docs/release-notes/DevelopmentToolsJava-it.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- DevelopmentToolsJava-it.xml 11 Jan 2006 07:17:52 -0000 1.3 +++ DevelopmentToolsJava-it.xml 23 Jan 2006 21:30:15 -0000 1.4 @@ -25,12 +25,12 @@ url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink> </para> <section id="sn-java-development"> - <title>Java Development</title> + <title>Sviluppo Java</title> <itemizedlist> <listitem> <para> - Per evitare conflitti sui nomi: + Per evitare conflitti sui nomi i seguenti sono stati rinominati: </para> <itemizedlist> <listitem> Index: I18n-it.xml =================================================================== RCS file: /cvs/docs/release-notes/I18n-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- I18n-it.xml 11 Jan 2006 07:17:52 -0000 1.2 +++ I18n-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -10,7 +10,7 @@ vari linguaggi in &DISTRO;. </para> <note> - <title>IIIMF replaced</title> + <title>IIIMF sostituito</title> <para> SCIM ha sostituito IIIMF in questa release di &FC;. </para> Index: Kernel-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Kernel-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Kernel-it.xml 11 Jan 2006 07:17:52 -0000 1.2 +++ Kernel-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -31,7 +31,7 @@ <command>rpm -qpl kernel-<version>.src.rpm</command> </screen> </section> - <section id="sn-kernel-changelog"> + <section id="sn-kernel-changelog"> <title>Changelog</title> <para> @@ -279,7 +279,7 @@ amministrazione. Di conseguenza, per rimuovere un simile kernel, ad esempio dopo un aggiornamento, non puoi semplicemente usare il comando <command>rpm -e kernel-<replaceable>version</replaceable></command> come - nelle precedenti distribuzioni poich�� questi pacchetti in user space + nelle precedenti distribuzioni poich�� questi pacchetti in user space dipendono dal pacchetto del kernel. </para> <para> Index: Multimedia-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Multimedia-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Multimedia-it.xml 11 Jan 2006 07:17:52 -0000 1.2 +++ Multimedia-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -7,7 +7,7 @@ </para> <variablelist> <varlistentry> - <term>Multimedia Players</term> + <term>Lettori multimediali</term> <listitem> <para>Per impostazione predefinita, &FC; viene installata con <filename>rhythmbox</filename>, <filename>totem</filename>, @@ -56,7 +56,7 @@ <term>MP3 & Supporto DVD</term> <listitem> <para>&FC; e &FEX; non possono includere il supporto per il playback o la - registrazione degli MP3 o DVD, perch�� i formati MP3 e MPEG (DVD) sono + registrazione degli MP3 o DVD, perch�� i formati MP3 e MPEG (DVD) sono protetti da copyright, ed i proprietari dei brevetti non forniscono le necessarie licenze. Per maggiori informazioni, fate riferimento a <xref linkend="sn-multimedia-excluded"/>. Index: Networking-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Networking-it.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Networking-it.xml 12 Jan 2006 06:56:15 -0000 1.3 +++ Networking-it.xml 23 Jan 2006 21:30:15 -0000 1.4 @@ -172,7 +172,7 @@ </varlistentry> </variablelist> <section sn="kernel-userspace-tools"> - <title>Userspace Tools</title> + <title>Strumenti utente</title> <para> L'algoritmo di cancellazione indirizzo IPv4 address non prendeva la lunghezza del prefisso in conto fino al kernel versione 2.6.12. Da quando ci�� @@ -198,7 +198,7 @@ </screen> <para> Non �� stato possibile dire se un interfaccia �� spenta - a scopo amministrativo o perch�� non c'�� linea (cavo + a scopo amministrativo o perch�� non c'�� linea (cavo staccato). Il flag <computeroutput>NO-CARRIER</computeroutput> �� stato introdotto per mostrare un link flag se il link �� amministrativamente su ma non viene trovata linea. Index: OverView-it.xml =================================================================== RCS file: /cvs/docs/release-notes/OverView-it.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- OverView-it.xml 14 Jan 2006 23:53:47 -0000 1.3 +++ OverView-it.xml 23 Jan 2006 21:30:15 -0000 1.4 @@ -84,13 +84,13 @@ </listitem> <listitem> <para> - Il kernel 2.6.14 �� incluso. Il suspend software �� abilitato + Il kernel 2.6.14 �� incluso. La sospensione software �� abilitata in questa versione. </para> </listitem> <listitem> <para> - Pup, un updater grafico che usa yum, �� disponibile in + Pup, un software di aggiornamento pacchetti grafico che usa yum, �� disponibile in questa versione. </para> </listitem> Index: PackageChanges-it.xml =================================================================== RCS file: /cvs/docs/release-notes/PackageChanges-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- PackageChanges-it.xml 12 Jan 2006 06:16:24 -0000 1.2 +++ PackageChanges-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -1046,13 +1046,13 @@ <title>Note</title> <para> L'utilit�� di configurazione <application>system-config-mouse</application> - �� stata scartata in questa release poich�� synaptic e la configurazione + �� stata scartata in questa release poich�� synaptic e la configurazione dei mouse a 3 bottoni viene fatta automaticamente ed i mouse seriali non sono supportati. </para> <para> Gli screensavers, per impostazione predefinita non sono pi�� installati? Spieghiamo - il perch�� e forniamo i comandi per installarli. + il perch�� e forniamo i comandi per installarli. </para> <!-- FIXME <para> Index: PackageNotes-it.xml =================================================================== RCS file: /cvs/docs/release-notes/PackageNotes-it.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- PackageNotes-it.xml 14 Jan 2006 23:56:12 -0000 1.3 +++ PackageNotes-it.xml 23 Jan 2006 21:30:15 -0000 1.4 @@ -118,7 +118,7 @@ </para> <para> Nelle precedenti releases fino alla &RHL; 9, l'impostazione predefinita per il - threading era LinuxThreads poich�� l'interfaccia era molto pi�� compatibile. + threading era LinuxThreads poich�� l'interfaccia era molto pi�� compatibile. I vantaggi dell'interfaccia NPTL sono che la manipolazione della cancellazione �� pi�� veloce (quando �� usato <parameter>-fexception</parameter>, anche nel codice C) e che le interfacce aggiuntive sono ora @@ -151,7 +151,7 @@ <envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar> </screen> <para> - Questa variabile aggiuntiva �� richiesta perch�� le librerie run/time + Questa variabile aggiuntiva �� richiesta perch�� le librerie run/time sono state spostate. Ci potrebbero essere programmi che non funzionano se usassero uno sfortunato <envar>DT_RPATH</envar> (che sovrascriver�� l'impostazione @@ -222,7 +222,7 @@ Precedentemente, l'X11 forwarding era effettuato in modo tale che le applicazioni fossero eseguite sempre come clients verificati. Alcune applicazioni potrebbero non funzionare correttamente se eseguite come client non verificati. Per eseguire l'X11 - forwarding affinch�� le applicazioni siano eseguite come clients verificati, invocate ssh con + forwarding affinch�� le applicazioni siano eseguite come clients verificati, invocate ssh con l'opzione <option>-Y</option> invece che l'opzione <option>-X</option>, o impostate <option>ForwardX11Trusted</option> nel file <option>~/.ssh/config</option>. Index: ProjectOverview-it.xml =================================================================== RCS file: /cvs/docs/release-notes/ProjectOverview-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ProjectOverview-it.xml 12 Jan 2006 06:16:24 -0000 1.2 +++ ProjectOverview-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -5,7 +5,7 @@ creare un sistema operativo completo, general-purpose esclusivamente da software open source. Lo sviluppo �� compiuto in un forum pubblico. Il progetto produce delle releases su base temporale di &FC; approssimativamente - 2-3 volte l'anno, con uno scadenziario pubblico delle release. Le squadre + 2-3 volte l'anno, con uno scadenzario pubblico delle release. Le squadre di ingegneri &RH; continuano a partecipare alla costruzione della &FC; ed invitano ed incoraggiano pi�� partecipanti esterni di quanto era possibile in passato. Utilizzando questo processo pi�� aperto, speriamo di Index: Samba-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Samba-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Samba-it.xml 12 Jan 2006 06:16:24 -0000 1.2 +++ Samba-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -8,12 +8,12 @@ </para> <section id="sn-samba-smb-browsing"> - <title>SMB Browsing</title> + <title>Esplorazione risorse SMB</title> <para> L'esplorazione delle condivisioni di Windows (conosciuta anche come esplorazione SMB) �� ora possibile. Nelle versioni precedenti alla &FC; &LOCALVER;, il firewall - preveniva l'appropriata funzionalit�� dell'SMB browsing. Con l'aggiunta + preveniva l'appropriata funzionalit�� di esplorazione risorse SMB. Con l'aggiunta del modulo kernel <filename>ip_conntrack_netbios_ns</filename> al kernel 2.6.14 e corrispondenti sviluppi a <application>system-config-securitylevel</application>, il Index: Security-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Security-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Security-it.xml 12 Jan 2006 06:16:24 -0000 1.2 +++ Security-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -10,7 +10,7 @@ <para> Introduzione generale alle molteplici proattive caratteristiche di sicurezza in - &FED;, lo status corrente e le policies sono disponibili sulla pagina<ulink + &FED;, lo status corrente e le policies sono disponibili sulla pagina <ulink url="http://fedoraproject.org/wiki/Security/Security">http://fedoraproject.org/wiki/Security</ulink> . </para> @@ -36,7 +36,7 @@ queste configurazioni di sicurezza non vengono sostituite. Invece esse vengono create come files <filename>.rpmnew</filename> e continuano a chiamare su <filename>pam_stack</filename>. Queste configurazioni di servizio - devono essere riviste affinch�� il modulo + devono essere riviste affinch�� il modulo <filename>pam_stack</filename> non venga usato. Fa riferimento ai files <filename>.rpmnew</filename> per i cambiamenti che occorrono. @@ -88,7 +88,7 @@ <para> Tutto il software nei repositori &FC; e &FEX; per questa versione sono compilati usando una caratteristica di sicurezza - chiamata <firstterm>fstack-protecter</firstterm>. fstack-protector + chiamata <firstterm>fstack-protector</firstterm>. fstack-protector pone un canary value sullo stack delle funzioni key. Appena prima dell'indirizzo di restituzione ed appena prima di essere restituito da quel valore. Il canary value viene verificato e se si verifica un buffer Index: WebServers-it.xml =================================================================== RCS file: /cvs/docs/release-notes/WebServers-it.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- WebServers-it.xml 12 Jan 2006 06:16:24 -0000 1.2 +++ WebServers-it.xml 23 Jan 2006 21:30:15 -0000 1.3 @@ -25,7 +25,7 @@ </listitem> <listitem> <para> - supporto per autenticazione ed autorizazione completamente rivisto + supporto per autenticazione ed autorizzazione completamente rivisto </para> </listitem> <listitem> Index: Welcome-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Welcome-it.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- Welcome-it.xml 12 Jan 2006 06:29:16 -0000 1.4 +++ Welcome-it.xml 23 Jan 2006 21:30:15 -0000 1.5 @@ -1,8 +1,8 @@ <section id="sn-splash"> <title>Benvenuti in &FC; &LOCALVER;</title> <para> - &FC; �� una piattaforma basata su Linux completamente gratuita, amichevole, sicura ed - uso generale. &FP; �� un progetto open source che �� utilizzabile, modificabile e distribuibile + &FC; �� una piattaforma basata su Linux completamente gratuita, amichevole, sicura d'uso + generale. &FP; �� un progetto open source che �� utilizzabile, modificabile e distribuibile liberamente da chiunque, ora e per sempre. Il &FP; �� un progetto open source che esplora le ultime tecnologie e concetti sponsorizzato da &RH; e supportato dalla comunit�� &FED;. Index: Xorg-it.xml =================================================================== RCS file: /cvs/docs/release-notes/Xorg-it.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Xorg-it.xml 5 Jan 2006 20:31:11 -0000 1.1 +++ Xorg-it.xml 23 Jan 2006 21:30:15 -0000 1.2 @@ -23,7 +23,7 @@ </para> <para> Il modulare X.Org X11R7 RC2 �� stato distribuito con &FED; development - (<firstterm>rawhide</firstterm>) il 16 November, 2005. Questa �� + (<firstterm>rawhide</firstterm>) il 16 Novembre, 2005. Questa �� la prima release modulare di Xorg. Fra i vari benefici, Xorg modulare da la possibilit�� agli utenti di ricevere gli aggiornamenti con un passo pi�� veloce, mentre aiuta gli sviluppatori a

1 0

docs-common/packaging insert-changelog.xsl, 1.2, 1.3 insert-colophon.xsl, 1.2, 1.3
by fedora-docs-commits＠redhat.com 22 Jan '06

22 Jan '06

Author: pfrields Update of /cvs/docs/docs-common/packaging In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31591/docs-common/packaging Modified Files: insert-changelog.xsl insert-colophon.xsl Log Message: Make sure we output our XML declaration and DOCTYPE when rewriting rpm-info Index: insert-changelog.xsl =================================================================== RCS file: /cvs/docs/docs-common/packaging/insert-changelog.xsl,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- insert-changelog.xsl 15 Jan 2006 22:33:03 -0000 1.2 +++ insert-changelog.xsl 22 Jan 2006 20:26:09 -0000 1.3 @@ -16,7 +16,9 @@ <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> - <xsl:output encoding="UTF-8" indent="yes" method="xml" omit-xml-declaration="yes" standalone="no" version="1.0"/> + <xsl:output encoding="UTF-8" indent="yes" method="xml" + omit-xml-declaration="no" standalone="no" version="1.0" + doctype-system="../docs-common/packaging/rpm-info.dtd"/> <xsl:template match="/"> <xsl:apply-templates/> Index: insert-colophon.xsl =================================================================== RCS file: /cvs/docs/docs-common/packaging/insert-colophon.xsl,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- insert-colophon.xsl 15 Jan 2006 23:27:34 -0000 1.2 +++ insert-colophon.xsl 22 Jan 2006 20:26:09 -0000 1.3 @@ -18,7 +18,9 @@ <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> - <xsl:output encoding="UTF-8" indent="yes" method="xml" omit-xml-declaration="yes" standalone="no" version="1.0"/> + <xsl:output encoding="UTF-8" indent="yes" method="xml" + omit-xml-declaration="no" standalone="no" version="1.0" + doctype-system="../docs-common/packaging/rpm-info.dtd"/>  <xsl:param name="othername" select="''"/>

1 0

example-tutorial example-tutorial-de.xml, 1.6, 1.7 example-tutorial-en.xml, 1.21, 1.22
by fedora-docs-commits＠redhat.com 21 Jan '06

21 Jan '06

Author: pfrields Update of /cvs/docs/example-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8324 Modified Files: example-tutorial-de.xml example-tutorial-en.xml Log Message: Minor change to flush left a CDATA section, make sure prettyprinting leaves it alone Index: example-tutorial-de.xml =================================================================== RCS file: /cvs/docs/example-tutorial/example-tutorial-de.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- example-tutorial-de.xml 21 Jan 2006 19:29:41 -0000 1.6 +++ example-tutorial-de.xml 21 Jan 2006 19:32:04 -0000 1.7 @@ -93,7 +93,7 @@ Line 2 Line 3 Line 4 <co id="pl-callout-L4"/> - </programlisting> +</programlisting> <calloutlist> <callout arearefs="pl-callout-L1"> <para> Index: example-tutorial-en.xml =================================================================== RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- example-tutorial-en.xml 21 Jan 2006 19:29:41 -0000 1.21 +++ example-tutorial-en.xml 21 Jan 2006 19:32:04 -0000 1.22 @@ -89,7 +89,7 @@ Line 2 Line 3 Line 4 <co id="pl-callout-L4"/> - </programlisting> +</programlisting> <calloutlist> <callout arearefs="pl-callout-L1"> <para>

1 0

example-tutorial example-tutorial-de.xml, 1.5, 1.6 example-tutorial-en.xml, 1.20, 1.21 rpm-info.xml, 1.14, 1.15
by fedora-docs-commits＠redhat.com 21 Jan '06

21 Jan '06

Author: pfrields Update of /cvs/docs/example-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8289 Modified Files: example-tutorial-de.xml example-tutorial-en.xml rpm-info.xml Log Message: Shameless bump to test prettyprinting, to 0.14.1 Index: example-tutorial-de.xml =================================================================== RCS file: /cvs/docs/example-tutorial/example-tutorial-de.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- example-tutorial-de.xml 28 Dec 2005 22:19:04 -0000 1.5 +++ example-tutorial-de.xml 21 Jan 2006 19:29:41 -0000 1.6 @@ -1,4 +1,5 @@  + <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ @@ -6,8 +7,8 @@ %FEDORA-ENTITIES-EN; <!ENTITY DOCNAME "example-tutorial"> -<!ENTITY DOCVERSION "0.14">  -<!ENTITY DOCDATE "2005-09-18">  +<!ENTITY DOCVERSION "0.14.1">  +<!ENTITY DOCDATE "2006-01-21">  <!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)"> <!ENTITY BUG-NUM "000000">  @@ -15,42 +16,42 @@ ]>  +  - + <article id="example-tutorial" lang="de"> -  <section id="sn-some-section"> <title>Some Section</title> - <indexterm> <primary>Index term</primary> </indexterm> - <para> - This is an example section. You should not use sect1, sect2, etc., since - those tags will make sections less modular, i.e., harder to + This is an example section. You should not use sect1, sect2, etc., + since those tags will make sections less modular, i.e., harder to relocate without changing a lot of other markup. </para> + <para> - Keep text within the <command>title</command> tags on the same line as the - tags. Nesting the title on a separate line from the enclosing tags results - in extra spaces in HTML rendering. + Keep text within the <command>title</command> tags on the same + line as the tags. Nesting the title on a separate line from the + enclosing tags results in extra spaces in HTML rendering. </para> <warning> <title>Warning</title> + <para> Example of an admonition. </para> </warning> <para> - This paragraph illustrates the use of command syntax to accomplish a - task. Note that specific filenames denoting versions should be + This paragraph illustrates the use of command syntax to accomplish + a task. Note that specific filenames denoting versions should be avoided. To install any RPM package, use the following syntax: </para> <screen> @@ -58,11 +59,11 @@ </screen> <para> Notice that the <command>screen</command> section is entirely - left-justified with no preceding indent. This is necessary to ensure - proper rendering in PDFs. Also notice that the entire + left-justified with no preceding indent. This is necessary to + ensure proper rendering in PDFs. Also notice that the entire <command>command</command> has been surrounded by - <command>userinput</command> since the user types this - command. Computer output would be enclosed in + <command>userinput</command> since the user types this command. + Computer output would be enclosed in <command>computeroutput</command> tags, as in the following sample. </para> @@ -72,42 +73,42 @@ </screen> <para> Lines should be broken <emphasis>exactly</emphasis> as they are - on-screen. Also, note that spaces inside <command>screen</command> tags - are automatically treated as non-breaking. + on-screen. Also, note that spaces inside <command>screen</command> + tags are automatically treated as non-breaking. </para> <tip> <title>Fill modes and <command>screen</command> tags</title> <para> - Using automatic or manual fill commands in Emacs/PSGML will sometimes - mangle <command>screen</command> sections. Use care when performing fill - operations, and check the results. + Using automatic or manual fill commands in Emacs/PSGML will + sometimes mangle <command>screen</command> sections. Use care + when performing fill operations, and check the results. </para> </tip> </section> <section> <title>Callout Example</title> - <programlisting id="pl-callout"> +<programlisting id="pl-callout"> Line 1 <co id="pl-callout-L1"/> Line 2 Line 3 Line 4 <co id="pl-callout-L4"/> </programlisting> - <calloutlist> - <callout arearefs="pl-callout-L1"> - <para> - Here is a callout. - </para> - </callout> - <callout arearefs="pl-callout-L4"> - <para> - The second callout. - </para> - </callout> - </calloutlist> + <calloutlist> + <callout arearefs="pl-callout-L1"> + <para> + Here is a callout. + </para> + </callout> + <callout arearefs="pl-callout-L4"> + <para> + The second callout. + </para> + </callout> + </calloutlist> </section> -<index id="generated-index"></index> + <index id="generated-index"></index> </article>  -<!ENTITY DOCDATE "2005-09-18">  +<!ENTITY DOCVERSION "0.14.1">  +<!ENTITY DOCDATE "2006-01-21">  <!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)"> <!ENTITY BUG-NUM "000000">  @@ -27,8 +27,8 @@ </indexterm> <para> This is an example section. You should not use sect1, sect2, etc., - since those tags will make sections less modular, i.e., - harder to relocate without changing a lot of other markup. + since those tags will make sections less modular, i.e., harder to + relocate without changing a lot of other markup. </para> <para> @@ -106,16 +106,31 @@ <section> <title>Deeply nested sections</title> - <para>Early to bed, early to rise</para> + + <para> + Early to bed, early to rise + </para> + <section> <title>Second Level</title> - <para>Is the curse of the working class</para> + + <para> + Is the curse of the working class + </para> + <section> <title>Third Level</title> - <para>He who can, does</para> + + <para> + He who can, does + </para> + <section> <title>Fourth Level</title> - <para>He who cannot, manages.</para> + + <para> + He who cannot, manages. + </para> </section> </section> </section> @@ -123,19 +138,23 @@ <section id="sn-procedure-test"> <title>Procedure Test</title> - <procedure> <step> - <para>First step</para> + <para> + First step + </para> </step> <step> - <para>Second step</para> + <para> + Second step + </para> </step> <step> - <para>Third step</para> + <para> + Third step + </para> </step> </procedure> - </section> <index id="generated-index"></index> Index: rpm-info.xml =================================================================== RCS file: /cvs/docs/example-tutorial/rpm-info.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- rpm-info.xml 7 Jan 2006 04:54:53 -0000 1.14 +++ rpm-info.xml 21 Jan 2006 19:29:41 -0000 1.15 @@ -1,7 +1,7 @@ -<?xml version="1.0" encoding="UTF-8"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> - <!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd"> + <rpm-info> <colophon> <worker email="me(a)home.net" firstname="Me" id="me" initials="I" surname="Myself" wholename="Me Myself"/> @@ -17,7 +17,7 @@ </license> <copyright> <year>2003, 2004, 2005</year> -  + <holder>Tammy Fox</holder> </copyright> <titles> @@ -31,33 +31,37 @@ </translation> </titles> <changelog order="newest-first"> + <revision date="2006-01-21" number="0.14.1" role="doc"> + <author worker="stickster"/> + <details lang="en">A shameless bump to test prettyprinting</details> + </revision> <revision date="Fri Jan 6 2006" number="2" role="rpm"> <author worker="stickster"/> - <details>A later RPM release</details> + <details lang="en">A later RPM release</details> </revision> <revision date="Thu Dec 29 2005" number="1" role="rpm"> <author worker="stickster"/> - <details>A matching RPM release</details> + <details lang="en">A matching RPM release</details> </revision> <revision date="2005-12-29" number="0.14" role="doc"> <author worker="stickster"/> - <details>Make sure version matches what's in DOCVERSION</details> + <details lang="en">Make sure version matches what's in DOCVERSION</details> </revision> - <revision date="2005-12-28" number="0.13.1"> + <revision date="2005-12-28" number="0.13.1" role="doc"> <author worker="stickster"/> - <details>Minor changes for testing purposes</details> + <details lang="en">Minor changes for testing purposes</details> </revision> <revision date="Sat Nov 26 2005" number="2" role="rpm"> <author worker="me"/> - <details>Some rpm-only changes</details> + <details lang="en">Some rpm-only changes</details> </revision> <revision date="Fri Nov 25 2005" number="1" role="rpm"> <author worker="stickster"/> - <details>Initial RPM version</details> + <details lang="en">Initial RPM version</details> </revision> - <revision date="2005-09-18" number="0.13"> + <revision date="2005-09-18" number="0.13" role="doc"> <author worker="stickster"/> - <details>Add revision history</details> + <details lang="en">Add revision history</details> <details lang="de">addierte Neuausgabengeschichte</details> </revision> </changelog>

1 0

← Newer
1
2
3
4
5
6
7
...
22
Older →

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