about a specific version.
\item [VolFile]
\index[fd]{VolFile }
The value is a file number, a list of file numbers, or a range of file
-numbers numbers to match on the current Volume. The file number represents
+numbers to match on the current Volume. The file number represents
the physical file on the Volume where the data is stored. For a tape volume,
this record is used to position to the correct starting file, and once the
tape is past the last specified file, reading will stop.
\item [VolBlock]
\index[fd]{VolBlock }
The value is a block number, a list of block numbers, or a range of block
-numbers numbers to match on the current Volume. The block number represents
+numbers to match on the current Volume. The block number represents
the physical block on the Volume where the data is stored. This record is
currently not used.
7.x (rh7), RedHat 8.0 (rh8), RedHat 9 (rh9), Fedora Core (fc1), Whitebox
Enterprise Linux (RHEL) 3.0 (wb3), Mandrake 10.x (mdk) and SuSE 9.x (su9).
The package build is controlled by a mandatory define set at the beginning of
-the file. These defines basically just control the dependancy information that
+the file. These defines basically just control the dependency information that
gets coded into the finished rpm package.
The platform define may be edited in the spec file directly (by default all
defines are set to 0 or ``not set''). For example, to build the RedHat 7.x
a regular user but you must make a few changes on your system to do this. If
you are building on your own system then the simplest method is to add write
permissions for all to the build directory (/usr/src/redhat/). To accomplish
-this execute the following command as root:
+this, execute the following command as root:
\footnotesize
\begin{verbatim}
\normalsize
If you are working on a shared system where you can not use the method above
-then you need to recreate the /usr/src/redhat directory tree with all of it's
+then you need to recreate the /usr/src/redhat directory tree with all of its
subdirectories inside your home directory. Then create a file named {\tt
.rpmmacros} in your home directory (or edit the file if it already exists)
and add the following line:
\item
\label{faq5}
{\bf I'm building my own rpms but on all platforms and compiles I get an
-unresolved dependancy for something called /usr/afsws/bin/pagsh.}
+unresolved dependency for something called /usr/afsws/bin/pagsh.}
This is a shell from the OpenAFS (Andrew File System). If you are seeing this
then you chose to include the docs/examples directory in your package. One of
the example scripts in this directory is a pagsh script. Rpmbuild, when
-scanning for dependancies, looks at the shebang line of all packaged scripts
+scanning for dependencies, looks at the shebang line of all packaged scripts
in addition to checking shared libraries. To avoid this do not package the
examples directory.
\end{enumerate}
\end{verbatim}
\normalsize
-The {\bf InitCatalog} level tells {\bf Bacula} simply get the information on
+The {\bf InitCatalog} level tells {\bf Bacula} simply to get the information on
the specified files and to put it into the catalog. That is your database is
initialized and no comparison is done. The {\bf InitCatalog} is normally run
one time manually.
The {\bf verify=pins1} is ignored during the {\bf InitCatalog} Job, but is
used during the subsequent {\bf Catalog} Jobs to specify what attributes of
the files should be compared to those found in the catalog. {\bf pins1} is a
-reasonable set to begin with, but you may want to look at the details these
+reasonable set to begin with, but you may want to look at the details of these
and other options. They can be found in the
\ilink{FileSet Resource}{FileSetResource} section of this manual.
Briefly, however, the {\bf p} of the {\bf pins1} tells Verify to compare the
at which point you respond {\bf yes}, and the Job will begin.
-There after the Job will automatically start according to the schedule you
+Thereafter the Job will automatically start according to the schedule you
have defined. If you wish to immediately verify it, you can simply run a
Verify {\bf Catalog} which will be the default. No differences should be
found.
to modify the {\bf FileSet} to exclude that file (or not to Include it), and
then re-run the {\bf InitCatalog}.
-The FileSet that is show below is what I use on my RedHat 7.3 system. With a
+The FileSet that is shown below is what I use on my RedHat 7.3 system. With a
bit more thought, you can probably add quite a number of additional files that
should be monitored.
projects / bacula / docs / commitdiff