--- Begin Message ---
Package: bacula-doc
Severity: serious
Tags: patch
latex bacula.tex will fail, even when all needed depends are installed.
No idea how you managed to build it in the first place. Attached is a
patch that makes it run. I did not check the output.
The files are full of further LaTeX problems: Use of the obsolete \bf
command instead of \bfseries (will cause trouble when fonts are changed,
and the letter kerning might already be amiss), declaration of a new
fontsize with hard-coded cmr which might also cause trouble, etc.pp.
Note that the attached patch loads the non-free html.sty, because the
original document uses commands from it. I'm going to file a separate
bug about this.
Regards, Frank
diff -Nur bacula-doc-1.38.11.1.old/manual/autochangers.tex
bacula-doc-1.38.11.1/manual/autochangers.tex
--- bacula-doc-1.38.11.1.old/manual/autochangers.tex 2006-04-14
19:08:57.000000000 +0200
+++ bacula-doc-1.38.11.1/manual/autochangers.tex 2006-07-28
16:54:40.000000000 +0200
@@ -98,7 +98,7 @@
\footnotesize
\begin{verbatim}
-cat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices
+cat /proc/scsi/sg/device\_hdr /proc/scsi/sg/devices
\end{verbatim}
\normalsize
Binary files bacula-doc-1.38.11.1.old/manual/bacula.pdf and
bacula-doc-1.38.11.1/manual/bacula.pdf differ
diff -Nur bacula-doc-1.38.11.1.old/manual/bacula.sty
bacula-doc-1.38.11.1/manual/bacula.sty
--- bacula-doc-1.38.11.1.old/manual/bacula.sty 2005-05-13 19:23:00.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/bacula.sty 2006-07-28 17:17:48.000000000
+0200
@@ -27,8 +27,9 @@
\ProvidesPackage{bacula}[2005/01/09]
%%
%%
+\RequirePackage{html}
\newcommand*{\elink}[2]{%
- \htmladdnormallink{#1}{#2}%
+ \href{#1}{#2}% url/hyperref, no need to escape #
}
%%
\newcommand*{\ilink}[2]{%
diff -Nur bacula-doc-1.38.11.1.old/manual/bacula.tex
bacula-doc-1.38.11.1/manual/bacula.tex
--- bacula-doc-1.38.11.1.old/manual/bacula.tex 2006-07-28 18:52:39.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/bacula.tex 2006-07-28 18:35:39.000000000
+0200
@@ -35,16 +35,14 @@
\title{\includegraphics{./bacula-logo.eps} \\ \bigskip
\begin{center}
- \large{It comes in the night and sucks
- the essence from your computers. }
+ \large{}It comes in the night and sucks the essence from your
+ computers.
\end{center}
}
\author{Kern Sibbald}
-\date{\vspace{1.0in}\today \\
- This manual documents Bacula version \input{version} \\
- \vspace{0.2in}\\
- Copyright \copyright 1999-2006, Kern Sibbald \\
- \vspace{0.2in}\\
+\date{\vspace{1.0in}\today % \\
+ This manual documents Bacula version \input{version} \\[0.5in]
+ Copyright \copyright 1999-2006, Kern Sibbald \\[0.5in]
Permission is granted to copy, distribute and/or modify this document under
the terms of the \\
GNU Free Documentation License, Version 1.2 published by the Free Software
Foundation; \\
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. \\
diff -Nur bacula-doc-1.38.11.1.old/manual/bootstrap.tex
bacula-doc-1.38.11.1/manual/bootstrap.tex
--- bacula-doc-1.38.11.1.old/manual/bootstrap.tex 2006-01-17
10:36:36.000000000 +0100
+++ bacula-doc-1.38.11.1/manual/bootstrap.tex 2006-07-28 17:47:22.000000000
+0200
@@ -11,7 +11,7 @@
own bootstrap files, or so that you can edit a bootstrap file produced by {\bf
Bacula}. However, normally the bootstrap file will be automatically created
for you during the
-\ilink{restore_command}{_ConsoleChapter} command in the Console program, or
+\ilink{restore-command}{_ConsoleChapter} command in the Console program, or
by using a
\ilink{ Write Bootstrap}{writebootstrap} record in your Backup
Jobs, and thus you will never need to know the details of this file.
diff -Nur bacula-doc-1.38.11.1.old/manual/catmaintenance.tex
bacula-doc-1.38.11.1/manual/catmaintenance.tex
--- bacula-doc-1.38.11.1.old/manual/catmaintenance.tex 2006-04-14
19:08:57.000000000 +0200
+++ bacula-doc-1.38.11.1/manual/catmaintenance.tex 2006-07-28
18:17:44.000000000 +0200
@@ -199,7 +199,7 @@
in the time to insert or search for records.
For each of the databases, you may get significant improvements by adding
-additional indexes. The comments in the Bacula make_xxx_tables give some
+additional indexes. The comments in the Bacula make\_xxx\_tables give some
indications as to what indexes may be appropriate. Please see below
for specific instructions on checking indexes.
@@ -226,9 +226,9 @@
There is also a PostgreSQL FAQ question number 3.3 that may
answer some of your questions about how to improve performance
of the PostgreSQL engine:
-\elink{
+\href{
http://www.postgresql.org/docs/faqs.FAQ.html#3.3}
-{http://www.postgresql.org/docs/faqs.FAQ.html#3.3}.
+{http://www.postgresql.org/docs/faqs.FAQ.html\#3.3}.
\subsection*{Performance Issues Indexes}
diff -Nur bacula-doc-1.38.11.1.old/manual/configure.tex
bacula-doc-1.38.11.1/manual/configure.tex
--- bacula-doc-1.38.11.1.old/manual/configure.tex 2005-11-04
19:26:00.000000000 +0100
+++ bacula-doc-1.38.11.1/manual/configure.tex 2006-07-28 18:13:37.000000000
+0200
@@ -113,7 +113,7 @@
\index[general]{Including other Configuration Files }
\index[general]{Files!Including other Configuration }
\index[general]{Using @ to include other files}
-\index[gener...@{\bf filename}}
+\index[genera...@{\bf filename}}
\addcontentsline{toc}{subsubsection}{Including other Configuration Files}
If you wish to break your configuration file into smaller pieces, you can do
diff -Nur bacula-doc-1.38.11.1.old/manual/console.tex
bacula-doc-1.38.11.1/manual/console.tex
--- bacula-doc-1.38.11.1.old/manual/console.tex 2006-06-29 09:09:53.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/console.tex 2006-07-28 18:15:03.000000000
+0200
@@ -810,7 +810,7 @@
configuration while Bacula is running, it is advisable to restart the
Director at the next convenient opportunity.
-\label{restore_command}
+\label{restore-command}
\item [restore]
\index[console]{restore}
The restore command allows you to select one or more Jobs (JobIds) to be
diff -Nur bacula-doc-1.38.11.1.old/manual/dirdconf.tex
bacula-doc-1.38.11.1/manual/dirdconf.tex
--- bacula-doc-1.38.11.1.old/manual/dirdconf.tex 2006-06-05
23:37:58.000000000 +0200
+++ bacula-doc-1.38.11.1/manual/dirdconf.tex 2006-07-28 18:15:54.000000000
+0200
@@ -333,7 +333,7 @@
\item [Enabled = \lt{}yes|no\gt{}]
\index[dir]{Enable}
- \index[dir]Directive!Enable}
+ \index[dir]{Directive!Enable}
This directive allows you to enable or disable automatic execution
via the scheduler of a Job.
diff -Nur bacula-doc-1.38.11.1.old/manual/fdl.tex
bacula-doc-1.38.11.1/manual/fdl.tex
--- bacula-doc-1.38.11.1.old/manual/fdl.tex 2006-06-05 23:37:58.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/fdl.tex 2006-07-28 18:20:09.000000000 +0200
@@ -1,17 +1,17 @@
%---------The file header---------------------------------------------
-\usepackage[english]{babel} %language selection
-\usepackage[T1]{fontenc}
+% \usepackage[english]{babel} %language selection
+% \usepackage[T1]{fontenc}
\pagenumbering{arabic}
-\usepackage{hyperref}
-\hypersetup{colorlinks,
- citecolor=black,
- filecolor=black,
- linkcolor=black,
- urlcolor=black,
- pdftex}
+% \usepackage{hyperref}
+% \hypersetup{colorlinks,
+% citecolor=black,
+% filecolor=black,
+% linkcolor=black,
+% urlcolor=black,
+% pdftex}
%---------------------------------------------------------------------
@@ -20,7 +20,7 @@
\index[general]{License!GNU ree Documentation}
\addcontentsline{toc}{section}{GNU ree Documentation License}
-%\label{label_fdl}
+\label{label-fdl}
\begin{center}
diff -Nur bacula-doc-1.38.11.1.old/manual/fileset.tex
bacula-doc-1.38.11.1/manual/fileset.tex
--- bacula-doc-1.38.11.1.old/manual/fileset.tex 2006-04-18 12:11:38.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/fileset.tex 2006-07-28 18:21:34.000000000
+0200
@@ -327,7 +327,7 @@
explicitly name each filesystem you want backed up. Explicitly naming the
filesystems you want backed up avoids the possibility of getting into a
infinite loop recursing filesystems. Another possibility is to
- use {\bf onefs=no} and to set {\bs fstype=ext2, ...}.
+ use {\bf onefs=no} and to set {\bf fstype=ext2, ...}.
See the example below for more details.
If you think that Bacula should be backing up a particular directory
diff -Nur bacula-doc-1.38.11.1.old/manual/install.tex
bacula-doc-1.38.11.1/manual/install.tex
--- bacula-doc-1.38.11.1.old/manual/install.tex 2006-06-29 18:20:01.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/install.tex 2006-07-28 18:22:03.000000000
+0200
@@ -306,10 +306,10 @@
\item Create the Bacula MySQL database and tables
(if using MySQL)
- \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or
+ \ilink{Installing and Configuring MySQL Phase II}{mysql-phase2} or
create the Bacula PostgreSQL database and tables
\ilink{Installing and Configuring PostgreSQL Phase
- II}{PostgreSQL_phase2} or alternatively if you are using
+ II}{PostgreSQL-phase2} or alternatively if you are using
SQLite
\ilink{Installing and Configuring SQLite Phase II}{phase2}.
diff -Nur bacula-doc-1.38.11.1.old/manual/messagesres.tex
bacula-doc-1.38.11.1/manual/messagesres.tex
--- bacula-doc-1.38.11.1.old/manual/messagesres.tex 2005-12-22
13:28:53.000000000 +0100
+++ bacula-doc-1.38.11.1/manual/messagesres.tex 2006-07-28 18:22:53.000000000
+0200
@@ -63,7 +63,6 @@
message generated by {\bf Bacula} ({\bf ERROR}, {\bf WARNING}, {\bf FATAL},
...), and {\bf address} varies according to the {\bf destination} keyword, but
is typically an email address or a filename.
-\end{description}
The following are the list of the possible record definitions that can be used
in a message resource.
@@ -138,7 +137,8 @@
\item [\lt{}destination\gt{} = \lt{}message-type1\gt{},
\lt{}message-type2\gt{}, ...]
\index[fd]{\lt{}destination\gt{}}
-
+ \end{description}
+
Where {\bf destination} may be one of the following:
\begin{description}
@@ -187,8 +187,8 @@
\index[fd]{syslog}
Send the message to the system log (syslog) using the facility specified in
the {\bf address} field. Note, for the moment, the {\bf address} field is
- ignored and the message is always sent to the LOG_DAEMON facility with
- level LOG_ERR. See {\bf man 3 syslog} for more details. Example:
+ ignored and the message is always sent to the LOG\_DAEMON facility with
+ level LOG\_ERR. See {\bf man 3 syslog} for more details. Example:
\begin{verbatim}
syslog = all, !skipped, !saved
\end{verbatim}
@@ -223,7 +223,8 @@
separated list in the {\bf address} field. This is similar to {\bf
mail} above, except that each message is sent as received. Thus there
is one email per message. This is most useful for {\bf mount} messages
- (see below). \end{description}
+ (see below).
+\end{description}
For any destination, the {\bf message-type} field is a comma separated
list of the following types or classes of messages:
diff -Nur bacula-doc-1.38.11.1.old/manual/mysql.tex
bacula-doc-1.38.11.1/manual/mysql.tex
--- bacula-doc-1.38.11.1.old/manual/mysql.tex 2006-02-06 14:51:32.000000000
+0100
+++ bacula-doc-1.38.11.1/manual/mysql.tex 2006-07-28 18:23:42.000000000
+0200
@@ -117,7 +117,7 @@
second phase of the MySQL installation are created during the Bacula
Installation.
-\label{mysql_phase2}
+\label{mysql-phase2}
\subsection*{Installing and Configuring MySQL -- Phase II}
\index[general]{Installing and Configuring MySQL -- Phase II }
\index[general]{Phase II!Installing and Configuring MySQL -- }
diff -Nur bacula-doc-1.38.11.1.old/manual/postgresql.tex
bacula-doc-1.38.11.1/manual/postgresql.tex
--- bacula-doc-1.38.11.1.old/manual/postgresql.tex 2006-06-27
10:33:51.000000000 +0200
+++ bacula-doc-1.38.11.1/manual/postgresql.tex 2006-07-28 18:24:58.000000000
+0200
@@ -52,7 +52,7 @@
to complete the installation. Please note, the installation files used in the
second phase of the PostgreSQL installation are created during the Bacula
Installation.
-\label{PostgreSQL_phase2}
+\label{PostgreSQL-phase2}
\subsection*{Installing and Configuring PostgreSQL -- Phase II}
\index[general]{Phase II!Installing and Configuring PostgreSQL -- }
@@ -143,7 +143,7 @@
\normalsize
Also, I had an authorization problem with the password. In the end,
-I had to modify my {\bf pg_hba.conf} file (in /var/lib/pgsql/data on my
machine)
+I had to modify my {\bf pg\_hba.conf} file (in /var/lib/pgsql/data on my
machine)
from:
\footnotesize
@@ -159,7 +159,7 @@
my regression scripts without having a password.
A more secure way to perform database authentication is with md5
-password hashes. Begin by editing the {\bf pg_hba.conf} file, and
+password hashes. Begin by editing the {\bf pg\_hba.conf} file, and
just prior the the existing ``local'' and ``host'' lines, add the line:
\footnotesize
diff -Nur bacula-doc-1.38.11.1.old/manual/progs.tex
bacula-doc-1.38.11.1/manual/progs.tex
--- bacula-doc-1.38.11.1.old/manual/progs.tex 2006-04-14 19:08:57.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/progs.tex 2006-07-28 18:25:40.000000000
+0200
@@ -963,7 +963,7 @@
If you are getting incorrect dates (e.g. 1970) and you are
running with a non-English language setting, you might try adding
-a LANG="en_US" immediately before the bsmtp call.
+a LANG="en\_US" immediately before the bsmtp call.
\subsection*{dbcheck}
\label{dbcheck}
diff -Nur bacula-doc-1.38.11.1.old/manual/python.tex
bacula-doc-1.38.11.1/manual/python.tex
--- bacula-doc-1.38.11.1.old/manual/python.tex 2006-06-27 10:33:51.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/python.tex 2006-07-28 18:26:45.000000000
+0200
@@ -356,7 +356,7 @@
It is because the DirStartUp script is calling a dynamically loaded
module (timemodule.so in the above case) that then tries to use
Python functions exported from the Python interpreter (in this case
-PyInt_FromLong). The way Bacula is currently linked with Python does
+PyInt\_FromLong). The way Bacula is currently linked with Python does
not permit this. The solution to the problem is to put such functions
(in this case the import of time into a separate Python script, which
will do your calculations and return the values you want. Then call
diff -Nur bacula-doc-1.38.11.1.old/manual/rescuefloppy.tex
bacula-doc-1.38.11.1/manual/rescuefloppy.tex
--- bacula-doc-1.38.11.1.old/manual/rescuefloppy.tex 2005-08-03
21:26:45.000000000 +0200
+++ bacula-doc-1.38.11.1/manual/rescuefloppy.tex 2006-07-28
18:28:07.000000000 +0200
@@ -319,7 +319,7 @@
/mnt/drive/. This is used just before running the statically linked Bacula so
that it can access your drives for the restore.
-\item [restore\_bacula]
+\item [restore-bacula]
\index[fd]{restore\_bacula }
This script will restore the File daemon from the Bacula Rescue disk.
Building the Bacula Rescue disk will be described later. This will provide
diff -Nur bacula-doc-1.38.11.1.old/manual/rescue.tex
bacula-doc-1.38.11.1/manual/rescue.tex
--- bacula-doc-1.38.11.1.old/manual/rescue.tex 2006-01-17 10:36:36.000000000
+0100
+++ bacula-doc-1.38.11.1/manual/rescue.tex 2006-07-28 18:29:14.000000000
+0200
@@ -282,7 +282,7 @@
\end{verbatim}
\normalsize
-For example a {\bf kernel-version} might be 2.6.14-1.1653_FC4.
+For example a {\bf kernel-version} might be 2.6.14-1.1653\_FC4.
For users of the bacula-rescue rpm the static bacula-fd has already been built
@@ -388,7 +388,7 @@
\end{verbatim}
\normalsize
-The rpm_release file prevents the "make bacula" from attempting to
+The rpm\_release file prevents the "make bacula" from attempting to
build or copy a File daemon, so that you can do it before the
"make iso" step. Once "make iso" is run, you can no longer add
anything to the in-memory part of the image. You can still add
@@ -487,7 +487,7 @@
made and burned the CDROM for client1, which of course, contains the client2
data.
-\label{restore_client}
+\label{restore-client}
\subsection*{Restoring a Client System}
\index[general]{Restoring a Client System}
\index[general]{System!Restoring a Client}
@@ -765,7 +765,7 @@
Note, I've had quite a number of problems with {\bf grub} because it is rather
complicated and not designed to install easily under a simplified system.
-In fact, the ./run_grub script is not going to work on most 2.6 kernels
+In fact, the ./run\_grub script is not going to work on most 2.6 kernels
with the latest grub, because grub-install references /usr/share/grub/...
and it uses /dev/pts, which will not be in /dev if you are using udev (as
do many 2.6 kernels).
@@ -791,7 +791,7 @@
Note, in this case, you omit the chroot command, and you must
replace /dev/hda with your boot device. If you don't know what your
-boot device is, run the ./run_grub script once and it will tell
+boot device is, run the ./run\_grub script once and it will tell
you.
@@ -806,7 +806,7 @@
If everything went well, you should now be back up and running. If not,
re-insert the emergency boot CDROM, boot, and figure out what is wrong.
-\label{restore_server}
+\label{restore-server}
\subsection*{Restoring a Server}
\index[general]{Restoring a Server}
\index[general]{Server!Restoring a}
@@ -861,7 +861,7 @@
\end{itemize}
For additional details of restoring your database, please see the
-\ilink{Restoring When Things Go Wrong}{database_restore} section
+\ilink{Restoring When Things Go Wrong}{database-restore} section
of the Console Restore Command chapter of this manual.
diff -Nur bacula-doc-1.38.11.1.old/manual/restore.tex
bacula-doc-1.38.11.1/manual/restore.tex
--- bacula-doc-1.38.11.1.old/manual/restore.tex 2006-06-05 23:37:58.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/restore.tex 2006-07-28 18:29:36.000000000
+0200
@@ -936,7 +936,7 @@
This command is the same as the {\bf help} command.
\end{description}
-\label{database_restore}
+\label{database-restore}
\subsection*{Restoring When Things Go Wrong}
\index[general]{Restoring When Things Go Wrong }
\index[general]{Restoring Your Database}
@@ -947,8 +947,8 @@
problems that can come up making restoring more difficult. I'll try to
provide a few ideas how to get out of these problem situations.
In addition to what is presented here, there is more specific information
-on restoring a \ilink{Client}{restore_client} and your
-\ilink{Server}{restore_server} in the \ilink{Disaster Recovery Using
+on restoring a \ilink{Client}{restore-client} and your
+\ilink{Server}{restore-server} in the \ilink{Disaster Recovery Using
Bacula}{_ChapterRescue} chapter of this manual.
\begin{description}
diff -Nur bacula-doc-1.38.11.1.old/manual/rpm-faq.tex
bacula-doc-1.38.11.1/manual/rpm-faq.tex
--- bacula-doc-1.38.11.1.old/manual/rpm-faq.tex 2006-06-04 17:30:14.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/rpm-faq.tex 2006-07-28 18:30:13.000000000
+0200
@@ -177,12 +177,12 @@
To avoid this do not package the examples directory. If you are seeing this
problem you are building a very old bacula package as the examples have
been
removed from the doc packaging.
-\end{enumerate}
-\item {\bf Support for RHEL3/4, CentOS 3/4 and x86_64}
+
+\item {\bf Support for RHEL3/4, CentOS 3/4 and x86\_64}
The examples below show
explicit build support for RHEL4 and CentOS 4. Build support
- for x86_64 has also been added. Test builds have been done on CentOS but
+ for x86\_64 has also been added. Test builds have been done on CentOS but
not RHEL4.
\footnotesize
@@ -209,6 +209,7 @@
For 64 bit support add '--define "build_x86_64 1"'
\end{verbatim}
\normalsize
+\end{enumerate}
\subsection*{Build Options}
\index[general]{Build Options}
diff -Nur bacula-doc-1.38.11.1.old/manual/tapetesting.tex
bacula-doc-1.38.11.1/manual/tapetesting.tex
--- bacula-doc-1.38.11.1.old/manual/tapetesting.tex 2006-05-04
15:20:12.000000000 +0200
+++ bacula-doc-1.38.11.1/manual/tapetesting.tex 2006-07-28 18:31:58.000000000
+0200
@@ -1122,13 +1122,13 @@
skipped. File number is always tracked for MTEOM.
Linux does support both SCSI SPACE Filemarks and End-of-data: When MTEOM
- is called in MT_ST_FAST_MTEOM mode, SCSI SPACE End-of-data is used.
+ is called in MT\_ST\_FAST\_MTEOM mode, SCSI SPACE End-of-data is used.
In the other case, SCSI SPACE Filemarks with count =
8388607 is used.
There is no real slow mode like in Solaris - I just expect, that for
older tape drives Filemarks may be slower than End-of-data, but not so
much as in Solaris slow mode. File number is tracked for MTEOM just
- without MT_ST_FAST_MTEOM - when MT_ST_FAST_MTEOM is used, it is not.
+ without MT\_ST\_FAST\_MTEOM - when MT\_ST\_FAST\_MTEOM is used, it is not.
FreeBSD does support both SCSI SPACE Filemarks and End-of-data, but when
MTEOD (MTEOM) is called, SCSI SPACE End-of-data is always used. FreeBSD
diff -Nur bacula-doc-1.38.11.1.old/manual/tips.tex
bacula-doc-1.38.11.1/manual/tips.tex
--- bacula-doc-1.38.11.1.old/manual/tips.tex 2006-06-05 23:37:58.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/tips.tex 2006-07-28 18:32:27.000000000
+0200
@@ -50,7 +50,7 @@
overwrite them providing that you do not do a {\bf make uninstall}.
If the new version of Bacula requires an upgrade to the database,
-you can upgrade it with the script {\bf update_bacula_tables}, which
+you can upgrade it with the script {\bf update\_bacula\_tables}, which
will be installed in your scripts directory (default {\bf /etc/bacula}),
or alternatively, you can find it in the
{\bf \lt{}bacula-source\gt{}/src/cats} directory.
diff -Nur bacula-doc-1.38.11.1.old/manual/win32.tex
bacula-doc-1.38.11.1/manual/win32.tex
--- bacula-doc-1.38.11.1.old/manual/win32.tex 2006-06-27 10:33:51.000000000
+0200
+++ bacula-doc-1.38.11.1/manual/win32.tex 2006-07-28 18:34:35.000000000
+0200
@@ -464,7 +464,7 @@
\normalsize
In the above Job Report listing, you see that the VSS snapshot was generated
for drive C (if
other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You
also see the
-reports from each of the writer program. Here they all report VSS_WS_STABLE,
which means
+reports from each of the writer program. Here they all report
VSS\_WS\_STABLE, which means
that you will get a consistent snapshot of the data handled by that writer.
\subsection*{VSS Problems}
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.16-2-686
Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15)
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
--- End Message ---
