[rpm-guide] Update/cleanup of chapter
Ben Cotton
bcotton at fedoraproject.org
Thu Oct 21 01:07:42 UTC 2010
commit bddddcf502022069e01117916e5dddc318b2f717
Author: Ben Cotton <bcotton at fedoraproject.org>
Date: Wed Oct 20 21:08:06 2010 -0400
Update/cleanup of chapter
en-US/rpm-guide-using-rpm-db.xml | 2751 ++++++++++++--------------------------
1 files changed, 840 insertions(+), 1911 deletions(-)
---
diff --git a/en-US/rpm-guide-using-rpm-db.xml b/en-US/rpm-guide-using-rpm-db.xml
index c384824..f2d2c0b 100644
--- a/en-US/rpm-guide-using-rpm-db.xml
+++ b/en-US/rpm-guide-using-rpm-db.xml
@@ -54,71 +54,69 @@
This chapter covers querying both the RPM database and RPM package
files. Both types of query are important:
</para>
- <para>
- *Query the RPM database to see what is installed, or not installed,
- on your system.
- </para>
- <para>
- *Query package files to see what the files require, as well as what
- the files provide.
- </para>
+ <itemizedlist>
+ <listitem>Query the RPM database to see what is installed, or not installed,
+ on your system.</listitem>
+ <listitem>Query package files to see what the files require, as well as what
+ the files provide.</listitem>
+ </itemizedlist>
<para>
In addition to querying the RPM database, you can use the database
to verify packages. Since this database is so important to the
management of your Linux system, this chapter covers how to back it
up, as well as how to repair a damaged RPM database.
</para>
- <sect1>
+ <section id="RPM_Guide-Using_RPM_DB-querying_database">
<title>Querying the RPM Database</title>
<para>
In <xref linkend="ch-using-rpm"/> , you saw that the rpm command usually takes one major
command-line option to tell it the operation to perform and a
myriad of command-line options to customize the operation. The rpm
command may also take the name of one or more RPM package files or
- the name of one or more installed packages. For example, the rpm
- –i command performs an installation operation, and the rpm –U
+ the name of one or more installed packages. For example, the <command>rpm
+ –i</command> command performs an installation operation, and the <command>rpm –U</command>
command performs an upgrade.
</para>
<para>
For querying the RPM database, the major command-line option is
- –q, short for query. This option tells the rpm command to query
- the RPM database. You can also use the long option --query.
+ <literal>–q</literal>, short for query. This option tells the rpm command to query
+ the RPM database. You can also use the long option <literal>--query</literal>.
</para>
<para>
- In the last few chapters, you've used the –q option with the rpm
+ In the last few chapters, you've used the <literal>–q</literal> option with the rpm
command to query just for the presence or absence of installed
- packages. You can expand the -q option to perform a wide array of
+ packages. You can expand the <literal>-q</literal> option to perform a wide array of
queries to find out information about the packages installed on a
Linux system.
</para>
- <sect2>
+ <section>
<title>Querying packages</title>
<para>
- The basic format of the rpm –q command follows:
+ The basic format of the <command>rpm –q<command> command follows:
</para>
<para>
- rpm –q package_name
+ <command>rpm –q <replaceable>package_name</replaceable></command>
</para>
<para>
You need to provide the name of a package to query. For example:
</para>
<para>
- rpm -q telnet-0.17
+ <command>rpm -q telnet-0.17</command>
</para>
<para>
This command returns the name of the package, if installed. For
example:
</para>
- <para>
+ <screen>
telnet-0.17-20
- </para>
+ </screen>
<para>
If the package is not installed, you’ll see a message like the
following:
</para>
- <para>
+ <screen>
package telnet-0.17 is not installed
- </para>
+ </screen>
<para>
You can provide the whole package name to the rpm command, which
includes the name, the version, and the RPM package number, as
@@ -131,53 +129,50 @@
the package:
</para>
<para>
- $ rpm -q telnet
+ <command>rpm -q telnet</command>
</para>
- <para>
+ <screen>
telnet-0.17-20
- </para>
- <para>
- Note
- </para>
- <para>
- The rpm –q command expects a package name. Although it
- supports some amount of customized queries, you really need to
- know which packages you want the rpm command to report on.
- </para>
+ </screen>
+ <important>
+ <para>
+ The rpm –q command expects a package name. Although it
+ supports some amount of customized queries, you really need to
+ know which packages you want the rpm command to report on.
+ </para>
+ </important>
<para>
You can provide more than one package name; the rpm command
reports on each package, as shown following.
</para>
<para>
- $ rpm -q telnet telnet-server
+ <command>rpm -q telnet telnet-server</command>
</para>
- <para>
+ <screen>
telnet-0.17-20
- </para>
- <para>
telnet-server-0.17-20
- </para>
- <para/>
+ </screen>
<para>
You need to change the way you query if you want to perform
searches when you do not know the full package name in advance.
The following sections cover options for creating various
queries.
</para>
- </sect2>
- <sect2>
+ </section>
+
+ <section id="RPM_Guide-Using_RPM_DB-query_everything">
<title>Querying everything</title>
<para>
Up to now, we have used the rpm command to query only for
- specific packages. The –a option tells the rpm command to
+ specific packages. The <literal>–a</literal> option tells the rpm command to
query for all packages. You can also use the longer option,
- --all, in place of –a.
+ <literal>--all</literal>, in place of <literal>–a</literal>.
</para>
<para>
For example:
</para>
<para>
- rpm -qa
+ <command>rpm -qa</command>
</para>
<para>
This command returns every package installed on your system,
@@ -185,84 +180,27 @@
shown following.
</para>
<para>
- words-2-17
- </para>
- <para>
- kudzu-0.99.23-1
- </para>
- <para>
- openldap-2.0.11-13
- </para>
- <para>
- rpm-4.0.3-1.03
- </para>
- <para>
- kernel-smp-2.4.7-10
- </para>
- <para>
- quota-3.01pre9-3
- </para>
- <para>
- expat-1.95.1-7
- </para>
- <para>
- groff-perl-1.17.2-3
- </para>
- <para>
- perl-DateManip-5.39-5
- </para>
- <para>
- perl-libnet-1.0703-6
- </para>
- <para>
- perl-URI-1.12-5
- </para>
- <para>
- perl-XML-Parser-2.30-7
- </para>
- <para>
- perl-XML-Twig-2.02-2
- </para>
- <para>
- a2ps-4.13b-15
- </para>
- <para>
- 4Suite-0.11-2
- </para>
- <para>
- XFree86-xfs-4.1.0-3
- </para>
- <para>
- ghostscript-6.51-12
- </para>
- <para>
- tcl-8.3.3-65
- </para>
- <para>
- portmap-4.0-38
- </para>
- <para>
- bind-utils-9.1.3-4
- </para>
- <para>
- ftp-0.17-12
- </para>
- <para>
- micq-0.4.6.p1-2
- </para>
- <para>
- Note
+<screen>m17n-db-gujarati-1.5.5-4.fc13.noarch
+libvisual-0.4.0-9.fc12.x86_64
+hal-filesystem-0.5.14-3.fc13.x86_64
+fedora-logos-13.0.2-1.fc13.noarch
+kdepim-runtime-libs-4.4.5-1.fc13.x86_64
+lpsolve-5.5.0.15-3.fc13.x86_64
+kipi-plugins-1.2.0-1.fc13.x86_64
+kbd-1.15-9.fc12.x86_64
+perl-Glib-1.201-4.fc12.x86_64
+kdeplasma-addons-4.4.5-1.fc13.x86_64</screen>
</para>
<para>
This output has been modified to meet size constraints. Try the
- rpm –qa command to see the full output for your system.
+ <command>rpm –qa</command> command to see the full output for your system.
</para>
<para>
There may be over a thousand packages on your system. Even so,
- the rpm –qa command executes surprisingly fast.
+ the <command>rpm –qa</command> command executes surprisingly fast.
</para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-refining_query">
<title>Refining the query</title>
<para>
When you query all the installed packages, you get too much
@@ -275,121 +213,55 @@
You can take advantage of the power of the Linux shells, though,
and the wonderful ability to pipe the output of one command into
another to work around this problem. With the large amount of
- output, you may want to pipe the output to the more or less
- programs, and display the output one page at a time.
+ output, you may want to pipe the output to the <command>more</command>
+ or <command>less</command> programs, and display the output one page at a time.
</para>
<para>
- Cross Reference
- </para>
- <para>
- For more information on the more or less commands, view the
- online manuals with the man more and man less commands.
- </para>
- <para>
- Even with more and less, the rpm –qa command outputs too much
+ Even with <command>more</command> and <command>less</command>, the
+ <command>rpm –qa</command> command outputs too much
information to be really useful, unless you can somehow filter
the information automatically.
</para>
- <sect3>
+ <section id="RPM_Guide-Using_RPM_DB-refining-grep">
<title>Piping the Output To grep</title>
<para>
- The Linux (and Unix) grep command provides a powerful tool for
- filtering through lots of textual data. If you pipe the output
- of the rpm –qa command into the grep command, you have a
- powerful search engine—Linux--at your fingertips.
+ The Linux (and Unix) <command>grep</command> command provides a powerful tool for
+ filtering through textual data. If you pipe the output of the
+ <command>rpm –qa</command> command into the <command>grep</command> command, you have a
+ powerful search engine at your fingertips.
</para>
<para>
- For example, if you know that most packages that use the
- Python scripting language have a py in their names, you can
- find all these packages by using a command like the following:
+ For example, if you know that most packages that provide tools for the SSH service have
+ "ssh" in their names, you can find all these packages by using a command like the following:
</para>
<para>
- rpm -qa | grep py
+ <command>rpm -qa | grep ssh</command>
</para>
<para>
This command outputs packages such as the following:
</para>
- <para>
- python-2.2.1-17
- </para>
- <para>
- pygtk2-1.99.12-7
- </para>
- <para>
- pyxf86config-0.3.1-2
- </para>
- <para>
- rpm404-python-4.0.4-8x.27
- </para>
- <para>
- python-devel-2.2.1-17
- </para>
- <para>
- gnome-python2-gtkhtml2-1.99.11-8
- </para>
- <para>
- orbit-python-1.99.0-4
- </para>
- <para>
- gnome-python2-canvas-1.99.11-8
- </para>
- <para>
- gnome-python2-bonobo-1.99.11-8
- </para>
- <para>
- gnome-python2-1.99.11-8
- </para>
- <para>
- pyOpenSSL-0.5.0.91-1
- </para>
- <para>
- rpm-python-4.1-1.06
- </para>
- <para>
- pygtk2-devel-1.99.12-7
- </para>
- <para>
- kdesdk-kspy-3.0.3-2
- </para>
- <para>
- mod_python-3.0.0-10
- </para>
- <para>
- gnome-python2-gconf-1.99.11-8
- </para>
- <para>
- libxslt-python-1.0.19-1
- </para>
- <para>
- python-tools-2.2.1-17
- </para>
- <para>
- libxml2-python-2.4.23-1
- </para>
- <para>
- pygtk2-libglade-1.99.12-7
- </para>
- <para>
- python-optik-1.3-2
- </para>
- <para>
- kfloppy-3.0.3-3
- </para>
+ <screen>ksshaskpass-0.5.3-1.fc13.x86_64
+openssh-server-5.4p1-3.fc13.x86_64
+libssh2-1.2.4-1.fc13.i686
+openssh-askpass-5.4p1-3.fc13.x86_64
+libssh2-1.2.4-1.fc13.x86_64
+openssh-5.4p1-3.fc13.x86_64
+openssh-clients-5.4p1-3.fc13.x86_64
+libssh-0.4.4-1.fc13.x86_64</screen>
<para>
You can also use the --pipe option to the rpm command,
introduced in <xref linkend="ch-using-rpm"/> . With this option, your command
becomes:
</para>
<para>
- rpm -qa --pipe "grep py"
- </para>
- <para>
- Cross Reference
+ <command>rpm -qa --pipe "grep ssh"</command>
</para>
+ <note>
<para>
<xref linkend="ch-rpm-programming-python"/> covers programming with the RPM system with the
Python scripting language.
</para>
+ </note>
<para>
You can take advantage of some of the options that the grep
command supports, including -i for ignoring the case of the
@@ -397,15 +269,13 @@
grep, and -v, to output only those entries that do not match
the search string.
</para>
- <para>
- Cross Reference
- </para>
- <para>
- If you are unfamiliar with grep, the online manual pages for
+ <note>
+ <para>If you are unfamiliar with grep, the online manual pages for
the grep command provide a listing of the command-line options
available for grep as well as a short tutorial on regular
- expressions supported by grep.
- </para>
+ expressions supported by grep.</para>
+ </note>
+
<para>
Table 5-1 lists some of the common package-naming conventions.
Remember that these are just conventions, not hard-and-fast
@@ -533,35 +403,33 @@
</tbody>
</tgroup>
</informaltable>
- </sect3>
- <sect3>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-refining-wildcards">
<title>Querying with Wildcards</title>
<para>
In addition to using other Linux commands, the rpm command
- supports some search options. You can pass a wildcard to rpm
- –qa (but not just rpm –q, you need the –a to look for
+ supports some search options. You can pass a wildcard to <command>rpm –qa</command>
+ (but not just <command>rpm –q</command>, you need the <literal>–a</literal> to look for
all packages). For example:
</para>
<para>
- $ rpm -qa "send*"
- </para>
- <para>
- sendmail-cf-8.11.6-3
- </para>
- <para>
- sendmail-8.11.6-3
- </para>
- <para>
- Note
+ <command>rpm -qa "kernel*"</command>
</para>
- <para>
- The quotation marks around "send*" are to prevent the Linux
+ <screen>kernel-2.6.33.6-147.fc13.x86_64
+kernel-2.6.33.5-112.fc13.x86_64
+kernel-devel-2.6.33.5-112.fc13.x86_64
+kernel-headers-2.6.33.6-147.fc13.x86_64
+kernel-2.6.33.5-124.fc13.x86_64
+kernel-devel-2.6.33.5-124.fc13.x86_64
+kernel-devel-2.6.33.6-147.fc13.x86_64</screen>
+ <important>
+ <para>The quotation marks around "kernel*" are to prevent the Linux
shell from expanding the wildcard character, *, to try to
match a list of file names in the local directory. By passing
- the command-line parameter as "send*", the rpm program gets to
+ the command-line parameter as "kernel*", the rpm program gets to
see the * character. Otherwise, the shell expands the
- parameter and the program, rpm in this case, never sees the *.
- </para>
+ parameter and the program, rpm in this case, never sees the *.</para>
+ </important>
<para>
This command searches for all package names starting with
send. You can reverse this with an exclamation mark. For
@@ -571,29 +439,21 @@
$ rpm -qa '!send*'
</para>
<para>
- This command works sort of like grep –v and searches for all
- packages that do not start with send.
+ This command works sort of like <command>grep –v</command> and
+ searches for all packages that do not start with "send".
</para>
<para>
There are quite a few other Linux commands you can use in
- pipelines with the rpm –qa command to better filter and
- display the data, such as wc –l to count the number of
+ pipelines with the <command>rpm –qa</command> command to
+ better filter and display the data, such as <command>wc –l</command>
+ to count the number of
packages that you query. You can also use a number of other
query options to find out more specialized information from
the RPM database.
</para>
- <para>
- Cross Reference
- </para>
- <para>
- If you aren’t familiar with grep or other Linux commands,
- pick up a Linux tutorial such as (insert shameless plug) Teach
- Yourself Linux by Steve Oualline and Eric Foster-Johnson,
- available from Wiley Publishing, Inc.
- </para>
- </sect3>
- </sect2>
- <sect2>
+ </section>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-which_package">
<title>Finding which packages own files</title>
<para>
One of the common problems with package management comes when
@@ -602,12 +462,13 @@
when installed, installed the particular file).
</para>
<para>
- The -qf option tells the rpm command to query for all packages
+ The <option>-qf</option> option tells the rpm command to query for all packages
that own a particular file. You can also use the longer option,
- --file, in place of –f. The basic syntax follows:
+ <option>--file</option>, in place of <option>–f</option>.
+ The basic syntax follows:
</para>
<para>
- rpm -qf filename
+ <command>rpm -qf <replaceable>filename</replaceable></command>
</para>
<para>
For example, the grep command used in previous examples is
@@ -618,65 +479,61 @@
</para>
<para>
First, we need the exact path to the file. For Linux commands,
- you can use the which command, if the program is in your path.
- (The grep program must be in your path, or commands with grep
- will fail.)
+ you can use the <command>which<command> command, if the program
+ is in your path. (The grep program must be in your path, or
+ commands with grep will fail.)
</para>
<para>
Try the following command:
</para>
<para>
- which grep
+ <command>which grep</command>
</para>
<para>
This command returns the path to grep:
</para>
<para>
- /bin/grep
+ <screen>/bin/grep</screen>
</para>
<para>
We can now check which package owns this file with the following
command:
</para>
<para>
- # rpm -qf /bin/grep
+ <command>rpm -qf /bin/grep</command>
</para>
<para>
- grep-2.4.2-7
+ <screen>grep-2.6.3-1</screen>
</para>
<para>
You can also use the Linux back-tick operator to perform this
check with one command.
</para>
<para>
- # rpm -qf `which grep`
- </para>
- <para>
- grep-2.4.2-7
+ <command>rpm -qf `which grep`</command>
</para>
<para>
- Production: note use of back-quote, `, above. Don’t change to
- “smart quotes” please. -Eric
+ <screen>grep-2.6.3-1</screen>
</para>
<para>
If you use the bash shell, you can use the $(command parameters)
syntax in place of the back tick, or `, characters. For example:
</para>
<para>
- # rpm -qf $(which grep)
+ <command>rpm -qf $(which grep)</command>
</para>
<para>
- grep-2.4.2-7
+ <screen>grep-2.6.3-1</screen>
</para>
<para>
If no package owns a given file, you’ll see output like the
following:
</para>
<para>
- # rpm -qf mail
+ <command>rpm -qf mail</command>
</para>
<para>
- file mail is not owned by any package
+ <screen>file mail is not owned by any package</screen>
</para>
<para>
Often, the package that owns a file does not have an intuitive
@@ -684,45 +541,44 @@
openssh-clients package, as shown following:
</para>
<para>
- # rpm -qf `which ssh`
+ <command>rpm -qf `which ssh`</command>
</para>
<para>
- openssh-clients-3.1p1-2
+ <screen>openssh-clients-5.4p1-3</screen>
</para>
<para>
As you can see, the name of a command does not always correspond
directly to the name of the package that provides that command.
- This is where the rpm –qf command proves very useful.
+ This is where the <command>rpm –qf</command> command proves very useful.
Otherwise, you would just have to know that OpenSSH is the
project responsible for this command.
</para>
- <para>
- Symbolic Links
- </para>
- <para>
- The rpm -qf command follows symbolic links. This was not always
- true with older versions of the rpm command, but the modern rpm
- command can now trace package ownership to files placed in
- linked directories.
- </para>
- <para>
- For example, the directory /usr/lib/X11 is a link to the real
- directory, /usr/X11R6/lib/X11. You can track the package
- ownership of a file in that directory, XKeysymDB, for example,
- by using the following command:
- </para>
- <para>
- # rpm -qf /usr/lib/X11/XKeysymDB
- </para>
- <para>
- XFree86-4.2.0-72
- </para>
- <para>
- This file, XKeysymDB, really resides in /usr/X11R6/lib/X11.
- </para>
- </sect2>
- </sect1>
- <sect1>
+ <note>
+ <title>Symbolic Links</title>
+ <para>
+ The <command>rpm -qf</command> command follows symbolic links. This
+ was not always true with older versions of RPM, but modern RPM versions
+ can trace package ownership to files placed in linked directories.
+ </para>
+ <para>
+ For example, the directory /usr/lib/X11 is a link to the real
+ directory, /usr/X11R6/lib/X11. You can track the package
+ ownership of a file in that directory, XKeysymDB, for example,
+ by using the following command:
+ </para>
+ <para>
+ <command>rpm -qf /usr/lib/X11/XKeysymDB</command>
+ </para>
+ <para>
+ <screen>XFree86-4.2.0-72</screen>
+ </para>
+ <para>
+ This file, XKeysymDB, really resides in /usr/X11R6/lib/X11.
+ </para>
+ </note>
+ </section>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-getting_information">
<title>Getting Information on Packages</title>
<para>
The query options for the rpm command include a whole set of
@@ -730,33 +586,33 @@
package, the scripts, and other parts of the original package. The
following sections cover these options.
</para>
- <sect2>
+ <section id="RPM_Guide-USing_RPM_DB-getting_information-describing_packages">
<title>Describing packages</title>
<para>
- The –i option with an rpm query command tells the rpm command
+ The <option>–i</option> option with an rpm query command tells the rpm command
to output descriptive information about the package. You can
- also use the longer option, --info, in place of –i. The basic
- syntax is:
+ also use the longer option, <option>--info</option>, in place of
+ <option>–i</option>. The basic syntax is:
</para>
<para>
- rpm -qi package
- </para>
- <para>
- Warning
+ <command>rpm -qi <replaceable>package</replaceable></command>
</para>
+ <warning>
+ <title>Warning</title>
<para>
The order of the command-line options is very important.
Remember that the rpm command has the following general syntax:
</para>
<para>
- rpm –MajorOperation –extra_options packages_or_files
+ <command>rpm <replaceable>–MajorOperation</replaceable>
+ <replaceable>–extra_options packages_or_files</replaceable></command>
</para>
<para>
- The rpm –i command installs packages. The rpm –q command
- queries packages. The rpm –qi command outputs the descriptive
- information on packages. If you make a mistake and place the i
- in front of the q, you are telling the rpm command to perform a
- different operation.
+ <command>rpm –i</command> installs packages and <command>rpm –q</command>
+ queries packages. The <command>rpm –qi</command> command outputs
+ the descriptive information on packages. If you make a mistake
+ and place the <literal>i</literal> in front of the <literal>q</literal>,
+ you are telling the rpm command to perform a different operation.
</para>
<para>
When you run this command, being very careful with the order of
@@ -764,132 +620,71 @@
describes the tcsh shell package.
</para>
<para>
- # rpm -qi tcsh-6.10-6
- </para>
- <para>
- Name : tcsh Relocations: (not relocateable)
- </para>
- <para>
- Version : 6.10 Vendor: Red Hat, Inc.
- </para>
- <para>
- Release : 6 Build Date: Sun 24 Jun 2001 10:45:29
- </para>
- <para>
- PM CDT
- </para>
- <para>
- Install date: Fri 14 Dec 2001 10:45:39 AM CST Build
- </para>
- <para>
- Host: porky.devel.redhat.com
- </para>
- <para>
- Group : System Environment/Shells Source RPM:
- tcsh-6.10-6.src.rpm
- </para>
- <para>
- Size : 764000 License: distributable
- </para>
- <para>
- Packager : Red Hat, Inc.
- <http://bugzilla.redhat.com/bugzilla>
- </para>
- <para>
- URL : http://www.primate.wisc.edu/software/csh-tcsh-book/
- </para>
- <para>
- Summary : An enhanced version of csh, the C shell.
- </para>
- <para>
- Description :
- </para>
- <para>
- Tcsh is an enhanced but completely compatible version of csh,
- the C
- </para>
- <para>
- shell. Tcsh is a command language interpreter which can be used
- both
- </para>
- <para>
- as an interactive login shell and as a shell script command
- processor.
- </para>
- <para>
- Tcsh includes a command line editor, programmable word
- completion,
- </para>
- <para>
- spelling correction, a history mechanism, job control and a C
- language
- </para>
- <para>
- like syntax.
- </para>
- <para>
- From this description, you can find out a lot about a package,
- such as where it comes from. Note how the description also names
- the source RPM used to build the package programs.
- </para>
- <para>
- Cross Reference
- </para>
+ <command>rpm -qi tcsh-6.17-6</command>
+ </para>
+ <screen>Name : tcsh Relocations: (not relocateable)
+Version : 6.17 Vendor: Fedora Project
+Release : 6 Build Date: Tue 15 Dec 2009 11:28:11 AM EST
+Install Date: Fri 27 Aug 2010 07:41:03 PM EDT Build Host: localhost
+Group : System Environment/Shells Source RPM: tcsh-6.17-6.fc13.src.rpm
+Size : 1191282 License: BSD
+Signature : RSA/SHA256, Fri 05 Feb 2010 09:30:43 AM EST, Key ID 7edc6ad6e8e40fde
+Packager : Fedora Project
+URL : http://www.tcsh.org/
+Summary : An enhanced version of csh, the C shell
+Description :
+Tcsh is an enhanced but completely compatible version of csh, the C
+shell. Tcsh is a command language interpreter which can be used both
+as an interactive login shell and as a shell script command processor.
+Tcsh includes a command line editor, programmable word completion,
+spelling correction, a history mechanism, job control and a C language
+like syntax.</screen>
<para>
The sections on custom queries following in this chapter show
how you can query for any information stored in a package
- header, including all of the information shown with the rpm
- –qi command, as well as any other header tag.
+ header, including all of the information shown with <command>rpm
+ –qi</command>, as well as any other header tag.
</para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-package_groups">
<title>Package groups</title>
<para>
RPM packages can be placed into groups, merely arbitrary names
- for a set of packages. The rpm –qi command, shown previously,
- lists the group for a package, if there is one. For the tcsh
- package shown in the previous example, the package is System
- Environment/Shells.
+ for a set of packages. The <command>rpm –qi</command> command,
+ shown previously, lists the group for a package, if there is one.
+ For the tcsh package shown in the previous example, the package is
+ <literal>System Environment/Shells</literal>.
</para>
<para>
- The –g option to the rpm –q command tells the rpm command to
- list all the packages in a given group. You can also use the
- longer option, --group, in place of –g. The basic syntax
- follows:
+ The <option>–g</option> option to <command>rpm –q</command> tells rpm
+ to list all the packages in a given group. You can also use the
+ longer option, <option>--group</option>, in place of <option>–g</option>.
+ The basic syntax follows:
</para>
<para>
- rpm –qg group_name
+ <command>rpm –qg <replaceable>group_name</replaceable></command>
</para>
<para>
For example:
</para>
<para>
- # rpm -qg "System Environment/Shells"
- </para>
- <para>
- bash-2.05b-5
- </para>
- <para>
- sh-utils-2.0.12-3
- </para>
- <para>
- ash-0.3.8-5
+ <command>rpm -qg "System Environment/Shells"</command>
</para>
- <para>
- tcsh-6.12-2
- </para>
- <para>
- Note
- </para>
- <para>
- This group has a space in its name, so you need quotation marks
- to pass the group name as one parameter to the rpm command.
- </para>
- </sect2>
- <sect2>
+ <screen>dash-0.5.5.1-3.x86_64
+bash-4.1.7-1.x86_64
+tcsh-6.17-6.x86_64</screen>
+ <note>
+ <title>Spaces in group names</title>
+ <para>
+ This group has a space in its name, so you need quotation marks
+ to pass the group name as one parameter to the rpm command.
+ </para>
+ </note>
+ </section>
+ <section>
<title>Listing the files in a package</title>
<para>
- The –l (ell) option queries all the files in a package. You
+ The <option>–l</option> (ell) option queries all the files in a package. You
can also use the longer option, --list, in place of –l. The
basic syntax is:
</para>
@@ -901,286 +696,137 @@
see the following:
</para>
<para>
- # rpm -ql tcsh
+ <command>rpm -ql tcsh</command>
</para>
- <para>
+ <screen>
/bin/csh
- </para>
- <para>
/bin/tcsh
- </para>
- <para>
/usr/share/doc/tcsh-6.10
- </para>
- <para>
/usr/share/doc/tcsh-6.10/FAQ
- </para>
- <para>
/usr/share/doc/tcsh-6.10/Fixes
- </para>
- <para>
/usr/share/doc/tcsh-6.10/NewThings
- </para>
- <para>
/usr/share/doc/tcsh-6.10/complete.tcsh
- </para>
- <para>
/usr/share/doc/tcsh-6.10/eight-bit.txt
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/header.html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/index.html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/lists.html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/top.html
- </para>
- <para>
/usr/share/locale/de/LC_MESSAGES/tcsh
- </para>
- <para>
/usr/share/locale/el/LC_MESSAGES/tcsh
- </para>
- <para>
/usr/share/locale/es/LC_MESSAGES/tcsh
- </para>
- <para>
/usr/share/locale/fr/LC_MESSAGES/tcsh
- </para>
- <para>
/usr/share/locale/it/LC_MESSAGES/tcsh
- </para>
- <para>
/usr/share/locale/ja/LC_MESSAGES/tcsh
- </para>
- <para>
/usr/share/man/man1/tcsh.1.gz
- </para>
- <para>
- Note
- </para>
+ </screen>
+ <note>
+ <title>Listing multiple packages</title>
<para>
You can pass more than one package name to this option, but it
won’t tell you which package owns which file. Use the
- --filesbypkg option to list files by package (see the related
- sidebar).
- </para>
- <para>
- Listing Files By Package
- </para>
- <para>
- The --filesbypkg option outputs the files by package, so you can
- make some sense of a list of files from more than one package.
+ <option>--filesbypkg</option> option to list files by package.
</para>
<para>
For example:
</para>
<para>
- # rpm -q --filesbypkg file openssh-clients
+ <command>rpm -q --filesbypkg file openssh-clients</command>
</para>
- <para>
+ <screen>
file /usr/bin/file
- </para>
- <para>
file /usr/share/magic
- </para>
- <para>
file /usr/share/magic.mgc
- </para>
- <para>
file /usr/share/magic.mime
- </para>
- <para>
file /usr/share/man/man1/file.1.gz
- </para>
- <para>
file /usr/share/man/man5/magic.5.gz
- </para>
- <para>
openssh-clients /etc/ssh/ssh_config
- </para>
- <para>
openssh-clients /usr/bin/sftp
- </para>
- <para>
openssh-clients /usr/bin/slogin
- </para>
- <para>
openssh-clients /usr/bin/ssh
- </para>
- <para>
openssh-clients /usr/bin/ssh-add
- </para>
- <para>
openssh-clients /usr/bin/ssh-agent
- </para>
- <para>
openssh-clients /usr/bin/ssh-keyscan
- </para>
- <para>
openssh-clients /usr/share/man/man1/sftp.1.gz
- </para>
- <para>
openssh-clients /usr/share/man/man1/slogin.1.gz
- </para>
- <para>
openssh-clients /usr/share/man/man1/ssh-add.1.gz
- </para>
- <para>
openssh-clients /usr/share/man/man1/ssh-agent.1.gz
- </para>
- <para>
openssh-clients /usr/share/man/man1/ssh-keyscan.1.gz
- </para>
- <para>
openssh-clients /usr/share/man/man1/ssh.1.gz
- </para>
+ </screen>
<para>
Use this option without –l, because the –l option will also
list the files alone, without any package name.
</para>
+ </note>
<para>
The –v (verbose) option can give you more information on the
files when used with the various query options. For example:
</para>
<para>
- # rpm -qlv tcsh
- </para>
- <para>
- lrwxrwxrwx 1 root root 4 Jun 24 2001 /bin/csh -> tcsh
- </para>
- <para>
- -rwxr-xr-x 1 root root 288604 Jun 24 2001 /bin/tcsh
- </para>
- <para>
- drwxr-xr-x 2 root root 0 Jun 24 2001 /usr/share/doc/tcsh-6.10
- </para>
- <para>
- -rw-r--r-- 1 root root 8306 Aug 25 2000
- /usr/share/doc/tcsh-6.10/FAQ
- </para>
- <para>
- -rw-r--r-- 1 root root 64761 Nov 19 2000
- /usr/share/doc/tcsh-6.10/Fixes
- </para>
- <para>
- -rw-r--r-- 1 root root 6518 Oct 2 1998
- /usr/share/doc/tcsh-6.10/NewThings
- </para>
- <para>
- -rw-r--r-- 1 root root 41328 Nov 19 2000
- /usr/share/doc/tcsh-6.10/complete.tcsh
- </para>
- <para>
- -rw-r--r-- 1 root root 4668 Jun 24 2001
- /usr/share/doc/tcsh-6.10/eight-bit.txt
- </para>
- <para>
- drwxr-xr-x 2 root root 0 Jun 24 2001
- /usr/share/doc/tcsh-6.10/tcsh.html
- </para>
- <para>
- -rw-r--r-- 1 root root 124 Jun 24 2001
- /usr/share/doc/tcsh-6.10/tcsh.html/header.html
- </para>
- <para>
- lrwxrwxrwx 1 root root 8 Jun 24 2001
- /usr/share/doc/tcsh-6.10/tcsh.html/index.html -> top.html
- </para>
- <para>
- -rw-r--r-- 1 root root 911 Jun 24 2001
- /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
- </para>
- <para>
- -rw-r--r-- 1 root root 0 Jun 24 2001
- /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
- </para>
- <para>
- -rw-r--r-- 1 root root 22542 Jun 24 2001
- /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
- </para>
- <para>
- -rw-r--r-- 1 root root 693 Jun 24 2001
- /usr/share/doc/tcsh-6.10/tcsh.html/top.html
- </para>
- <para>
- -rw-r--r-- 1 root root 45861 Jun 24 2001
- /usr/share/locale/de/LC_MESSAGES/tcsh
- </para>
- <para>
- -rw-r--r-- 1 root root 47566 Jun 24 2001
- /usr/share/locale/el/LC_MESSAGES/tcsh
- </para>
- <para>
- -rw-r--r-- 1 root root 47413 Jun 24 2001
- /usr/share/locale/es/LC_MESSAGES/tcsh
- </para>
- <para>
- -rw-r--r-- 1 root root 47156 Jun 24 2001
- /usr/share/locale/fr/LC_MESSAGES/tcsh
- </para>
- <para>
- -rw-r--r-- 1 root root 48264 Jun 24 2001
- /usr/share/locale/it/LC_MESSAGES/tcsh
- </para>
- <para>
- -rw-r--r-- 1 root root 18682 Jun 24 2001
- /usr/share/locale/ja/LC_MESSAGES/tcsh
- </para>
- <para>
- -rw-r--r-- 1 root root 62399 Jun 24 2001
- /usr/share/man/man1/tcsh.1.gz
- </para>
+ <command>rpm -qlv tcsh</command>
+ </para>
+ <screen>
+lrwxrwxrwx 1 root root 4 Dec 15 2009 /bin/csh -> tcsh
+-rwxr-xr-x 1 root root 386984 Dec 15 2009 /bin/tcsh
+drwxr-xr-x 2 root root 0 Dec 15 2009 /usr/share/doc/tcsh-6.17
+-rw-r--r-- 1 root root 17782 Mar 2 2006 /usr/share/doc/tcsh-6.17/BUGS
+-rw-r--r-- 1 root root 12773 May 19 2004 /usr/share/doc/tcsh-6.17/FAQ
+-rw-r--r-- 1 root root 85246 Jul 10 2009 /usr/share/doc/tcsh-6.17/Fixes
+-rw-r--r-- 1 root root 6518 Oct 2 1998 /usr/share/doc/tcsh-6.17/NewThings
+-rw-r--r-- 1 root root 11809 May 19 2004 /usr/share/doc/tcsh-6.17/WishList
+-rw-r--r-- 1 root root 56615 Oct 1 2007 /usr/share/doc/tcsh-6.17/complete.tcsh
+-rw-r--r-- 1 root root 46682 Dec 15 2009 /usr/share/locale/de/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 48387 Dec 15 2009 /usr/share/locale/el/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45670 Dec 15 2009 /usr/share/locale/en/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 48234 Dec 15 2009 /usr/share/locale/es/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45130 Dec 15 2009 /usr/share/locale/et/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 47757 Dec 15 2009 /usr/share/locale/fi/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 47978 Dec 15 2009 /usr/share/locale/fr/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 49085 Dec 15 2009 /usr/share/locale/it/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 33848 Dec 15 2009 /usr/share/locale/ja/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45160 Dec 15 2009 /usr/share/locale/pl/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 46148 Dec 15 2009 /usr/share/locale/ru/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45492 Dec 15 2009 /usr/share/locale/uk/LC_MESSAGES/tcsh
+lrwxrwxrwx 1 root root 9 Dec 15 2009 /usr/share/man/man1/csh.1.gz -> tcsh.1.gz
+-rw-r--r-- 1 root root 63984 Dec 15 2009 /usr/share/man/man1/tcsh.1.gz
+ </screen>
<para>
This information is the same as a long listing on the files.
</para>
<para>
- As you can see, the –l option results in quite a lot of
+ As you can see, the <option>–l</option> option results in quite a lot of
output. In some cases, though, you aren’t interested in
documentation and other miscellaneous files in the package.
It’s the commands and libraries that cause the most
package-related problems. To help with this, you can use a
series of rpm options to list only certain types of files.
</para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-listing_conf_files">
<title>Listing the configuration files for a package</title>
<para>
- The –c option tells the rpm –q command to list the
+ The <option>–c</option> option tells <command>rpm –q<command> to list the
configuration files for a package. You can also use the longer
- option, --configfiles, in place of –c. The basic syntax is:
+ option, <option>--configfiles</option>, in place of <option>–c</option>.
+ The basic syntax is:
</para>
<para>
- rpm –qc package_name
+ <command>rpm –qc <replaceable>package_name</replaceable><command>
</para>
<para>
For example:
</para>
<para>
- # rpm -qc bash
+ <command>rpm -qc bash</command>
</para>
- <para>
+ <screen>
/etc/skel/.bash_logout
- </para>
- <para>
/etc/skel/.bash_profile
- </para>
- <para>
/etc/skel/.bashrc
- </para>
+ </screen>
<para>
This command lists the configuration files for the bash package.
</para>
@@ -1189,235 +835,141 @@
following:
</para>
<para>
- # rpm -qc python
- </para>
- <para>
- #
+ <command>rpm -qc python</command>
</para>
+ <screen>
+
+ </screen>
<para>
In this case, the rpm command provides no output. Other packages
have a lot of configuration files, such as the sendmail mail
transfer agent, as shown following:
</para>
<para>
- # rpm -qc sendmail
+ <command>rpm -qc sendmail</command>
</para>
- <para>
+ <screen>
/etc/aliases
- </para>
- <para>
/etc/mail/Makefile
- </para>
- <para>
/etc/mail/access
- </para>
- <para>
/etc/mail/domaintable
- </para>
- <para>
/etc/mail/helpfile
- </para>
- <para>
/etc/mail/local-host-names
- </para>
- <para>
/etc/mail/mailertable
- </para>
- <para>
/etc/mail/sendmail.mc
- </para>
- <para>
/etc/mail/statistics
- </para>
- <para>
/etc/mail/trusted-users
- </para>
- <para>
/etc/mail/virtusertable
- </para>
- <para>
/etc/rc.d/init.d/sendmail
- </para>
- <para>
/etc/sendmail.cf
- </para>
- <para>
/etc/sysconfig/sendmail
- </para>
- <para>
/usr/lib/sasl/Sendmail.conf
- </para>
- <para>
- As with the –l option, the –v option provides more
- information on each file, as shown following:
- </para>
- <para>
- #rpm -qcv bash
- </para>
- <para>
- -rw-r--r-- 1 root root 24 Jul 9 2001 /etc/skel/.bash_logout
- </para>
+ </screen>
<para>
- -rw-r--r-- 1 root root 191 Jul 9 2001 /etc/skel/.bash_profile
+ As with the <option>–l</option> option, the <option>–v</option>
+ option provides more information on each file, as shown following:
</para>
<para>
- -rw-r--r-- 1 root root 124 Jul 9 2001 /etc/skel/.bashrc
+ <command>rpm -qcv bash</command>
</para>
- </sect2>
- <sect2>
+ <screen>
+-rw-r--r-- 1 root root 18 May 21 13:32 /etc/skel/.bash_logout
+-rw-r--r-- 1 root root 176 May 21 13:32 /etc/skel/.bash_profile
+-rw-r--r-- 1 root root 124 May 21 13:32 /etc/skel/.bashrc
+ </screen>
+ </section>
+ <section>
<title>Listing the documentation files for a package</title>
<para>
- Similarly to the –c option, the –d option tells the rpm –q
- command to list just the documentation files for a package. The
- basic syntax is:
+ Similarly to the <option>–c</option> option, the <option>–d</option>
+ option tells the <command>rpm –q</command> command to list just the
+ documentation files for a package. The basic syntax is:
</para>
<para>
- rpm –qd package_name
+ <command>rpm –qd <replaceable>package_name</replaceable></command>
</para>
<para>
For example:
</para>
<para>
- # rpm -qd tcsh
+ <command>rpm -qd tcsh</command>
</para>
- <para>
+ <screen>
/usr/share/doc/tcsh-6.10/FAQ
- </para>
- <para>
/usr/share/doc/tcsh-6.10/Fixes
- </para>
- <para>
/usr/share/doc/tcsh-6.10/NewThings
- </para>
- <para>
/usr/share/doc/tcsh-6.10/complete.tcsh
- </para>
- <para>
/usr/share/doc/tcsh-6.10/eight-bit.txt
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/header.html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/index.html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/lists.html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
- </para>
- <para>
/usr/share/doc/tcsh-6.10/tcsh.html/top.html
- </para>
- <para>
/usr/share/man/man1/tcsh.1.gz
- </para>
- <para>
- Note
- </para>
- <para>
- You can add the –v option to all of the file-listing options
- to get more information.
- </para>
+ </screen>
+ <note>
+ <title>Getting more information</title>
+ <para>
+ You can add the –v option to all of the file-listing options
+ to get more information.
+ </para>
+ </note>
<para>
- You can also use the longer option, --docfiles, in place of
- –d.
+ You can also use the longer option, <option>--docfiles</option>,
+ in place of <option>–d</option>.
</para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-file_state">
<title>Listing the state of the files in a package</title>
<para>
- The –s option to the rpm –q command lists the state of each
- file in a package. The basic syntax follows.
+ The <option>–s</option> option to the <command>rpm –q</command>
+ command lists the state of each file in a package. The basic syntax is:
</para>
<para>
- rpm –qs package_name
+ <command>rpm –qs <replaceable>package_name</replaceable></command>
</para>
<para>
For example:
</para>
<para>
- # rpm -qs tcsh
+ <command>rpm -qs tcsh</command>
</para>
- <para>
+ <screen>
normal /bin/csh
- </para>
- <para>
normal /bin/tcsh
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/FAQ
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/Fixes
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/NewThings
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/complete.tcsh
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/eight-bit.txt
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/tcsh.html
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/tcsh.html/header.html
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/tcsh.html/index.html
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
- </para>
- <para>
normal /usr/share/doc/tcsh-6.10/tcsh.html/top.html
- </para>
- <para>
not installed /usr/share/locale/de/LC_MESSAGES/tcsh
- </para>
- <para>
not installed /usr/share/locale/el/LC_MESSAGES/tcsh
- </para>
- <para>
not installed /usr/share/locale/es/LC_MESSAGES/tcsh
- </para>
- <para>
not installed /usr/share/locale/fr/LC_MESSAGES/tcsh
- </para>
- <para>
not installed /usr/share/locale/it/LC_MESSAGES/tcsh
- </para>
- <para>
not installed /usr/share/locale/ja/LC_MESSAGES/tcsh
- </para>
- <para>
normal /usr/share/man/man1/tcsh.1.gz
- </para>
+ </screen>
<para>
- You can also use the longer option, --state, in place of –s.
+ You can also use the long option, <option>--state</option>,
+ in place of <option>–s</option>.
</para>
<para>
- You can combine the –s option with other file filters, such as
- –d, for listing only the documentation files for a package.
+ You can combine the <option>–s<option> option with other file filters,
+ such as <option>–d</option>, for listing only the documentation files
+ for a package.
</para>
<para>
- Table 5-2 lists the states that the rpm command supports.
+ Table 5-2 lists the states that RPM supports.
</para>
<para>
Table 5-2 RPM File States
@@ -1478,281 +1030,124 @@
</informaltable>
<para>
Sometimes files in a package may have been skipped during
- installation with options such as --excludedocs. This can lead
- to non-normal states. You may have also modified files installed
- from a given package.
- </para>
- <para>
- Cross Reference
+ installation with options such as <option>--excludedocs</option>.
+ This can lead to non-normal states. You may have also modified
+ files installed from a given package.
</para>
- <para>
- See <xref linkend="ch-using-rpm"/> for more on installing RPMs.
- </para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-listing_scripts">
<title>Listing the scripts in a package</title>
<para>
RPM packages can have preinstallation, postinstallation,
preuninstallation, and postuninstallation scripts. These are
scripts that the rpm command will execute before and after
installing a package, as well as before and after removing the
- package. The --scripts option to the rpm –q command lists the
+ package. The <option>--scripts</option> option to the
+ <command>rpm –q</command> command lists the
scripts associated with a package. The basic syntax follows:
</para>
<para>
- rpm -q --scripts package_name
+ <command>rpm -q --scripts <replaceable>package_name</replaceable></command>
</para>
<para>
For example:
</para>
<para>
- # rpm -q --scripts tcsh
- </para>
- <para>
- postinstall scriptlet (through /bin/sh):
- </para>
- <para>
- if [ ! -f /etc/shells ]; then
- </para>
- <para>
- echo "/bin/tcsh" >> /etc/shells
- </para>
- <para>
- echo "/bin/csh" >> /etc/shells
- </para>
- <para>
- else
- </para>
- <para>
- grep '^/bin/tcsh$' /etc/shells > /dev/null || echo
- "/bin/tcsh" >> /etc/shell
- </para>
- <para>
- s
- </para>
- <para>
- grep '^/bin/csh$' /etc/shells > /dev/null || echo "/bin/csh"
- >> /etc/shells
- </para>
- <para>
- fi
- </para>
- <para>
- postuninstall scriptlet (through /bin/sh):
- </para>
- <para>
- if [ ! -x /bin/tcsh ]; then
- </para>
- <para>
- grep -v '^/bin/tcsh$' /etc/shells | grep -v '^/bin/csh$'>
- /etc/shells.rpm
- </para>
- <para>
- mv /etc/shells.rpm /etc/shells
- </para>
- <para>
- fi
- </para>
- <para>
- PRODUCTION: NOTE THE “fi” on a line by itself at the end of
- this listing. Thanks, -Eric
- </para>
+ <command>rpm -q --scripts tcsh</command>
+ </para>
+ <screen>
+if [ ! -f /etc/shells ]; then
+ echo "/bin/tcsh" >> /etc/shells
+ echo "/bin/csh" >> /etc/shells
+else
+ grep -q '^/bin/tcsh$' /etc/shells || \
+ echo "/bin/tcsh" >> /etc/shells
+ grep -q '^/bin/csh$' /etc/shells || \
+ echo "/bin/csh" >> /etc/shells
+fi
+postuninstall scriptlet (using /bin/sh):
+if [ ! -x /bin/tcsh ]; then
+ grep -v '^/bin/tcsh$' /etc/shells | \
+ grep -v '^/bin/csh$' > /etc/shells.rpm && \
+ mv /etc/shells.rpm /etc/shells
+fi
+ </screen>
<para>
The simple scripts shown here add an entry to the /etc/shells
file and clean up the entry when uninstalled.
</para>
- <para>
- Cross Reference
- </para>
- <para>
- Cleaning up any changes your package makes on uninstallation is
- a very good idea. See the chapters in Part II, Creating RPMs,
- for details on making your own well-behaved packages.
- </para>
+ <important>
+ <title>Cleaning up</title>
+ <para>
+ Cleaning up any changes your package makes on uninstallation is
+ a very good idea. See the chapters in Part II, Creating RPMs,
+ for details on making your own well-behaved packages.
+ </para>
+ </important>
<para>
Other packages have more complex scripts, as shown following:
</para>
<para>
- # rpm -q --scripts sendmail
- </para>
- <para>
- preinstall scriptlet (through /bin/sh):
- </para>
- <para>
- /usr/sbin/useradd -u 47 -d /var/spool/mqueue -r -s /dev/null
- mailnull >/dev/null
- </para>
- <para>
- 2>&1 || :
- </para>
- <para>
- postinstall scriptlet (through /bin/sh):
- </para>
- <para>
- #
- </para>
- <para>
- # Convert old format to new
- </para>
- <para>
- #
- </para>
- <para>
- if [ -f /etc/mail/deny ] ; then
- </para>
- <para>
- cat /etc/mail/deny | \
- </para>
- <para>
- awk 'BEGIN{ print "# Entries from obsoleted /etc/mail/deny"} \
- </para>
- <para>
- {print $1" REJECT"}' >> /etc/mail/access
- </para>
- <para>
- cp /etc/mail/deny /etc/mail/deny.rpmorig
- </para>
- <para>
- fi
- </para>
- <para>
- for oldfile in relay_allow ip_allow name_allow ; do
- </para>
- <para>
- if [ -f /etc/mail/$oldfile ] ; then
- </para>
- <para>
- cat /etc/mail/$oldfile | \
- </para>
- <para>
- awk "BEGIN { print \"# Entries from obsoleted /etc/mail/$oldfile
- </para>
- <para>
- \" ;} \
- </para>
- <para>
- { print \$1\" RELAY\" }" >> /etc/mail/access
- </para>
- <para>
- cp /etc/mail/$oldfile /etc/mail/$oldfile.rpmorig
- </para>
- <para>
- fi
- </para>
- <para>
- done
- </para>
- <para/>
- <para>
- #
- </para>
- <para>
- # Oops, these files moved
- </para>
- <para>
- #
- </para>
- <para>
- if [ -f /etc/sendmail.cw ] ; then
- </para>
- <para>
- cat /etc/sendmail.cw | \
- </para>
- <para>
- awk 'BEGIN { print "# Entries from obsoleted /etc/sendmail.cw"
- ;} \
- </para>
- <para>
- { print $1 }' >> /etc/mail/local-host-names
- </para>
- <para>
- cp /etc/sendmail.cw /etc/sendmail.cw.rpmorig
- </para>
- <para>
- fi
- </para>
- <para>
- #
- </para>
- <para>
- # Rebuild maps (next reboot will rebuild also)
- </para>
- <para>
- #
- </para>
- <para>
- { /usr/bin/newaliases
- </para>
- <para>
- for map in virtusertable access domaintable mailertable
- </para>
- <para>
- do
- </para>
- <para>
- if [ -f /etc/mail/${map} ] ; then
- </para>
- <para>
- /usr/bin/makemap hash /etc/mail/${map} < /etc/mail/${map}
- </para>
- <para>
- sleep 1
- </para>
- <para>
- fi
- </para>
- <para>
- done
- </para>
- <para>
- } > /dev/null 2>&1
- </para>
- <para/>
- <para>
- /sbin/chkconfig --add sendmail
- </para>
- <para>
- preuninstall scriptlet (through /bin/sh):
- </para>
- <para>
- if [ $1 = 0 ]; then
- </para>
- <para>
+ <command>rpm -q --scripts sendmail</command>
+ </para>
+ <screen>
+preinstall scriptlet (using /bin/sh):
+/usr/sbin/useradd -u 47 -d /var/spool/mqueue -r -s /sbin/nologin mailnull >/dev/null 2>&1
+/usr/sbin/useradd -u 51 -d /var/spool/mqueue -r -s /sbin/nologin smmsp >/dev/null 2>&1
+exit 0
+postinstall scriptlet (using /bin/sh):
+/sbin/chkconfig --add sendmail
+# Set up the alternatives files for MTAs.
+/usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/sendmail.sendmail 90 \
+ --slave /usr/bin/mailq mta-mailq /usr/bin/mailq.sendmail \
+ --slave /usr/bin/newaliases mta-newaliases /usr/bin/newaliases.sendmail \
+ --slave /usr/bin/rmail mta-rmail /usr/bin/rmail.sendmail \
+ --slave /usr/lib/sendmail mta-sendmail /usr/lib/sendmail.sendmail \
+ --slave /etc/pam.d/smtp mta-pam /etc/pam.d/smtp.sendmail \
+ --slave /usr/share/man/man8/sendmail.8.gz mta-sendmailman /usr/share/man/man8/sendmail.sendmail.8.gz \
+ --slave /usr/share/man/man1/mailq.1.gz mta-mailqman /usr/share/man/man1/mailq.sendmail.1.gz \
+ --slave /usr/share/man/man1/newaliases.1.gz mta-newaliasesman /usr/share/man/man1/newaliases.sendmail.1.gz \
+ --slave /usr/share/man/man5/aliases.5.gz mta-aliasesman /usr/share/man/man5/aliases.sendmail.5.gz \
+ --initscript sendmail
+
+# Rebuild maps
+{
+ chown root /etc/aliases.db /etc/mail/access.db \
+ /etc/mail/mailertable.db /etc/mail/domaintable.db \
+ /etc/mail/virtusertable.db
+ SM_FORCE_DBREBUILD=1 /etc/mail/make
+ SM_FORCE_DBREBUILD=1 /etc/mail/make aliases
+} > /dev/null 2>&1
+exit 0
+preuninstall scriptlet (using /bin/sh):
+if [ $1 = 0 ]; then
/etc/rc.d/init.d/sendmail stop >/dev/null 2>&1
- </para>
- <para>
/sbin/chkconfig --del sendmail
- </para>
- <para>
- fi
- </para>
- <para>
- postuninstall scriptlet (through /bin/sh):
- </para>
- <para>
- if [ "$1" -ge "1" ]; then
- </para>
- <para>
+ /usr/sbin/alternatives --remove mta /usr/sbin/sendmail.sendmail
+fi
+exit 0
+postuninstall scriptlet (using /bin/sh):
+if [ "$1" -ge "1" ]; then
/etc/rc.d/init.d/sendmail condrestart >/dev/null 2>&1
- </para>
- <para>
+ mta=`readlink /etc/alternatives/mta`
+ if [ "$mta" == "/usr/sbin/sendmail.sendmail" ]; then
+ /usr/sbin/alternatives --set mta /usr/sbin/sendmail.sendmail
fi
- </para>
- <para>
- exit 0
- </para>
+fi
+exit 0
+ </screen>
<para>
In this case, the main script is the post-install script, which
tries to convert old-format data into the new format, thereby
helping users upgrade to the newer release.
</para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Listing_changed">
<title>Listing what has changed</title>
<para>
- The --changelog option lists what has changed, as described in a
- file that logs changes, from previous versions of a given
- package. The change log is just a convention, so not all
+ The <option>--changelog</option> option lists what has changed,
+ as described in a file that logs changes, from previous versions
+ of a given package. The change log is just a convention, so not all
packages will sport this nifty feature. In addition, the change
log for many packages documents the changes in the RPM
packaging, not the changes in the underlying application. If a
@@ -1770,228 +1165,144 @@
The basic format of the command is:
</para>
<para>
- rpm –q --changelog package_name
- </para>
- <para>
- For example, the following shows the beginning of the log-change
- log for the bash package, with names and e-mail addresses
- changed to protect the innocent:
- </para>
- <para>
- # rpm -q --changelog bash
- </para>
- <para>
- * Fri Aug 23 2002 Bob Marley <bob at marley.com.>
- </para>
- <para/>
- <para>
- - re-bzip the docs, something was corrupted
- </para>
- <para/>
- <para>
- * Thu Aug 22 2002 Peter Tosh <peter at tosh.com> 2.05b-4
- </para>
- <para/>
- <para>
- - Fix history substitution modifiers in UTF-8 (bug #70294, bug
- #71186).
- </para>
- <para>
- - Fix ADVANCE_CHAR at end of string (bug #70819).
+ <command>rpm –q --changelog <replaceable>package_name</replaceable></command>
</para>
<para>
- - docs: CWRU/POSIX.NOTES no longer exists, but ship POSIX.
+ For example, the following shows the beginning of the changelog
+ for the bash package:
</para>
- <para/>
<para>
- * Wed Aug 07 2002 Jimmy Cliff <jimmy at cliff.com> 2.05b-3
+ <command>rpm -q --changelog bash</command>
</para>
- <para/>
- <para>
- - Fixed out of memory problem with readline.
- </para>
- <para/>
- <para>
- * Tue Jul 23 2002 Jimmy Cliff <jimmy at cliff.com> 2.05b-2
- </para>
- <para/>
- <para>
- - Added symlink for sh.1 in man1 section so that man sh works
- (#44039).
- </para>
- </sect2>
- <sect2>
+ <screen>
+* Fri May 21 2010 Roman Rakus rrakus at redhat.com - 4.1.7-1
+- Patch level 7
+
+* Wed Mar 31 2010 Roman Rakus rrakus at redhat.com - 4.1.2-4
+- Corrected requires patch (#563301)
+
+* Fri Jan 22 2010 rrakus at redhat.com 4.1.2-3
+- Don't use cond-rmatch patch
+- Use manso patch
+- Include COPYING in base bash rpm
+
+* Fri Jan 22 2010 rrakus at redhat.com 4.1.2-2
+- Correct patchlevel 2
+
+* Fri Jan 22 2010 Roman Rakus rrakus at redhat.com 4.1.2-1
+- Patchlevel 4.2
+- Removed old patch
+- Returned back manso patch
+
+* Fri Jan 08 2010 Roman Rakus rrakus at redhat.com 4.1.0-2
+- Include COPYING in doc dir
+
+* Mon Jan 04 2010 Roman Rakus rrakus at redhat.com - 4.1.0-1
+- Upstream 4.1
+
+* Sun Dec 27 2009 Roman Rakus rrakus at redhat.com - 4.1-0.2.rc1
+- Fixed patch for fuzz=0
+
+* Sun Dec 27 2009 Roman Rakus rrakus at redhat.com - 4.1-0.1.rc1
+- Upstream 4.1.rc1
+
+* Fri Dec 11 2009 Roman Rakus rrakus at redhat.com - 4.0.35-2
+- Don't segfault when TERM=eterm* and EMACS is unset (#530911)
+
+* Thu Oct 29 2009 Roman Rakus rrakus at redhat.com - 4.0.35-1
+- Patch level 35
+ </screen>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Combining_queries">
<title>Combining queries</title>
<para>
The rpm command is very flexible in allowing you to combine
- queries. Just start the command with rpm –q and add the
- various options either on their own, such as –q with –s and
- –f, or together, such as –qsf.
+ queries. Just start the command with <command>rpm –q</command>
+ and add the various options either on their own, such as
+ <option>–q</option> with <option>–s</option> and
+ <option>–f</option>, or together, such as
+ <option>–qsf</option>.
</para>
<para>
The following sections show a few handy combinations of the
options you can use for real-world package-management tasks.
</para>
- <sect3>
+ <section id="RPM_Guide-Using_RPM_DB-Combining_queries-Decription_documentation">
<title>Listing Package Description and Documentation Files</title>
<para>
To find information on a package and where it is documented,
- use the –qdi option to the rpm command (a combination of the
- –q, –d, and –i options):
- </para>
- <para>
- # rpm -qdi grep
- </para>
- <para>
- Name : grep Relocations: /usr
- </para>
- <para>
- Version : 2.5.1 Vendor: Red Hat,
- </para>
- <para>
- Inc.
- </para>
- <para>
- Release : 4 Build Date: Sat 20 Jul
- </para>
- <para>
- 2002 01:08:48 AM CDT
- </para>
- <para>
- Install date: Sat 05 Oct 2002 12:21:58 PM CDT Build
- </para>
- <para>
- Host: stripples.devel.redhat.com
- </para>
- <para>
- Group : Applications/Text Source RPM: grep-2.5.1-
- </para>
- <para>
- 4.src.rpm
- </para>
- <para>
- Size : 475770 License: GPL
- </para>
- <para>
- Signature : DSA/SHA1, Tue 03 Sep 2002 04:17:47 PM CDT, Key ID
- </para>
- <para>
- 219180cddb42a60ePackager : Red Hat, Inc.
- </para>
- <para>
- <http://bugzilla.redhat.com/bugzilla>
- </para>
- <para>
- Summary : The GNU versions of grep pattern matching utilities.
- </para>
- <para>
- Description :
- </para>
- <para>
- The GNU versions of commonly used grep utilities. Grep
- searches
- </para>
- <para>
- through textual input for lines which contain a match to a
- specified
- </para>
- <para>
- pattern and then prints the matching lines. GNU's grep
- utilities
- </para>
- <para>
- include grep, egrep, and fgrep.
- </para>
- <para/>
- <para>
- You should install grep on your system, because it is a very
- useful
- </para>
- <para>
- utility for searching text.
- </para>
- <para>
- /usr/share/doc/grep-2.5.1/ABOUT-NLS
- </para>
- <para>
- /usr/share/doc/grep-2.5.1/AUTHORS
- </para>
- <para>
- /usr/share/doc/grep-2.5.1/ChangeLog
- </para>
- <para>
- /usr/share/doc/grep-2.5.1/NEWS
- </para>
- <para>
- /usr/share/doc/grep-2.5.1/README
- </para>
- <para>
- /usr/share/doc/grep-2.5.1/THANKS
- </para>
- <para>
- /usr/share/doc/grep-2.5.1/TODO
- </para>
- <para>
- /usr/share/info/grep.info-1.gz
- </para>
- <para>
- /usr/share/info/grep.info-2.gz
- </para>
- <para>
- /usr/share/info/grep.info-3.gz
- </para>
- <para>
- /usr/share/info/grep.info.gz
- </para>
- <para>
- /usr/share/man/man1/egrep.1.gz
- </para>
- <para>
- /usr/share/man/man1/fgrep.1.gz
- </para>
- <para>
- /usr/share/man/man1/grep.1.gz
- </para>
- <para>
- It's often hard to track down the documentation for a given
- package. Some packages use Unix manual pages; others use info
- files, and still others provide HTML for other formatted
+ use the <option>–qdi</option> option to rpm (a combination of the
+ <option>–q</option>, <option>–d</option>, and <option>–i</option> options):
+ </para>
+ <para>
+ <command>rpm -qdi grep</command>
+ </para>
+ <screen>
+Name : grep Relocations: (not relocatable)
+Version : 2.6.3 Vendor: Fedora Project
+Release : 1.fc13 Build Date: Wed 07 Apr 2010 05:58:58 PM EDT
+Install Date: Fri 27 Aug 2010 07:03:07 PM EDT Build Host: x86-06.phx2.fedoraproject.org
+Group : Applications/Text Source RPM: grep-2.6.3-1.fc13.src.rpm
+Size : 800493 License: GPLv3+
+Signature : RSA/SHA256, Wed 07 Apr 2010 06:48:20 PM EDT, Key ID 7edc6ad6e8e40fde
+Packager : Fedora Project
+URL : http://www.gnu.org/software/grep/
+Summary : Pattern matching utilities
+Description :
+The GNU versions of commonly used grep utilities. Grep searches through
+textual input for lines which contain a match to a specified pattern and then
+prints the matching lines. GNU's grep utilities include grep, egrep and fgrep.
+
+GNU grep is needed by many scripts, so it shall be installed on every system.
+/usr/share/doc/grep-2.6.3/ABOUT-NLS
+/usr/share/doc/grep-2.6.3/AUTHORS
+/usr/share/doc/grep-2.6.3/COPYING
+/usr/share/doc/grep-2.6.3/ChangeLog
+/usr/share/doc/grep-2.6.3/NEWS
+/usr/share/doc/grep-2.6.3/README
+/usr/share/doc/grep-2.6.3/THANKS
+/usr/share/doc/grep-2.6.3/TODO
+/usr/share/info/grep.info.gz
+/usr/share/man/man1/egrep.1.gz
+/usr/share/man/man1/fgrep.1.gz
+/usr/share/man/man1/grep.1.gz
+ </screen>
+ <para>
+ It can sometimes be difficult to track down the documentation for
+ a given package. Some packages use Unix manual pages; others use
+ info files, and still others provide HTML for other formatted
manuals. Some have no real documentation at all.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files">
<title>Listing the State of Configuration Files</title>
<para>
To find the state of all the configuration files for a given
- Linux command, use a command with the –qcsf option with the
- name of the file, as shown here, or the -qcs option with the
- name of a package.
+ Linux command, use a command with the <option>–qcsf</option>
+ option with the name of the file, as shown here, or the
+ <option>-qcs</option> option with the name of a package.
</para>
<para>
For example:
</para>
<para>
- # rpm -qcsf /bin/bash
- </para>
- <para>
- normal /etc/skel/.bash_logout
- </para>
- <para>
- normal /etc/skel/.bash_profile
+ <command>rpm -qcsf /bin/bash</command>
</para>
- <para>
- normal /etc/skel/.bashrc
- </para>
- </sect3>
- <sect3>
+ <screen>
+normal /etc/skel/.bash_logout
+normal /etc/skel/.bash_profile
+normal /etc/skel/.bashrc
+ </screen>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed">
<title>Listing the Most Recently Installed Packages</title>
<para>
To list the most recently installed packages, use the
- following command with the --last option. This is very useful
- if you recently installed or upgraded a number of packages and
- something unexpected happens. If you cannot remember the
- package names, you can use the --last option to list out
- packages in reverse order of installation.
+ following command with the <option>--last</option> option. This
+ is very useful if you recently installed or upgraded a number of
+ packages and something unexpected happens. If you cannot remember
+ the package names, you can use the <option>--last</option> option
+ to list out packages in reverse order of installation.
</para>
<para>
You can pipe the output of a query to the head command to show
@@ -1999,93 +1310,54 @@
shown following:
</para>
<para>
- # rpm -qa --last | head
- </para>
- <para>
- comps-8.0-0.20020910 Sat 05 Oct 2002 01:17:30 PM CDT
- </para>
- <para>
- tkinter-2.2.1-17 Sat 05 Oct 2002 01:16:58 PM CDT
- </para>
- <para>
- tix-8.2.0b1-74 Sat 05 Oct 2002 01:16:52 PM CDT
- </para>
- <para>
- tclx-8.3-74 Sat 05 Oct 2002 01:16:44 PM CDT
- </para>
- <para>
- python-tools-2.2.1-17 Sat 05 Oct 2002 01:16:41 PM CDT
- </para>
- <para>
- mx-2.0.3-6 Sat 05 Oct 2002 01:16:34 PM CDT
- </para>
- <para>
- libxslt-python-1.0.19-1 Sat 05 Oct 2002 01:16:31 PM CDT
- </para>
- <para>
- librpm404-devel-4.0.4-8x.27 Sat 05 Oct 2002 01:16:27 PM CDT
- </para>
- <para>
- itcl-3.2-74 Sat 05 Oct 2002 01:16:12 PM CDT
- </para>
- <para>
- gnumeric-1.0.9-2 Sat 05 Oct 2002 01:15:46 PM CDT
+ <command>rpm -qa --last | head</command>
</para>
+ <screen>
+kmod-nvidia-2.6.34.6-47.fc13.x86_64-256.53-1.fc13 Sat 18 Sep 2010 09:54:48 AM EDT
+xorg-x11-drv-nvidia-256.53-1.fc13 Sat 18 Sep 2010 09:51:00 AM EDT
+kmod-nvidia-2.6.34.6-54.fc13.x86_64-256.53-1.fc13.3 Sat 18 Sep 2010 09:50:59 AM EDT
+xorg-x11-drv-nvidia-libs-256.53-1.fc13 Sat 18 Sep 2010 09:50:57 AM EDT
+google-talkplugin-1.5.1.0-1 Wed 15 Sep 2010 07:38:46 PM EDT
+mythplugins-0.23.1-2.fc13 Sun 12 Sep 2010 09:35:42 PM EDT
+mythweather-0.23.1-2.fc13 Sun 12 Sep 2010 09:35:40 PM EDT
+perl-DateTime-Format-ISO8601-0.07-1.fc13 Sun 12 Sep 2010 09:35:39 PM EDT
+perl-DateTime-Format-Builder-0.7901-5.fc13 Sun 12 Sep 2010 09:35:38 PM EDT
+perl-Class-Factory-Util-1.7-6.fc13 Sun 12 Sep 2010 09:35:37 PM EDT
+ </screen>
<para>
You can pass options to the head command to show more or fewer
than ten lines. In general, starting with the last ten
packages can help you track down something you installed the
day before.
</para>
- </sect3>
- </sect2>
- <sect2>
+ </section>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Cusomt_queries">
<title>Creating custom queries</title>
<para>
- The --qf or --queryformat option allows you to create custom
- queries with the rpm command, although in a rather difficult
- manner. You need to pass a query format string, the syntax of
- which originates with the C printf function and requires
+ The <option>--qf</option> or <option>--queryformat</option> option
+ allows you to create custom queries with the rpm command, although
+ in a rather difficult manner. You need to pass a query format string,
+ the syntax of which originates with the C printf function and requires
precision.
</para>
<para>
- The basic syntax of the query format is %{tag_name}. (The
- percent sign is about the only part that comes from the C printf
+ The basic syntax of the query format is <option>%{tag_name}</option>.
+ (The percent sign is about the only part that comes from the C printf
function.) You can combine tag names to display more than one
item per package. You can also add formatting options following
C language conventions.
</para>
<para>
For example, to list all package names, use a command like the
- following:
- </para>
- <para>
- # rpm -qa --qf "%{NAME}"
- </para>
- <para>
- redhat-menusglibccracklibgdbmgmplibacllibjpeglincpcreshadow-
- </para>
- <para>
- utilslibtermcapfreetypeinfofileutilspsmiscntpmountcracklib-dictskrb5-libscyrus-
- </para>
- <para>
- saslusermodeXftlibpnglibxmllibbonobopythonpygtk2pyxf86configredhat-config-
+ following (the output is abbreviated):
</para>
<para>
- usersredhat-config-keyboardrpm404-pythongnome-vfs2libgnomeuiashbind-utilscyrus-
- </para>
- <para>
- sasl-plaindos2unixethtoolfingergroffautofskbdconfiglesslibtool-
- </para>
- <para>
- libslockdevmailcapMAKEDEVmouseconfignetpbmntsysvORBitpartedppppsutilsrdaterhnlibrp
- </para>
- <para>
- mrshsetuptoolstatserialtarlilopciutilstimeconfigunzipkernel-pcmcia-
- </para>
- <para>
- csanacronXFree86
+ <command>rpm -qa --qf "%{NAME}"</command>
</para>
+ <screen>
+libxml2tcp_wrappers-libstracerouteperl-Config-Tinylibsampleratefedora-icon-themefftw2dvb-appsreport-plugin-localsaveglib2-develqwtintltoolperl-Locale-Maketext-Gettextliblastfmxorg-x11-fonts-ISO8859-1-100dpilibpng-devellibgeotifffontconfigPackageKit-glibshared-mime-infoxorg-x11-drv-sisusbxmlgraphics-commonsopenoffice.org-graphicfilterm17n-db-oriyadejavu-sans-fontslibselinux-pythonapr-utilxorg-x11-drv-cirruslibsilcmysql-serverpnm2ppanssmythmusicdbus-glibcyrus-sasl-libfedora-release-notesekigaperl-Net-SSLeayperl-HTML-Parsermingettyphp-clixorg-x11-drv-nvidia-libspatchgnome-games-extra
+ </screen>
<para>
This command used the simplest format, which is just the value
of the tag in the package headers, in this case the package
@@ -2099,225 +1371,106 @@
For example (showing just the first few entries):
</para>
<para>
- # rpm -qa --qf "%{NAME}\n"
- </para>
- <para>
- redhat-menus
- </para>
- <para>
- glibc
- </para>
- <para>
- cracklib
- </para>
- <para>
- gdbm
- </para>
- <para>
- gmp
- </para>
- <para>
- libacl
- </para>
- <para>
- libjpeg
- </para>
- <para>
- linc
- </para>
- <para>
- pcre
- </para>
- <para>
- shadow-utils
- </para>
- <para>
- libtermcap
- </para>
- <para>
- freetype
- </para>
- <para>
- info
- </para>
- <para>
- fileutils
- </para>
- <para>
- psmisc
- </para>
- <para>
- ntp
- </para>
- <para>
- mount
- </para>
- <para>
- cracklib-dicts
- </para>
- <para>
- krb5-libs
- </para>
- <para>
- cyrus-sasl
- </para>
- <para>
- usermode
- </para>
- <para>
- Xft
+ <command>rpm -qa --qf "%{NAME}\n"</command>
</para>
+ <screen>
+libxml2
+tcp_wrappers-libs
+traceroute
+perl-Config-Tiny
+libsamplerate
+fedora-icon-theme
+fftw2
+dvb-apps
+report-plugin-localsave
+glib2-devel
+ </screen>
<para>
This command provides a custom query that is essentially the
- same as the rpm -qa command. You’ll likely not use this
+ same as <command>rpm -qa</command>. You’ll likely not use this
command in favor of the simpler rpm option, but you can use this
example as a guide for creating your own custom queries.
</para>
- <para>
- Cross Reference
- </para>
- <para>
- A great many of the command-line options to the rpm command are
- defined as popt aliases. These popt aliases define the rpm
- command-line options in terms of longer query format strings.
- See <xref linkend="ch-customizing-rpm"/> for more information on popt.
- </para>
+ <note>
+ <title>popt aliases</title>
+ <para>
+ A great many of the command-line options to the rpm command are
+ defined as popt aliases. These popt aliases define the rpm
+ command-line options in terms of longer query format strings.
+ See <xref linkend="ch-customizing-rpm"/> for more information on popt.
+ </para>
+ </note>
<para>
You can add items to the query string and use C language
conventions for formatting and controlling the amount of space
- provided for each item output.
- </para>
- <para>
- For example, the following command prints the name and platform
- for all packages, showing the first few entries, formatted with
- 20 characters for each item:
- </para>
- <para>
- rpm -qa --qf "%-20{NAME} %-20{PLATFORM}\n"
- </para>
- <para>
- redhat-menus noarch-redhat-linux-gnu
- </para>
- <para>
- glibc i686-redhat-linux-gnu
- </para>
- <para>
- cracklib i386-redhat-linux
- </para>
- <para>
- gdbm i386-redhat-linux-gnu
- </para>
- <para>
- gmp i386-redhat-linux-gnu
- </para>
- <para>
- libacl i386-redhat-linux-gnu
- </para>
- <para>
- libjpeg i386-redhat-linux
- </para>
- <para>
- linc i386-redhat-linux-gnu
- </para>
- <para>
- pcre i386-redhat-linux
- </para>
- <para>
- shadow-utils i386-redhat-linux-gnu
- </para>
- <para>
- libtermcap i386-redhat-linux
- </para>
- <para>
- freetype i386-redhat-linux-gnu
- </para>
- <para>
- info i386-redhat-linux-gnu
- </para>
- <para>
- fileutils i386-redhat-linux-gnu
- </para>
- <para>
- psmisc i386-redhat-linux
- </para>
- <para>
- ntp i386-redhat-linux-gnu
- </para>
- <para>
- mount i386-redhat-linux-gnu
- </para>
- <para>
- cracklib-dicts i386-redhat-linux
- </para>
- <para>
- krb5-libs i386-redhat-linux-gnu
- </para>
- <para>
- cyrus-sasl i386-redhat-linux-gnu
- </para>
- <para>
- usermode i386-redhat-linux-gnu
- </para>
- <para>
- Xft i386-redhat-linux-gnu
- </para>
- <para/>
- <sect3>
+ provided for each item output. For example, the following command
+ prints the name and platform for all packages, showing the first
+ few entries, formatted with 20 characters for each item:
+ </para>
+ <para>
+ <command>rpm -qa --qf "%-20{NAME} %-20{PLATFORM}\n"</command>
+ </para>
+ <screen>
+libxml2 x86_64-redhat-linux-gnu
+tcp_wrappers-libs i686-redhat-linux-gnu
+traceroute x86_64-redhat-linux-gnu
+perl-Config-Tiny noarch-redhat-linux-gnu
+libsamplerate x86_64-redhat-linux-gnu
+fedora-icon-theme noarch-redhat-linux-gnu
+fftw2 x86_64-redhat-linux-gnu
+dvb-apps x86_64-redhat-linux-gnu
+report-plugin-localsave x86_64-redhat-linux-gnu
+glib2-devel x86_64-redhat-linux-gnu
+ </screen>
+ </para>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Query_format_tags">
<title>Working With Query Format Tags</title>
<para>
- To build queries with the --queryformat option, you need to
- know what tags you can use. To list the names of the available
- query format tags, use the --querytags option, which returns a
- large set of tags, truncated here for space:
+ To build queries with the <option>--queryformat</option> option,
+ you need to know what tags you can use. To list the names of the
+ available query format tags, use the <option>--querytags</option>
+ option, which returns a large set of tags, truncated here for space:
</para>
<para>
- # rpm --querytags
+ <command>rpm --querytags</command>
</para>
- <para>
+ <screen>
NAME
- </para>
- <para>
VERSION
- </para>
- <para>
RELEASE
- </para>
- <para>
SUMMARY
- </para>
- <para>
DESCRIPTION
- </para>
- <para>
BUILDTIME
- </para>
+ </screen>
<para>
- Each of these tags also has a version with a RPMTAG_ prefix,
- such as RPMTAG_NAME. You can use this tags with or without the
- RPMTAG_ prefix. For example:
+ Each of these tags also has a version with a <literal>RPMTAG_</literal>
+ prefix, such as <literal>RPMTAG_NAME</literal>. You can use this tags
+ with or without the <literal>RPMTAG_</literal> prefix. For example:
</para>
<para>
- $ rpm -q --qf "%{RPMTAG_NAME}\n" sendmail
+ <command>rpm -q --qf "%{RPMTAG_NAME}\n" sendmail</command>
</para>
- <para>
+ <screen>
sendmail
- </para>
+ </screen>
<para>
- Note how this command uses the –q option to query for one
- package, instead of –qa to query for all packages. You can
- use query formats with any of the rpm queries.
+ Note how this command uses the <option>–q</option> option to query
+ for one package, instead of <option>–qa</option> to query for all
+ packages. You can use query formats with any of the rpm queries.
</para>
<para>
The next sections cover the available tags based on the type
of the information stored in the tag.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Querying_for_package_information">
<title>Querying for Package Information</title>
<para>
Many of the query format tags refer to package-information
- data stored in the RPM header, introduced in <xref linkend="ch-rpm-overview"/> . Table
- 5-3 lists the package-information tags.
+ data stored in the RPM header, introduced in
+ <xref linkend="ch-rpm-overview"/> . Table 5-3 lists the
+ package-information tags.
</para>
<para>
Table 5-3 Package-information query tags
@@ -2593,12 +1746,12 @@
</tgroup>
</informaltable>
<para>
- All of these tags, except for the CHANGELOGTIME, CHANGELOGTEXT
- and CHANGELOGNAME tags, are single-value tags. You can query
- for these tag values using
+ All of these tags, except for the <literal>CHANGELOGTIME</literal>,
+ <literal>CHANGELOGTEXT</literal> and <literal>CHANGELOGNAME</literal>
+ tags, are single-value tags.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Formatting_arrays">
<title>Formatting Arrays</title>
<para>
Many of the header entries are arrays, so the header tags can
@@ -2610,120 +1763,54 @@
brackets. For example:
</para>
<para>
- $ rpm -q --queryformat "[%-50{FILENAMES} %{FILESIZES}\n]"
- sendmail
- </para>
- <para>
- /etc/aliases 1295
- </para>
- <para>
- /etc/aliases.db 12288
- </para>
- <para>
- /etc/mail 4096
- </para>
- <para>
- /etc/mail/Makefile 748
- </para>
- <para>
- /etc/mail/access 331
- </para>
- <para>
- /etc/mail/access.db 12288
- </para>
- <para>
- /etc/mail/domaintable 0
- </para>
- <para>
- /etc/mail/domaintable.db 12288
- </para>
- <para>
- /etc/mail/helpfile 5588
- </para>
- <para>
- /etc/mail/local-host-names 64
+ <command>rpm -q --queryformat "[%-50{FILENAMES} %{FILESIZES}\n]"
+ sendmail</command>
</para>
+ <screen>
+/etc/NetworkManager/dispatcher.d/10-sendmail 96
+/etc/mail 4096
+/etc/mail/Makefile 92
+/etc/mail/access 469
+/etc/mail/access.db 0
+/etc/mail/aliasesdb-stamp 0
+/etc/mail/domaintable 233
+/etc/mail/domaintable.db 0
+/etc/mail/helpfile 5584
+/etc/mail/local-host-names 64
+ </screen>
<para>
This example lists the files and file sizes within a package,
with the listing of files truncated for size.
</para>
<para>
If you want to mix array tags with non-array tags, you can use
- an equals sign, =, in front of the tag name to specify that
- the given tag should be repeated for each item in the array.
- For example:
- </para>
- <para>
- $ rpm -q --queryformat "[%-15{=NAME} %-50{FILENAMES}\n]"
- sendmail jikes
- </para>
- <para>
- sendmail /usr/lib/sendmail
- </para>
- <para>
- sendmail /usr/sbin/mailstats
- </para>
- <para>
- sendmail /usr/sbin/makemap
- </para>
- <para>
- sendmail /usr/sbin/praliases
- </para>
- <para>
- sendmail /usr/sbin/sendmail.sendmail
- </para>
- <para>
- sendmail /usr/sbin/smrsh
- </para>
- <para>
- sendmail /usr/share/man/man1/mailq.sendmail.1.gz
- </para>
- <para>
- sendmail /usr/share/man/man1/newaliases.sendmail.1.gz
- </para>
- <para>
- sendmail /usr/share/man/man5/aliases.sendmail.5.gz
- </para>
- <para>
- sendmail /usr/share/man/man8/mailstats.8.gz
- </para>
- <para>
- sendmail /usr/share/man/man8/makemap.8.gz
- </para>
- <para>
- sendmail /usr/share/man/man8/praliases.8.gz
- </para>
- <para>
- sendmail /usr/share/man/man8/rmail.8.gz
- </para>
- <para>
- sendmail /usr/share/man/man8/sendmail.8.gz
- </para>
- <para>
- sendmail /usr/share/man/man8/smrsh.8.gz
- </para>
- <para>
- sendmail /var/spool/clientmqueue
- </para>
- <para>
- sendmail /var/spool/mqueue
- </para>
- <para>
- jikes /usr/bin/jikes
- </para>
- <para>
- jikes /usr/doc/jikes-1.18/license.htm
- </para>
- <para>
- jikes /usr/man/man1/jikes.1.gz
- </para>
+ an equals sign, <literal>=</literal>, in front of the tag name
+ to specify that the given tag should be repeated for each item
+ in the array. For example:
+ </para>
+ <para>
+ <command>rpm -q --queryformat "[%-15{=NAME} %-50{FILENAMES}\n]"
+ sendmail bash</command>
+ </para>
+ <screen>
+sendmail /etc/NetworkManager/dispatcher.d/10-sendmail
+sendmail /etc/mail
+sendmail /etc/mail/Makefile
+sendmail /etc/mail/access
+sendmail /etc/mail/access.db
+bash /bin/bash
+bash /bin/sh
+bash /etc/skel/.bash_logout
+bash /etc/skel/.bash_profile
+bash /etc/skel/.bashrc
+ </screen>
<para>
This example, also truncated for size, lists the package name
along with the file name for the files contained in these two
packages.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Special_formatting">
<title>Special Formatting</title>
<para>
Some of the tags within an RPM package header contain special
@@ -2732,23 +1819,24 @@
formatting options, using a syntax like the following:
</para>
<para>
- %{tag:special_format}
- </para>
- <para>
- For example, to print the INSTALLTIME tag, use
- %{INSTALLTIME:date}, which specifies to print the INSTALLTIME
- tag in date format. For example:
+ <literal>%{tag:special_format}</literal>
</para>
<para>
- $ rpm -q --qf "%{NAME}-%{VERSION}-%{RELEASE}
- %{INSTALLTIME:date}\n" jikes
+ For example, to print the <literal>INSTALLTIME</literal> tag, use
+ <literal>%{INSTALLTIME:date}</literal>, which specifies to print
+ the <literal>INSTALLTIME</literal> tag in date format. For example:
</para>
<para>
- jikes-1.18-1 Fri 06 Dec 2002 09:19:30 PM CST
+ <command>rpm -q --qf "%{NAME}-%{VERSION}-%{RELEASE}
+ %{INSTALLTIME:date}\n" bash</command>
</para>
+ <screen>
+bash-4.1.7-1.fc13 Fri 27 Aug 2010 07:02:33 PM EDT
+ </screen>
<para>
- This example prints the NAME-VERSION-RELEASE of the package,
- along with the INSTALLTIME in date format.
+ This example prints the <literal>NAME-VERSION-RELEASE</literal>
+ of the package, along with the <literal>INSTALLTIME</literal>
+ in date format.
</para>
<para>
Most tags in a header are optional. You can print the value of
@@ -2757,7 +1845,7 @@
language ternary operator. The basic syntax is:
</para>
<para>
- %|tag?{print_if_present}:{print_if_absent}|
+ <literal>%|tag?{print_if_present}:{print_if_absent}|</literal>
</para>
<para>
With the normal %{tag} syntax, this conditional syntax gets
@@ -2765,18 +1853,16 @@
For example:
</para>
<para>
- $ rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n"
- perl
+ <command>rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n"
+ perl</command>
</para>
+ <screen>
+ perl 4
+ </screen>
<para>
- perl 1
- </para>
- <para/>
- <para>
- If the package has a value for the EPOCH tag, you will see
- output as shown in this example. Most packages do not have an
- EPOCH defined, in which case, you will see output like the
- following:
+ If the package has a value for the <literal>EPOCH</literal> tag,
+ you will see output as shown in this example. Most packages do not
+ have an <literal>EPOCH</literal> defined, in which case, you will \ see output like the following:
</para>
<para>
RPM files likely hold packages that are not installed. If you
@@ -2784,27 +1870,20 @@
text, as shown following:
</para>
<para>
- $ rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n"
- sendmail
- </para>
- <para>
- sendmail (no Epoch)
- </para>
- <para/>
- <para>
- Cross Reference
+ <command>rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n"
+ sendmail</command>
</para>
+ <screen>
+sendmail (no Epoch)
+ </screen>
<para>
See the "Getting Information on Package Files" section in this
- chapter for more on querying RPM package files.
- </para>
- <para>
- Other special-formatting options are described in the
- following sections on the dependency and file information
- tags.
+ chapter for more on querying RPM package files. Other
+ special-formatting options are described in the
+ following sections on the dependency and file information tags.
</para>
- </sect3>
- <sect3>
+ </section>
+ <section id=>
<title>Querying for Package Dependencies</title>
<para>
A number of tags provide package dependency information. Each
@@ -3072,8 +2151,8 @@
required RPM versions, for example,
rpmlib(CompressedFileNames).
</para>
- </sect3>
- <sect3>
+ </section>
+ <section id="RPM-Guide-Using_RPM_DB-Querying_file_information">
<title>Querying for File Information</title>
<para>
The file-information tags hold data on the files within the
@@ -3299,44 +2378,68 @@
</tgroup>
</informaltable>
<para>
- The OLDFILENAMES tag is used when the files are not
- compressed, when the REQUIRENAME tag does not indicate
+ The <literal>OLDFILENAMES</literal> tag is used when the files are not
+ compressed, when the <literal>REQUIRENAME</literal> tag does not indicate
rpmlib(CompressedFileNames).
</para>
<para>
- The FILESIZES tag specifies the size of each file in the
- payload, while the FILEMODES tag specifies the file modes
- (permissions) and the FILEMTIMES tag holds the last
+ The <literal>FILESIZES</literal> tag specifies the size of each file in the
+ payload, while the <literal>FILEMODES</literal> tag specifies the file modes
+ (permissions) and the <literal>FILEMTIMES</literal> tag holds the last
modification time for each file.
</para>
<para>
- The BASENAMES tag holds an array of the base file names for
- the files in the payload. The DIRNAMES tag holds an array of
- the directories for the files. The DIRINDEXES tag contains an
- index into the DIRNAMES for the directory. Each RPM must have
- either OLDFILENAMES or the triple of BASENAMES, DIRNAMES, and
- DIRINDEXES, but not both.
+ The <literal>BASENAMES</literal> tag holds an array of the base file names for
+ the files in the payload. The <literal>DIRNAMES</literal> tag holds an array of
+ the directories for the files. The <literal>DIRINDEXES</literal> tag contains an
+ index into the <literal>DIRNAMES</literal> for the directory. Each RPM must have
+ either <literal>OLDFILENAMES</literal> or the triple of <literal>BASENAMES</literal>,
+ <literal>DIRNAMES</literal>, and <literal>DIRINDEXES</literal>, but not both.
</para>
<para>
When listing file information, use the square bracket array
syntax with your query formats. You can use the perms special
formatting option for the file modes. For example:
</para>
- <para>
- $ rpm -q --qf "[%-15{=NAME} %-36{FILENAMES}
- %{FILEMODES:perms}\n]" jikes
- </para>
- <para>
- jikes /usr/bin/jikes -rwxr-xr-x
- </para>
- <para>
- jikes /usr/doc/jikes-1.18/license.htm -rw-r--r--
- </para>
- <para>
- jikes /usr/man/man1/jikes.1.gz -rw-r--r--
- </para>
- </sect3>
- <sect3>
+ <screen>
+$ rpm -q --qf "[%-15{=NAME} %-36{FILENAMES} %{FILEMODES:perms}\n]" sudo
+sudo /etc/pam.d/sudo -rw-r--r--
+sudo /etc/pam.d/sudo-i -rw-r--r--
+sudo /etc/sudoers -r--r-----
+sudo /etc/sudoers.d drwxr-x---
+sudo /usr/bin/sudo ---s--x--x
+sudo /usr/bin/sudoedit ---s--x--x
+sudo /usr/bin/sudoreplay ---x--x--x
+sudo /usr/libexec/sesh -rwxr-xr-x
+sudo /usr/libexec/sudo_noexec.so -rwxr-xr-x
+sudo /usr/sbin/visudo -rwxr-xr-x
+sudo /usr/share/doc/sudo-1.7.4p4 drwxr-xr-x
+sudo /usr/share/doc/sudo-1.7.4p4/ChangeLog -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/HISTORY -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/LICENSE -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/NEWS -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/README -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/README.LDAP -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/TROUBLESHOOTING -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/UPGRADE -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.pam -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.sudoers -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.syslog.conf -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.ActiveDirectory -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.OpenLDAP -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.iPlanet -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sudoers.ldap.pod -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sudoers2ldif -rw-r--r--
+sudo /usr/share/man/man5/sudoers.5.gz -rw-r--r--
+sudo /usr/share/man/man5/sudoers.ldap.5.gz -rw-r--r--
+sudo /usr/share/man/man8/sudo.8.gz -rw-r--r--
+sudo /usr/share/man/man8/sudoedit.8.gz -rw-r--r--
+sudo /usr/share/man/man8/sudoreplay.8.gz -rw-r--r--
+sudo /usr/share/man/man8/visudo.8.gz -rw-r--r--
+sudo /var/db/sudo drwx------
+ </screen>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags">
<title>Other Query Format Tags</title>
<para>
In addition to all these tags, there are a number of other
@@ -3478,38 +2581,30 @@
For example, you can list the version of RPM that created a
package with a command like the following:
</para>
- <para>
- $ rpm -qp --qf "%{name} - rpm %{rpmversion}\n" *.rpm
- </para>
- <para>
- acroread - rpm 2.5.5
- </para>
- <para>
- canvas - rpm 3.0.3
- </para>
- <para>
- jikes - rpm 4.0.2
- </para>
- <para>
- SDL - rpm 2.5.1
- </para>
- <para>
- ted - rpm 2.5.5
- </para>
- <para>
- Cross Reference
- </para>
+ <screen>
+$ rpm -qp --qf "%{name} - rpm %{rpmversion}\n" *.rpm
+qt - rpm 4.7.2
+qt - rpm 4.7.2
+qt-devel - rpm 4.7.2
+qt-mysql - rpm 4.7.2
+qt-sqlite - rpm 4.7.2
+qt-sqlite - rpm 4.7.2
+qt-x11 - rpm 4.7.2
+qt-x11 - rpm 4.7.2
+ </screen>
+ <note>
+ <title>Cross Reference</title>
<para>
See <xref linkend="ch-package-structure"/> for a listing of all the tags in an RPM file.
</para>
- </sect3>
- </sect2>
- <sect2>
+ </note>
+ </section>
+ </section>
+ <section>
<title>Other queries</title>
<para>
If what you’ve seen so far isn’t enough, the rpm command
- supports a number of extra queries, mostly of use to developers
- at Red Hat.
+ supports a number of extra queries, mostly of use to developers.
</para>
<para>
Table 5-7 summarizes these extra queries.
@@ -3623,9 +2718,9 @@
</tbody>
</tgroup>
</informaltable>
- </sect2>
- </sect1>
- <sect1>
+ </section>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files">
<title>Getting Information on Package Files</title>
<para>
In addition to querying the RPM database about installed packages,
@@ -3637,69 +2732,55 @@
what the corresponding packages provide.
</para>
<para>
- The –p option tells the rpm command to provide information on
+ The <literal>–p</literal> option tells the rpm command to provide information on
the given package file. The basic syntax is:
</para>
<para>
- rpm –qp option_query_options filename.rpm
+ <command>rpm –qp <replaceable>query_options</replaceable> <replaceable>filename</replaceable>
</para>
<para>
- You can use the longer option, --package, in place of –p. You
+ You can use the longer option, <literal>--package</literal>, in place of <literal>–p</literal>. You
can also pass more than one RPM file to the command.
</para>
<para>
The query information options shown previously for installed
packages also work for RPM files. For example, to list the
- configuration files for a package, combine the -q, -p, and -c
- options with the name of a package file, as shown following:
- </para>
- <para>
- # rpm -qpc telnet-server-0.17-23.i386.rpm
- </para>
- <para>
- /etc/xinetd.d/telnet
- </para>
- <para>
- To list all the files in an RPM package, combine the -q, -p, and
- -l options:
- </para>
- <para>
- # rpm -qpl telnet-server-0.17-23.i386.rpm
- </para>
- <para>
- /etc/xinetd.d/telnet
- </para>
- <para>
- /usr/sbin/in.telnetd
- </para>
- <para>
- /usr/share/man/man5/issue.net.5.gz
- </para>
- <para>
- /usr/share/man/man8/in.telnetd.8.gz
- </para>
- <para>
- /usr/share/man/man8/telnetd.8.gz
- </para>
- <para>
- Querying Package Files Remotely
- </para>
+ configuration files for a package, combine the <literal>-q</literal>, <literal>-p</literal>,
+ and <literal>-c</literal> options with the name of a package file, as shown following:
+ </para>
+ <screen>
+$ rpm -qpc qt-4.6.2-17.fc12.x86_64.rpm
+/etc/Trolltech.conf
+ </screen>
+ <para>
+ To list all the files in an RPM package, combine the <literal>-q</literal>,
+ <literal>-p</literal>, and <literal>-l</literal> options (example output truncated):
+ </para>
+ <screen>
+$ rpm -qpl qt-4.6.2-17.fc12.x86_64.rpm
+/etc/Trolltech.conf
+/usr/bin/qdbus
+/usr/lib64/libQtCore.so.4
+/usr/lib64/libQtCore.so.4.6
+/usr/lib64/libQtCore.so.4.6.2
+/usr/lib64/libQtDBus.so.4
+/usr/lib64/libQtDBus.so.4.6
+/usr/lib64/libQtDBus.so.4.6.2
+/usr/lib64/libQtNetwork.so.4
+/usr/lib64/libQtNetwork.so.4.6
+ </screen>
+ <section id="RPM_Guide_Using_RPM_DB-Querying_package_files_remotely">
+ <title>Querying Package Files Remotely</title>
<para>
As shown in <xref linkend="ch-using-rpm"/> , you can access RPM package files over a
network using FTP or HTTP connections. To query remote files, use
the same rules as shown in <xref linkend="ch-using-rpm"/> , with the following syntax:
</para>
<para>
- rpm -qp ftp://username:password@hostname:port/path/to/rpm/file
- </para>
- <para>
- rpm -qp ftp://username@hostname:port/path/to/rpm/file
+ <command>rpm -qp ftp://<replaceable>username</replaceable>:<replaceable>password</replaceable>@<replaceable>hostname</replaceable>:<replaceable>port</replaceable>/<replaceable>path/to/rpm/file</replaceable></command>
</para>
<para>
- rpm -qp ftp://hostname:port/path/to/rpm/file
- </para>
- <para>
- rpm -qp http://hostname:port/path/to/rpm/file
+ <command>rpm -qp http://<replaceable>hostname</replaceable>:<replaceable>port</replaceable>/<replaceable>path/to/rpm/file</replaceable></command>
</para>
<para>
If your system resides behind a firewall with a proxy server, use
@@ -3773,47 +2854,40 @@
</tgroup>
</informaltable>
<para/>
- </sect1>
- <sect1>
+ </section>
+ <section id="RPM-Guide-Using_RPM-DB-verifying_packages">
<title>Verifying Installed RPM Packages</title>
<para>
You can do a lot more than just query packages in the RPM
database. You can ask the rpm command to verify packages with the
- -V (or --verify) option.
+ <option>-V</option> (or <option>--verify</option>) option.
+ The rpm -V command will also report missing dependencies.
</para>
<para>
The basic syntax is:
</para>
<para>
- rpm -V verify_options package_name
+ <command>rpm -V <replaceable>verify_options</replaceable> <replaceable>package_name</replaceable>
</para>
<para>
For example:
</para>
- <para>
- # rpm -V telnet
- </para>
- <para>
+ <screen>
+ rpm -V telnet
#
- </para>
+ </screen>
<para>
If everything checks out, you'll get no response. The rpm command
reports problems only. For example, if you have an installation of
the telnet-server package that is missing some files, the rpm -V
command will let you know, as shown following:
</para>
- <para>
- # rpm -V telnet-server
- </para>
- <para>
+ <screen>
+ $ rpm -V telnet-server
missing c /etc/xinetd.d/telnet
- </para>
- <para>
missing /usr/sbin/in.telnetd
- </para>
- <para>
missing d /usr/share/man/man5/issue.net.5.gz
- </para>
+ </screen>
<para>
In this example, the c and d stand for configuration and
documentation files, respectively.
@@ -3821,47 +2895,26 @@
<para>
Note
</para>
- <para>
- The rpm -V command will also report missing dependencies.
- </para>
- <sect2>
+ <section id="RPM_Guide-Using_RPM_DB-verifying_system">
<title>Verifying your entire system</title>
<para>
- To verify your entire system, use the -a option.
+ To verify your entire system, use the <option>-a</option> option.
</para>
<para>
For example:
</para>
- <para>
+ <screen>
# rpm -Va
- </para>
- <para>
SM5....T c /usr/share/info/dir
- </para>
- <para>
.......T c /etc/krb5.conf
- </para>
- <para>
.......T /usr/share/pixmaps/gnome-default-dlg.png
- </para>
- <para>
.......T /usr/share/pixmaps/gnome-error.png
- </para>
- <para>
.......T /usr/share/pixmaps/gnome-info.png
- </para>
- <para>
.......T /usr/share/pixmaps/gnome-question.png
- </para>
- <para>
.......T /usr/share/pixmaps/gnome-warning.png
- </para>
- <para>
S.5....T c /etc/sysconfig/pcmcia
- </para>
- <para>
.....U.. /dev/winradio0
- </para>
+ </screen>
<para>
Each line that the rpm command outputs indicates a problem with
the given file. The rpm command uses letter codes to show the
@@ -3986,8 +3039,8 @@
</tbody>
</tgroup>
</informaltable>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-controlling_verification">
<title>Controlling the verification</title>
<para>
You can use a number of options to tell the verification command
@@ -4208,114 +3261,55 @@
</tgroup>
</informaltable>
<para>
- Cross Reference
- </para>
- <para>
- <xref linkend="ch-rpmbuild"/> covers another option for verifying a package file,
- the rpm –K command.
- </para>
- <para>
- The --nofiles option is often used with the –Va option to
+ The <option>--nofiles</option> option is often used with <option> –Va</option> to
verify the whole system but skip tests of file attributes. This
- command is used to often it has become an idiom for RPM usage,
+ command is used so often it has become an idiom for RPM usage,
especially for debugging RPM problems. Run a command like the
following:
</para>
<para>
- $ rpm -Va --nofiles
+ <command>rpm -Va --nofiles</command>
</para>
- </sect2>
- </sect1>
- <sect1>
+ </section>
+ </section>
+ <section id="RPM_GUide-Using_RPM_DB-working_with_RPM_db">
<title>Working With the RPM Database</title>
<para>
As mentioned in <xref linkend="ch-rpm-overview"/> , the RPM database is stored in
/var/lib/rpm. The files in that directory are Berkeley DB files,
as shown by the file command:
</para>
- <para>
+ <screen>
# file /var/lib/rpm/*
- </para>
- <para>
- /var/lib/rpm/Basenames: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Conflictname: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
- <para>
+ /var/lib/rpm/Basenames: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Conflictname: Berkeley DB (Hash, version 7, native byte-order)
/var/lib/rpm/__db.001: data
- </para>
- <para>
/var/lib/rpm/__db.002: X11 SNF font data, LSB first
- </para>
- <para>
/var/lib/rpm/__db.003: X11 SNF font data, LSB first
- </para>
- <para>
- /var/lib/rpm/Dirnames: Berkeley DB (Btree, version 8, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Filemd5s: Berkeley DB (Btree, version 8, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Group: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Installtid: Berkeley DB (Btree, version 8, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Name: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Packages: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Providename: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Provideversion: Berkeley DB (Btree, version 8, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Requirename: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Requireversion: Berkeley DB (Btree, version 8, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Sha1header: Berkeley DB (Btree, version 8, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Sigmd5: Berkeley DB (Btree, version 8, native
- byte-order)
- </para>
- <para>
- /var/lib/rpm/Triggername: Berkeley DB (Hash, version 7, native
- byte-order)
- </para>
+ /var/lib/rpm/Dirnames: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Filemd5s: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Group: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Installtid: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Name: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Packages: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Providename: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Provideversion: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Requirename: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Requireversion: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Sha1header: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Sigmd5: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Triggername: Berkeley DB (Hash, version 7, native byte-order)
+ </screen>
<para>
Each file is a separate database in Berkeley DB format, except for
a few __db data files. (These are not really X11 font files, just
plain data files. The file command is confused by the data in the
files.)
</para>
+ <note>
+ <title>The Berkeley DB Library</title>
<para>
- The Berkeley DB Library
- </para>
- <para>
- Available from SleepyCat Software at www.sleepycat.com/, the
+ Available from Oracle at http://www.oracle.com/technetwork/database/berkeleydb/overview/, the
Berkeley DB library provides a simple database API. This is not a
traditional relational database. Instead, data values are stored
in what amounts to a persistent hash table of name/value pairs.
@@ -4323,11 +3317,7 @@
as a package name) but is not so quick for iterating over all the
entries.
</para>
- <para>
- One of the nice things about this library is that it is available
- in an open-source format, and you can get programming API
- libraries for C, C++, Java, Python, Perl, and Tcl languages.
- </para>
+ </note>
<para>
The RPM database is really a number of Berkeley DB databases, each
designed for a different type of query.
@@ -4338,84 +3328,52 @@
database, although that is generally not needed. First and
foremost, however, you should back up this database.
</para>
- <para/>
- <sect2>
+ <section id="RPM_Guide-Using_RPM_DB-Backing_up_RPM_db">
<title>Backing up the RPM database</title>
<para>
As mentioned before, the RPM database resides in the
- /var/lib/rpm. You can back up the RPM database by using commands
+ /var/lib/rpm. You can back up the RPM database by using a command
such as the following:
</para>
<para>
- # cd /var/lib
+ <command>tar cf <replaceable>rpmdb.tar</replaceable> /var/lib/rpm</command>
</para>
- <para>
- # tar cvf rpmdb.tar ./rpm
- </para>
- <para>
- # gzip rpmdb.tar
- </para>
- <para>
- These commands create a tar archive from the contents of the rpm
- directory (where the RPM database is stored) and compress the
- file with the gzip command.
- </para>
- <para>
- Note
- </para>
- <para>
- Adding the z option to the tar command can create a compressed
- archive directly, without the need for the gzip command.
- </para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db">
<title>Rebuilding the RPM database</title>
<para>
If the RPM database has been corrupted in some way, you can use
- the --rebuilddb option to tell the rpm command to rebuild your
- database.
- </para>
- <para>
- For example:
+ the <option>--rebuilddb</option> option to tell the rpm command to rebuild your
+ database. For example:
</para>
<para>
- rpm --rebuilddb
+ <command>rpm --rebuilddb</command>
</para>
<para>
This command rebuilds the RPM database from the installed
- packages, the file named Packages in the /var/lib/rpm directory.
- Only the Packages file is required. All the other files can be
- recreated from the Packages file. If your database is OK, this
+ packages, the file named <filename>Packages</filename> in the /var/lib/rpm directory.
+ Only the <filename>Packages</filename> file is required. All the other files can be
+ recreated from the <filename>Packages</filename> file. If your database is OK, this
command won't do much, other than shrink the size of your RPM
database by removing unused entries. This command will take some
time to execute, though.
</para>
- <para>
- Warning
- </para>
+ <warning>
<para>
Before running this command, back up your RPM database.
</para>
+ </warning>
<para>
- To check that the rpm --rebuilddb command has not damaged the
+ To check that the <command>rpm --rebuilddb</command> command has not damaged the
RPM database, you can check with a file listing, query all
- packages, and then check the results of the rpm –rebuilddb
+ packages, and then check the results of the <command>rpm –rebuilddb</command>
command with another file listing when done.
</para>
- <para>
- Another useful technique that can help with a corrupted RPM
- database is to use the db_dump and db_load utilities that come
- with RPM (from the SleepyCat DB database library). Use db_dump
- to dump the Packages file. Then, use db_load to reload the
- Packages file. The act of dumping and restoring may fix a
- corrupted file. As always, back up your RPM database prior to
- performing these commands.
- </para>
- </sect2>
- <sect2>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-new_db">
<title>Creating a new RPM database</title>
<para>
- If all else fails, use the --initdb option to tell the rpm
+ If all else fails, use the <option>--initdb</option> option to tell the rpm
command to create a new empty RPM database. In almost all cases,
you do not want to create a new RPM database, since this
database will be empty. It will not have any knowledge about the
@@ -4427,13 +3385,7 @@
The basic syntax follows.
</para>
<para>
- rpm --initdb
- </para>
- <para>
- Note
- </para>
- <para>
- This command should not damage an existing database.
+ <command>rpm --initdb</command>
</para>
<para>
If the RPM system cannot be rebuilt, you may have to reinstall
@@ -4443,18 +3395,16 @@
database.
</para>
<para>
- You can also use the --dbpath option to tell the rpm command to
+ You can also use the <option>--dbpath</option> option to tell the rpm command to
create an RPM database in a different directory.
</para>
<para>
For example:
</para>
- <para>
- mkdir /tmp/rpm
- </para>
- <para>
+ <screen>
+ mkdir /tmp/rpm
rpm --initdb --dbpath /tmp/rpm
- </para>
+ </screen>
<para>
These commands create a temporary directory and an RPM database
in the /tmp/rpm directory.
@@ -4462,30 +3412,9 @@
<para>
After running this command, you can examine the files created.
</para>
- <para>
- # ls -l /tmp/rpm
- </para>
- <para>
- total 288
- </para>
- <para>
- -rw-r--r-- 1 root root 8192 Oct 10 20:29 __db.001
- </para>
- <para>
- -rw-r--r-- 1 root root 1310720 Oct 10 20:29 __db.002
- </para>
- <para>
- -rw-r--r-- 1 root root 360448 Oct 10 20:29 __db.003
- </para>
- <para>
- -rw-r--r-- 1 root root 12288 Oct 10 20:29 Packages
- </para>
- <para>
- This shows an empty RPM database.
- </para>
- </sect2>
- </sect1>
- <sect1>
+ </section>
+ </section>
+ <section id="RPM_Guide-Using_RPM_DB-summary">
<title>Summary</title>
<para>
This chapter covers the rpm command options to query the RPM
@@ -4500,10 +3429,10 @@
after any installation, upgrade, or removal of packages.
</para>
<para>
- You can also use the --rebuilddb option to the rpm command to
+ You can also use the <option>--rebuilddb</option> option to the rpm command to
rebuild a damaged RPM database.
</para>
- </sect1>
+ </section>
</chapter>
<!--
More information about the docs-commits
mailing list