yum-software-management Makefile,1.4,1.5
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29926
Modified Files:
Makefile
Log Message:
Update Makefile to new standards
Index: Makefile
===================================================================
RCS file: /cvs/docs/yum-software-management/Makefile,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Makefile 9 Jul 2005 15:06:36 -0000 1.4
+++ Makefile 18 Sep 2005 22:44:53 -0000 1.5
@@ -8,13 +8,9 @@
# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-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 = yum-software-management-$(LANG)
-XMLFILE = $(DOCNAME).xml
-XMLEXTRAFILES =
+LANGUAGES = en
+DOCBASE = yum-software-management
+XMLEXTRAFILES-en =
######################################################
include ../docs-common/Makefile.common
18 years, 7 months
mirror-tutorial Makefile,1.5,1.6 mirror-tutorial-en.xml,1.9,1.10
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29805
Modified Files:
Makefile mirror-tutorial-en.xml
Log Message:
Update Makefile as well as some content editing
Index: Makefile
===================================================================
RCS file: /cvs/docs/mirror-tutorial/Makefile,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Makefile 29 Jun 2005 14:34:37 -0000 1.5
+++ Makefile 18 Sep 2005 22:43:44 -0000 1.6
@@ -8,13 +8,9 @@
# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-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 = mirror-tutorial-$(LANG)
-XMLFILE = $(DOCNAME).xml
-XMLEXTRAFILES =
+LANGUAGES = en
+DOCBASE = mirror-tutorial
+XMLEXTRAFILES-en =
######################################################
include ../docs-common/Makefile.common
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- mirror-tutorial-en.xml 2 Aug 2005 22:07:37 -0000 1.9
+++ mirror-tutorial-en.xml 18 Sep 2005 22:43:44 -0000 1.10
@@ -5,7 +5,7 @@
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "mirror-tutorial-0.30 (2005-08-01)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "mirror-tutorial-0.31 (2005-08-29)"> <!-- change version of manual and date here -->
<!ENTITY BUG-NUM "130125">
<!ENTITY FCLOCALVER "4">
@@ -13,7 +13,7 @@
<article id="mirror-tutorial" lang="en">
<articleinfo>
- <title>Mirror Tutorial</title>
+ <title>Mirror Tutorial - <emphasis>BETA</emphasis></title>
<copyright>
<year>
2004
@@ -148,6 +148,16 @@
</para>
</revdescription>
</revision>
+ <revision>
+ <revnumber>0.31</revnumber>
+ <date>2005-08-29</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Use bug reporting entity, add BETA classification.
+ </para>
+ </revdescription>
+ </revision>
</revhistory>
</articleinfo>
@@ -163,7 +173,7 @@
enhance user experience, adding to the perceived value of
non-proprietary operating systems and software.
</para>
- &DRAFTNOTICE;
+ &BUG-REPORTING;
</section>
<section id="sn-audience">
<title>Audience</title>
@@ -307,22 +317,24 @@
<para>
The
<filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/os</filename>
- directory contains a copy of all the original distribution files for
- &FC; &FCVER;. They are the same files found on the CD-ROM version of the
- distribution. The <filename>&FED;</filename> subfolder contains all the
- files that are necessary for installation, including the entire
- collection of &FC; RPM packages. The <filename>images</filename> folder
- contains copies of any floppy diskette or CD-ROM images that boot a
- system into installation or rescue modes. The
+ directory contains a copy of all the original distribution files
+ for &FC; &FCVER;. They are the same files found on the DVD and
+ CD-ROM version of the distribution. The
+ <filename>&FED;</filename> subfolder contains all the files that
+ are necessary for installation, including the entire collection
+ of &FC; RPM packages. The <filename>images</filename> folder
+ contains copies of any floppy diskette or CD-ROM images that
+ boot a system into installation or rescue modes. The
<filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/iso</filename>
- folder contains images of the CD-ROM version of the distribution.
+ folder contains images of the CD-ROM version of the
+ distribution.
</para>
<note>
<title>RPM packages</title>
<para>
<firstterm>RPM</firstterm><indexterm>
<primary>RPM</primary>
- </indexterm>, originally the Red Hat Package Manager, now the RPM
+ </indexterm>, originally the Red Hat Package Manager and now the RPM
Package Manager, is not just a file format. RPM is also a system which
tracks and interconnects software and version information. The RPM
system is quite popular, and many other Linux distributions use RPM as
@@ -396,7 +408,7 @@
</para>
<screen>
-<computeroutput>/path/i386/iso/FC&FCVER;-i386-disc1.iso /path/i386/os/disc1 iso9660 defaults 0 0</computeroutput>
+<computeroutput>/path/i386/iso/FC&FCVER;-i386-disc1.iso /path/i386/os/disc1 iso9660 defaults 0 0</computeroutput>
</screen>
<para>
@@ -406,9 +418,6 @@
<application>system-config-packages</application> also continue to work
properly when pointed at the parent of the ISO image mount points.
</para>
-
-<!-- FIXME: Is the above true? See other questions below... -->
-
<para>
There are drawbacks to using CD ISO images in this fashion. For
instance, no one directory contains the entire distribution of RPM
@@ -418,6 +427,15 @@
hardware, however, cannot use this image to make discs for their own
use.
</para>
+ <para>
+ You only need a single line in <filename>/etc/fstab</filename>
+ for mounting the &FC; DVD ISO image. The entry looks like this:
+ </para>
+
+<screen>
+<computeroutput>/path/i386/iso/FC&FCVER;-i386-DVD.iso /path/i386/os iso9660 defaults 0 0</computeroutput>
+</screen>
+
</section>
<section id="sn-trimming-tree">
@@ -491,13 +509,13 @@
<term>The <filename>debug</filename> folders.</term>
<listitem>
<para>
- These folders contain packages that enable developers and skilled
- users to interpret data created when a program crashes or
- encounters a bug. If you participate actively in &FED;
- development, you should not trim these folders. If you trim this
- branch, you may still download individual packages on an
- <foreignphrase>ad hoc</foreignphrase> basis from a nearby public
- mirror site.
+ These folders contain packages that enable developers and
+ skilled users to interpret data created when a program
+ crashes or encounters a bug. If you participate actively
+ in &FED; development, you should not trim these
+ folders. If you trim this branch, you may still download
+ individual packages as needed from a nearby public mirror
+ site.
</para>
</listitem>
</varlistentry>
@@ -506,10 +524,10 @@
thereto).</term>
<listitem>
<para>
- These folders contain the original source for all the binary RPM
- packages in the distribution. You may download these packages on
- an <foreignphrase>ad hoc</foreignphrase> basis if you need to save
- space on your local mirror.
+ These folders contain the original source for all the
+ binary RPM packages in the distribution. You may download
+ these packages individually as needed to save space on
+ your local mirror.
</para>
</listitem>
</varlistentry>
@@ -1016,61 +1034,40 @@
Packages installed without satisfying their dependencies may not work
correctly. Dependencies may create a problem for users who are trying to
install a single package. Manually determining and resolving
- dependencies is difficult. &FC; has several methods for solving these
+ dependencies is difficult. &FC; provides the
+ <command>yum</command> utility for solving these
dependencies automatically, providing an improved user experience.
</para>
- <section id="sn-rhn-history">
- <title>Red Hat Network</title>
- <para>
- <emphasis>Red Hat Network</emphasis><indexterm>
- <primary>Red Hat Network</primary>
- </indexterm>, or <emphasis>RHN</emphasis><indexterm>
- <primary>RHN</primary>
- <see>Red Hat Network</see>
- </indexterm>, is a systems management and deployment tool that was
- introduced in Red Hat Linux, and continues to be used with Red Hat
- Enterprise Linux. RHN makes updates available to registered users, and
- allows them to remotely schedule and manage their systems using a
- single Web-based console. The client systems run the
- <application>up2date</application> application to communicate with
- RHN.
- </para>
- <para>
- Although &FC; systems do not inter-operate with RHN, they still include
- an <application>up2date</application> client. This client is
- enhanced to support non-RHN update services. These services, like RHN,
- solve RPM package dependencies automatically.
- </para>
- </section>
-
- <section id="sn-yum">
- <title><command>yum</command></title>
- <para>
- The Yellow Dog Updater Modified, or
- <emphasis>yum</emphasis><indexterm>
- <primary>yum</primary>
- </indexterm>, is a Python-based system for computing and solving RPM
- dependencies. A <command>yum</command> client retrieves a cache of
- headers from its repository server, as well as a list of available RPM
- packages and their exact locations on the server. It can do this via
- HTTP or FTP, as well as using standard file system calls (either local
- or remote via NFS). The client computes solutions to any package
- dependencies using the downloaded header information, and simply
- requests all necessary RPM packages once it has finished. The
- <command>yum</command> command relies on <command>rpm</command> to
- perform all computation involved in the process.
- </para>
- <para>
- A drawback to <command>yum</command> is that the first time it is run,
- it must download a header for every package installed on the system in
- order to determine available updates. However, running a local mirror
- nullifies this drawback. The <command>yum</command> command can, of
- course, download many megabytes of headers almost instantly on a
- standard Ethernet LAN. <command>yum</command> is the most popular
- update method for &FC;.
- </para>
- </section>
+ <para>
+ The Yellow Dog Updater Modified, or
+ <emphasis>yum</emphasis><indexterm> <primary>yum</primary>
+ </indexterm>, is a Python-based system for computing and solving
+ RPM dependencies. A <command>yum</command> client retrieves a
+ cache of headers from its repository server, as well as a list
+ of available RPM packages and their exact locations on the
+ server. It can do this via HTTP or FTP, as well as using
+ standard file system calls (either local or remote via NFS). The
+ client computes solutions to any package dependencies using the
+ downloaded header information, and simply requests all necessary
+ RPM packages once it has finished. The <command>yum</command>
+ command relies on <command>rpm</command> functions to perform
+ many of the computations involved in the process.
+ </para>
+ <para>
+ A drawback to <command>yum</command> is that the first time it
+ is run, it must download a header for every package installed on
+ the system in order to determine available updates. However,
+ running a local mirror nullifies this drawback. The
+ <command>yum</command> command can, of course, download many
+ megabytes of headers almost instantly on a standard Ethernet
+ LAN. The <command>yum</command> utility is the most popular
+ update method for &FC;.
+ </para>
+ <para>
+ For more information about using <command>yum</command>, refer
+ to <ulink url="http://fedora.redhat.com/docs/yum/"/>.
+ </para>
</section>
@@ -1092,6 +1089,21 @@
<command>yum</command> it supports. It is permissible to have both kinds
of repository information in a single repository.
</para>
+ <para>
+ To support older <command>yum</command> clients, use the
+ <command>yum-arch</command> command. To support current
+ <command>yum</command> clients, use the
+ <command>createrepo</command> command.
+ </para>
+ <important>
+ <title>Supporting &FC; 3 and beyond</title>
+ <para>
+ &FC; 3 ships with a newer version of <command>yum</command>.
+ To support &FC; 3 <command>yum</command> clients, you
+ <emphasis>must</emphasis> use <command>createrepo</command> on
+ your server's repositories.
+ </para>
+ </important>
<section id="sn-yum-arch">
<title><command>yum-arch</command></title>
@@ -1133,25 +1145,16 @@
<command>createrepo</command> program also searches recursively for
RPM packages to include in the repository data.
</para>
+ <para>
+ The following command creates the repository data in the directory
+ <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/repodata</filename>.
+ </para>
<screen>
<userinput>createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput>
</screen>
<para>
- The command above creates the repository data in the directory
- <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/repodata</filename>.
- </para>
- <important>
- <title>Supporting &FC; 3 and beyond</title>
- <para>
- &FC; 3 ships with a newer version of <command>yum</command>. To
- support &FC; 3 <command>yum</command> clients, you
- <emphasis>must</emphasis> use <command>createrepo</command> on your
- server's repositories.
- </para>
- </important>
- <para>
You may not be able to foresee all the possible uses for your server's
repositories. To minimize problems for your clients, create both kinds
of repository data for any repositories.
@@ -1389,18 +1392,18 @@
</para>
<tip id="tp-s-c-p-stock-only">
- <title><application>up2date</application> and
+ <title><command>yum</command> and
<application>system-config-packages</application></title>
<para>
If you plan to carry updates on your mirror, as most administrators
do, you will probably not use
<application>system-config-packages</application> much. Once the
- installed package versions become out of sync with the stock
- distribution versions, <application>up2date</application> becomes much
+ installed package versions become out of sync with the original
+ distribution versions, <command>yum</command> becomes much
more useful. The preferred method for installing a package in that
- case would be <command>up2date --install
+ case would be <command>yum install
<replaceable>package_name</replaceable></command>. See <xref
- linkend="sn-up2date"/> for more information.
+ linkend="sn-solving-dependencies"/> for more information.
</para>
</tip>
@@ -1583,119 +1586,6 @@
</section>
- <section id="sn-up2date">
- <title>Configuring <application>up2date</application></title>
- <para>
- The <application>up2date</application> application in &FC; now
- allows use of <command>yum</command> and
- <command>apt</command> repositories. The client must have a
- configuration that points at the desired repositories.
- </para>
-
- <section id="sn-up2date-config">
- <title><filename>/etc/sysconfig/rhn/up2date</filename></title>
- <para>
- The <filename>/etc/sysconfig/rhn/up2date</filename> file controls the
- global configuration of the <application>up2date</application>
- application. This file is well commented and is not explained in great
- detail here. Here are some points to keep in mind, however:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- By default, the user must intervene to update
- <command>kernel</command> packages. See the
- <command>pkgSkipList</command> variable. At the command line, use
- the <command>-f</command> option to force an override. At the GUI
- interface, <application>up2date</application> allows the user to
- override.
- </para>
- </listitem>
- <listitem>
- <para>
- By default, <command>up2date</command> does not remove old
- <command>kernel</command> packages. See the
- <command>pkgsToInstallNotUpdate</command> variable. When
- <command>up2date</command> installs a new kernel package, the old
- version remains in place until removed explicitly.
- </para>
- </listitem>
- <listitem>
- <para>
- The configuration file also allows use of an HTTP proxy if
- desired. A number of variables pertain to this function.
- </para>
- </listitem>
- <listitem>
- <para>
- By default, <application>up2date</application> sends mail to
- <email>root@localhost</email> when packages are updated in batch
- mode. (Running <command>up2date -u</command> starts
- <application>up2date</application> in batch mode.) See the
- <command>adminAddress</command> option. If you support multiple
- clients and intend to use batch mode at your site, you should set
- a new address here.
- </para>
- </listitem>
- </itemizedlist>
-
- </section>
-
- <section id="sn-up2date-sources">
- <title><filename>/etc/sysconfig/rhn/sources</filename></title>
- <para>
- The <filename>/etc/sysconfig/rhn/sources</filename> file is used to
- declare the repositories that are used with
- <application>up2date</application>. A repository is declared in any of
- the following ways:
- </para>
-
-<screen>
-<computeroutput>apt <replaceable>label</replaceable> <replaceable>service:server</replaceable> <replaceable>path</replaceable> <replaceable>repository_name</replaceable>
-yum <replaceable>label</replaceable> <replaceable>URL</replaceable>
-dir <replaceable>label</replaceable> <replaceable>local_path</replaceable></computeroutput>
-</screen>
-
- <para>
- For <command>apt</command> repositories,
- <command>service:server</command> is the standard Internet protocol
- and host name — for example, http://mirror.example.com. For
- <command>yum</command> repositories, the URL points to the directory
- on a server which <emphasis>contains</emphasis> the
- <filename>headers</filename> folder. A <command>dir</command>
- repository simply points to a folder that contains RPM packages. The
- folder may contain the RPM packages in subdirectories.
- </para>
- <para>
- The <command>yum-mirror</command> syntax points to a file that is a
- list of alternative sources for the same repository:
- </para>
-
-<screen>
-<computeroutput>yum-mirror <replaceable>label</replaceable> <replaceable>URL</replaceable></computeroutput>
-</screen>
-
- <para>
- Edit <filename>/etc/sysconfig/rhn/sources</filename> for the clients
- at your site to point to your repository. For any repository, point to
- the URL for the directory containing the <filename>headers</filename>
- folder. You created this folder using <command>yum-arch</command> in
- <xref linkend="sn-repositories"/>. You will likely have two
- repositories, one for the stock distribution and one for updates.
- Examples are shown below; you may wish to point to an internal address
- rather than an outward-facing server. Use a URL appropriate to your
- network and Apache configuration.
- </para>
-
-<screen>
-<userinput>yum fedora-core-&FCVER; http://www.mydomain.org/pub/linux/fedora/core/&FCVER;/i386/os
-yum fc&FCVER;-updates http://www.mydomain.org/pub/linux/fedora/core/updates/&FCVER;/i386</userinput>
-</screen>
-
- </section>
-
- </section>
-
</section>
<!--
@@ -1721,3 +1611,10 @@
</index>
</article>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
18 years, 7 months
docs-common Makefile.common,1.8,1.9
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10318/docs-common
Modified Files:
Makefile.common
Log Message:
Added multi-language support.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Makefile.common 20 Aug 2005 14:34:09 -0000 1.8
+++ Makefile.common 17 Sep 2005 14:41:42 -0000 1.9
@@ -21,51 +21,100 @@
# providing additional rules, also marked with double-colons, in the
# document Makefile.
#########################################################################
+# Supply default values for the boilerplate files _unless_ the user has
+# provided their own values.
+ifeq (${XSLPDF},)
+XSLPDF = ../docs-common/xsl/main-pdf.xsl
+endif
+ifeq (${XSLHTML},)
+XSLHTML = ../docs-common/xsl/main-html.xsl
+endif
+ifeq (${XSHTMLNOCHUNKS},)
+XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl
+endif
+#########################################################################
# PUT NO TARGETS BEFORE THIS ONE, not even in your base Makefile
# In a properly-constructed Makefile, this will be the default target
-.PHONY: all tarball pdf html html-nochunks clean distclean
+TARGETS=all tarball pdf html html-nochunks clean distclean
+.PHONY: ${TARGETS}
-all:: ${DOCNAME}/index.html
+all:: html html-nochunks tarball # pdf
-# The "tarball" or "${DOCNAME}.tar.gz" target will bind the HTML formatted
-# document into a compressed tar archive.
+${TARGETS}::
-tarball ${DOCNAME}.tar.gz:: ${DOCNAME}/index.html
- 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.
-
-pdf ${DOCNAME}.pdf:: ${XMLFILE} ${XMLEXTRAFILES}
- xmlto pdf -x $(XSLPDF) $(XMLFILE)
-
-# The "html" or "${DOCNAME}.
-html ${DOCNAME}/index.html:: ${XMLFILE} ${XMLEXTRAFILES}
- xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
- mkdir -p $(DOCNAME)/stylesheet-images
- cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
- cp ../docs-common/css/fedora.css $(DOCNAME)
-
-html-nochunks $(DOCNAME).html:: ${XMLFILE} ${XMLEXTRAFILES}
- xmlto html-nochunks -x $(XSLHTMLNOCHUNKS) $(XMLFILE)
- mkdir -p stylesheet-images
- cp ../docs-common/stylesheet-images/*.png stylesheet-images
+#########################################################################
+# For each LANG in LANGUAGES, generate a target and rule similar to:
+# mydoc-en/index.html:: mydoc-en.xml ${XMLEXTRAFILES}-en
+# LANG=en.UTF-8 xmlto html -x $(XSLHTML) -o mydoc-en mydoc-en.xml
+# mkdir -p mydoc-en/stylesheet-images
+# cp ../docs-common/stylesheet-images/*.png mydoc-en/stylesheet-images/
+# cp ../docs-common/css/fedora.css mydoc-en/
+#
+define HTML_template
+${DOCBASE}-$(1)/index.html:: ${DOCBASE}-$(1).xml $$(XMLEXTRAFILES-$(1))
+ LANG=$(1).UTF-8 xmlto html -x $(XSLHTML) -o $(DOCBASE)-$(1) $(DOCBASE)-$(1).xml
+ mkdir -p $(DOCBASE)-$(1)/stylesheet-images/
+ cp ../docs-common/stylesheet-images/*.png $(DOCBASE)-$(1)/stylesheet-images
+ cp ../docs-common/css/fedora.css $$(DOCBASE)-$(1)/
+endef
+#
+html:: $(foreach LANG,${LANGUAGES},$(DOCBASE)-$(LANG)/index.html)
+
+$(foreach LANG,${LANGUAGES},$(eval $(call HTML_template,${LANG})))
+#
+#########################################################################
+# For each language in ${LANGUAGES}, generate a single HTML file
+define HTMLNOCHUNK_template
+${DOCBASE}-$(1).html:: ${DOCBASE}-$(1).xml $$(XMLEXTRAFILES-$(1))
+ xmlto html-nochunks -x $(XSLHTMLNOCHUNKS) $(DOCBASE)-$(1).xml
+ mkdir -p stylesheet-images/
+ cp ../docs-common/stylesheet-images/*.png stylesheet-images/
cp ../docs-common/css/fedora.css .
-
-# The "view" target ensures that the HTML version of the document is built
-# then displays it using the "htmlview" tool to start up the browser. It
-# assumes that the current working directory is immediately above the HTML
-# document directory. (We could change this if we wanted to futz around
-# with making up an absolute pathname, but why bother.)
-
-view:: ${DOCNAME}/index.html
- /usr/bin/htmlview file://localhost/${PWD}/${DOCNAME}/index.html
-
-# The "clean" or "distclean" target will remove all generated and temporary
-# files.
-
-distclean clean:
- ${RM} -r ${DOCNAME}.pdf $(DOCNAME) \
- ${DOCNAME}.tar.gz \
- ${DOCNAME}.html stylesheet-images fedora.css
+endef
+#
+html-nochunks:: $(foreach LANG,${LANGUAGES},$(DOCBASE)-$(LANG).html)
+
+$(foreach LANG,${LANGUAGES},$(eval $(call HTMLNOCHUNK_template,${LANG})))
+#
+#########################################################################
+# For each language in ${LANGUAGES}, build a tarball of the HTML files.
+#
+define TAR_template
+${DOCBASE}-$(1).tar.gz:: ${DOCBASE}-$(1)/index.html
+ tar -zc --exclude '*.eps' -f ${DOCBASE}-$(1).tar.gz ${DOCBASE}-$(1)
+endef
+#
+tarball:: $(foreach LANG,${LANGUAGES},$(DOCBASE)-$(LANG).tar.gz)
+
+$(foreach LANG,${LANGUAGES},$(eval $(call TAR_template,${LANG})))
+#
+#########################################################################
+# For each language in ${LANGUAGES}, generate an Adobe Portable Document
+# Format (PDF) file.
+define PDF_template
+${DOCBASE}-$(1).pdf:: ${DOCBASE}-$(1).xml $$(XMLEXTRAFILES-$(1))
+ xmlto pdf -x $(XSLPDF) $(DOCBASE)-$(1).xml
+endef
+#
+pdf:: $(foreach LANG,${LANGUAGES},$(DOCBASE)-$(LANG).pdf)
+
+$(foreach LANG,${LANGUAGES},$(eval $(call PDF_template,${LANG})))
+#
+#########################################################################
+# For each language in ${LANGUAGES}, clean up!
+define CLEAN_template
+${DOCBASE}-$(1)-clean::
+ ${RM} -r ${DOCBASE}-$(1)
+ ${RM} -r ${DOCBASE}-$(1).html stylesheet-images fedora.css
+ ${RM} -r ${DOCBASE}-$(1).pdf
+ ${RM} -r ${DOCBASE}-$(1).tar.gz
+endef
+#
+distclean clean:: $(foreach LANG,${LANGUAGES},${DOCBASE}-${LANG}-clean)
+
+$(foreach LANG,${LANGUAGES},$(eval $(call CLEAN_template,${LANG})))
+#
+#########################################################################
+# End of Makefile.common
+#########################################################################
18 years, 7 months
example-tutorial Makefile,1.10,1.11
by fedora-docs-commits@redhat.com
Author: jtr
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10318/example-tutorial
Modified Files:
Makefile
Log Message:
Added multi-language support.
Index: Makefile
===================================================================
RCS file: /cvs/docs/example-tutorial/Makefile,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- Makefile 29 Jun 2005 14:17:01 -0000 1.10
+++ Makefile 17 Sep 2005 14:41:42 -0000 1.11
@@ -7,24 +7,22 @@
# Copyright 2003 Tammy Fox, Red Hat, Inc.
# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-
-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 = example-tutorial-$(LANG)
-XMLFILE = $(DOCNAME).xml
-XMLEXTRAFILES =
-
+#
+# Document-specific definitions.
+#
+LANGUAGES = en
+DOCBASE = example-tutorial
+XMLEXTRAFILES-en=
+#
######################################################
include ../docs-common/Makefile.common
######################################################
-
+#
# If you want to add additional steps to any of the
# targets defined in "Makefile.common", be sure to use
# 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::
+#${DOCBASE}-en/index.html::
# echo FINISHED AT LAST
18 years, 7 months
jargon-buster jargon-buster-en.xml,1.9,1.10
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/jargon-buster
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4026/jargon-buster
Modified Files:
jargon-buster-en.xml
Log Message:
quick style edit, bump to 1.9.3
Index: jargon-buster-en.xml
===================================================================
RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- jargon-buster-en.xml 7 Sep 2005 12:55:34 -0000 1.9
+++ jargon-buster-en.xml 7 Sep 2005 22:20:46 -0000 1.10
@@ -4,7 +4,7 @@
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "jargon-buster-1.9.2 (2005-08-26)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "jargon-buster-1.9.3 (2005-09-07)"> <!-- change version of manual and date here -->
]>
@@ -170,6 +170,16 @@
</para>
</revdescription>
</revision>
+ <revision>
+ <revnumber>1.9.3</revnumber>
+ <date>7 Sep 2005</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Style editing.
+ </para>
+ </revdescription>
+ </revision>
</revhistory>
</articleinfo>
@@ -870,17 +880,16 @@
To use a disk device such as a CD, USB drive, or floppy
diskette, you must first <command>mount</command> 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
- <systemitem>A:</systemitem> or <systemitem>C:</systemitem>.
- When you <command>mount</command> a disk device, its file
- system becomes part of the unified file system on &FED;.
- The device is mounted on a <firstterm>mount
- point</firstterm>, which is a directory that points to that
- device, such as <filename>/media/floppy</filename>. 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.
+ Windows systems, on the other hand, use a "drive letter" for
+ each disk device, such as <systemitem>A:</systemitem> or
+ <systemitem>C:</systemitem>. When you
+ <command>mount</command> a disk device, its file system
+ becomes part of the unified file system on &FED;. The
+ device is mounted on a <firstterm>mount point</firstterm>,
+ which is a directory that points to that device, such as
+ <filename>/media/floppy</filename>. 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.
</para>
<para>
Since these functions are often handled through
18 years, 7 months
jargon-buster jargon-buster-en.xml,1.8,1.9
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/jargon-buster
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18426
Modified Files:
jargon-buster-en.xml
Log Message:
Trivial name change
Index: jargon-buster-en.xml
===================================================================
RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- jargon-buster-en.xml 4 Sep 2005 13:52:20 -0000 1.8
+++ jargon-buster-en.xml 7 Sep 2005 12:55:34 -0000 1.9
@@ -23,7 +23,7 @@
</author>
<author>
<firstname>Paul</firstname>
- <othername role="mi">W</othername>
+ <othername role="mi">W.</othername>
<surname>Frields</surname>
</author>
</authorgroup>
18 years, 7 months
docs-common/xsl main-html.xsl,1.6,1.7
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/xsl
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32673
Modified Files:
main-html.xsl
Log Message:
Readability changes, add title to revhistory page summary
Index: main-html.xsl
===================================================================
RCS file: /cvs/docs/docs-common/xsl/main-html.xsl,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- main-html.xsl 4 Sep 2005 14:19:07 -0000 1.6
+++ main-html.xsl 4 Sep 2005 14:50:25 -0000 1.7
@@ -37,16 +37,17 @@
section nop
</xsl:param>
-<xsl:template match="revhistory"><!-- mode="titlepage.mode">-->
+<xsl:template match="revhistory">
<xsl:variable name="numcols">
<xsl:choose>
<xsl:when test="//authorinitials">3</xsl:when>
<xsl:otherwise>2</xsl:otherwise>
</xsl:choose>
</xsl:variable>
+ <xsl:variable name="doctitle" select="//title"/>
<div class="{name(.)}">
- <table border="1" width="100%" summary="Revision history">
+ <table border="1" width="100%" summary="Revision history - {$doctitle}">
<tr>
<th align="left" valign="top" colspan="{$numcols}">
<b>
@@ -105,35 +106,35 @@
<xsl:template match="revhistory" mode="titlepage.mode">
<xsl:variable name="id">revhistory</xsl:variable>
- <xsl:variable name="filename">
- <xsl:call-template name="make-relative-filename">
- <xsl:with-param name="base.dir" select="$base.dir"/>
- <xsl:with-param name="base.name" select="concat('rv-',$id,$html.ext)"/>
- </xsl:call-template>
- </xsl:variable>
+ <xsl:variable name="filename">
+ <xsl:call-template name="make-relative-filename">
+ <xsl:with-param name="base.dir" select="$base.dir"/>
+ <xsl:with-param name="base.name" select="concat('rv-',$id,$html.ext)"/>
+ </xsl:call-template>
+ </xsl:variable>
- <a href="{concat('rv-',$id,$html.ext)}">Revision History</a>
+ <a href="{concat('rv-',$id,$html.ext)}">Revision History</a>
- <xsl:call-template name="write.chunk">
- <xsl:with-param name="filename" select="$filename"/>
- <xsl:with-param name="quiet" select="$chunk.quietly"/>
- <xsl:with-param name="content">
- <xsl:call-template name="user.preroot"/>
- <html>
- <head>
- <xsl:call-template name="system.head.content"/>
- <xsl:call-template name="head.content"/>
- <xsl:call-template name="user.head.content"/>
- </head>
- <body>
- <xsl:call-template name="body.attributes"/>
- <div class="{local-name(.)}">
- <xsl:apply-templates select="."/>
- </div>
- </body>
- </html>
- </xsl:with-param>
- </xsl:call-template>
+ <xsl:call-template name="write.chunk">
+ <xsl:with-param name="filename" select="$filename"/>
+ <xsl:with-param name="quiet" select="$chunk.quietly"/>
+ <xsl:with-param name="content">
+ <xsl:call-template name="user.preroot"/>
+ <html>
+ <head>
+ <xsl:call-template name="system.head.content"/>
+ <xsl:call-template name="head.content"/>
+ <xsl:call-template name="user.head.content"/>
+ </head>
+ <body>
+ <xsl:call-template name="body.attributes"/>
+ <div class="{local-name(.)}">
+ <xsl:apply-templates select="."/>
+ </div>
+ </body>
+ </html>
+ </xsl:with-param>
+ </xsl:call-template>
</xsl:template>
18 years, 7 months
docs-common/xsl main-html.xsl,1.5,1.6
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/xsl
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32618
Modified Files:
main-html.xsl
Log Message:
Generate revision history to separate file, yeah baby!
Index: main-html.xsl
===================================================================
RCS file: /cvs/docs/docs-common/xsl/main-html.xsl,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- main-html.xsl 29 Jun 2005 14:32:49 -0000 1.5
+++ main-html.xsl 4 Sep 2005 14:19:07 -0000 1.6
@@ -37,6 +37,106 @@
section nop
</xsl:param>
+<xsl:template match="revhistory"><!-- mode="titlepage.mode">-->
+ <xsl:variable name="numcols">
+ <xsl:choose>
+ <xsl:when test="//authorinitials">3</xsl:when>
+ <xsl:otherwise>2</xsl:otherwise>
+ </xsl:choose>
+ </xsl:variable>
+
+ <div class="{name(.)}">
+ <table border="1" width="100%" summary="Revision history">
+ <tr>
+ <th align="left" valign="top" colspan="{$numcols}">
+ <b>
+ <xsl:call-template name="gentext">
+ <xsl:with-param name="key" select="'RevHistory'"/>
+ </xsl:call-template>
+ </b>
+ </th>
+ </tr>
+ <xsl:apply-templates>
+ <xsl:with-param name="numcols" select="$numcols"/>
+ </xsl:apply-templates>
+ </table>
+ </div>
+</xsl:template>
+
+<xsl:template match="revhistory/revision">
+ <xsl:param name="numcols" select="'3'"/>
+ <xsl:variable name="revnumber" select=".//revnumber"/>
+ <xsl:variable name="revdate" select=".//date"/>
+ <xsl:variable name="revauthor" select=".//authorinitials"/>
+ <xsl:variable name="revremark" select=".//revremark|.//revdescription"/>
+ <tr>
+ <td align="left">
+ <xsl:if test="$revnumber">
+ <xsl:call-template name="gentext">
+ <xsl:with-param name="key" select="'Revision'"/>
+ </xsl:call-template>
+ <xsl:call-template name="gentext.space"/>
+ <xsl:apply-templates select="$revnumber[1]"/>
+ </xsl:if>
+ </td>
+ <td align="left">
+ <xsl:apply-templates select="$revdate[1]"/>
+ </td>
+ <xsl:choose>
+ <xsl:when test="$revauthor">
+ <td align="left">
+ <xsl:apply-templates select="$revauthor[1]"/>
+ </td>
+ </xsl:when>
+ <xsl:when test="$numcols > 2">
+ <td> </td>
+ </xsl:when>
+ <xsl:otherwise></xsl:otherwise>
+ </xsl:choose>
+ </tr>
+ <xsl:if test="$revremark">
+ <tr>
+ <td align="left" colspan="{$numcols}">
+ <xsl:apply-templates select="$revremark[1]"/>
+ </td>
+ </tr>
+ </xsl:if>
+</xsl:template>
+
+<xsl:template match="revhistory" mode="titlepage.mode">
+ <xsl:variable name="id">revhistory</xsl:variable>
+ <xsl:variable name="filename">
+ <xsl:call-template name="make-relative-filename">
+ <xsl:with-param name="base.dir" select="$base.dir"/>
+ <xsl:with-param name="base.name" select="concat('rv-',$id,$html.ext)"/>
+ </xsl:call-template>
+ </xsl:variable>
+
+ <a href="{concat('rv-',$id,$html.ext)}">Revision History</a>
+
+ <xsl:call-template name="write.chunk">
+ <xsl:with-param name="filename" select="$filename"/>
+ <xsl:with-param name="quiet" select="$chunk.quietly"/>
+ <xsl:with-param name="content">
+ <xsl:call-template name="user.preroot"/>
+ <html>
+ <head>
+ <xsl:call-template name="system.head.content"/>
+ <xsl:call-template name="head.content"/>
+ <xsl:call-template name="user.head.content"/>
+ </head>
+ <body>
+ <xsl:call-template name="body.attributes"/>
+ <div class="{local-name(.)}">
+ <xsl:apply-templates select="."/>
+ </div>
+ </body>
+ </html>
+ </xsl:with-param>
+ </xsl:call-template>
+</xsl:template>
+
+
<!-- Navigation
<xsl:param name="navig.graphics" select="1"></xsl:param>
<xsl:param name="navig.graphics.extension" select="'.png'"></xsl:param>
18 years, 7 months
yum-software-management yum-software-management-en.xml,1.46,1.47
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31054
Modified Files:
yum-software-management-en.xml
Log Message:
Fix up revision history properly, should be good from here on out.
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- yum-software-management-en.xml 27 Aug 2005 23:46:44 -0000 1.46
+++ yum-software-management-en.xml 4 Sep 2005 13:53:03 -0000 1.47
@@ -67,6 +67,27 @@
</para>
</revdescription>
</revision>
+ <revision>
+ <revnumber>1.0.1</revnumber>
+ <date>2005-08-18</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
+ Added information on installing without repository and
+ manually adding keys.
+ </para>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>1.0.2</revnumber>
+ <date>2005-08-26</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
+ Fix localinstall information.
+ </para>
+ </revdescription>
+ </revision>
</revhistory>
</articleinfo>
18 years, 7 months
jargon-buster jargon-buster-en.xml,1.7,1.8
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/jargon-buster
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31017
Modified Files:
jargon-buster-en.xml
Log Message:
Finished new round of editing, next up are additions...
Index: jargon-buster-en.xml
===================================================================
RCS file: /cvs/docs/jargon-buster/jargon-buster-en.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- jargon-buster-en.xml 30 Aug 2005 21:33:36 -0000 1.7
+++ jargon-buster-en.xml 4 Sep 2005 13:52:20 -0000 1.8
@@ -141,7 +141,7 @@
</revdescription>
</revision>
<revision>
- <revnumber>1.9</revnumber>
+ <revnumber>1.9.1</revnumber>
<date>30 Sept 2004</date>
<authorinitials>PaulWFrields,TammyFox</authorinitials>
<revdescription>
@@ -151,7 +151,7 @@
</revdescription>
</revision>
<revision>
- <revnumber>1.9.1</revnumber>
+ <revnumber>1.9.1.1</revnumber>
<date>17 Aug 2005</date>
<authorinitials>PaulWFrields</authorinitials>
<revdescription>
@@ -324,7 +324,6 @@
accurate. However, many users simply call the updated
system "&FC;."
</para>
- <glossseealso otherterm="names">&RHL; Names</glossseealso>
</glossdef>
</glossentry>
<glossentry id="gl-jb-cpu">
@@ -668,6 +667,17 @@
</para>
</glossdef>
</glossentry>
+ <glossentry id="gl-jb-inkscape">
+ <glossterm>Inkscape</glossterm>
+ <glossdef>
+ <para>
+ Inkscape is a vector graphics illustration program. It uses
+ SVG as the default file format. For more information about
+ Inkscape, refer to <ulink url="http://www.inkscape.org/"/>.
+ </para>
+ <glossseealso otherterm="gl-jb-sodipodi"/>
+ </glossdef>
+ </glossentry>
<glossentry id="gl-jb-irc">
<glossterm>IRC</glossterm>
<glossdef>
@@ -841,6 +851,18 @@
</para>
</glossdef>
</glossentry>
+ <glossentry id="gl-jb-mirror">
+ <glossterm>mirror</glossterm>
+ <glossdef>
+ <para>
+ A mirror is a complete copy of an online resource. System
+ administrators of computers connected to the Internet often
+ create and provide mirrors for public use. If a resource
+ has one or more mirrors, many more users can access its
+ content without overloading the original resource.
+ </para>
+ </glossdef>
+ </glossentry>
<glossentry id="gl-jb-mount">
<glossterm>mount</glossterm>
<glossdef>
@@ -888,142 +910,103 @@
<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>
+ The <xref linkend="gl-jb-gnome"/> desktop environment
+ includes a file manager called Nautilus which provides a
+ graphical display of your system and personal files.
+ Nautilus also allows you to configure your desktop and
+ &FED;, browse your photo collection, access your network
+ resources, and more, all from an integrated interface. In
+ essence, Nautilus becomes a shell for your entire desktop
+ experience. <remark role="FIXME">Insert link to Nautilus
+ resource here.</remark>
</para>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gl-jb-package">
<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="gl-jb-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>
+ Users often refer to a <xref linkend="gl-jb-rpm"/> file as a
+ <firstterm>package</firstterm>.
+ </para>
+ <glossseealso otherterm="gl-jb-rpm"/>
</glossdef>
</glossentry>
- <glossentry>
- <glossterm>Psyche</glossterm>
+ <glossentry id="gl-jb-pine">
+ <glossterm>Pine</glossterm>
<glossdef>
<para>
- The name given to &RHL; 8
+ <acronym>Pine</acronym>, short for a Program for Internet
+ News and Email, is a tool for reading, sending, and managing
+ electronic messages. Refer to <ulink
+ url="http://www.washington.edu/pine/"/> for more information
+ about <command>Pine</command>.
</para>
- <glossseealso otherterm="names">&RHL; Names</glossseealso>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gl-jb-rawhide">
<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.).
+ Rawhide is a package repository which contains the latest
+ development versions of packages which will eventually be
+ included in &FED;. These latest versions are sometimes
+ called "bleeding edge" <xref
+ linkend="gl-jb-package"/>, since they often
+ include new and untested technology. You should consider
+ the Rawhide repository "unstable," since any Rawhide package
+ <emphasis>might</emphasis> be badly broken if the
+ programmers are trying to add, change, or test features. If
+ you want to develop programs for &FED;, you may want to
+ install a system from Rawhide. If you only want to use a
+ stable &FED; system, you should use the standard &FC;
+ distribution instead.
</para>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gl-jb-rhel">
<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.
+ Red Hat Enterprise Linux, or <acronym>&RHEL;</acronym>, is
+ the premiere operating system for open source computing.
+ &RHEL; runs on many system architectures, is certified by
+ top enterprise software and hardware vendors, and is backed
+ by a &RHN; subscription and up to 24x7 support with one-hour
+ response. Refer to <ulink
+ url="http://www.redhat.com/software/rhel/"/> for more
+ information about &RHEL;.
</para>
</glossdef>
</glossentry>
- <glossentry id="rhconfpkg">
+ <glossentry id="gl-jb-redhat-config-packages">
<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
+ The <application>redhat-config-packages</application>
+ utility is a package installation for new &FC; systems which
+ have no software updates installed yet. Since most
+ administrators and users update their system software
+ regularly, <application>redhat-config-packages</application>
+ is not often used. Users should instead use the <xref
+ linkend="gl-jb-yum"/> utility to install new software.
</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;
+ <glossterm>rhgb</glossterm>
+ <glossdef>
+ <para>
+ &RH; Graphical Boot, or
+ <application><acronym>rhgb</acronym></application>, is an
+ optional component of the boot process. The
+ <application>rhgb</application> application produces a boot
+ screen with a progress bar and fewer technical messages.
+ The <application>rhgb</application> application allows you
+ to click a link to see the technical boot messages if
+ desired. Systems that have been upgraded from &RHL; to &FC;
+ are not configured to include
+ <application>rhgb</application>.
</para>
</glossdef>
</glossentry>
@@ -1031,9 +1014,13 @@
<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.
+ The <application>rhn-applet</application> utility was
+ originally designed for use with &RHEL; and Red Hat Network.
+ It provides a notification and user interface for system
+ updates using <xref linkend="gl-jb-up2date"/>. It allows
+ the user to retrieve and install system updates, but this
+ usage is no longer recommended. Users should use <xref
+ linkend="gl-jb-yum"/> for system updates instead.
</para>
</glossdef>
</glossentry>
@@ -1041,179 +1028,118 @@
<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.
+ <acronym>RPM</acronym> stands for RPM Package Manager. RPM
+ is a robust database system for maintaining software on
+ &FED; systems. Software packaged for &FED; is distributed
+ in special package files called RPM files, or RPMs. System
+ owners use the <command>rpm</command> utility to query the
+ RPM database for information about installed software.
+ Although some administrators use <command>rpm</command> to
+ install, update, and remove software, it is recommended that
+ you use <command>yum</command> for these purposes.
</para>
</glossdef>
</glossentry>
- <glossentry>
- <glossterm>Rsync</glossterm>
+ <glossentry id="gl-jb-rsync">
+ <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>
+ The <command>rsync</command> provides fast incremental file
+ transfers. Administrators frequently use
+ <command>rsync</command> to create a <xref
+ linkend="gl-jb-mirror"/> of an online resource. Refer to
+ <ulink url="http://samba.anu.edu.au/rsync/"/> for more
+ information about <command>rsync</command>.
</para>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gl-jb-selinux">
<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
+ SELinux is a set of extensions to the Linux <xref
+ linkend="gl-jb-kernel"/> that provide extremely strong
+ security. SELinux is based on role definitions, and allows
+ very granular control over access to system resources based
+ on those roles. These security measures limit the risk
+ associated with computer intrusions by unauthorized persons.
+ For more information about SELinux, refer to <ulink
+ url="http://www.nsa.gov/selinux/"/> and <ulink
+ url="http://fedora.redhat.com/docs/selinux-faq"/>.
</para>
- <glossseealso otherterm="names">&RHL; Names</glossseealso>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gl-jb-sodipodi">
<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>
+ Sodipodi is a vector graphics illustration application. It
+ uses W3C SVG as its default format. Refer to <ulink
+ url="http://sourceforge.net/projects/sodipodi/"/> for more
+ information.
</para>
+ <glossseealso otherterm="gl-jb-inkscape"/>
</glossdef>
</glossentry>
- <glossentry>
- <glossterm>SRPMs</glossterm>
+ <glossentry id="gl-jb-srpm">
+ <glossterm>SRPM</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.
+ A source <xref linkend="gl-jb-rpm"/>, or
+ <acronym>SRPM</acronym>, contains the source code for a
+ <xref linkend="gl-jb-rpm"/> package. If you want to read or
+ modify a program's source, use its SRPM. You do not need any
+ SRPMs to install or use software.
</para>
<glossseealso otherterm="gl-jb-rpm">RPM</glossseealso>
</glossdef>
</glossentry>
- <glossentry>
- <glossterm>Tettnang</glossterm>
+ <glossentry id="gl-jb-up2date">
+ <glossterm>up2date</glossterm>
<glossdef>
<para>
- "Tettnang" is the second release (version 2) of Fedora Core.
+ The <application>up2date</application> application is a
+ complete system for managing and updating software on &RHEL;
+ and &FED; systems. It has both command line and gui
+ modes. The <application>up2date</application> application is
+ no longer recommended for software management, since it has
+ been superseded by <command>yum</command>. Refer to <ulink
+ url="http://fedora.redhat.com/docs/yum/"/> for more
+ information on managing software on your &FED; system.
</para>
- <glossseealso otherterm="names">&RHL; Names</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 id="gl-jb-vino">
+ <glossterm>vino</glossterm>
+ <glossdef>
+ <para>
+ The <command>vino</command> utility is a variant of <xref
+ linkend="gl-jb-vnc"/> used in &FC; 4 and beyond.
+ </para>
+ </glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gl-jb-vnc">
<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>
+ <application>VNC</application> stands for Virtual Network
+ Computing. It is remote control software which allows you to
+ view and interact with another computer over the network.
+ Refer to <ulink url="http://www.realvnc.com/"/> for more
+ information about VNC.
</para>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gl-jb-xfs">
<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
+ SGI's IRIX operating system. It is also available for &FED;
+ systems.. It is extremely scalable and has a journalling
+ capability to protect against corruption. Refer to <ulink
+ url="http://oss.sgi.com/projects/xfs/faq.html#whatisxfs"/>
+ for more information about XFS.
</para>
</glossdef>
</glossentry>
@@ -1221,68 +1147,31 @@
<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
+ The X Window System, or simply "X," is the underlying
+ technology for GNOME, KDE, and other graphical environments
+ used in &FED;. X is a network-based system for displaying
+ and communicating graphical input and output. It is very
+ flexible and is suitable for a wide variety of
+ configurations such as remote desktops and thin-client
+ applications.
</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>
</glossdef>
</glossentry>
<glossentry id="gl-jb-yum">
- <glossterm>Yum</glossterm>
+ <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>
+ The Yellow Dog Updater, or <acronym>yum</acronym>, is a
+ complete software management utility for RPM-based systems
+ such as &FED;. It automatically determines software
+ requirements, or <firstterm>dependencies</firstterm>, and
+ uses this data to install, update, or remove packages.
+ Refer to <ulink
+ url="http://linux.duke.edu/projects/yum/"/> for more
+ information about <command>yum</command>.
</para>
</glossdef>
</glossentry>
-<!--
-
-
-
-
-<glossentry>
- <glossterm></glossterm>
-<glossdef>
- <para> </para>
-</glossdef>
-</glossentry>
-
-<glossentry>
- <glossterm></glossterm>
-<glossdef>
- <para> </para>
-</glossdef>
-</glossentry>
-
-
-
-
--->
</glossdiv>
</glossary>
</article>
18 years, 7 months