yum-software-management yum-software-management-en.xml,1.42,1.43
by fedora-docs-commits@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 @@
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "yum-software-management-1.0 (2005-08-13)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "yum-software-management-1.0.1 (2005-08-18)"> <!-- change version of manual and date here -->
<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "155190">
@@ -113,7 +113,7 @@
<para>
This document describes the configuration of
<command>yum</command> on &FED; &FCLOCALVER; systems. You must
- perform the additional step described in
+ perform the additional step noted in
<xref linkend="sn-authorizing-package-sources" /> to enable
<command>yum</command> on &FED; 3.
</para>
@@ -618,14 +618,19 @@
</indexterm>
<para>
Use the <command>yum</command> utility to modify the software on
- your system in three ways:
+ your system in four ways:
</para>
<para>
<itemizedlist>
<listitem>
<para>
- To install new software from repositories or a package file
+ To install new software from package repositories
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To install new software from an individual package file
</para>
</listitem>
<listitem>
@@ -640,6 +645,18 @@
</listitem>
</itemizedlist>
</para>
+<!-- SE: This duplicates text from the admonition in sn-about-repositories. It's here as well because the Fedora site has a link straight to this section -->
+ <important>
+ <title>Installing Software from a Package File</title>
+
+ <para>
+ The <command>yum</command> commands shown in this section use
+ repositories as package sources. Refer to
+ <xref linkend="sn-yum-installing-frompackage"/> for details of
+ using <command>yum</command> to install software from an
+ individual package file.
+ </para>
+ </important>
<para>
To use <command>yum</command>, specify a function and one or more
@@ -690,13 +707,10 @@
</example>
<para>
- Review the list of changes, and then press
- <keycap>y</keycap>
- to accept and begin the process. If you press
- <keycap>N</keycap>
- or
- <keycap>Enter</keycap>
- , <command>yum</command> does not download or change any packages.
+ Review the list of changes, and then press <keycap>y</keycap> to
+ accept and begin the process. If you press <keycap>N</keycap> or
+ <keycap>Enter</keycap> , <command>yum</command> does not download
+ or change any packages.
</para>
<note>
@@ -710,9 +724,9 @@
</note>
<para>
- The <command>yum</command> utility imports the repository public
- key if it is not already installed on the <command>rpm</command>
- keyring.
+ The <command>yum</command> utility also imports the repository
+ public key if it is not already installed on the
+ <command>rpm</command> keyring.
</para>
<example id="yum-publickey-import">
@@ -731,13 +745,18 @@
</example>
<para>
- Check the public key, and then press
- <keycap>y</keycap>
- to import the key and authorize the key for use. If you press
- <keycap>N</keycap>
- or
- <keycap>Enter</keycap>
- , <command>yum</command> stops without installing any packages.
+ Check the public key, and then press <keycap>y</keycap> to import
+ the key and authorize the key for use. If you press
+ <keycap>N</keycap> or <keycap>Enter</keycap> ,
+ <command>yum</command> stops without installing any packages.
+ </para>
+
+ <para>
+ To ensure that downloaded packages are genuine,
+ <command>yum</command> 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, <command>yum</command> applies them to your system.
</para>
<tip>
<title>Downloads are Cached</title>
@@ -1268,19 +1287,15 @@
class="username">root</systemitem> password.
</para>
- <para>
- 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:
- </para>
-<screen>
-<userinput>su -c 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'</userinput>
-</screen>
- <para>
- At the prompt, enter the
- <systemitem
- class="username">root</systemitem> password.
- </para>
+ <important>
+ <title>Importing the &FED; Key on &FED; 3</title>
+
+ <para>
+ To add the &FED; public key to the <command>rpm</command>
+ keyring on &FED; 3 systems, run the command <command>su -c
+ 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'</command>.
+ </para>
+ </important>
</section>
<section id="sn-compat-repositories">
@@ -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.
+ </para>
+
+ <para>
+ 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.
</para>
<caution>
<title>Incompatible Repositories</title>
<para>
- If you use incompatible repositories <command>yum</command>
- operations may fail.
+ If you configure your system to use incompatible repositories
+ <command>yum</command> operations may fail.
</para>
</caution>
@@ -1477,9 +1498,9 @@
</indexterm>
<para>
By default, <command>yum</command> 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:
</para>
<screen>
<userinput>su -c 'yum clean headers'</userinput>
18 years, 8 months
securing-filesystems ch-constitutes_filesystem.xml,NONE,1.1
by fedora-docs-commits@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 ---
<?xml version="1.0" encoding="US-ASCII"?>
<!-- ...................................................................... -->
<!-- SECURING FILESYSTEMS ................................................ -->
<!-- File: ch-constitutes_filesystem.xml .................................. -->
<!-- &Id$ -->
<chapter id="ch-fs">
<title>What Constitutes a Filesystem?</title>
<para>
That is a pretty broad question. Take the following definition into
consideration:
</para>
<para>
<blockquote>
<attribution>
<orgname class="nonprofit">
The Free On-line Dictionary of Computing
</orgname>
</attribution>
<literallayout>
<emphasis role="bold">file system</emphasis>
(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)
</literallayout>
</blockquote>
</para>
<para>
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.
</para>
<para>
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.
</para>
<para>
Now that we are done kicking the tires — lets open the hood and see
what this baby has got, shall we?!
</para>
<section id="sn-fs-stds">
<title>Filesystem Standardization and Compliance</title>
<section id="sn-fs-stds-what">
<title>What is a Standard?</title>
<para>
With regards to a filesystem, <emphasis>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.</emphasis> 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.
</para>
<para>
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.
</para>
</section>
<section id="sn-fs-stds-fedora">
<title>Standards Implemented in Fedora</title>
<para>
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.
</para>
<section id="sn-fs-stds-fhs">
<title>The Filesystem Hierarchy Standard</title>
<para>
This standard, commonly referred to as the <abbrev>FHS</abbrev>, 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.
</para>
<para>
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 <abbrev>FHS</abbrev>-compliant system. This of
course is further dependent on the filesystem objects themselves.
Given the information provided by the <abbrev>FHS</abbrev> and that
derived from the procedures performed in various other sections of
this document, we can reliably begin to secure the filesystems of
fedora.
</para>
</section>
<section id="sn-fs-stds-ieee">
<title>IEEE &posix;.1</title>
<para>The following &posix; draft standards are recognized:</para>
<itemizedlist>
<listitem>
<para>
&posix; 1003.1e - Security <abbrev>API</abbrev>s
</para>
</listitem>
<listitem>
<para>
&posix; 1003.2c - Security Command and Utilities
</para>
</listitem>
</itemizedlist>
<para>
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.
</para>
</section>
</section>
<section id="sn-fs-stds-compliance">
<title>Yes! Fedora is Non-Compliant</title>
<para>Give listing of non-compliance.</para>
</section>
</section>
<section id="sn-fs-objs">
<title>A Review of the Structure and Objects of a Filesystem</title>
<para>
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.
</para>
<itemizedlist>
<title>Key Terminology and Concepts</title>
<listitem>
<para>
<emphasis>object</emphasis> - this entity is passive in nature. The
object is the entity that provides the information or data that is
being requested.
</para>
</listitem>
<listitem>
<para>
<emphasis>subject</emphasis> - 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.
</para>
</listitem>
<listitem>
<para>
<emphasis>access</emphasis> - the process of information transfer
between an object and a subject.
</para>
</listitem>
<listitem>
<para>
<command>ls</command> - the application utilized to list the contents
of a directory object type. Common options are as follows: the
<option>-l</option> option formats the output into a long listing.
Provides details such as mode-based permissions, owning user and
owning group. The <option>-d</option> 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.
</para>
</listitem>
<listitem>
<para>
<command>stat</command> - the application utilized to display the
status of an object or filesystem. Common options are as follows:
the <option>-f</option> option presents the status of a filesystem
rather than the status of the special object that is associated with
the requested entity.
</para>
</listitem>
</itemizedlist>
<important>
<para>
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.
</para>
<para>
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!
</para>
</important>
<section id="sn-fs-objs-std">
<title>Standard Objects</title>
<para></para>
<section id="sn-fs-objs-std-reg">
<title>Regular File</title>
<para>
The <firstterm>regular file</firstterm> 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.
</para>
<para>
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 <quote><firstterm>file
type</firstterm></quote> 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.
</para>
<para>
First, is the file type that is utilized in
<firstterm>kernel-space</firstterm> — from this point forward
known as the <firstterm>object file type</firstterm> 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
<xref linkend="sn-fs-objs-spl">Special Objects</xref>.
</para>
<para>
Second, is the file type that is utilized in <firstterm>user-space
</firstterm>. 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.
</para>
<para>
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 <xref
linkend="sn-sec-eval-purpose">Determining a Filesystem Objects
Purpose</xref>. 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.
</para>
<procedure id="sn-fs-objs-std-reg-1">
<para>
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:
</para>
<itemizedlist>
<listitem>
<para>
<xref linkend="sn-fs-objs-std-reg-1-ls"/> - Using the
<command>ls</command> command
</para>
</listitem>
<listitem>
<para>
<xref linkend="sn-fs-objs-std-reg-1-stat"/> - Using the
<command>stat</command> command
</para>
</listitem>
</itemizedlist>
<step id="sn-fs-objs-std-reg-1-ls">
<title>Using the <command>ls</command> command</title>
<para>
The use of the <command>ls <option>-l</option></command>
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
<filename>/home/thomas/Documents/example</filename>)
and presents the output in a long format.
</para>
<substeps>
<step id="sn-fs-objs-std-reg-1-ls-execution">
<title>Execution of the command</title>
<screen>
thomas@bodhittsatva:~/Documents/example> ls -l watch_osiris.sh
</screen>
</step>
<step id="sn-fs-objs-std-reg-1-ls-output">
<title>Output from the command</title>
<para>
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.
</para>
<screen>
-<co id="regular_file_type"/>rwxr--r-- 1 thomas<co id="regular_file_owner"/> thomas<co
id="regular_file_owning_group"/> 2506 2005-08-01 10:34 watch_osiris.sh
</screen>
</step>
<step id="sn-fs-objs-std-reg-1-ls-analysis">
<title>Analysis of the output</title>
<para>
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.
</para>
<para>
Upon review of the example output presented in
<xref linkend="sn-fs-objs-std-reg-1-ls-output"/>, we
can determine the following specific information about
the suspected regular file object:
</para>
<calloutlist>
<title>
<filename>
/home/thomas/Documents/example/watch_osiris.sh
</filename>
</title>
<callout arearefs="regular_file_type">
This filesystem object is a regular file. The
representation of this information is in the form
of the <quote>-</quote> (dash) preceeding the
informational image location.
</callout>
<callout arearefs="regular_file_owner">
This regular file object is owned by the
<systemitem class="username">thomas</systemitem>
owner
</callout>
<callout arearefs="regular_file_owning_group">
This regular file object is owned by the
<systemitem class="groupname">thomas</systemitem>
owning group
</callout>
</calloutlist>
</step>
</substeps>
</step>
<step id="sn-fs-objs-std-reg-1-stat">
<title>Using the ??? command</title>
<para>
The same information can be gleaned from the utilization of
the <command>???</command> command.
</para>
</step>
</procedure>
</section>
<section id="sn-fs-objs-std-dir">
<title>Directory</title>
<para></para>
</section>
</section>
<section id="sn-fs-objs-spl">
<title>Special Objects</title>
<para></para>
<section id="sn-fs-objs-spl-char">
<title>Character Device</title>
<para>
As are most objects of a native filesystem of a linux operating
system, the special files known as character devices are also
categorized as <quote>file-like</quote> 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.
</para>
<para>
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
<filename>/dev</filename> directory. This convention is standardized
by the following standards bodies:
</para>
<itemizedlist>
<listitem>
<para>Filesystem Hierarchy Standard</para>
<itemizedlist>
<listitem>
<para>
The most current standardization at time of this
writing is 2.3
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Linux Standard Base</para>
<itemizedlist>
<listitem>
<para>
The most current standardization at time of this
writing is 3.0
</para>
</listitem>
<listitem>
<para>
The related specification is located in Chapter 5,
Section 12.1
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Single Unix Specification</para>
<itemizedlist>
<listitem>
<para>
The most current standardization at time of this
writing is ?????
</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>
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:
</para>
<para>
<ulink url="http://www.pathname.com/fhs/pub/fhs-2.3.html#DEVDEVICEFILES">
http://www.pathname.com/fhs/pub/fhs-2.3.html#DEVDEVICEFILES</ulink>
</para>
<para>Sometimes a character device is also called a </para>
</section>
<section id="sn-fs-objs-spl-blk">
<title>Block Device</title>
<para></para>
</section>
<section id="sn-fs-objs-spl-sym">
<title>Symbolic Link</title>
<para></para>
</section>
<section id="sn-fs-objs-spl-sock">
<title>Socket</title>
<para></para>
</section>
<section id="sn-fs-objs-spl-pipe">
<title>Pipe</title>
<para></para>
</section>
</section>
<section id="sn-fs-objs-adm">
<title>Administrative Objects</title>
<para></para>
<section id="sn-fs-objs-adm-inode">
<title>Inode: the Administration Data Object</title>
<para></para>
</section>
</section>
<section id="sn-fs-objs-path">
<title>Understanding a Pathname</title>
<para></para>
</section>
</section>
<section id="sn-fs-types">
<title>Types of Filesystems</title>
<para>
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.
</para>
<section id="sn-fs-types-ext2">
<title>Ext2</title>
<para></para>
</section>
<section id="sn-fs-types-ext3">
<title>Ext3</title>
<para></para>
</section>
<section id="sn-fs-types-reiserfs">
<title>ReiserFS</title>
<para></para>
</section>
<section id="sn-fs-types-jfs">
<title>JFS</title>
<para></para>
</section>
<section id="sn-fs-types-xfs">
<title>XFS</title>
<para></para>
</section>
<section id="sn-fs-types-cfs">
<title>CFS</title>
<para></para>
</section>
<section id="sn-fs-types-tcfs">
<title>TCFS</title>
<para></para>
</section>
<section id="sn-fs-types-ramfs">
<title>RAMFS</title>
<para></para>
</section>
</section>
</chapter>
<!-- End of File: ch-constitutes_filesystem.xml ........................... -->
18 years, 8 months
jargon-buster jargon-buster-en.xml, NONE, 1.1 Makefile, 1.3, 1.4 fedora-jargon-buster-en.xml, 1.9, NONE
by fedora-docs-commits@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 ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY BOOKID "jargon-buster-1.9.1 (2005-08-17)"> <!-- change version of manual and date here -->
]>
<article>
<title>Fedora Jargon Buster</title>
<articleinfo>
<revhistory>
<revision>
<revnumber>1.0</revnumber>
<date>7 Nov 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
Initial Release
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.1</revnumber>
<date>8 Nov 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
More added from Fedora list.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.2</revnumber>
<date>10 Nov 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
More added from Fedora list.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.3</revnumber>
<date>10 Nov 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
More added from various places (e.g. DV).
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.4</revnumber>
<date>10 Nov 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
Added LegalNotice and std ents.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.5</revnumber>
<date>11 Nov 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
More additions from list.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.6</revnumber>
<date>11 Nov 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
More additions from list and A-Z toc. Needs art.xsl
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.7</revnumber>
<date>19 Dec 2003</date>
<authorinitials>DaveP</authorinitials>
<revdescription>
<para>
Update
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.8</revnumber>
<date>30 Jan 2004</date>
<authorinitials>TammyFox</authorinitials>
<revdescription>
<para>
Modified to build in fedora-docs module, Red Hat is 2 words,
other edits and corrections
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.9</revnumber>
<date>7 Mar 2004</date>
<authorinitials>DaveP,TammyFox</authorinitials>
<revdescription>
<para>
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)
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.9</revnumber>
<date>30 Sept 2004</date>
<authorinitials>PaulWFrields,TammyFox</authorinitials>
<revdescription>
<para>
Added Tettnang.
</para>
</revdescription>
</revision>
</revhistory>
&LEGALNOTICE;
</articleinfo>
<para>
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.
</para>
<para>
If you would like a word added to this document, please email the
mailing list
<email>fedora-docs-list(a)redhat.com</email>
. A list to the subscription page is available on the
<ulink url="http://fedora.redhat.com/projects/docs/">project home
page</ulink>. If you find a problem with these terms, file a
<ulink url="http://bugzilla.redhat.com/bugzilla/">Bugzilla</ulink>
report against the fedora-docs component. There is also a bug
reporting link on the
<ulink url="http://fedora.redhat.com/projects/docs/">project
page</ulink> as well.
</para>
<glossary id="fedora-glossary">
<glossdiv>
<title>Jargon Buster</title>
<glossentry>
<glossterm>alsa</glossterm>
<glossdef>
<para>
The Advanced Linux Sound Architecture (ALSA) provides audio
and MIDI functionality to the Linux operating system. Refer
to
<ulink
url="http://www.alsa-project.org/">alsa-project.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Anaconda</glossterm>
<glossdef>
<para>
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
<ulink url="http://fedora.redhat.com/projects/anaconda-installer/">&RH;</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>apt-get</glossterm>
<glossdef>
<para>
Refer to
<ulink
url="https://moin.conectiva.com.br/AptRpm">https://moin.conectiva.com.br/AptRpm</ulink>.
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>ATrpms </glossterm>
<glossdef>
<para>
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
<ulink url="http://atrpms.physik.fu-berlin.de/">atrpms.physik.fu-berlin.de</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>BitTorrent</glossterm>
<glossdef>
<para>
An alternative to a simple FTP or HTTP download. Utilizes
multiple channels to download. Refer to
<ulink
url="http://bitconjurer.org/BitTorrent/">BitTorrent
website</ulink>
</para>
<para>
<ulink url="http://torrent.dulug.duke.edu/">Duke.edu</ulink>
This is the tracker for Fedora Core 1 'Yarrow' release.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm><trademark>Bluecurve</trademark>
</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bugzilla</glossterm>
<glossdef>
<para>
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
<ulink url="http://www.bugzilla.org/">Bugzilla</ulink> home
page.
</para>
</glossdef>
</glossentry>
<glossentry id="core1">
<glossterm>Core 1</glossterm>
<glossdef>
<para>
The Yarrow version of Fedora. Sometimes abbreviated to FC 1
or fc1, Fedora Core 1.
</para>
<glossseealso otherterm="names">&RHL; Names</glossseealso>
</glossdef>
</glossentry>
<glossentry id="core2">
<glossterm>Core 2</glossterm>
<glossdef>
<para>
The Tettnang version of Fedora. Sometimes abbreviated to FC
2 or fc2, Fedora Core 2.
</para>
<glossseealso otherterm="names">&RHL; Names</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>cron</glossterm>
<glossdef>
<para>
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;
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>CUPS</glossterm>
<glossdef>
<para>
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.<ulink
url="http://www.cups.org/">Home
page.</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>desktop switcher</glossterm>
<glossdef>
<para>
The switchdesk-gnome package provides a GNOME look and feel
for the Desktop Switcher program provided in the switchdesk
package.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>eth0</glossterm>
<glossdef>
<para>
(Normally) the first ethernet port on your system
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>ethtool</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>FAQ</glossterm>
<glossdef>
<para>
Frequently Asked Questions, for Fedora see
<ulink url=" http://fedora.redhat.com/about/faq/">fedora.redhat.com</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>FDL</glossterm>
<glossdef>
<para>
GNU Free Documentation License (FDL), see
<ulink url="http://www.gnu.org/licenses/fdl.html">gnu.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>FHS - File System Hierarchy Standard</glossterm>
<glossdef>
<para>
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
<emphasis>should</emphasis> go where. Refer to
<ulink url="http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-filesy...">&RH;</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>FreshRPMS</glossterm>
<glossdef>
<para>
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
<ulink url="http://freshrpms.net/">freshrpms.net</ulink>
</para>
<glossseealso otherterm="RPM">RPM</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>fsck</glossterm>
<glossdef>
<para>
fsck is a command line tool used to check and optionally
repair Linux file systems.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>fsh</glossterm>
<glossdef>
<para>
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.
</para>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>gimp</glossterm>
<glossdef>
<para>
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 <ulink url="http://www.gimp.org/">gimp.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>glibc</glossterm>
<glossdef>
<para>
The GNU C library is used as the C library in the GNU system
and most newer systems with the Linux kernel. Refer to
<ulink url="http://www.gnu.org/software/libc/libc.html">gnu.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>GNOME</glossterm>
<glossdef>
<para>
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 <ulink url="http://www.gnome.org">Home
page </ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>GPG</glossterm>
<glossdef>
<para>
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
<ulink
url="http://gnupg.org/">gnupg.org</ulink>. You may
also see RPM-GPG-KEY referenced, which relates to the keys
used for checking packages. E.g. see
<ulink
url="http://rpmfind.net/linux/rawhide/1.0/i386/">rpmfind
</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>GPL & non-GPL http://www.fsf.org/licenses/gpl-faq.htm</glossterm>
<glossdef>
<para>
Gnu General Public Licence. Refer to
<ulink url="http://www.fsf.org/licenses/licenses.html">fsf.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>GRUB</glossterm>
<glossdef>
<para>
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
<ulink url="http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-grub-w...">&RH;</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>i386</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>IRC</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>ISO</glossterm>
<glossdef>
<para>
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.
</para>
<para>
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
<ulink url="http://www.iso.org">iso.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>KDE</glossterm>
<glossdef>
<para>
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
<trademark
class="registered">Microsoft</trademark>
<trademark
class="registered">Windows</trademark>. Refer
to the <ulink
url="http://www.kde.org/whatiskde/">Home
page</ulink> for more information.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>kernel</glossterm>
<glossdef>
<para>
The heart of Linux. The main code derived from Linus's
original software.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>kickstart</glossterm>
<glossdef>
<para>
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
<ulink
url="http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/ch-kic...">&RH;
</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Kudzu</glossterm>
<glossdef>
<para>
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.
<ulink
url="http://fedora.redhat.com/projects/additional-projects/kudzu/">fedora.redhat.com</ulink>
for more.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>LDAP</glossterm>
<glossdef>
<para>
Lightweight Directory Access Protocol
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>lilo</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>LSB</glossterm>
<glossdef>
<para>
Linux standard base. The goal of the LSB is to develop and
promote a set of standards that will increase compatability
among Linux distributions
<ulink
url="http://www.linuxbase.org/">linuxbase.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>lspci</glossterm>
<glossdef>
<para>
lspci is a utility for displaying information about all PCI
buses in the system and all devices connected to them.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Mandrake</glossterm>
<glossdef>
<para>
Another Linux distribution
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>md5sum</glossterm>
<glossdef>
<para>
md5sum computes a 128-bit checksum (or fingerprint or
message-digest) for each specified file. Refer to
<ulink
url="http://www.gnu.org/software/textutils/manual/textutils/html_chapter/textu...">gnu.org</ulink>
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.
</para>
<para>
For windows,
<ulink
url="http://downloads.activestate.com/contrib/md5sum/Windows/">activestate.com</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Memtest86</glossterm>
<glossdef>
<para>
Memory testing may be performed prior to installing Fedora
Core by entering <command> memtest86</command> at the boot:
prompt. This causes the <command>Memtest86</command>
standalone memory testing software to run.
<command>Memtest86</command> memory testing continues until
the Esc key is pressed.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Mount point</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Mozilla</glossterm>
<glossdef>
<para>
Mozilla is an open-source web browser, designed for
standards compliance, performance and portability. Refer to
<ulink url="http://www.mozilla.org">Mozilla.org</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Nautilus</glossterm>
<glossdef>
<para>
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.
<ulink url="http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/getting-started-gui...">redhat</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>package</glossterm>
<glossdef>
<para>
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
</para>
<glossseealso otherterm="RPM">RPM</glossseealso>
<glossseealso otherterm="rhconfpkg">redhat-config-packages</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>pine</glossterm>
<glossdef>
<para>
Pine — a Program for Internet News & Email —
is a tool for reading, sending, and managing electronic
messages (email). Refer to
<ulink url="http://www.washington.edu/pine/">washington.edu</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Psyche</glossterm>
<glossdef>
<para>
The name given to &RHL; 8
</para>
<glossseealso otherterm="names">&RHL; Names</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Rawhide</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry id="names">
<glossterm>&RHL; Names</glossterm>
<glossdef>
<para>
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.).
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>RHEL</glossterm>
<glossdef>
<para>
&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
<ulink
url="http://www.redhat.com/software/rhel/">&RH;
</ulink> for more.
</para>
</glossdef>
</glossentry>
<glossentry id="rhconfpkg">
<glossterm>redhat-config-packages</glossterm>
<glossdef>
<para>
redhat-config-packages is the package manager for &RHL; and
&DISTRO;. It supports installation of packages from CD or
other sources
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>&RH; End User Licence Agreement (RHEULA)</glossterm>
<glossdef>
<para>
Each of &RH; software products is covered by an End User
License Agreement. Refer to
<ulink url="http://www.redhat.com/licenses/">&RH;</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>rhgb </glossterm>
<glossdef>
<para>
&RH; Graphical Boot.
</para>
<para>
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 <filename>/etc/sysconfig/init</filename> file;
set it to "no" to permanently disable graphical booting. In
addition, the parameter rhgb must be appended to your
bootloader command line.
</para>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>RHN</glossterm>
<glossdef>
<para>
&RHN;
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>RHN Applet</glossterm>
<glossdef>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry id="RPM">
<glossterm>RPM</glossterm>
<glossdef>
<para>
&RH; Package Manager, or nowadays, RPM Package Manager.
</para>
<para>
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Rsync</glossterm>
<glossdef>
<para>
rsync is an open source utility that provides fast
incremental file transfer. Refer to
<ulink url="http://samba.anu.edu.au/rsync/">samba.anu.edu</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>SELinux</glossterm>
<glossdef>
<para>
<ulink url="http://www.nsa.gov/selinux/">nsa.gov</ulink>,
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.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Severn</glossterm>
<glossdef>
<para>
The beta version of Fedora, closed off early November 2003,
severn was the beta version 0.95
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Shrike</glossterm>
<glossdef>
<para>
The name given to &RHL; 9
</para>
<glossseealso otherterm="names">&RHL; Names</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Sodipodi</glossterm>
<glossdef>
<para>
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
<ulink url="http://sourceforge.net/projects/sodipodi">Sourceforge</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>SRPMs</glossterm>
<glossdef>
<para>
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.
</para>
<glossseealso otherterm="RPM">RPM</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Tettnang</glossterm>
<glossdef>
<para>
"Tettnang" is the second release (version 2) of Fedora Core.
</para>
<glossseealso otherterm="names">&RHL; Names</glossseealso>
<glossseealso otherterm="core2">Core 2</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Up2date</glossterm>
<glossdef>
<para>
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
<ulink
url="http://www.redhat.com/advice/tips/up2date.html">&RH;
site</ulink> for more detail.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>VMware</glossterm>
<glossdef>
<para>
A commercial product,
<trademark class="registered">VMware</trademark> Workstation
is virtual machine software for the desktop. Optimized for
the power user, VMware Workstation runs multiple operating
systems, including Microsoft Windows, Linux, and
<trademark class="registered">Novell</trademark>
<trademark class="registered">NetWare</trademark>,
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
<ulink url="http://www.vmware.com/">home page </ulink> for
more information.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>VNC</glossterm>
<glossdef>
<para>
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
<ulink url="http://www.realvnc.com/">realvnc.com</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>XFS</glossterm>
<glossdef>
<para>
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
<ulink
url="http://oss.sgi.com/projects/xfs/faq.html#whatisxfs">oss.sgi.com</ulink>
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Ximian</glossterm>
<glossdef>
<para>
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 <citetitle>Release Notes</citetitle>
for details.
</para>
<para>
Ximian had its genesis in the GNOME project and offers a
complete Linux desktop environment and productivity
application suite. Refer to
<ulink url="http://www.ximian.com/about_us/">the home
page</ulink>. 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
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>X Window System</glossterm>
<glossdef>
<para>
Possibly a misnomer, though often used to describe the GUI
(Window like ) user interface for Linux. Refer to
<ulink
url="http://www.ntlug.org/~cbbrowne/xwindows.html">ntlug.org</ulink>
for the rationale.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Yarrow</glossterm>
<glossdef>
<para>
"Severn" was a beta version of Fedora and "yarrow" is the
first release version 1, November 6, 2003
</para>
<para>
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.
</para>
<glossseealso otherterm="names">&RHL; Names</glossseealso>
<glossseealso otherterm="core1">Core 1</glossseealso>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Yum</glossterm>
<glossdef>
<para>
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
<ulink
url="http://linux.duke.edu/projects/yum/">Duke
University</ulink>
</para>
</glossdef>
</glossentry>
<!--
<glossentry>
<glossterm></glossterm>
<glossdef>
<para> </para>
</glossdef>
</glossentry>
<glossentry>
<glossterm></glossterm>
<glossdef>
<para> </para>
</glossdef>
</glossentry>
-->
</glossdiv>
</glossary>
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
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 <tfox(a)redhat.com>
-# Last edited by: Tammy Fox <tfox(a)redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds(a)MegaCoder.com>
# 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 ---
18 years, 8 months
yum-software-management yum-software-management-en.xml,1.41,1.42
by fedora-docs-commits@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 @@
<!ENTITY BOOKID "yum-software-management-1.0 (2005-08-13)"> <!-- change version of manual and date here -->
-<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
-
<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "155190">
<!ENTITY FCLOCALVER "4">
-<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">
]>
18 years, 8 months
example-tutorial example-tutorial-en.xml,1.13,1.14
by fedora-docs-commits@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 @@
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "example-tutorial-0.12 (2003-08-20)"> <!-- change version of manual and date here -->
-
-<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
+<!ENTITY BOOKID "example-tutorial-0.13 (2005-08-17)"> <!-- change version of manual and date here -->
]>
@@ -15,7 +13,7 @@
<articleinfo>
<title>Example Tutorial</title>
<copyright>
- <year>2003</year>
+ <year>2003, 2005</year>
<holder>&FORMAL-RHI;</holder>
<holder>Tammy Fox</holder>
</copyright>
@@ -41,9 +39,9 @@
</indexterm>
<para>
- 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.
</para>
<para>
Keep text within the <command>title</command> tags on the same line as the
@@ -119,3 +117,9 @@
<index id="generated-index"></index>
</article>
+
+<!--
+Local variables:
+mode: xml
+End:
+-->
18 years, 8 months
docs-common/man/man1 tidy-bowl.1,NONE,1.1
by fedora-docs-commits@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(a)MegaCoder.com
.fi
18 years, 8 months
docs-common/bin tidy-bowl,1.1,1.2
by fedora-docs-commits@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
18 years, 8 months
docs-common/man/man1 - New directory
by fedora-docs-commits@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
18 years, 8 months
docs-common/man - New directory
by fedora-docs-commits@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
18 years, 8 months
securing-filesystems sn-introduction.xml,1.2,1.3
by fedora-docs-commits@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.
</para>
+
<para>
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.
</para>
+
<section id="sn-introduction-audience">
<title>Intended Audience</title>
<para>
@@ -38,6 +40,7 @@
topic so that the following categories of audience can readily acquire
valuable relevant information that corresponds to their skill level:
</para>
+
<itemizedlist>
<listitem><para>System Administrators</para></listitem>
<listitem><para>Security Practitioners</para></listitem>
@@ -80,6 +83,7 @@
document outline.
</revremark>
</revision>
+
<revision>
<revnumber>0.2</revnumber>
<date>2005-05-13</date>
@@ -89,6 +93,7 @@
inclusive nature of the document title.
</revremark>
</revision>
+
<revision>
<revnumber>0.1</revnumber>
<date>2005-05-04</date>
@@ -165,6 +170,7 @@
<entry><quote>Quoted text</quote></entry>
<entry>Quotes from people, quoted computer output.</entry>
</row>
+
<row>
<entry><screen>terminal view</screen></entry>
<entry>
@@ -172,12 +178,14 @@
terminal, usually rendered with a light grey background.
</entry>
</row>
+
<row>
<entry><command>command</command></entry>
<entry>
Name of a command that can be entered on the command line.
</entry>
</row>
+
<row>
<entry><varname>VARIABLE</varname></entry>
<entry>
@@ -185,6 +193,7 @@
in <varname>$VARNAME</varname>.
</entry>
</row>
+
<row>
<entry><option>option</option></entry>
<entry>
@@ -192,6 +201,7 @@
option to the <command>ls</command> command</quote>.
</entry>
</row>
+
<row>
<entry><parameter>argument</parameter></entry>
<entry>
@@ -199,6 +209,7 @@
<parameter>ls</parameter></command></quote>.
</entry>
</row>
+
<row>
<entry>
<cmdsynopsis>
@@ -210,6 +221,7 @@
Command synopsis or general usage, on a separated line.
</entry>
</row>
+
<row>
<entry><filename>filename</filename></entry>
<entry>
@@ -217,6 +229,7 @@
to the <filename>/usr/bin</filename> directory.</quote>
</entry>
</row>
+
<row>
<entry><keycap>Key</keycap></entry>
<entry>
@@ -224,6 +237,7 @@
<keycap>Q</keycap> to quit</quote>.
</entry>
</row>
+
<row>
<entry><guibutton>Button</guibutton></entry>
<entry>
@@ -231,6 +245,7 @@
button.
</entry>
</row>
+
<row>
<entry>
<menuchoice>
@@ -247,6 +262,7 @@
</menuchoice> in your browser.</quote>
</entry>
</row>
+
<row>
<entry><emphasis>Terminology</emphasis></entry>
<entry>
@@ -255,10 +271,12 @@
system.</quote>
</entry>
</row>
+
<row>
<entry>See ?????</entry>
<entry>link to related subject within this guide.</entry>
</row>
+
<row>
<entry>
<ulink url="http://www.buddhalinux.com">The authors
18 years, 8 months