From fedora-docs-commits at redhat.com Mon Aug 1 21:23:54 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Mon, 1 Aug 2005 17:23:54 -0400 Subject: mirror-tutorial mirror-tutorial-en.xml,1.7,1.8 Message-ID: <200508012123.j71LNsIH017138@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17121 Modified Files: mirror-tutorial-en.xml Log Message: Add entities and draft notice; bump to 0.30 Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- mirror-tutorial-en.xml 22 Jul 2005 12:43:58 -0000 1.7 +++ mirror-tutorial-en.xml 1 Aug 2005 21:23:52 -0000 1.8 @@ -5,8 +5,10 @@ %FEDORA-ENTITIES-EN; - + + + ]>
@@ -136,6 +138,16 @@ + + 0.30 + 2005-08-01 + PaulWFrields + + + Add entities and draft notice. + + + @@ -151,14 +163,7 @@ enhance user experience, adding to the perceived value of non-proprietary operating systems and software. - - A note about &FC; and this document - - This document applies to &FC; &FCVER;, which may not be the newest - release of &FC;. You can find more information about the newest - version at &FP-URL;. - - + &DRAFTNOTICE;
Audience From fedora-docs-commits at redhat.com Tue Aug 2 21:45:52 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 2 Aug 2005 17:45:52 -0400 Subject: docs-common/bin xmlformat-fdp.conf,1.2,1.3 Message-ID: <200508022145.j72Ljqc7019283@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19266 Modified Files: xmlformat-fdp.conf Log Message: Add guibutton to list of interface tags to inline Index: xmlformat-fdp.conf =================================================================== RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- xmlformat-fdp.conf 7 Jul 2005 16:22:38 -0000 1.2 +++ xmlformat-fdp.conf 2 Aug 2005 21:45:50 -0000 1.3 @@ -90,7 +90,7 @@ entry-break = 0 exit-break = 0 -menuchoice guilabel guimenu guisubmenu guimenuitem +menuchoice guilabel guimenu guisubmenu guimenuitem guibutton format = inline wordasword systemitem citetitle footnote From fedora-docs-commits at redhat.com Tue Aug 2 22:00:16 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 2 Aug 2005 18:00:16 -0400 Subject: docs-common/common fedora-entities-en.ent,1.3,1.4 Message-ID: <200508022200.j72M0GxK019531@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19514/docs-common/common Modified Files: fedora-entities-en.ent Log Message: Add entities for IG URL and DocG URL Index: fedora-entities-en.ent =================================================================== RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- fedora-entities-en.ent 3 Jun 2005 03:43:08 -0000 1.3 +++ fedora-entities-en.ent 2 Aug 2005 22:00:14 -0000 1.4 @@ -59,6 +59,11 @@ + + + + + From fedora-docs-commits at redhat.com Tue Aug 2 22:05:56 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 2 Aug 2005 18:05:56 -0400 Subject: docs-common/common fedora-entities-en.ent,1.4,1.5 Message-ID: <200508022205.j72M5vTG020673@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20656/docs-common/common Modified Files: fedora-entities-en.ent Log Message: Whoops, gotta use the right syntax there... Index: fedora-entities-en.ent =================================================================== RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- fedora-entities-en.ent 2 Aug 2005 22:00:14 -0000 1.4 +++ fedora-entities-en.ent 2 Aug 2005 22:05:33 -0000 1.5 @@ -61,8 +61,8 @@ - - +"> +"> From fedora-docs-commits at redhat.com Tue Aug 2 22:07:53 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 2 Aug 2005 18:07:53 -0400 Subject: mirror-tutorial mirror-tutorial-en.xml,1.8,1.9 Message-ID: <200508022207.j72M7r11020713@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20695 Modified Files: mirror-tutorial-en.xml Log Message: Add link to IG Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- mirror-tutorial-en.xml 1 Aug 2005 21:23:52 -0000 1.8 +++ mirror-tutorial-en.xml 2 Aug 2005 22:07:37 -0000 1.9 @@ -217,9 +217,8 @@
Additional Resources - For more information on installing &FC; see the &FC; &IG;. For more information on basic Internet protocols, see - http://library.albany.edu/internet/internet.html, or search Google at http://www.google.com/. For more From fedora-docs-commits at redhat.com Tue Aug 9 23:16:43 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Tue, 9 Aug 2005 19:16:43 -0400 Subject: securing-filesystems sn-introduction.xml,1.1,1.2 Message-ID: <200508092316.j79NGhZw011859@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11842/securing-filesystems Modified Files: sn-introduction.xml Log Message: Added introductory statements. Index: sn-introduction.xml =================================================================== RCS file: /cvs/docs/securing-filesystems/sn-introduction.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- sn-introduction.xml 29 Jul 2005 15:00:15 -0000 1.1 +++ sn-introduction.xml 9 Aug 2005 23:16:40 -0000 1.2 @@ -3,17 +3,40 @@ - + Introduction + + Access Control is a technology that is attracting more and + more attention as corporations and general end-users reel back from the onslaught + of advancements made by the malicious denizens of todays digitally connected + world. By utilizing various access control technologies the single loss exposure + introduced by these malicious users can be greatly reduced. With this reduction of + risk we can also reduce the total cost of ownership of a Fedora Core distribution. + Corporations and end-users alike benefit from the resultant product generated by a + little due diligence and due care of the filesystems available to them. + + + This due diligence and due care will be presented as a review, implementation, and + monitoring of the object instances that compose a filesystem by using the + various Open Source access control techniques and implementations available to the + general public. To enable end-users and system administrators alike to glean + meaningful content from this document, there will be a comprehensive review of + the structure and design of a filesystem at its most basic level. Further + explanation of access control mechanisms and methodologies should provide a solid + base from which to start securing the filesystems of fedora. This document will + also describe the administrative considerations and effects of the procedures + presented to ensure a cohesive and comprehensive understanding of the topic of + filesystem access control. +
Intended Audience This document is intended for all end-users of the fedora distribution. However it is my intention to present, as effectively as possible, this - topic so that the following experienced audience can readily acquire - valuable relevant information from this document as well: + topic so that the following categories of audience can readily acquire + valuable relevant information that corresponds to their skill level: System Administrators @@ -53,8 +76,8 @@ 2005-07-18 TRJ - Imported into fedora-docs CVS. Altered document outline. Added - the character device content. + Initial fedora-docs CVS access. Altered + document outline. From fedora-docs-commits at redhat.com Wed Aug 10 19:11:34 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Wed, 10 Aug 2005 15:11:34 -0400 Subject: yum-software-management yum-software-management-en.xml,1.32,1.33 Message-ID: <200508101911.j7AJBY7U007686@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7605 Modified Files: yum-software-management-en.xml Log Message: - Added Acknowledgements section. - Removed note on case-sensitivity as yum is actually only case-insensitive accidently, and this behaviour may not be relied on. - Added note on FC versions - section on enabling Fedora repositories on FC3 to come. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- yum-software-management-en.xml 28 Jul 2005 22:03:12 -0000 1.32 +++ yum-software-management-en.xml 10 Aug 2005 19:11:32 -0000 1.33 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -100,6 +100,17 @@ Experienced Linux users should start with . + + + Versions of &FC; + + + This document describes the configuration of + yum on &FED; &FCLOCALVER; systems. You must + manually configure yum on &FED; 3 to use + the &FED; repositories. + + Most of the examples in this document use the package @@ -418,10 +429,7 @@ - - - - + For clarity, yum itself lists packages in the format name.architecture. Repositories also @@ -909,17 +917,6 @@ installed and available packages. - - Searches are not Case-sensitive - - - The and options of - yum are not case-sensitive. A query for - palmpilot automatically finds - PalmPilot packages. - - - The format of the results depends upon the option. If the query produces no information, there are no packages matching the @@ -1054,9 +1051,9 @@ For example, a search query for shadowutils or shadow-util would not produce the package shadow-utils. This package would - match and be shown if the query was either - shadow-util\? or - Shadow\*. + match and be shown if the query was + shadow-util\?, or + shadow\*.
@@ -1633,6 +1630,17 @@
+ + +
+ Acknowledgements + + + Paul Frields edited this document. Timothy Murphy reviewed the + beta release. + +
+
From fedora-docs-commits at redhat.com Wed Aug 10 23:30:55 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Wed, 10 Aug 2005 19:30:55 -0400 Subject: yum-software-management yum-software-management-en.xml,1.33,1.34 Message-ID: <200508102330.j7ANUtVT013765@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13743 Modified Files: yum-software-management-en.xml Log Message: - Added manual key import required for FC3. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- yum-software-management-en.xml 10 Aug 2005 19:11:32 -0000 1.33 +++ yum-software-management-en.xml 10 Aug 2005 23:30:51 -0000 1.34 @@ -100,15 +100,16 @@ Experienced Linux users should start with . - + Versions of &FC; This document describes the configuration of yum on &FED; &FCLOCALVER; systems. You must - manually configure yum on &FED; 3 to use - the &FED; repositories. + perform the additional step described in + to enable + yum on &FED; 3. @@ -1247,6 +1248,25 @@ su -c 'rpm --import http://www.therepository.com/GPG-PUB-KEY.asc' + + At the prompt, enter the + root password. + + + + You must manually import all public keys on &FED; 3 and earlier + systems. This includes the &FED; public key. To import the &FED; + public key on &FED; 3, type this command: + + +su -c 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora' + + + At the prompt, enter the + root password. +
From fedora-docs-commits at redhat.com Fri Aug 12 12:47:18 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 12 Aug 2005 08:47:18 -0400 Subject: hardening hardening-tutorial-en.xml,1.2,1.3 Message-ID: <200508121247.j7CClIZA003502@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/hardening In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3483 Modified Files: hardening-tutorial-en.xml Log Message: Make sure your document will build before committing when possible... :-) Index: hardening-tutorial-en.xml =================================================================== RCS file: /cvs/docs/hardening/hardening-tutorial-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- hardening-tutorial-en.xml 26 Jul 2005 08:37:14 -0000 1.2 +++ hardening-tutorial-en.xml 12 Aug 2005 12:47:16 -0000 1.3 @@ -1377,7 +1377,7 @@ You can also find more information on md5sum, and a more complete - example in the previous section: . + example in the previous section: .
@@ -1448,7 +1448,7 @@ Disabling unnecessary users can stop possible attacks by limiting the avenues that an attacker can use to penetrate your system. The procedure has already been discussed in . + linkend="sn-userconfig-gui">. @@ -1498,7 +1498,7 @@ things to disable is root's direct access via SSH. If you plan not to use SSH for remote access to your system, then you can disable SSH completely as described in . However, if you ARE planning to + linkend="sn-services-gui">. However, if you ARE planning to use SSH, then you will want to limit direct access as root. "Direct access" means that you login to the system as root, instead of SSH'ing as a normal user, then su'ing to root (or using sudo, which will be discussed From fedora-docs-commits at redhat.com Fri Aug 12 13:24:58 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Fri, 12 Aug 2005 09:24:58 -0400 Subject: yum-software-management yum-software-management-en.xml,1.34,1.35 Message-ID: <200508121324.j7CDOwJ4004799@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4782 Modified Files: yum-software-management-en.xml Log Message: - Added note that FC3 requires Extras to be configured post-install. - Trivial style fix. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- yum-software-management-en.xml 10 Aug 2005 23:30:51 -0000 1.34 +++ yum-software-management-en.xml 12 Aug 2005 13:24:55 -0000 1.35 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -102,7 +102,7 @@ - Versions of &FC; + Previous Versions of &FED; This document describes the configuration of @@ -122,9 +122,9 @@ ApplicationsInternetTerminal Server Client. To use the examples, substitute the name of the relevant package for - tsclient. The &FED; package group - MySQL Database is used for the package - group examples. + tsclient. The example commands for &FED; + package groups use the MySQL Database + group. @@ -293,6 +293,17 @@ + Previous Versions of &FED; + + + &FED; &FCLOCALVER; automatically supports all three + repositories. You must manually configure &FED; 3 systems to + use &FEX;, as noted in + . + + + + All &FED; Packages are Open Source Software From fedora-docs-commits at redhat.com Sat Aug 13 21:36:34 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 13 Aug 2005 17:36:34 -0400 Subject: yum-software-management yum-software-management-en.xml,1.35,1.36 Message-ID: <200508132136.j7DLaYl1022835@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22818 Modified Files: yum-software-management-en.xml Log Message: - Moved out of beta - Removed draft notice - Made correction to note about configuration file retention Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- yum-software-management-en.xml 12 Aug 2005 13:24:55 -0000 1.35 +++ yum-software-management-en.xml 13 Aug 2005 21:36:31 -0000 1.36 @@ -17,8 +17,7 @@
- Software Management with <command>yum</command> - <emphasis>BETA - DOCUMENT</emphasis> + Software Management with <command>yum</command> 2005 Stuart Ellis @@ -61,12 +60,22 @@ + + 1.0 + 2005-08-13 + PaulWFrields + + + Publish to official project page. + + +
Introduction - &DRAFTNOTICE; +
Purpose @@ -443,12 +452,12 @@ - For clarity, yum itself lists packages in the - format name.architecture. Repositories also - commonly store packages in separate directories by architecture. - In each case, the hardware architecture specified for the - package is the minimum type of machine - required to use the package. + For clarity, yum lists packages in the format + name.architecture. Repositories also + commonly store packages in separate directories by architecture. + In each case, the hardware architecture specified for the + package is the minimum type of machine + required to use the package. @@ -716,15 +725,11 @@ This is an example of the public key import: - -warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 public key not available for tsclient-0.132-6.i386.rpm Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora Importing GPG key 0x4F2A6FD2 "Fedora Project " -Is this ok [y/N]: -]]> - +Is this ok [y/N]: @@ -901,12 +906,13 @@ - Data and Settings are Retained + Data and Configuration File Retention - The removal process leaves configuration files and data in - place. If you reinstall removed software the new installation - uses the original configuration files. + The removal process leaves user data in place but may remove + configuration files in some cases. If a package removal does + not include the configuration file, and you reinstall the + package later, it may reuse the old configuration file.
From fedora-docs-commits at redhat.com Sat Aug 13 21:43:27 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 13 Aug 2005 17:43:27 -0400 Subject: yum-software-management yum-software-management-en.xml,1.36,1.37 Message-ID: <200508132143.j7DLhR6M022861@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22844 Modified Files: yum-software-management-en.xml Log Message: Trivial style edit. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.36 retrieving revision 1.37 diff -u -r1.36 -r1.37 --- yum-software-management-en.xml 13 Aug 2005 21:36:31 -0000 1.36 +++ yum-software-management-en.xml 13 Aug 2005 21:43:24 -0000 1.37 @@ -1533,9 +1533,9 @@ Public Key is Required - You must ensure that the public key for the package source has - been imported before installing a package without a repository. - Refer to . + Ensure that the public key for the package source has been + imported before you install a package without a repository. + Refer to . From fedora-docs-commits at redhat.com Sat Aug 13 21:46:29 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 13 Aug 2005 17:46:29 -0400 Subject: yum-software-management yum-software-management-en.xml,1.37,1.38 Message-ID: <200508132146.j7DLkT4e022894@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22877 Modified Files: yum-software-management-en.xml Log Message: Fix to correct build problem, sorry Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.37 retrieving revision 1.38 diff -u -r1.37 -r1.38 --- yum-software-management-en.xml 13 Aug 2005 21:43:24 -0000 1.37 +++ yum-software-management-en.xml 13 Aug 2005 21:46:26 -0000 1.38 @@ -728,7 +728,7 @@ warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 public key not available for tsclient-0.132-6.i386.rpm Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora -Importing GPG key 0x4F2A6FD2 "Fedora Project " +Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora at redhat.com&rt;" Is this ok [y/N]: From fedora-docs-commits at redhat.com Sat Aug 13 21:47:22 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 13 Aug 2005 17:47:22 -0400 Subject: yum-software-management yum-software-management-en.xml,1.38,1.39 Message-ID: <200508132147.j7DLlM9V022918@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22901 Modified Files: yum-software-management-en.xml Log Message: Somebody shoot me, please... Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.38 retrieving revision 1.39 diff -u -r1.38 -r1.39 --- yum-software-management-en.xml 13 Aug 2005 21:46:26 -0000 1.38 +++ yum-software-management-en.xml 13 Aug 2005 21:47:19 -0000 1.39 @@ -728,7 +728,7 @@ warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 public key not available for tsclient-0.132-6.i386.rpm Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora -Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora at redhat.com&rt;" +Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora at redhat.com>" Is this ok [y/N]: From fedora-docs-commits at redhat.com Sat Aug 13 23:52:34 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 13 Aug 2005 19:52:34 -0400 Subject: docs-common/bin xmlformat-fdp.conf,1.3,1.4 Message-ID: <200508132352.j7DNqY8w026154@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26135/docs-common/bin Modified Files: xmlformat-fdp.conf Log Message: Make indexterm normalization explicit, add keycap Index: xmlformat-fdp.conf =================================================================== RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- xmlformat-fdp.conf 2 Aug 2005 21:45:50 -0000 1.3 +++ xmlformat-fdp.conf 13 Aug 2005 23:52:32 -0000 1.4 @@ -76,7 +76,7 @@ indexterm format = block -# normalize = yes + normalize = no primary secondary format = block @@ -90,7 +90,7 @@ entry-break = 0 exit-break = 0 -menuchoice guilabel guimenu guisubmenu guimenuitem guibutton +menuchoice guilabel guimenu guisubmenu guimenuitem guibutton keycap format = inline wordasword systemitem citetitle footnote From fedora-docs-commits at redhat.com Tue Aug 16 21:56:01 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 16 Aug 2005 17:56:01 -0400 Subject: docs-common/common deprecatednotice-en.xml, NONE, 1.1 fedora-entities-en.ent, 1.5, 1.6 Message-ID: <200508162156.j7GLu1QG003672@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3654 Modified Files: fedora-entities-en.ent Added Files: deprecatednotice-en.xml Log Message: Added deprecation notice to common entities --- NEW FILE deprecatednotice-en.xml --- DEPRECATED DOCUMENT This document is no longer supported by the &FDP;. One or more of the following situations may have occurred: Changes in Fedora may have made this document inaccurate. A more relevant document may be available. This document may have been subsumed in a different document. Refer to the revision history for more information. Index: fedora-entities-en.ent =================================================================== RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- fedora-entities-en.ent 2 Aug 2005 22:05:33 -0000 1.5 +++ fedora-entities-en.ent 16 Aug 2005 21:55:59 -0000 1.6 @@ -68,3 +68,4 @@ + From fedora-docs-commits at redhat.com Tue Aug 16 22:07:04 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 16 Aug 2005 18:07:04 -0400 Subject: updates Makefile,1.1,1.2 updates-en.xml,1.3,1.4 Message-ID: <200508162207.j7GM74ff004927@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/updates In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4903 Modified Files: Makefile updates-en.xml Log Message: Deprecated document but fixed Makefile first Index: Makefile =================================================================== RCS file: /cvs/docs/updates/Makefile,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Makefile 27 Aug 2004 20:01:07 -0000 1.1 +++ Makefile 16 Aug 2005 22:06:16 -0000 1.2 @@ -1,31 +1,30 @@ ############################################################################### -# Makefile for Fedora docs project +# Makefile for RHLP docs project # Created by: Tammy Fox -# Last edited by: Tammy Fox +# Last edited by: Tommy Reynolds # WARNING: need passivetex 1.24 for pdf generation to work # License: GPL -# Copyright 2003-2004 Tammy Fox, Red Hat, Inc. +# Copyright 2003 Tammy Fox, Red Hat, Inc. +# Copyright 2005 Tommy Reynolds, MegaCoder.com ############################################################################### -XSLPDF = ../xsl/main-pdf.xsl -XSLHTML = ../xsl/main-html.xsl -LANG = en -DOCNAME = updates-$(LANG) -XMLFILE = $(DOCNAME).xml +XSLPDF = ../docs-common/xsl/main-pdf.xsl +XSLHTML = ../docs-common/xsl/main-html.xsl +XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl +LANG = en +DOCNAME = updates-$(LANG) +XMLFILE = $(DOCNAME).xml +XMLEXTRAFILES = ###################################################### -html: - @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE) - @mkdir -p $(DOCNAME)/stylesheet-images - @cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images - @cp ../css/fedora.css $(DOCNAME) - @mkdir -p $(DOCNAME)/images/callouts - @cp /usr/share/sgml/docbook/xsl-stylesheets/images/callouts/*.png $(DOCNAME)/images/callouts - - -pdf: - @xmlto pdf -x $(XSLPDF) $(XMLFILE) +include ../docs-common/Makefile.common ###################################################### -clean: - @rm -rfv *.html *.pdf *.tex $(DOCNAME) +# If you want to add additional steps to any of the +# targets defined in "Makefile.common", be sure to use +# a double-colon in your rule here. For example, to +# print the message "FINISHED AT LAST" after building +# the HTML document version, uncomment the following +# line: +#${DOCNAME}/index.html:: +# echo FINISHED AT LAST Index: updates-en.xml =================================================================== RCS file: /cvs/docs/updates/updates-en.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- updates-en.xml 31 Aug 2004 02:03:25 -0000 1.3 +++ updates-en.xml 16 Aug 2005 22:06:16 -0000 1.4 @@ -3,18 +3,17 @@ + %FEDORA-ENTITIES-EN; - + - ]>
- Keeping Up to Date + Keeping Up to Date - DEPRECATED 2004 Red Hat, Inc. @@ -50,12 +49,25 @@ + + 0.1.4 + 16 August 2005 + PaulWFrields + + + Document deprecated. Refer to "Yum Software Management" tutorial + instead at + + +
Background + &DEPRECATEDNOTICE; + After installing &FC;, you should determine if your installation is up to date with the most recent package versions. If your CDs are more than a @@ -69,6 +81,8 @@
Updating Sources + &DEPRECATEDNOTICE; + The &FP; lists a number of Web resources which may be trusted and used for your updates. You may need more than one if you plan to download updates @@ -250,6 +264,8 @@
Using <command>yum</command> + &DEPRECATEDNOTICE; + yum is a command line program. man yum provides the local documentation. The basic operations are its setup, checking for From fedora-docs-commits at redhat.com Tue Aug 16 22:08:42 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 16 Aug 2005 18:08:42 -0400 Subject: updates updates-en.xml,1.4,1.5 Message-ID: <200508162208.j7GM8gL2004972@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/updates In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4951 Modified Files: updates-en.xml Log Message: One more page needs the notice Index: updates-en.xml =================================================================== RCS file: /cvs/docs/updates/updates-en.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- updates-en.xml 16 Aug 2005 22:06:16 -0000 1.4 +++ updates-en.xml 16 Aug 2005 22:08:37 -0000 1.5 @@ -320,6 +320,7 @@ References + &DEPRECATEDNOTICE; From fedora-docs-commits at redhat.com Tue Aug 16 22:37:04 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Tue, 16 Aug 2005 18:37:04 -0400 Subject: yum-software-management yum-software-management-en.xml,1.39,1.40 Message-ID: <200508162237.j7GMb423005314@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5297 Modified Files: yum-software-management-en.xml Log Message: - Amended title to be less clunky. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.39 retrieving revision 1.40 diff -u -r1.39 -r1.40 --- yum-software-management-en.xml 13 Aug 2005 21:47:19 -0000 1.39 +++ yum-software-management-en.xml 16 Aug 2005 22:37:02 -0000 1.40 @@ -17,7 +17,7 @@
- Software Management with <command>yum</command> + Managing Software with <command>yum</command> 2005 Stuart Ellis @@ -61,14 +61,14 @@ - 1.0 - 2005-08-13 - PaulWFrields - - - Publish to official project page. - - + 1.0 + 2005-08-13 + PaulWFrields + + + Publish to official project page. + + @@ -453,11 +453,11 @@ For clarity, yum lists packages in the format - name.architecture. Repositories also - commonly store packages in separate directories by architecture. - In each case, the hardware architecture specified for the - package is the minimum type of machine - required to use the package. + name.architecture. Repositories also + commonly store packages in separate directories by architecture. + In each case, the hardware architecture specified for the + package is the minimum type of machine + required to use the package. @@ -910,7 +910,7 @@ The removal process leaves user data in place but may remove - configuration files in some cases. If a package removal does + configuration files in some cases. If a package removal does not include the configuration file, and you reinstall the package later, it may reuse the old configuration file. @@ -1534,8 +1534,8 @@ Ensure that the public key for the package source has been - imported before you install a package without a repository. - Refer to . + imported before you install a package without a repository. + Refer to . From fedora-docs-commits at redhat.com Tue Aug 16 22:40:47 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 16 Aug 2005 18:40:47 -0400 Subject: yum-software-management yum-software-management-en.xml,1.40,1.41 Message-ID: <200508162240.j7GMelGQ005382@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5365 Modified Files: yum-software-management-en.xml Log Message: Bumping up the revision in canonical CVS. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.40 retrieving revision 1.41 diff -u -r1.40 -r1.41 --- yum-software-management-en.xml 16 Aug 2005 22:37:02 -0000 1.40 +++ yum-software-management-en.xml 16 Aug 2005 22:40:45 -0000 1.41 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + From fedora-docs-commits at redhat.com Wed Aug 17 02:45:13 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Tue, 16 Aug 2005 22:45:13 -0400 Subject: securing-filesystems sn-introduction.xml,1.2,1.3 Message-ID: <200508170245.j7H2jDIJ011872@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11855/securing-filesystems Modified Files: sn-introduction.xml Log Message: Aesthetic changes to structure. Index: sn-introduction.xml =================================================================== RCS file: /cvs/docs/securing-filesystems/sn-introduction.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- sn-introduction.xml 9 Aug 2005 23:16:40 -0000 1.2 +++ sn-introduction.xml 17 Aug 2005 02:45:11 -0000 1.3 @@ -17,6 +17,7 @@ Corporations and end-users alike benefit from the resultant product generated by a little due diligence and due care of the filesystems available to them. + This due diligence and due care will be presented as a review, implementation, and monitoring of the object instances that compose a filesystem by using the @@ -30,6 +31,7 @@ presented to ensure a cohesive and comprehensive understanding of the topic of filesystem access control. +
Intended Audience @@ -38,6 +40,7 @@ topic so that the following categories of audience can readily acquire valuable relevant information that corresponds to their skill level: + System Administrators Security Practitioners @@ -80,6 +83,7 @@ document outline. + 0.2 2005-05-13 @@ -89,6 +93,7 @@ inclusive nature of the document title. + 0.1 2005-05-04 @@ -165,6 +170,7 @@ Quoted text Quotes from people, quoted computer output. + terminal view @@ -172,12 +178,14 @@ terminal, usually rendered with a light grey background. + command Name of a command that can be entered on the command line. + VARIABLE @@ -185,6 +193,7 @@ in $VARNAME. + @@ -192,6 +201,7 @@ option to the ls command. + argument @@ -199,6 +209,7 @@ ls. + @@ -210,6 +221,7 @@ Command synopsis or general usage, on a separated line. + filename @@ -217,6 +229,7 @@ to the /usr/bin directory. + Key @@ -224,6 +237,7 @@ Q to quit. + Button @@ -231,6 +245,7 @@ button. + @@ -247,6 +262,7 @@ in your browser. + Terminology @@ -255,10 +271,12 @@ system. + See ????? link to related subject within this guide. + The authors From fedora-docs-commits at redhat.com Wed Aug 17 07:10:51 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Wed, 17 Aug 2005 03:10:51 -0400 Subject: docs-common/man - New directory Message-ID: <200508170710.j7H7ApvS019494@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/docs-common/man In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19479/man Log Message: Directory /cvs/docs/docs-common/man added to the repository From fedora-docs-commits at redhat.com Wed Aug 17 07:11:05 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Wed, 17 Aug 2005 03:11:05 -0400 Subject: docs-common/man/man1 - New directory Message-ID: <200508170711.j7H7B5vn019514@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/docs-common/man/man1 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19500/man1 Log Message: Directory /cvs/docs/docs-common/man/man1 added to the repository From fedora-docs-commits at redhat.com Wed Aug 17 07:58:04 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Wed, 17 Aug 2005 03:58:04 -0400 Subject: docs-common/bin tidy-bowl,1.1,1.2 Message-ID: <200508170758.j7H7w4Eh020026@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19997/bin Modified Files: tidy-bowl Log Message: A) Added man(1) page for tidy-bowl script B) Synchronized docs-common/bin version with the modules/ version. Index: tidy-bowl =================================================================== RCS file: /cvs/docs/docs-common/bin/tidy-bowl,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- tidy-bowl 27 Jun 2005 19:49:21 -0000 1.1 +++ tidy-bowl 17 Aug 2005 07:58:01 -0000 1.2 @@ -27,13 +27,15 @@ ME=`/bin/basename $0` PREFIX=`/usr/bin/dirname $0` ######################################################################## -USAGE="Usage: ${ME} [-T tool] [-t tool-args] file..." +USAGE="Usage: ${ME} [-T tool] [-n] [-t tool-args] file..." NORMTOOL=${PREFIX}/xmlformat -NORMARGS="-i -v -f ${PREFIX}/xmlformat-fdp.conf" -while getopts T:t: c +NORMARGS="-v -f ${PREFIX}/xmlformat-fdp.conf" +INPLACE='-i' +while getopts T:nt: c do case "${c}" in T) NORMTOOL="${OPTARG}";; + n) INPLACE="";; t) NORMARGS="${OPTARG}";; *) /bin/echo "${USAGE}" >&2; exit 1;; esac @@ -50,7 +52,7 @@ exit 1 fi # Try to clean it up - ${NORMTOOL} ${NORMARGS} "${fn}" + ${NORMTOOL} ${NORMARGS} ${INPLACE} "${fn}" if [ $? -ne 0 ]; then /bin/echo $0 "File '${fn}' unclean." exit 1 From fedora-docs-commits at redhat.com Wed Aug 17 07:58:04 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Wed, 17 Aug 2005 03:58:04 -0400 Subject: docs-common/man/man1 tidy-bowl.1,NONE,1.1 Message-ID: <200508170758.j7H7w4qh020031@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/docs-common/man/man1 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19997/man/man1 Added Files: tidy-bowl.1 Log Message: A) Added man(1) page for tidy-bowl script B) Synchronized docs-common/bin version with the modules/ version. --- NEW FILE tidy-bowl.1 --- .TH TIDY-BOWL 1 "2005-08-17" "GPL" "megacoder" .SH NAME tidy-bowl \- xml pretty printer .SH SYNOPSIS .B tidy-bowl [ .I \-T .B tool ] [ .I \-n ] [ .I \-t .B tool-args ] .IR file.xml " ..." .SH DESCRIPTION .LP The Fedora Document Project is a collaborative authoring environment where many different authors contribute individual paragraphs, separate files, or entire documents. To mask the text formatting foibles of individual authors, the Fedora Document Steering Committee has instituted an automated prettyprinting system. Each document checked into the Fedora Docs CVS repository is automatically normalized, or reformatted, to conform to a reasonable layout standard. .LP The format normalization is automatic: authors just check in their files normally and the reformatting tools are applied automatically. .LP So that authors can have access to the same technology used by the CVS system, a copy of the normalization tools are included in the .B docs-common/bin directory. .LP The .BR tidy-bowl( 1 ) script normalizes the formatting of all .B XML files as they are checked into the project's .B CVS repository. By enforcing a standardized source layout, .BR tidy-bowl( 1 ) minimalizes the differing text editing practices of multiple contributors. In the long term, this will keep the .B XML formatting uniform, so that the documents appear to be written by a single author. .LP Document authors need to recognize that after checking out a document, editing it, commiting the changes, the repository document may not match their local file, so a .sp 1 $ cvs diff myfile .sp 1 may display unexpected changes, because checking in a document applies the normalization in the .BR tidy-bowl( 1 ) rules. .SH BEST PRACTICES .LP Authors are encouraged to reformat their contributions using .BR tidy-bowl( 1 ) before committing any changes. This will tend to minimize any spurious differences that may result. .LP $ ../docs-common/bin/tidy-bowl myFile.xml .LP will reformat the document in-place. .LP $ ../docs-common/bin/tidy-bowl -n myFile.xml | less .LP will display the reformatted text using a pager. .SH OPTIONS .IP "\fI\-T\fP \fBtool\fP" By default, the actual formatting is done by the .BR xmlformat( 1 ) tool, assumed located in the same directory as the .BR tidy-bowl( 1 ) script. If the program is located in a different location on your system, or if you would prefer a different formatter, provide the path to that tool in the \fItool\fP argument. .IP "\fI\-t\fP \fBtool-args\fP" By default, .BR tidy-bowl( 1 ) runs the .B xmlformat tool using a configuration file .B xmlformat-fdp.conf located in the same directory as the tool. If you would like to use a different layout spec, or if you are using a different prettyprinting tool, supply the \fIentire\fP remaining command line in the \fBtool-args\fP argument. .IP "\fI\-n\fP" By default, .BR tidy-bowl( 1 ) updates the input .B XML files in place, overwriting the input content. For automatic operation as part of our .B CVS repository processing, this is what we want. If you would like to run the script but write the reformatted text to .I stdout instead, use the \fI\-n\fP switch instead. .IP file.xml... Each file to be processed must be given on the command line; .BR tidy-bowl( 1 ) is not true filter. The file name suffix must be ".xml", in any case combination. .SH SEE ALSO .BR xmlformat( 1 ), .SH AUTHOR .PD 0 .nf Tommy.Reynolds at MegaCoder.com .fi From fedora-docs-commits at redhat.com Wed Aug 17 16:58:21 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 17 Aug 2005 12:58:21 -0400 Subject: example-tutorial example-tutorial-en.xml,1.13,1.14 Message-ID: <200508171658.j7HGwLW1007058@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/example-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7041 Modified Files: example-tutorial-en.xml Log Message: Fix a little section guidance, omit superfluous entity declaration... time to get this underway shortly Index: example-tutorial-en.xml =================================================================== RCS file: /cvs/docs/example-tutorial/example-tutorial-en.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- example-tutorial-en.xml 14 Jun 2005 20:53:21 -0000 1.13 +++ example-tutorial-en.xml 17 Aug 2005 16:58:18 -0000 1.14 @@ -5,9 +5,7 @@ %FEDORA-ENTITIES-EN; - - - + ]> @@ -15,7 +13,7 @@ Example Tutorial - 2003 + 2003, 2005 &FORMAL-RHI; Tammy Fox @@ -41,9 +39,9 @@ - This is an example section. You can also use sect1, sect2, etc., but those - tags will make sections less modular — that is, harder to relocate - without changing a lot of other markup. + This is an example section. You should not use sect1, sect2, etc., since + those tags will make sections less modular — that is, harder to + relocate without changing a lot of other markup. Keep text within the title tags on the same line as the @@ -119,3 +117,9 @@
+ + From fedora-docs-commits at redhat.com Wed Aug 17 17:02:48 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 17 Aug 2005 13:02:48 -0400 Subject: yum-software-management yum-software-management-en.xml,1.41,1.42 Message-ID: <200508171702.j7HH2mlK008342@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8323 Modified Files: yum-software-management-en.xml Log Message: Removed superfluous entities; legal and draft notices declared in common stuff Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.41 retrieving revision 1.42 diff -u -r1.41 -r1.42 --- yum-software-management-en.xml 16 Aug 2005 22:40:45 -0000 1.41 +++ yum-software-management-en.xml 17 Aug 2005 17:02:18 -0000 1.42 @@ -6,12 +6,9 @@ - - - ]> From fedora-docs-commits at redhat.com Wed Aug 17 17:09:05 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 17 Aug 2005 13:09:05 -0400 Subject: jargon-buster jargon-buster-en.xml, NONE, 1.1 Makefile, 1.3, 1.4 fedora-jargon-buster-en.xml, 1.9, NONE Message-ID: <200508171709.j7HH95Ob008438@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8390 Modified Files: Makefile Added Files: jargon-buster-en.xml Removed Files: fedora-jargon-buster-en.xml Log Message: - Tidy-bowled doc. - Instead of 2200+ line diff, halved by renaming file to remove redundant "fedora-" - Fixed Makefile --- NEW FILE jargon-buster-en.xml --- %FEDORA-ENTITIES-EN; ]>
Fedora Jargon Buster 1.0 7 Nov 2003 DaveP Initial Release 1.1 8 Nov 2003 DaveP More added from Fedora list. 1.2 10 Nov 2003 DaveP More added from Fedora list. 1.3 10 Nov 2003 DaveP More added from various places (e.g. DV). 1.4 10 Nov 2003 DaveP Added LegalNotice and std ents. 1.5 11 Nov 2003 DaveP More additions from list. 1.6 11 Nov 2003 DaveP More additions from list and A-Z toc. Needs art.xsl 1.7 19 Dec 2003 DaveP Update 1.8 30 Jan 2004 TammyFox Modified to build in fedora-docs module, Red Hat is 2 words, other edits and corrections 1.9 7 Mar 2004 DaveP,TammyFox Added request for input statement, added KDE and VMware terms (DaveP); added trademark tags around relevant words in new entries and modified para on contributing (TammyFox) 1.9 30 Sept 2004 PaulWFrields,TammyFox Added Tettnang. &LEGALNOTICE; This document attempts to clarify some of the terms used on various lists, &RH; pages, and IRC, when talking about Linux, &RHL; versions, releases, etc. Many thanks to the people on the fedora-list at &RH; for their input. If you would like a word added to this document, please email the mailing list fedora-docs-list at redhat.com . A list to the subscription page is available on the project home page. If you find a problem with these terms, file a Bugzilla report against the fedora-docs component. There is also a bug reporting link on the project page as well. Jargon Buster alsa The Advanced Linux Sound Architecture (ALSA) provides audio and MIDI functionality to the Linux operating system. Refer to alsa-project.org Anaconda Anaconda is the installation program for Red Hat distributions. During installation, the system's hardware is identified and configured, and the appropriate file systems for the system's architecture are created. Finally, it allows the user to install the operating system software on the system. Optionally, it can upgrade existing Red Hat installations. Anaconda can run in a fully interactive mode (text or graphical), or in a kickstart mode, which is allows the installation to be scripted for unattended operation. Refer to &RH; apt-get Refer to https://moin.conectiva.com.br/AptRpm. APT (Advanced Package Tool) is a dependency tool, well known to Debian users since it is used by default with their dpkg packages. But apt has been ported to work with RPM packages too, by Conectiva, who has now used it for some time in their GNU/Linux distribution. The good news is that apt for RPM may be used with any other RPM-based distribution. All you need is the tool compiled for your version of RPM and at least a repository where RPM packages and their apt metadata can be downloaded from. ATrpms This is a 3rd party RPM repository for &RHL; distributions. The original focus laid upon software used in natural sciences, especially in the field of high energy physics, e.g. tools for numerical programming or such for scientific publications. But since then this repository has included many non-scientific software titles, like system tools or multimedia packages, resulting in a far more generic repository. Refer to atrpms.physik.fu-berlin.de BitTorrent An alternative to a simple FTP or HTTP download. Utilizes multiple channels to download. Refer to BitTorrent website Duke.edu This is the tracker for Fedora Core 1 'Yarrow' release. Bluecurve An easy-to-navigate interface with intuitively organized menus. Bluecurve has been upgraded in &RHL; 9 and now extends to more areas of the operating system, including the menu and layout of the desktop. Bugzilla This is the &RH; bug-tracking system, our database for recording bugs in &RH; products. For more information about the Bugzilla bug tracking system, please refer to the main Bugzilla home page. Core 1 The Yarrow version of Fedora. Sometimes abbreviated to FC 1 or fc1, Fedora Core 1. &RHL; Names Core 2 The Tettnang version of Fedora. Sometimes abbreviated to FC 2 or fc2, Fedora Core 2. &RHL; Names cron A daemon to execute scheduled commands, for example to check email each day at noon. Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; CUPS The Common UNIX Printing System ("CUPS") is a cross-platform printing solution for all UNIX environments. It is based on the "Internet Printing Protocol" and provides complete printing services to most PostScript and raster printers.Home page. desktop switcher The switchdesk-gnome package provides a GNOME look and feel for the Desktop Switcher program provided in the switchdesk package. eth0 (Normally) the first ethernet port on your system ethtool Ethtool is a Linux net driver diagnostic and tuning tool for the Linux 2.4.x (or later) series of kernels. It obtains information and diagnostics related to media, link status, driver version, PCI (or other) bus location, and more. FAQ Frequently Asked Questions, for Fedora see fedora.redhat.com FDL GNU Free Documentation License (FDL), see gnu.org FHS - File System Hierarchy Standard A collaborative document that defines the names and locations of many files and directories on a Linux system. Worth getting to know if you want to know what should go where. Refer to &RH; FreshRPMS A source of RPMs. Matthias Saou, the host, says: In late 2000, I started building quite a few RPM packages for my own needs, that couldn't easily be found elsewhere, or at least not so well suited for &RHL;. A few months later, the website on which these packages were hosted changed its name to become what people know today. A long time has passed and I still maintain all the packages I used to, and more of course! A whole community of users, testers and contributors has grown around the website and its packages, which is something I really didn't expect but really enjoy. Refer to freshrpms.net RPM fsck fsck is a command line tool used to check and optionally repair Linux file systems. fsh Remote command execution via a cryptographically strong method such as lsh or ssh is often painfully slow, especially if either of the involved computers is slow. The biggest problem is that the client and the server perform a lot of complex calculations during connection establishment. fsh uses lsh or ssh to establish a secure tunnel to the remote system. This takes as long as a normal connection establishment, but once the tunnel is established, fsh can reuse it to start new sessions on the remote system almost instantaneously. You get the security of ssh and the speed of rsh. gimp The GIMP is the GNU Image Manipulation Program. It is a freely distributed piece of software suitable for such tasks as photo retouching, image composition and image authoring. Refer to gimp.org glibc The GNU C library is used as the C library in the GNU system and most newer systems with the Linux kernel. Refer to gnu.org GNOME The GNOME Project is an effort to create a complete, free and easy-to-use desktop environment for users, as well as a powerful application development framework for software developers. Refer to Home page GPG GnuPG is a complete and free replacement for PGP. Because it does not use the patented IDEA algorithm, it can be used without any restrictions. GnuPG is a RFC2440 (OpenPGP) compliant application. Refer to gnupg.org. You may also see RPM-GPG-KEY referenced, which relates to the keys used for checking packages. E.g. see rpmfind GPL & non-GPL http://www.fsf.org/licenses/gpl-faq.htm Gnu General Public Licence. Refer to fsf.org GRUB GNU GRand Unified Boot loader or GRUB is a program which enables the user to select which installed operating system or kernel to load at system boot time. It also allows the user to pass arguments to the kernel. Refer to &RH; i386 i386. The entire x86 line of computers and processors, from the Intel 386 forward all the way to Intel Pentium 4 and Athlon chips. All those are compatible with i386 instruction sets, the "lowest common denominator". Often used as shorthand for the distribution set of files meant for this line of computers or processors. IRC IRC (Internet Relay Chat) channel. IRC is a real-time, text-based form of communication. With it, you can have conversations with multiple people in an open channel or chat with someone privately one-on-one. ISO As an acronym, ISO = International Standards Organization. More usefully, an abbreviation for the format of the downloadable version of the CD images, since the ISO defined the CD format. ISO standard ISO 9660:1988 entitled "Information processing -- Volume and file structure of CD-ROM for information interchange" does define the order of bits on a CD-ROM and so an image of an ISO 9660:1988 compliant media is called an ISO. For details see iso.org KDE KDE is a desktop environment for UNIX workstations. KDE seeks to fill the need for an easy to use desktop for Unix workstations, similar to the desktop environments found under Mac OS or Microsoft Windows. Refer to the Home page for more information. kernel The heart of Linux. The main code derived from Linus's original software. kickstart Many system administrators would prefer to use an automated installation method to install &RHL; on their machines. To answer this need, &RH; created the kickstart installation method. Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical &RHL; installation. Refer to &RH; Kudzu kudzu is the hardware autodetection & configuration tool, originally introduced in &RHL; 6.1. It detects changes in the system's hardware configuration, and gives the option of configuring added or removed devices. It's set up by default to run at each boot. fedora.redhat.com for more. LDAP Lightweight Directory Access Protocol lilo LILO (LInux LOader) is a basic system program which boots your Linux system. LILO loads the Linux kernel from a floppy or a hard drive, boots the kernel and passes control of the system to the kernel. LILO can also boot other operating systems. LSB Linux standard base. The goal of the LSB is to develop and promote a set of standards that will increase compatability among Linux distributions linuxbase.org lspci lspci is a utility for displaying information about all PCI buses in the system and all devices connected to them. Mandrake Another Linux distribution md5sum md5sum computes a 128-bit checksum (or fingerprint or message-digest) for each specified file. Refer to gnu.org for Linux man pages. Why is it useful? Having downloaded Fedora, you'll mostly see a related file MD5SUM which holds some rather strange numbers. Run md5sum against the downloaded file or image, and you'll see a match if you are lucky, or if you don't get the match, you can be assured that the download is somehow faulty, and you need to download again, before you burn the CD. For windows, activestate.com Memtest86 Memory testing may be performed prior to installing Fedora Core by entering memtest86 at the boot: prompt. This causes the Memtest86 standalone memory testing software to run. Memtest86 memory testing continues until the Esc key is pressed. Mount point Mounting a CD is the equivalent of telling the Operating System that you want to use it. In Linux the only file system that is automatically mounted is the root file system which is automatically mounted on the root directory. Other file systems (eg. your floppy drive, cd rom drive, windows partitions, and any linux partitions other than root) can be mounted and unmounted as required. In the case of drives used with portable media (such as floppy drives, cd rom drives, and zip drives) it is necessary to unmount the drive before being able to remove the media from the drive. Mozilla Mozilla is an open-source web browser, designed for standards compliance, performance and portability. Refer to Mozilla.org Nautilus The graphical desktop includes a file manager called Nautilus that gives you a graphical display of your system and personal files. Nautilus is designed to be much more than a visual listing of files, however. It allows you to configure your desktop, configure your &RHL; system, browse your photo collection, access your network resources, and more all from one integrated interface. In essence, Nautilus becomes a shell for your entire desktop experience. redhat package An alternate name for an RPM. Usually a number of files which together form an application or other usable software entity. Normally meant for installation by a package manager RPM redhat-config-packages pine Pine — a Program for Internet News & Email — is a tool for reading, sending, and managing electronic messages (email). Refer to washington.edu Psyche The name given to &RHL; 8 &RHL; Names Rawhide The bleeding edge, Rawhide is where the next version of packages are developed and tested. It is usually sort of stable, but on any given day any given package MIGHT be badly broken where the programmers are trying to add something or change something. Do not use on production machines, use at your own risk, etc. &RHL; Names Tettnang, Yarrow, Shrike, Psyche, et al. Names are given to individual versions of &RHL; and &DISTRO; for reference and easy memory. People often forget whether they are using RHL 8.0 (Psyche), RHL 9 (Shrike), or Fedora Core 1 (Yarrow), but the names are harder to forget. Note that other operating systems do the same thing, including other Linux distros and Microsoft (various versions of Windows have been named Chicago, Cairo, etc.). RHEL &RHEL; is the premiere operating system for open source computing. It's sold by annual subscription, runs on seven system architectures, is certified by top enterprise software and hardware vendors, and backed by a &RHN; subscription and up to 24x7 support with one-hour response. Refer to &RH; for more. redhat-config-packages redhat-config-packages is the package manager for &RHL; and &DISTRO;. It supports installation of packages from CD or other sources &RH; End User Licence Agreement (RHEULA) Each of &RH; software products is covered by an End User License Agreement. Refer to &RH; rhgb &RH; Graphical Boot. Fedora Core 1 now uses a graphical interface while booting. The graphical boot screen will appear once the kernel has loaded. Graphical booting is controlled by the GRAPHICAL line in the /etc/sysconfig/init file; set it to "no" to permanently disable graphical booting. In addition, the parameter rhgb must be appended to your bootloader command line. Systems that have been upgraded to Fedora Core 1 will not be configured to include the graphical boot feature. You must install the rhgb package, and add the rhgb boot-time parameter to your bootloader configuration. RHN &RHN; RHN Applet This applet, although called the rhn-applet really has nothing to do with RHN in Fedora. It is really just the convenient mechanism for GUI access to up2date. RPM &RH; Package Manager, or nowadays, RPM Package Manager. The standard way to build and distribute any application for &RHL;, &DISTRO;, and other Linux distributions that now use the same format. This includes Mandrake and possibly others of which I might be unaware. RPM is also the name for the application and command with which you install, upgrade, query, or remove an RPM package, and you often refer to a package as "the Apache RPM" meaning the RPM file for that application. Can also check dependencies between installed and new packages. Rsync rsync is an open source utility that provides fast incremental file transfer. Refer to samba.anu.edu SELinux nsa.gov, from which, Security-Enhanced Linux. This version of Linux has a strong, flexible mandatory access control architecture incorporated into the major subsystems of the kernel. Severn The beta version of Fedora, closed off early November 2003, severn was the beta version 0.95 Shrike The name given to &RHL; 9 &RHL; Names Sodipodi Sodipodi is general vector illustrating application for Linux/Unix and Windows. It uses W3C SVG as native file and in-memory image format and can do many neat things. Refer to Sourceforge SRPMs Source RPM, contains the source code for the package in case you want to read it or modify it. You do not need any SRPMS to install or use the software. RPM Tettnang "Tettnang" is the second release (version 2) of Fedora Core. &RHL; Names Core 2 Up2date up2date is a complete system for managing and updating RPM packages on &RHL; and &DISTRO; system. It has both command line and gui modes. Refer to &RH; site for more detail. VMware A commercial product, VMware Workstation is virtual machine software for the desktop. Optimized for the power user, VMware Workstation runs multiple operating systems, including Microsoft Windows, Linux, and Novell NetWare, simultaneously on a single PC in fully networked, portable virtual machines. VMware Workstation works by enabling multiple operating systems and their applications to run concurrently on a single physical machine. These operating systems and applications are isolated in secure virtual machines that co-exist on a single piece of hardware. The VMware virtualization layer maps the physical hardware resources to the virtual machine's resources, so each virtual machine has its own CPU, memory, disks, I/O devices, etc. Virtual machines are the full equivalent of a standard x86 machine. Refer to its home page for more information. VNC VNC stands for Virtual Network Computing. It is remote control software which allows you to view and interact with one computer (the "server") using a simple program (the "viewer") on another computer anywhere on the Internet. Refer to realvnc.com XFS XFS is a journalling filesystem developed by SGI and used in SGI's IRIX operating system. It is now also available under GPL for linux. It is extremely scalable, using btrees extensively to support large and/or sparse files, and extremely large directories. The journalling capability means no more waiting for fsck's or worrying about meta-data corruption. Refer to oss.sgi.com Ximian Provides a modified version of GNOME, which can be installed on a Linux distributions. Warning: After installing Ximian GNOME, it must be uninstalled before upgrading &RHL; or &DISTRO;. Refer to the Release Notes for details. Ximian had its genesis in the GNOME project and offers a complete Linux desktop environment and productivity application suite. Refer to the home page. The company was founded by some of the GNOME developers as a commercial entity related to GNOME. This led to the development of Evolution and improvement in GNOME. Bought by Novell Aug 2003 X Window System Possibly a misnomer, though often used to describe the GUI (Window like ) user interface for Linux. Refer to ntlug.org for the rationale. Yarrow "Severn" was a beta version of Fedora and "yarrow" is the first release version 1, November 6, 2003 Also, yarrow - ubiquitous strong-scented mat-forming Eurasian herb of wasteland, hedgerow or pasture having narrow serrate leaves and small usually white florets; widely naturalized in North America. Yarrow is also, like Severn, a river in the UK. &RHL; Names Core 1 Yum Yum is an automatic updater and package installer/remover for RPM systems. It automatically computes dependencies and figures out what actions should occur to install packages. Refer to Duke University
Index: Makefile =================================================================== RCS file: /cvs/docs/jargon-buster/Makefile,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Makefile 24 Feb 2004 19:14:47 -0000 1.3 +++ Makefile 17 Aug 2005 17:09:02 -0000 1.4 @@ -1,29 +1,30 @@ ############################################################################### # Makefile for RHLP docs project # Created by: Tammy Fox -# Last edited by: Tammy Fox +# Last edited by: Tommy Reynolds # WARNING: need passivetex 1.24 for pdf generation to work # License: GPL -# Copyright 2003-2004 Tammy Fox, Red Hat, Inc. +# Copyright 2003 Tammy Fox, Red Hat, Inc. +# Copyright 2005 Tommy Reynolds, MegaCoder.com ############################################################################### -XSLPDF = ../xsl/main-pdf.xsl -XSLHTML = ../xsl/main-html.xsl -LANG = en -DOCNAME = fedora-jargon-buster-$(LANG) -XMLFILE = $(DOCNAME).xml +XSLPDF = ../docs-common/xsl/main-pdf.xsl +XSLHTML = ../docs-common/xsl/main-html.xsl +XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl +LANG = en +DOCNAME = jargon-buster-$(LANG) +XMLFILE = $(DOCNAME).xml +XMLEXTRAFILES = ###################################################### -html: - @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE) - @mkdir -p $(DOCNAME)/stylesheet-images - @cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images - @cp ../css/fedora.css $(DOCNAME) - - -pdf: - @xmlto pdf -x $(XSLPDF) $(XMLFILE) +include ../docs-common/Makefile.common ###################################################### -clean: - @rm -rfv *.html *.pdf *.tex $(DOCNAME) +# If you want to add additional steps to any of the +# targets defined in "Makefile.common", be sure to use +# a double-colon in your rule here. For example, to +# print the message "FINISHED AT LAST" after building +# the HTML document version, uncomment the following +# line: +#${DOCNAME}/index.html:: +# echo FINISHED AT LAST --- fedora-jargon-buster-en.xml DELETED --- From fedora-docs-commits at redhat.com Thu Aug 18 03:25:17 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Wed, 17 Aug 2005 23:25:17 -0400 Subject: securing-filesystems ch-constitutes_filesystem.xml,NONE,1.1 Message-ID: <200508180325.j7I3PHkG026069@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26053/securing-filesystems Added Files: ch-constitutes_filesystem.xml Log Message: Initial Commit to the Fedora Docs Repository --- NEW FILE ch-constitutes_filesystem.xml --- What Constitutes a Filesystem? That is a pretty broad question. Take the following definition into consideration:
The Free On-line Dictionary of Computing file system (FS, or "filesystem") 1. A system for organizing directories and files, generally in terms of how it is implemented in the disk operating system. E.g., "The Macintosh file system is just dandy as long as you don't have to interface it with any other file systems". 2. The collection of files and directories stored on a given drive (floppy drive, hard drive, disk partition, logical drive, RAM drive, etc.). E.g., "mount attaches a named file system to the file system hierarchy at the pathname location directory [...]" -- Unix manual page for "mount(8)". As an extension of this sense, "file system" is sometimes used to refer to the representation of the file system's organization (e.g. its file allocation table) as opposed the actual content of the files in the file system. Unix manual page: fs(5), mount(8). (1997-04-10)
Although the above statements properly define a filesystem, they do not properly convey the complexities and nuances presented when interacting and securing the various types of filesystems available to an end-user of the &FC; distribution. It does, however, present a generalized description at a higher-level. This high-level description is sufficient if you have a very limited exposure to the components of a given filesystem. Then again that is not what we are here to do, is it? With this in mind, we will be delving much deeper into the internals of the entity collectively known as the "filesystem" to gain as much valuable knowledge as possible to properly and most of all securely administer the filesystem(s) available to the end-users of the &FC; distribution. We are going to dive in head first into the convoluted world of objects, subjects, and the permissions utilized by these entities during their communications with one another. The intention of this entire chapter is to build a in-depth understanding of the internal structure of a filesystem and the utilization of the data contained therein. Within the next few sections we will review these points and begin to build a solid comprehension of the object and subject relationship that is the cornerstone of access control and subsequently a secure filesystem. Now that we are done kicking the tires — lets open the hood and see what this baby has got, shall we?!
Filesystem Standardization and Compliance
What is a Standard? With regards to a filesystem, a standard is a published document that contains a set of guidelines as to what, when, and how a specific entity should behave in a given situation. Essentially, the documents that are referenced in the following sections are all guidelines for the placement, structure, and behavior of the objects that compose a filesystem. As you will soon see, these are just guidelines. These guidelines are not regulatory requirements. Deviation from a standard is generally discouraged by the regulatory bodies. However, you will be presented with some situations that warrant such a deviation from the standard. I don't want to ruin it for you by saying anything more — so let's get started.
Standards Implemented in Fedora Fedora attempts to comply with as many of the industry standards as possible. This position helps to ensure that the &FC; distribution complies with the technical computing capabilities as the distribution is further developed and is inundated with advances into more complex and exciting technologies as they become available to the public.
The Filesystem Hierarchy Standard This standard, commonly referred to as the FHS, has been developed to provide a set of requirements and guidelines for file and directory placement under any UNIX-like operating system. It is intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these operating systems. With reference to the topic at hand, it also provides the capability to determine the appropriate access permissions needed for a given object; due to the fact that this standardization provides another source of information to ascertain the intended purposes of the object located within this FHS-compliant system. This of course is further dependent on the filesystem objects themselves. Given the information provided by the FHS and that derived from the procedures performed in various other sections of this document, we can reliably begin to secure the filesystems of fedora.
IEEE &posix;.1 The following &posix; draft standards are recognized: &posix; 1003.1e - Security APIs &posix; 1003.2c - Security Command and Utilities It is important to recognize that these are draft standards. Thus, these drafts have not been officially approved for recommendation as a standard by the standards bodies. However, given that there is a void of comparative standards in the area of access control; these specifications are currently the best-of-breed.
Yes! Fedora is Non-Compliant Give listing of non-compliance.
A Review of the Structure and Objects of a Filesystem In order to understand and follow the concepts and procedures provided in this section there will need to be a degree of familiarity with the commands, their available options and related terminology. This information is not meant as a replacement for the commands documentation(e.g. Manual Pages) but is intended as a tool to obtain a brief summary of the resources utilized in this section. Please read and familiarize yourself with the following resources before continuing. Key Terminology and Concepts object - this entity is passive in nature. The object is the entity that provides the information or data that is being requested. subject - this entity is active in nature. The subject is the entity that is requesting the information or data that is located in or about the object. access - the process of information transfer between an object and a subject. ls - the application utilized to list the contents of a directory object type. Common options are as follows: the option formats the output into a long listing. Provides details such as mode-based permissions, owning user and owning group. The option presents the information for the directory object type instead of its contents. This option queries the parent object to the requested directory object type to obtain the appropriate information. stat - the application utilized to display the status of an object or filesystem. Common options are as follows: the option presents the status of a filesystem rather than the status of the special object that is associated with the requested entity. It is very important that the concept of an object and subject is easily understood. Otherwise, procedures and/or techniques presented in later chapters will be without meaning. I would like to take the time to re-emphasize that a subject is the active entity that is requesting the data or information. Conversely, the object is the passive entity that houses the data or information that is being requested!
Standard Objects
Regular File The regular file object is the most prevalent object type found in a &FC; system. On my development system there are some 263,000 plus regular file objects. This number will vary greatly between different systems due to installed applications, and the utilization of the system itself. The amount of regular file objects located on your system is not significant to the topic at hand. However, it is relevant to know that most objects that you will be securing will be of this type of filesystem object. The regular file object type is composed of a great many file types. Yes, that is very confusing; but read on. There are two very different and completely separate references to a file type in a Linux operating system such as &FC;. These references are not as relevant to a regular file object type as they are of the special object type but are indeed a needed facility to convey the applicability of these concepts for all objects that compose a filesystem. First, is the file type that is utilized in kernel-space — from this point forward known as the object file type to reduce confusion. This object file type is an all-encompassing data object for all objects of the regular file type. Essentially the kernel bundles all the regular file objects into a single category, the object file type when processing these objects. It is irrelevant to the kernel whether or not a file being accessed is a shell script or an XML file. All the object file types are accessed the same way within the kernel-space. This is in direct contrast to how the kernel reacts when presented with the filesystem objects that are considered to be of a special type. You may read this information in Special Objects. Second, is the file type that is utilized in user-space . This file type is the entity that you as an end-user will interact with on a daily basis and is considered the standard form of a regular file objects file type(unless you are a kernel or device driver developer). In contrast with the kernel-space version, this file type is not all-encompassing at all. In user-space, the regular file objects are distinctly separated according to the attributes of the object in question. These types of files are sometimes identified by the file extension portion of the filename that is declared for this regular file object in its parent directory object. And yet they sometimes are identified by the data or information located in the file itself. I can hear you already saying -- "What does that mean?". This concept comes into play when determining the purpose of the regular file object which will be presented and performed in Determining a Filesystem Objects Purpose. To make things a little easier to understand, lets perform analysis of an object believed to be of the regular file object type. As are most scenarios in a Linux environment, there are many ways to go about obtaining the same information. We will obtain this information by utilizing various methods and alterative procedures so that we cannot only establish the necessary steps needed but also to become increasingly familiar with the Linux environment and its available security mechanisms. The first procedure we will perform in this section will be to identify whether or not the object is in fact of the regular file object type. This procedure is performed in the following different steps: - Using the ls command - Using the stat command Using the <command>ls</command> command The use of the ls command sequence will perform a listing of the object that we request which is located in the current directory(which happens to be the directory /home/thomas/Documents/example) and presents the output in a long format. Execution of the command thomas at bodhittsatva:~/Documents/example> ls -l watch_osiris.sh Output from the command As you can see from the output below, the long format option provides us a great deal of information about the regular file objects in this directory. -rwxr--r-- 1 thomas thomas 2506 2005-08-01 10:34 watch_osiris.sh Analysis of the output The example output above provides other information such as permissions. But, this will be reviewed in another chapter so we will disregard this information at this time and continue on with our topic. Upon review of the example output presented in , we can determine the following specific information about the suspected regular file object: <filename> /home/thomas/Documents/example/watch_osiris.sh </filename> This filesystem object is a regular file. The representation of this information is in the form of the - (dash) preceeding the informational image location. This regular file object is owned by the thomas owner This regular file object is owned by the thomas owning group Using the ??? command The same information can be gleaned from the utilization of the ??? command.
Directory
Special Objects
Character Device As are most objects of a native filesystem of a linux operating system, the special files known as character devices are also categorized as file-like objects. Many characteristics of a device file object are similar and sometimes identical to that of the filesystem objects previously discussed. However, there are a few key differences between other filesystem objects and character device objects that will need to be examined. We will review the affect these differences have on the specific filesystem object as well as the security implications these differences have on the fedora system as a whole. Building upon the previous examples, a character device is accessed by the end-user via the names given them in the filesystem. These names can be determined by a low-level review of the directory entries that are located in the directory object that is parent to the character device. Generally, most character devices are located in the /dev directory. This convention is standardized by the following standards bodies: Filesystem Hierarchy Standard The most current standardization at time of this writing is 2.3 Linux Standard Base The most current standardization at time of this writing is 3.0 The related specification is located in Chapter 5, Section 12.1 Single Unix Specification The most current standardization at time of this writing is ????? As has been previously declared, we will be utilizing the &fhs; specification as the standardization of choice for this document. You may navigate to the following link for more information about character devices implemented under the &fhsu; standard: http://www.pathname.com/fhs/pub/fhs-2.3.html#DEVDEVICEFILES Sometimes a character device is also called a
Block Device
Symbolic Link
Socket
Pipe
Administrative Objects
Inode: the Administration Data Object
Understanding a Pathname
Types of Filesystems The following sections provide a listing of the filesystems that are supported by the fedora kernel. This listing in no way is meant to be an all inclusive summary. Due to the Linux kernels open source licensing there are a great multitude of filesystems that have been developed and/or ported for use. This licensing unencumberance provides end-users, and all users of Linux distributions; an easy avenue by which to remedy stability and integrity issues of their filesystems introduced by various other operating systems.
Ext2
Ext3
ReiserFS
JFS
XFS
CFS
TCFS
RAMFS
From fedora-docs-commits at redhat.com Thu Aug 18 22:52:54 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Thu, 18 Aug 2005 18:52:54 -0400 Subject: yum-software-management yum-software-management-en.xml,1.42,1.43 Message-ID: <200508182252.j7IMqsTG027843@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27815 Modified Files: yum-software-management-en.xml Log Message: - Added note about installing without repository to the "Managing" section, so that the section reads better on the Website. - Amended section on manually adding keys, as yum 2.1.1 does actually support gpgcheck (if you have a definition file that actually uses the option). - Tidied up wording of "Repository Compatibility" on alternatives to Fedora packages. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.42 retrieving revision 1.43 diff -u -r1.42 -r1.43 --- yum-software-management-en.xml 17 Aug 2005 17:02:18 -0000 1.42 +++ yum-software-management-en.xml 18 Aug 2005 22:52:52 -0000 1.43 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -113,7 +113,7 @@ This document describes the configuration of yum on &FED; &FCLOCALVER; systems. You must - perform the additional step described in + perform the additional step noted in to enable yum on &FED; 3. @@ -618,14 +618,19 @@ Use the yum utility to modify the software on - your system in three ways: + your system in four ways: - To install new software from repositories or a package file + To install new software from package repositories + + + + + To install new software from an individual package file @@ -640,6 +645,18 @@ + + + Installing Software from a Package File + + + The yum commands shown in this section use + repositories as package sources. Refer to + for details of + using yum to install software from an + individual package file. + + To use yum, specify a function and one or more @@ -690,13 +707,10 @@ - Review the list of changes, and then press - y - to accept and begin the process. If you press - N - or - Enter - , yum does not download or change any packages. + Review the list of changes, and then press y to + accept and begin the process. If you press N or + Enter , yum does not download + or change any packages. @@ -710,9 +724,9 @@ - The yum utility imports the repository public - key if it is not already installed on the rpm - keyring. + The yum utility also imports the repository + public key if it is not already installed on the + rpm keyring. @@ -731,13 +745,18 @@ - Check the public key, and then press - y - to import the key and authorize the key for use. If you press - N - or - Enter - , yum stops without installing any packages. + Check the public key, and then press y to import + the key and authorize the key for use. If you press + N or Enter , + yum stops without installing any packages. + + + + To ensure that downloaded packages are genuine, + yum verifies the digital signature of each + package against the public key of the provider. Once all of the + packages required for the transaction are successfully downloaded + and verified, yum applies them to your system. Downloads are Cached @@ -1268,19 +1287,15 @@ class="username">root password. - - You must manually import all public keys on &FED; 3 and earlier - systems. This includes the &FED; public key. To import the &FED; - public key on &FED; 3, type this command: - - -su -c 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora' - - - At the prompt, enter the - root password. - + + Importing the &FED; Key on &FED; 3 + + + To add the &FED; public key to the rpm + keyring on &FED; 3 systems, run the command su -c + 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'. + +
@@ -1304,18 +1319,24 @@ Always read the web site of the repository for information on package compatibility before you add it as a package source. Separate repository providers may offer different and - incompatible versions of the same software. In some cases, - third-party repositories may also include alternative packages - for software provided by &FP; repositories that are not - compatible with other &FED; packages. + incompatible versions of the same software. Third-party + repositories may also provide alternative packages for software + that is included in &FED; repositories. + + + + Alternative packages may contain versions of the software that + function differently from the version in the &FP; packages. + Determine the benefits and potential incompatibilities before + replacing &FP; packages with alternative versions. Incompatible Repositories - If you use incompatible repositories yum - operations may fail. + If you configure your system to use incompatible repositories + yum operations may fail. @@ -1477,9 +1498,9 @@ By default, yum retains the packages and - package data files that it downloads, so they may be reused in - future operations without being downloaded again. To purge the - package data files, use this command: + package data files that it downloads, so that they may be reused + in future operations without being downloaded again. To purge + the package data files, use this command: su -c 'yum clean headers' From fedora-docs-commits at redhat.com Fri Aug 19 20:09:15 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Fri, 19 Aug 2005 16:09:15 -0400 Subject: yum-software-management yum-software-management-en.xml,1.43,1.44 Message-ID: <200508192009.j7JK9FeF031814@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31797 Modified Files: yum-software-management-en.xml Log Message: Very minor tweak Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.43 retrieving revision 1.44 diff -u -r1.43 -r1.44 --- yum-software-management-en.xml 18 Aug 2005 22:52:52 -0000 1.43 +++ yum-software-management-en.xml 19 Aug 2005 20:09:12 -0000 1.44 @@ -1147,7 +1147,7 @@ script activates the script /etc/cron.daily/yum.cron, which causes the cron service to perform the system - update automatically each day. + update automatically at 4am each day.
From fedora-docs-commits at redhat.com Sat Aug 20 14:34:12 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 20 Aug 2005 10:34:12 -0400 Subject: docs-common Makefile.common,1.7,1.8 Message-ID: <200508201434.j7KEYCIM031324@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31307/docs-common Modified Files: Makefile.common Log Message: Omit sizable .EPS files from tarball makes, since they are not useful anyway Index: Makefile.common =================================================================== RCS file: /cvs/docs/docs-common/Makefile.common,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- Makefile.common 12 Jul 2005 15:28:36 -0000 1.7 +++ Makefile.common 20 Aug 2005 14:34:09 -0000 1.8 @@ -32,7 +32,7 @@ # document into a compressed tar archive. tarball ${DOCNAME}.tar.gz:: ${DOCNAME}/index.html - tar -zcf ${DOCNAME}.tar.gz ${DOCNAME} + tar -zc --exclude '*.eps' -f ${DOCNAME}.tar.gz ${DOCNAME} # The "pdf" or "${DOCNAME}.pdf" target produces an Adobe Portable Document # Format (PDF) file as output. From fedora-docs-commits at redhat.com Sat Aug 20 21:34:53 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 20 Aug 2005 17:34:53 -0400 Subject: docs-common/common fedora-entities-en.ent,1.6,1.7 Message-ID: <200508202134.j7KLYrXG008827@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8810/docs-common/common Modified Files: fedora-entities-en.ent Log Message: Add entity for FDP Bugzilla product Index: fedora-entities-en.ent =================================================================== RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- fedora-entities-en.ent 16 Aug 2005 21:55:59 -0000 1.6 +++ fedora-entities-en.ent 20 Aug 2005 21:34:50 -0000 1.7 @@ -26,6 +26,7 @@ http://bugzilla.redhat.com/"> + From fedora-docs-commits at redhat.com Sat Aug 20 21:35:23 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 20 Aug 2005 17:35:23 -0400 Subject: docs-common/bin xmlformat-fdp.conf,1.4,1.5 Message-ID: <200508202135.j7KLZOKh008865@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8836/docs-common/bin Modified Files: xmlformat-fdp.conf Log Message: Add formatting for email XML tag Index: xmlformat-fdp.conf =================================================================== RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- xmlformat-fdp.conf 13 Aug 2005 23:52:32 -0000 1.4 +++ xmlformat-fdp.conf 20 Aug 2005 21:35:21 -0000 1.5 @@ -93,7 +93,7 @@ menuchoice guilabel guimenu guisubmenu guimenuitem guibutton keycap format = inline -wordasword systemitem citetitle footnote +wordasword systemitem citetitle footnote email format = inline # Make and less goofy in their use of whitespace From fedora-docs-commits at redhat.com Sun Aug 21 13:27:03 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 21 Aug 2005 09:27:03 -0400 Subject: docs-common/common bugreporting-en.xml,NONE,1.1 Message-ID: <200508211327.j7LDR3qY002842@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2826/common Added Files: bugreporting-en.xml Log Message: Add snippet for bug reporting; this entity should go in introduction to every document --- NEW FILE bugreporting-en.xml --- Reporting Document Errors To report an error or omission in this document, file a bug report in &BZ; at &BZ-URL;. When you file your bug, select "&BZ-PROD;" as the Product, and select the title of this document as the Component. The version of this document is &BOOKID;. The maintainers of this document will automatically receive your bug report. On behalf of the entire &FED; community, thank you for helping us make improvements. From fedora-docs-commits at redhat.com Sun Aug 21 13:30:33 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 21 Aug 2005 09:30:33 -0400 Subject: docs-common/common fedora-entities-en.ent,1.7,1.8 Message-ID: <200508211330.j7LDUXBZ002880@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2863 Modified Files: fedora-entities-en.ent Log Message: Add bug-reporting snippet to entities Index: fedora-entities-en.ent =================================================================== RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- fedora-entities-en.ent 20 Aug 2005 21:34:50 -0000 1.7 +++ fedora-entities-en.ent 21 Aug 2005 13:30:31 -0000 1.8 @@ -48,6 +48,7 @@ + @@ -65,7 +66,7 @@ "> "> - + From fedora-docs-commits at redhat.com Sun Aug 21 14:07:57 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 21 Aug 2005 10:07:57 -0400 Subject: docs-common/common fedora-entities-en.ent,1.8,1.9 Message-ID: <200508211407.j7LE7vDn004171@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4138 Modified Files: fedora-entities-en.ent Log Message: Oops, do that entity correctly... Index: fedora-entities-en.ent =================================================================== RCS file: /cvs/docs/docs-common/common/fedora-entities-en.ent,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- fedora-entities-en.ent 21 Aug 2005 13:30:31 -0000 1.8 +++ fedora-entities-en.ent 21 Aug 2005 14:07:53 -0000 1.9 @@ -48,7 +48,7 @@ - + From fedora-docs-commits at redhat.com Wed Aug 24 12:30:29 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 24 Aug 2005 08:30:29 -0400 Subject: documentation-guide docs-getting-files-en.xml,1.3,1.4 Message-ID: <200508241230.j7OCUTQi019297@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/documentation-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19280 Modified Files: docs-getting-files-en.xml Log Message: Clean up CVS instructions a bit, removing excess tagging in screens, some style changes Index: docs-getting-files-en.xml =================================================================== RCS file: /cvs/docs/documentation-guide/docs-getting-files-en.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- docs-getting-files-en.xml 14 May 2005 20:00:15 -0000 1.3 +++ docs-getting-files-en.xml 24 Aug 2005 12:30:26 -0000 1.4 @@ -32,34 +32,31 @@ The custom scripts and stylesheets used are all stored in CVS on the cvs.fedora.redhat.com CVS server. - - - You need to check them out along with the DocBook XML files for the existing docs. - Get started by following these once-only steps. - When asked for a CVS password, just press the ENTER key. + You should perform these steps only once, when you first make a checkout + from docs CVS. When you see the password prompt, just press the + Enter key. -$ mkdir my-fedora-docs -$ cd my-fedora-docs -$ export CVSROOT=:pserver:anonymous at cvs.fedora.redhat.com:/cvs/docs -$ cvs login -<enter> -$ cvs co docs-setup +mkdir my-fedora-docs +cd my-fedora-docs +export CVSROOT=:pserver:anonymous at cvs.fedora.redhat.com:/cvs/docs +cvs login +cvs co docs-setup - Checking the files out anonymously means that you can view them and - retreive the latest versions, but you can not add (commit) any updates or - new files back to the repository. - You need CVS write access for that; check with the - http://fedoraproject.org/wiki/DocsProject/NewWriters - site to learn about getting write access to CVS. + When you perform an anonymous CVS checkout, you can view the files and + retreive the latest versions. You can not add (commit) any updates or new + files back to the repository. To commit changes to CVS, you must have + CVS write access. Refer to to learn + about getting write access to CVS. @@ -72,12 +69,12 @@ Pick your document of interest and then download it to your working directory: -$ cvs co example-tutorial +cvs co example-tutorial - Except for the &IG;, all docs must be tutorials - written in DocBook XML article format using the template in the - example-tutorial directory. Each tutorial + Except for the &IG;, all documentation in CVS must + be tutorials written in DocBook XML article format using the template in + the example-tutorial directory. Each tutorial must be in its own directory. No XML files should be in the root directory. From fedora-docs-commits at redhat.com Wed Aug 24 12:33:08 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 24 Aug 2005 08:33:08 -0400 Subject: documentation-guide docs-getting-files-en.xml,1.4,1.5 Message-ID: <200508241233.j7OCX83R019322@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/documentation-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19305 Modified Files: docs-getting-files-en.xml Log Message: Trivial style change, remove superfluous adverb Index: docs-getting-files-en.xml =================================================================== RCS file: /cvs/docs/documentation-guide/docs-getting-files-en.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- docs-getting-files-en.xml 24 Aug 2005 12:30:26 -0000 1.4 +++ docs-getting-files-en.xml 24 Aug 2005 12:33:05 -0000 1.5 @@ -38,7 +38,7 @@ You should perform these steps only once, when you first make a checkout - from docs CVS. When you see the password prompt, just press the + from docs CVS. When you see the password prompt, press the Enter key. From fedora-docs-commits at redhat.com Wed Aug 24 12:36:28 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 24 Aug 2005 08:36:28 -0400 Subject: documentation-guide docs-getting-files-en.xml,1.5,1.6 Message-ID: <200508241236.j7OCaSfB019345@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/documentation-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19328 Modified Files: docs-getting-files-en.xml Log Message: Ugh, stupid spelling error Index: docs-getting-files-en.xml =================================================================== RCS file: /cvs/docs/documentation-guide/docs-getting-files-en.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- docs-getting-files-en.xml 24 Aug 2005 12:33:05 -0000 1.5 +++ docs-getting-files-en.xml 24 Aug 2005 12:36:25 -0000 1.6 @@ -52,7 +52,7 @@ When you perform an anonymous CVS checkout, you can view the files and - retreive the latest versions. You can not add (commit) any updates or new + retreive the latest versions. You cannot add (commit) any updates or new files back to the repository. To commit changes to CVS, you must have CVS write access. Refer to to learn From fedora-docs-commits at redhat.com Wed Aug 24 19:41:57 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 24 Aug 2005 15:41:57 -0400 Subject: documentation-guide docs-getting-files-en.xml,1.6,1.7 Message-ID: <200508241941.j7OJfvRN031655@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/documentation-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31638 Modified Files: docs-getting-files-en.xml Log Message: Oops, fix one other extraneous prompt... sorry quaid Index: docs-getting-files-en.xml =================================================================== RCS file: /cvs/docs/documentation-guide/docs-getting-files-en.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- docs-getting-files-en.xml 24 Aug 2005 12:36:25 -0000 1.6 +++ docs-getting-files-en.xml 24 Aug 2005 19:41:55 -0000 1.7 @@ -63,7 +63,7 @@ To see a list of the available documents: -$ cvs co -c +cvs co -c Pick your document of interest and then download it to your working directory: From fedora-docs-commits at redhat.com Wed Aug 24 20:37:38 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Wed, 24 Aug 2005 16:37:38 -0400 Subject: documentation-guide documentation-guide-en.xml,1.19,1.20 Message-ID: <200508242037.j7OKbcUo000573@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/documentation-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv556 Modified Files: documentation-guide-en.xml Log Message: Rolling version. Index: documentation-guide-en.xml =================================================================== RCS file: /cvs/docs/documentation-guide/documentation-guide-en.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- documentation-guide-en.xml 28 Jun 2005 21:46:45 -0000 1.19 +++ documentation-guide-en.xml 24 Aug 2005 20:37:35 -0000 1.20 @@ -7,9 +7,9 @@ %FEDORA-ENTITIES-EN; - + - + @@ -34,7 +34,7 @@ &FP; Documentation Guide Version &VERSION; - 2003,2004 + 2003,2004,2005 &FORMAL-RHI; Tammy Fox Johnray Fuller From fedora-docs-commits at redhat.com Thu Aug 25 17:42:56 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Thu, 25 Aug 2005 13:42:56 -0400 Subject: jargon-buster jargon-buster-en.xml,1.1,1.2 Message-ID: <200508251742.j7PHgu93002260@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2243 Modified Files: jargon-buster-en.xml Log Message: Removed a few superfluous entries, edited others, pushed release to 1.9.2 Index: jargon-buster-en.xml =================================================================== RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jargon-buster-en.xml 17 Aug 2005 17:09:02 -0000 1.1 +++ jargon-buster-en.xml 25 Aug 2005 17:42:53 -0000 1.2 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + ]> @@ -12,6 +12,30 @@ Fedora Jargon Buster + + + Dave + Pawson + + + Tammy + Fox + + + Paul + W + Frields + + + + 2003 + 2004 + 2005 + Dave Pawson + Paul W. Frields + &FORMAL-RHI; + + &LEGALNOTICE; 1.0 @@ -126,161 +150,183 @@ + + 1.9.1 + 17 Aug 2005 + PaulWFrields + + + Began new round of editing. + + + + + 1.9.2 + 25 Aug 2005 + PaulWFrields + + + Additional term editing. + + + - - &LEGALNOTICE; - + - This document attempts to clarify some of the terms used on various - lists, &RH; pages, and IRC, when talking about Linux, &RHL; - versions, releases, etc. Many thanks to the people on the - fedora-list at &RH; for their input. + This document clarifies some of the terms used on various lists, web + pages, and IRC, when talking about &FED;. Many thanks to the people + on the fedora-list and at &RH; for their input. - - If you would like a word added to this document, please email the - mailing list - fedora-docs-list at redhat.com - . A list to the subscription page is available on the - project home - page. If you find a problem with these terms, file a - Bugzilla - report against the fedora-docs component. There is also a bug - reporting link on the - project - page as well. - + &BUG-REPORTING; Jargon Buster - - alsa + + ALSA The Advanced Linux Sound Architecture (ALSA) provides audio - and MIDI functionality to the Linux operating system. Refer - to - alsa-project.org + and MIDI functionality to the Linux operating system. Refer + to for more + information. - + Anaconda - Anaconda is the installation program for Red Hat - distributions. During installation, the system's hardware is - identified and configured, and the appropriate file systems - for the system's architecture are created. Finally, it - allows the user to install the operating system software on - the system. Optionally, it can upgrade existing Red Hat - installations. Anaconda can run in a fully interactive mode - (text or graphical), or in a kickstart mode, which is allows - the installation to be scripted for unattended operation. - Refer to - &RH; + Anaconda is the installation + program for &FC;. During installation, + Anaconda identifies and + configures the system's hardware, and creates appropriate + file systems. Anaconda also + allows the user to install the operating system software on + the system. Optionally, it upgrades existing &RHL; or &FED; + installations. Anaconda runs in a + fully interactive text or graphical mode, or in a + kickstart mode, which allows the + owner or administrator to automate installation for + unattended operation. Refer to + for more information. - - apt-get + + apt - Refer to - https://moin.conectiva.com.br/AptRpm. - APT (Advanced Package Tool) is a dependency tool, well known - to Debian users since it is used by default with their dpkg - packages. But apt has been ported to work with RPM packages - too, by Conectiva, who has now used it for some time in - their GNU/Linux distribution. The good news is that apt for - RPM may be used with any other RPM-based distribution. All - you need is the tool compiled for your version of RPM and at - least a repository where RPM packages and their apt metadata - can be downloaded from. - - - - - ATrpms - - - This is a 3rd party RPM repository for &RHL; distributions. - The original focus laid upon software used in natural - sciences, especially in the field of high energy physics, - e.g. tools for numerical programming or such for scientific - publications. But since then this repository has included - many non-scientific software titles, like system tools or - multimedia packages, resulting in a far more generic - repository. Refer to - atrpms.physik.fu-berlin.de + The apt (Advanced Package Tool) utility + is a dependency tool developed for use with Debian Linux + dpkg packages. The + apt-rpm utility extends + apt for use with RPM packages. Since + apt has specific problems with + multilib, however, it is not + recommended for use with &FED; systems. Use instead. - - BitTorrent + + ATrpms - An alternative to a simple FTP or HTTP download. Utilizes - multiple channels to download. Refer to - BitTorrent - website - - - Duke.edu - This is the tracker for Fedora Core 1 'Yarrow' release. - - - - - Bluecurve - - - - An easy-to-navigate interface with intuitively organized - menus. Bluecurve has been upgraded in &RHL; 9 and now - extends to more areas of the operating system, including the - menu and layout of the desktop. + ATrpms a third party RPM repository for &FED; + distributions. The original focus for ATrpms was software + used in natural sciences, especially in the field of high + energy physics. The repository included tools for use in + numerical programming and scientific publications. But since + then this repository has included many non-scientific + software titles, like system tools or multimedia packages, + resulting in a far more generic repository. Refer to for more + information. - - Bugzilla - - - This is the &RH; bug-tracking system, our database for - recording bugs in &RH; products. For more information about - the Bugzilla bug tracking system, please refer to the main - Bugzilla home - page. - - - - - Core 1 - - - The Yarrow version of Fedora. Sometimes abbreviated to FC 1 - or fc1, Fedora Core 1. - - &RHL; Names - - - - Core 2 + + BitTorrent - The Tettnang version of Fedora. Sometimes abbreviated to FC - 2 or fc2, Fedora Core 2. + BitTorrent is a peer-to-peer + file sharing which downloads from multiple channels at + once. Refer to for more + information. + + + Use BitTorrent to download &FC; + by downloading and opening a torrent file. The official + &FC; torrent tracker is located at . Download a torrent + file there to begin downloading a release of &FC;. + + + + + Bluecurve + + + Bluecurve is a theme which unifies + the look and feel of the &FED; desktop. Bluecurve was + introduced in &RHL; 9 and was used as the default for &FC; + through release 3. Bluecurve was replaced in &FC; 4 by + . Bluecurve included + icons and settings for the menu and layout of the desktop. + + + + + &BZ; + + + &BZ; is an online database for recording flaws, or + bugs, in &FED; software, + documentation, and other projects. &BZ; also tracks bugs in + &RH; software. When you encounter a problem with &FED;, you + can help the community fix the problem by making a record in + &BZ;. This procedure is called "entering a bug." For more + information about &BZ;, refer to &BZ-URL;. + + + + + Clearlooks + + + Clearlooks is the default theme for a GNOME desktop + environment in &FC; 4. The Clearlooks design is based on + the original . + + + + + Core + + + Core is a numbered release of a subset of &FED; software, + and is usually called "&FC;." Core packages are maintained + mainly by employees of &RH;, and are made up of free and + open source software produced by the Linux community. + + + Although the software in &FC; is updated regularly, the + original release of &FC; does not change. For this reason, + when users discuss the state of their &FED; system software, + they might refer to "&FC; plus updates." When you request + help from the community, this terminology is the most + accurate. However, many users simply call the updated + system "&FC;." &RHL; Names - + cron @@ -938,7 +984,6 @@ "Tettnang" is the second release (version 2) of Fedora Core. &RHL; Names - Core 2 @@ -1059,10 +1104,9 @@ Severn, a river in the UK. &RHL; Names - Core 1 - + Yum From fedora-docs-commits at redhat.com Fri Aug 26 02:43:45 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Thu, 25 Aug 2005 22:43:45 -0400 Subject: jargon-buster jargon-buster-en.xml,1.2,1.3 Message-ID: <200508260243.j7Q2hjbl025782@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25763 Modified Files: jargon-buster-en.xml Log Message: Additional editing (down to the F's) Index: jargon-buster-en.xml =================================================================== RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jargon-buster-en.xml 25 Aug 2005 17:42:53 -0000 1.2 +++ jargon-buster-en.xml 26 Aug 2005 02:43:42 -0000 1.3 @@ -185,7 +185,7 @@ Jargon Buster - + ALSA @@ -196,7 +196,7 @@ - + Anaconda @@ -229,7 +229,7 @@ apt has specific problems with multilib, however, it is not recommended for use with &FED; systems. Use instead. + linkend="gl-jb-yum"/> instead. @@ -326,14 +326,16 @@ &RHL; Names - + cron - A daemon to execute scheduled commands, for example to check - email each day at noon. Cron searches /var/spool/cron for - crontab files which are named after accounts in /etc/passwd; + The cron system executes automatic jobs + on behalf of the system or an individual user on a schedule. + An example of a system cron job might + include running nightly to update + the system. @@ -341,75 +343,115 @@ CUPS - The Common UNIX Printing System ("CUPS") is a cross-platform - printing solution for all UNIX environments. It is based on - the "Internet Printing Protocol" and provides complete - printing services to most PostScript and raster - printers.Home - page. + The Common UNIX Printing System, or CUPS, + is a cross-platform printing solution for all UNIX-type + environments, including Linux and Macintosh OS X. It is + based on the Internet Printing Protocol and provides + complete printing services to most printers. CUPS drivers + are available at + which allow Windows systems to use printers shared from + Linux systems. Refer to + for more information about CUPS. - desktop switcher - - - The switchdesk-gnome package provides a GNOME look and feel - for the Desktop Switcher program provided in the switchdesk - package. - + Desktop Switcher + + + The Desktop Switcher tool allows + a user to convert the &FED; desktop between and . To + run the Desktop Switcher tool + from the Main Menu, select + DesktopPreferencesMore + PreferencesDesktop + Switcher. If you do not see this + item in your menu, you may not have the + switchdesk-gui package installed. Refer + to &FDPDOCS-URL; to learn how to use to install software packages. + - - eth0 + + eth0 + + + The eth0 name represents the first + discovered interface in a + &FED; system. If your &FED; system has more than one such + interface, the others will be numbered + eth1, + eth2, and so on. + + + + + Ethernet - (Normally) the first ethernet port on your system + Ethernet is the most common type of network technology for + small computer networks. - + ethtool - Ethtool is a Linux net driver diagnostic and tuning tool for - the Linux 2.4.x (or later) series of kernels. It obtains + The ethtool utility is a Linux network + driver diagnostic and tuning tool for Linux 2.4 or later + kernels. The ethtool utility obtains information and diagnostics related to media, link status, - driver version, PCI (or other) bus location, and more. + driver version, bus location, and more. - + FAQ - Frequently Asked Questions, for Fedora see - fedora.redhat.com + A FAQ is a list of Frequently Asked + Questions. Refer to for a FAQ about + the &FP;. Refer to for a FAQ about using &FED;. - + FDL - GNU Free Documentation License (FDL), see - gnu.org + The GNU Free Documentation License (FDL) + is a means of ensuring freedom for program documentation. + The &FDP; uses the FDL for its official documentation. In + fact, this document is licensed through the FDL. As is the + case with all freedoms, the FDL carries both rights and + responsibilities. You have the right to modify and + redistribute FDL materials, or create other works based on + them. You then have the responsibility of licensing any + such material under the FDL as well. In this fashion the + FDL guarantees that documentation cannot be made less free + by a recipient. - FHS - File System Hierarchy Standard + FHS - A collaborative document that defines the names and - locations of many files and directories on a Linux system. - Worth getting to know if you want to know what - should go where. Refer to - &RH; + The File Hierarchy Standard, or FHS, is a + collaborative document that defines the names and locations + of many files and directories on a Linux system. The FHS + also sets standards for the types of files that should + inhabit specific system directories. Refer to for more information + about the FHS. - + FreshRPMS @@ -479,7 +521,7 @@ - + GNOME @@ -509,8 +551,8 @@ - - GPL & non-GPL http://www.fsf.org/licenses/gpl-faq.htm + + GPL Gnu General Public Licence. Refer to @@ -573,7 +615,7 @@ - + KDE @@ -1106,7 +1148,7 @@ &RHL; Names - + Yum From fedora-docs-commits at redhat.com Fri Aug 26 17:12:00 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 26 Aug 2005 13:12:00 -0400 Subject: jargon-buster jargon-buster-en.xml,1.3,1.4 Message-ID: <200508261712.j7QHC0Re018164@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18145 Modified Files: jargon-buster-en.xml Log Message: More editing, only changing rev date since this is not to be republished yet Index: jargon-buster-en.xml =================================================================== RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- jargon-buster-en.xml 26 Aug 2005 02:43:42 -0000 1.3 +++ jargon-buster-en.xml 26 Aug 2005 17:11:57 -0000 1.4 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + ]> @@ -162,7 +162,7 @@ 1.9.2 - 25 Aug 2005 + 26 Aug 2005 PaulWFrields @@ -408,6 +408,22 @@ + + ext3 + + + The ext3 file system is a method of + organizing data on storage devices. It is based on the + older but still vital ext2 Linux + file system. Most users do not need to understand file + system internals because Linux translates this system into + understandable concepts such as files and folders. Refer to + , however, + for more information on ext2 and + ext3. + + + FAQ @@ -438,7 +454,7 @@ - + FHS @@ -451,76 +467,81 @@ about the FHS. - - + + FreshRPMS - A source of RPMs. Matthias Saou, the host, says: In late - 2000, I started building quite a few RPM packages for my own - needs, that couldn't easily be found elsewhere, or at least - not so well suited for &RHL;. A few months later, the - website on which these packages were hosted changed its name - to become what people know today. A long time has passed and - I still maintain all the packages I used to, and more of - course! A whole community of users, testers and contributors - has grown around the website and its packages, which is - something I really didn't expect but really enjoy. Refer to - freshrpms.net + A third-party repository of + software packages. FreshRPMS is soon to be subsumed into + the larger RPMForge repository. Refer to for more information. - RPM - + fsck - fsck is a command line tool used to check and optionally - repair Linux file systems. + The fsck utility is a command line tool + used to check and repair file systems. It is normally used + with Linux file systems such as , but also has the ability to make + repairs on some Windows file systems. - + fsh Remote command execution via a cryptographically strong - method such as lsh or ssh is often painfully slow, - especially if either of the involved computers is slow. The - biggest problem is that the client and the server perform a - lot of complex calculations during connection establishment. + method such as lsh or + ssh is often slow, especially if either + of the involved computers is slow. The process is slow + because the client and the server must perform a series of + complex calculations during connection establishment. - fsh uses lsh or ssh to establish a secure tunnel to the - remote system. This takes as long as a normal connection - establishment, but once the tunnel is established, fsh can - reuse it to start new sessions on the remote system almost - instantaneously. You get the security of ssh and the speed - of rsh. + The fsh utility uses + lsh or ssh to + establish a secure tunnel to the remote system. This process + takes as long as a normal connection establishment. Once + the tunnel is established, however, fsh + reuses it to start new sessions on the remote system almost + instantaneously. With this process, fsh + combines the security of ssh and the speed of rsh. - - gimp + + GIMP - The GIMP is the GNU Image Manipulation Program. It is a - freely distributed piece of software suitable for such tasks - as photo retouching, image composition and image authoring. - Refer to gimp.org + The GIMP is the GNU Image Manipulation Program. The GIMP is + graphics software suitable for such tasks as photo + retouching, image composition and image authoring. The GIMP + will read and write graphics files in a variety of formats, + including JPG, PNG, BMP, GIF. It will also import some + proprietary image formats from other graphics programs. + Refer to for more + information about the GIMP. - + glibc - The GNU C library is used as the C library in the GNU system - and most newer systems with the Linux kernel. Refer to - gnu.org + The GNU C library, or glibc, is + used as the C library in &FED;. Most software programs for + your &FED; system rely on glibc for + basic common functions. Refer to for more + information about glibc. - + GNOME @@ -810,7 +831,7 @@ which together form an application or other usable software entity. Normally meant for installation by a package manager - RPM + RPM redhat-config-packages @@ -939,7 +960,7 @@ - + RPM @@ -1016,7 +1037,7 @@ you want to read it or modify it. You do not need any SRPMS to install or use the software. - RPM + RPM From fedora-docs-commits at redhat.com Fri Aug 26 22:56:53 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Fri, 26 Aug 2005 18:56:53 -0400 Subject: yum-software-management yum-software-management-en.xml,1.44,1.45 Message-ID: <200508262256.j7QMur8t027613@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27580 Modified Files: yum-software-management-en.xml Log Message: - Edited Additional Repositories section for better style - Fixed up localinstall Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.44 retrieving revision 1.45 diff -u -r1.44 -r1.45 --- yum-software-management-en.xml 19 Aug 2005 20:09:12 -0000 1.44 +++ yum-software-management-en.xml 26 Aug 2005 22:56:50 -0000 1.45 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -709,7 +709,7 @@ Review the list of changes, and then press y to accept and begin the process. If you press N or - Enter , yum does not download + Enter, yum does not download or change any packages. @@ -1187,11 +1187,13 @@ - If the &FP; does not provide a specific software package, the - manufacturer of the software may provide or recommend a separate - repository. Members of the community also maintain repositories to - provide packages for &FED; systems. Third-party repositories - provide information on their web sites. + If the &FP; does not supply packages for a product, the + manufacturer may provide or recommend a separate repository. + Members of the community also maintain repositories to provide + packages for &FED; systems. For example, + distributes popular Java + software as packages.
@@ -1540,11 +1542,10 @@ Use repositories and the standard yum commands - to install new software, unless the software is only available as - a package. In these cases, use the - function to install the software from the package file. The - function does not connect to any - repository. + to locate and install new software, unless the software is only + available as a package. In these cases, use the + function to install the software + from the package file. @@ -1570,16 +1571,35 @@ class="username">root password. - - Meeting Dependencies + + Previously Installed Software is Updated - You must ensure that all of the dependencies are already - installed on your system, because yum cannot - download additional packages to complete the installation when - performing a operation. + If the package provides a later version of software that is + already installed on your system, yum updates + the installed software. - + + + + If the package requires software that is not installed on your + system, yum attempts to meet the dependencies + with packages from the configured repositories. You may need to + manually download and install additional packages in order to + satisfy all of the dependencies. + + + + Maintaining Manually Installed Software + + + If you install software that is not provided by a repository, + yum update cannot automatically upgrade it as + new versions become available. To ensure that you have the + latest packages, subscribe to e-mail or RSS services that notify + you when new versions are released. + +
@@ -1593,8 +1613,8 @@ You may access repositories through standard web proxy servers. If - your system is connected to the Internet through a web proxy - server, specify the proxy server details in + your system accesses the Internet through a web proxy server, + specify the proxy server details in /etc/yum.conf. The setting must specify the proxy server as a complete URL, including the TCP port number. If your proxy server requires a username and From fedora-docs-commits at redhat.com Sat Aug 27 01:47:41 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 26 Aug 2005 21:47:41 -0400 Subject: jargon-buster jargon-buster-en.xml,1.4,1.5 Message-ID: <200508270147.j7R1lfYQ031952@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31933 Modified Files: jargon-buster-en.xml Log Message: More editing, got to the G's now :-) Index: jargon-buster-en.xml =================================================================== RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- jargon-buster-en.xml 26 Aug 2005 17:11:57 -0000 1.4 +++ jargon-buster-en.xml 27 Aug 2005 01:47:39 -0000 1.5 @@ -401,10 +401,11 @@ The ethtool utility is a Linux network - driver diagnostic and tuning tool for Linux 2.4 or later - kernels. The ethtool utility obtains - information and diagnostics related to media, link status, - driver version, bus location, and more. + driver diagnostic and tuning tool for a Linux 2.4 or later + . The + ethtool utility obtains information and + diagnostics related to media, link status, driver version, + bus location, and more. @@ -541,34 +542,51 @@ information about glibc. - + GNOME - The GNOME Project is an effort to create a complete, free - and easy-to-use desktop environment for users, as well as a - powerful application development framework for software - developers. Refer to Home - page + GNOME is the short name for the GNOME + Desktop, a product of the GNOME Project. GNOME is a + complete, free and easy-to-use desktop environment for + users. It is also a powerful application development + framework for software developers. GNOME provides a + complete set of human interface guidelines, which means that + GNOME strives to have a consistent look and feel for all its + applications. Read more about GNOME at . - - GPG + + GNU + + + GNU is an acronym that stands for "GNU's + Not UNIX," and is pronounced "guh-NOO." GNU was originally + intended to be a complete UNIX-like operating system. It + has become a broader term describing free software licensed + under the . Because the and much of the other software in a + Linux system are licensed under the , many people call that system + GNU/Linux. + + + + + GnuPG (GPG) - GnuPG is a complete and free replacement for PGP. Because it - does not use the patented IDEA algorithm, it can be used - without any restrictions. GnuPG is a RFC2440 (OpenPGP) - compliant application. Refer to - gnupg.org. You may - also see RPM-GPG-KEY referenced, which relates to the keys - used for checking packages. E.g. see - rpmfind - + GnuPG, the GNU Privacy Guard, is a complete and free + replacement for PGP, Pretty Good Privacy. GnuPG software + allows you to digitally sign or encrypt data using public + key encryption methods. GnuPG is OpenPGP compliant, so data + signed or encrypted by GnuPG can be exchanged with almost + any computer user. Refer to for more information about + GPG. @@ -576,20 +594,35 @@ GPL - Gnu General Public Licence. Refer to - fsf.org + The GNU General Public Licence, or GPL, + is a software license designed to preserve users' rights to + share and modify software. The GPL does this by restricting + anyone from denying you those rights. Use of software is + usually subject to the terms under which it is licensed. + Many software licenses restrict you from copying, sharing, + or even examining the software they cover. The terms of the + GPL, however, allow you very broad rights to share, modify, + and redistribute software. In return the GPL requires you + to give others those rights if you share the results. The + GPL encourages software programmers to learn and contribute + to each other's work. Refer to for + more information about the GPL. For a about the GPL, refer to . - - + + GRUB - GNU GRand Unified Boot loader or GRUB is a program which - enables the user to select which installed operating system - or kernel to load at system boot time. It also allows the - user to pass arguments to the kernel. Refer to - &RH; + The GNU GRand Unified Boot Loader, or + GRUB is a program which enables the user + to select which installed operating system or kernel to load + at system boot time. It also allows the user to pass + arguments to the kernel. Refer to &RH; @@ -654,7 +687,7 @@ - + kernel From fedora-docs-commits at redhat.com Sat Aug 27 23:46:51 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sat, 27 Aug 2005 19:46:51 -0400 Subject: yum-software-management yum-software-management-en.xml,1.45,1.46 Message-ID: <200508272346.j7RNkqhx031586@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31567 Modified Files: yum-software-management-en.xml Log Message: Just one quick tweak, since the old verbiage was a little confusing Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.45 retrieving revision 1.46 diff -u -r1.45 -r1.46 --- yum-software-management-en.xml 26 Aug 2005 22:56:50 -0000 1.45 +++ yum-software-management-en.xml 27 Aug 2005 23:46:44 -0000 1.46 @@ -1542,8 +1542,8 @@ Use repositories and the standard yum commands - to locate and install new software, unless the software is only - available as a package. In these cases, use the + to locate and install new software, unless the software package is + not available from any repository. In these cases, use the function to install the software from the package file. From fedora-docs-commits at redhat.com Sun Aug 28 21:53:53 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 28 Aug 2005 17:53:53 -0400 Subject: jargon-buster jargon-buster-en.xml,1.5,1.6 Message-ID: <200508282153.j7SLrs1C004604@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4585 Modified Files: jargon-buster-en.xml Log Message: More edits, into the L section now Index: jargon-buster-en.xml =================================================================== RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- jargon-buster-en.xml 27 Aug 2005 01:47:39 -0000 1.5 +++ jargon-buster-en.xml 28 Aug 2005 21:53:51 -0000 1.6 @@ -327,6 +327,18 @@ &RHL; Names + + CPU + + + The Central Processing Unit, or CPU, is + the "brain" of a computer. The rest of the computer is + organized around the CPU, so people often refer to computer + systems by the type of processor inside. Examples of CPUs + include Pentium-4, Athlon64, and PowerPC. + + + cron @@ -550,12 +562,12 @@ GNOME is the short name for the GNOME Desktop, a product of the GNOME Project. GNOME is a complete, free and easy-to-use desktop environment for - users. It is also a powerful application development - framework for software developers. GNOME provides a - complete set of human interface guidelines, which means that - GNOME strives to have a consistent look and feel for all its - applications. Read more about GNOME at . + UNIX-like operating systems such as &FED;. It is also a + powerful application development framework for software + developers. GNOME provides a complete set of human + interface guidelines, which means that GNOME strives to have + a consistent look and feel for all its applications. Read + more about GNOME at . @@ -617,36 +629,55 @@ GRUB - The GNU GRand Unified Boot Loader, or - GRUB is a program which enables the user - to select which installed operating system or kernel to load - at system boot time. It also allows the user to pass - arguments to the kernel. Refer to &RH; + The GRand Unified Boot Loader, + or GRUB, is a program which enables the + user to select an operating system or kernel to boot. It + also allows the user to pass arguments to the kernel. Refer + to for more + information about GRUB. - + i386 - i386. The entire x86 line of computers and processors, from - the Intel 386 forward all the way to Intel Pentium 4 and - Athlon chips. All those are compatible with i386 instruction - sets, the "lowest common denominator". Often used as + The entire set of computer processors that are compatible + with the Intel x86 platform, including Intel Pentium and + Celeron, AMD Athlon and Duron, and VIA C3 s, are commonly referred to as + i386. The + i386 term is often used as shorthand for the distribution set of files meant for this line of computers or processors. - + + IM + + + Instant messaging, or IM, is a real-time, + text-based form of communication. You can use IM to have + conversations with individuals or groups. America Online, an + Internet service provider, popularized IM in the 1990's, but + many other providers such as Yahoo and Google offer similar + services. &FED; has programs such as + gaim that allow you to use IM to + communicate with other Internet users. + + + + IRC - IRC (Internet Relay Chat) channel. IRC is a real-time, - text-based form of communication. With it, you can have - conversations with multiple people in an open channel or - chat with someone privately one-on-one. + Internet Relay Chat, or IRC, is a + real-time, text-based form of communication. You can use + IRC to have conversations with individuals or groups. IRC + is very similar to , and offers + many of the same capabilities, but predates IM by many + years. @@ -654,18 +685,15 @@ ISO - As an acronym, ISO = International Standards Organization. - More usefully, an abbreviation for the format of the - downloadable version of the CD images, since the ISO defined - the CD format. - - - ISO standard ISO 9660:1988 entitled "Information processing - -- Volume and file structure of CD-ROM for information - interchange" does define the order of bits on a CD-ROM and - so an image of an ISO 9660:1988 compliant media is called an - ISO. For details see - iso.org + ISO is an acronym that stands for + International Standards Organization. It is also used as an + abbreviation for the ISO-9660 format of a standard data + CD-ROM. &FED; offers installation CDs for &FC; as + downloadable files on the Internet, in the form of CD image + files sometimes called ISO files. These files can be burned + directly to CD media using a CD-Recordable drive, and the + resulting CD will contain all the files on the original &FC; + media. @@ -673,17 +701,12 @@ KDE - KDE is a desktop environment for UNIX workstations. KDE - seeks to fill the need for an easy to use desktop for Unix - workstations, similar to the desktop environments found - under Mac OS or - Microsoft - Windows. Refer - to the Home - page for more information. + KDE is a free and open desktop environment for UNIX-like + operating systems such as &FED;. KDE also offers a complete + development framework for writing graphical applications, as + well as an office application suite. Refer to for more information + about KDE. @@ -691,53 +714,60 @@ kernel - The heart of Linux. The main code derived from Linus's - original software. + A kernel is the core of an operating system, responsible for + managing memory and conducting hardware operations. The + Linux kernel used in &FED; is free and open source software, + originally written by Linux Torvalds. Many computer + scientists and programmers from around the world now + contribute to its development. - + kickstart - Many system administrators would prefer to use an automated - installation method to install &RHL; on their machines. To - answer this need, &RH; created the kickstart installation - method. Using kickstart, a system administrator can create a - single file containing the answers to all the questions that - would normally be asked during a typical &RHL; installation. - Refer to - &RH; - + Many system administrators prefer to use an automated + installation method to install &FED; on their machines. With + kickstart, a system administrator can create a single file + containing answers to all the questions asked during a &FED; + installation. Refer to for more + information about kickstart. - - Kudzu + + kudzu - kudzu is the hardware autodetection & configuration - tool, originally introduced in &RHL; 6.1. It detects changes - in the system's hardware configuration, and gives the option - of configuring added or removed devices. It's set up by - default to run at each boot. - fedora.redhat.com - for more. + The kudzu utility usually runs at boot + time. The kudzu utility detects changes + in the system's hardware configuration, and configures the + devices for use with &FED; software. Refer to + for more information about kudzu. - + LDAP - Lightweight Directory Access Protocol + The Lightweight Directory Access Protocol, or + LDAP, is a standard for hierarchically + organizing and accessing collections of information. This + information may be practically anything, but LDAP is most + often used to collect information about organizations, + including personnel and resource information. &FED; + includes support for OpenLDAP, which is a free and open + source implementation of LDAP. For more information about + OpenLDAP, refer to . - - lilo + + LILO LILO (LInux LOader) is a basic system program which boots From fedora-docs-commits at redhat.com Tue Aug 30 21:33:39 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 30 Aug 2005 17:33:39 -0400 Subject: jargon-buster jargon-buster-en.xml,1.6,1.7 Message-ID: <200508302133.j7ULXdUG015905@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15886 Modified Files: jargon-buster-en.xml Log Message: Additional editing, down to "mozilla" Index: jargon-buster-en.xml =================================================================== RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- jargon-buster-en.xml 28 Aug 2005 21:53:51 -0000 1.6 +++ jargon-buster-en.xml 30 Aug 2005 21:33:36 -0000 1.7 @@ -624,7 +624,7 @@ url="http://www.fsf.org/licensing/licenses/gpl-faq.html"/>. - + GRUB @@ -681,7 +681,7 @@ - + ISO @@ -770,40 +770,35 @@ LILO - LILO (LInux LOader) is a basic system program which boots - your Linux system. LILO loads the Linux kernel from a floppy - or a hard drive, boots the kernel and passes control of the - system to the kernel. LILO can also boot other operating - systems. + The LInux LOader, or LILO, is a basic + system program which boots your Linux system. LILO loads the + Linux kernel from a floppy or a hard drive, boots the kernel + and passes control of the system to the kernel. LILO can + also boot other operating systems. LILO has been superseded + by in &FED;. - + LSB - Linux standard base. The goal of the LSB is to develop and - promote a set of standards that will increase compatability - among Linux distributions - linuxbase.org + The Linux Standard Base, or LSB, is a + project that develops and promotes a set of standards to + increase compatibility among Linux distributions. For more + information about LSB, refer to . - + lspci - lspci is a utility for displaying information about all PCI - buses in the system and all devices connected to them. - - - - - Mandrake - - - Another Linux distribution + The lspci utility displays information + about all PCI buses in the system and all devices connected + to them. It is frequently used to diagnose problems with + hardware recognition or driver compatibility. @@ -811,66 +806,85 @@ md5sum - md5sum computes a 128-bit checksum (or fingerprint or - message-digest) for each specified file. Refer to - gnu.org - for Linux man pages. Why is it useful? Having downloaded - Fedora, you'll mostly see a related file MD5SUM which holds - some rather strange numbers. Run md5sum against the - downloaded file or image, and you'll see a match if you are - lucky, or if you don't get the match, you can be assured - that the download is somehow faulty, and you need to - download again, before you burn the CD. + The md5sum utility computes a 128-bit + message digest hash value for any specified files. A hash + value is a "fingerprint" for a given file, created by a + computation that makes it very unlikely that any two files + will create the same hash value. + + + Download mirrors for &FC; image + files also include a related MD5SUMS file which contains the + hash values for the files. Run + md5sum against the downloaded files to + verify the hash value. If a file's hash value does not + match, you should not use that file to burn a CD. Try + downloading the file again. - For windows, - activestate.com + To download an MD5 hash program for Windows operating + systems, refer to . - - Memtest86 + + memtest86 - Memory testing may be performed prior to installing Fedora - Core by entering memtest86 at the boot: - prompt. This causes the Memtest86 - standalone memory testing software to run. - Memtest86 memory testing continues until - the Esc key is pressed. + The &FC; Installation CD 1 includes a memory testing utility + called memtest86. To perform memory + testing before you install Fedora Core, or to diagnose a RAM + problem, enter memtest86 at the + boot: prompt. The tests continue until you + press the Esc key. - - Mount point + + mount - Mounting a CD is the equivalent of telling the Operating - System that you want to use it. In Linux the only file - system that is automatically mounted is the root file system - which is automatically mounted on the root directory. Other - file systems (eg. your floppy drive, cd rom drive, windows - partitions, and any linux partitions other than root) can be - mounted and unmounted as required. In the case of drives - used with portable media (such as floppy drives, cd rom - drives, and zip drives) it is necessary to unmount the drive - before being able to remove the media from the drive. + To use a disk device such as a CD, USB drive, or floppy + diskette, you must first mount it. &FED; + uses a single unified file system for all attached devices. + This is in direct contrast to Windows systems, which use a + "drive letter" for each disk device, such as + A: or C:. + When you mount a disk device, its file + system becomes part of the unified file system on &FED;. + The device is mounted on a mount + point, which is a directory that points to that + device, such as /media/floppy. You + must also unmount the file system before you eject or remove + the disk, to insure all file information is safely written + to the device. + + Since these functions are often handled through + user-friendly helpers, you may perform all mounting, + unmounting, and file browsing through the graphical desktop + interface. For instance, if you use the Desktop, the file management utility makes it + easy to perform these tasks. + - + Mozilla - Mozilla is an open-source web browser, designed for - standards compliance, performance and portability. Refer to - Mozilla.org + The Mozilla Project produces several user applications such + as the Firefox web browser and the Thunderbird email client. + These programs are designed for standards compliance, + performance and portability. For more information about + Mozilla software, refer to . - + Nautilus