From 3ce12b68f0f10e4be097bbc8a202c543f75c4baa Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Mon, 4 May 2009 17:07:00 +0000 Subject: [PATCH] Updates --- docs/manuals/en/catalog/Makefile.in | 3 +- docs/manuals/en/catalog/catalog.tex | 4 - docs/manuals/en/concepts/Makefile.in | 3 +- docs/manuals/en/concepts/concepts.tex | 4 - docs/manuals/en/concepts/newfeatures.tex | 22 ++- docs/manuals/en/console/Makefile.in | 3 +- docs/manuals/en/console/console.tex | 4 - docs/manuals/en/developers/Makefile.in | 3 +- docs/manuals/en/developers/developers.tex | 29 ++-- docs/manuals/en/developers/generaldevel.tex | 142 +++++++++++--------- docs/manuals/en/install/Makefile.in | 3 +- docs/manuals/en/install/fileset.tex | 23 ++++ docs/manuals/en/install/install.tex | 4 - docs/manuals/en/problems/Makefile.in | 3 +- docs/manuals/en/problems/problems.tex | 4 - docs/manuals/en/utility/Makefile.in | 2 + docs/manuals/en/utility/rpm-faq.tex | 21 ++- docs/manuals/en/utility/utility.kilepr | 12 +- docs/manuals/en/utility/utility.tex | 4 - 19 files changed, 171 insertions(+), 122 deletions(-) diff --git a/docs/manuals/en/catalog/Makefile.in b/docs/manuals/en/catalog/Makefile.in index 76d1c0cd..279cad47 100644 --- a/docs/manuals/en/catalog/Makefile.in +++ b/docs/manuals/en/catalog/Makefile.in @@ -78,7 +78,7 @@ html: latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \ -init_file latex2html-init.pl ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}.html - cp ${IMAGES}/bacula-logo.png ${DOC} + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making html" web: @@ -94,6 +94,7 @@ web: latex2html -split 3 -local_icons -t "Bacula Catalog Database Guide" -long_titles 4 \ -toc_stars -contents_in_nav -init_file latex2html-init.pl -white -notransparent ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}/Bacula_Catalo*.html + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making web" show: xdvi ${DOC} diff --git a/docs/manuals/en/catalog/catalog.tex b/docs/manuals/en/catalog/catalog.tex index d98d70a5..0e5723de 100644 --- a/docs/manuals/en/catalog/catalog.tex +++ b/docs/manuals/en/catalog/catalog.tex @@ -65,10 +65,6 @@ \clearpage \tableofcontents \clearpage -\listoffigures -\clearpage -\listoftables -\clearpage \include{catmaintenance} \include{mysql} diff --git a/docs/manuals/en/concepts/Makefile.in b/docs/manuals/en/concepts/Makefile.in index 6642d6e1..11ab7a6c 100644 --- a/docs/manuals/en/concepts/Makefile.in +++ b/docs/manuals/en/concepts/Makefile.in @@ -82,7 +82,7 @@ html: latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \ -init_file latex2html-init.pl ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}.html - cp ${IMAGES}/bacula-logo.png ${DOC} + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making html" web: @@ -98,6 +98,7 @@ web: latex2html -split 3 -local_icons -t "Bacula Concepts and Overview Guide" -long_titles 4 \ -toc_stars -contents_in_nav -init_file latex2html-init.pl -white -notransparent ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}/Bacula_Concep_Overvi_Guide.html + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making web" show: xdvi ${DOC} diff --git a/docs/manuals/en/concepts/concepts.tex b/docs/manuals/en/concepts/concepts.tex index 3d7bd17a..5a3d9b11 100644 --- a/docs/manuals/en/concepts/concepts.tex +++ b/docs/manuals/en/concepts/concepts.tex @@ -72,10 +72,6 @@ \pagenumbering{roman} \tableofcontents \clearpage -\listoffigures -\clearpage -\listoftables -\clearpage \pagestyle{myheadings} \markboth{Bacula Version \version}{Bacula Version \version} diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex index 4d7d2a2e..f4fb5610 100644 --- a/docs/manuals/en/concepts/newfeatures.tex +++ b/docs/manuals/en/concepts/newfeatures.tex @@ -28,12 +28,16 @@ backup, there is no difference, but for {\bf Differential} and {\bf backed up, and the File daemon will use that list to determine if any new files have been added or or moved and if any files have been deleted. This allows Bacula to make an accurate backup of your system to that point in time so that -if you do a restore, it will restore your system exactly. One note of caution +if you do a restore, it will restore your system exactly. + +One note of caution about using Accurate backup is that it requires more resources (CPU and memory) on both the Director and the Client machines to create the list of previous files backed up, to send that list to the File daemon, for the File daemon to keep the list (possibly very big) in memory, and for the File daemon to do -comparisons between every file in the FileSet and the list. +comparisons between every file in the FileSet and the list. In particular, +if your client has lots of files (more than a few million), you will need +lots of memory on the client machine. Accurate must not be enabled when backing up with a plugin that is not specially designed to work with Accurate. If you enable it, your restores @@ -336,7 +340,8 @@ which has a version number to permit running multiple versions of the libraries if desired (not normally the case). If you have problems with libtool or you wish to use the old -way of building static libraries, you can do so by disabling +way of building static libraries, or you want to build a static +version of Bacula you may disable libtool on the configure command line with: \begin{verbatim} @@ -344,6 +349,17 @@ libtool on the configure command line with: \end{verbatim} +\section{Building Static versions of Bacula} +\index[general]{Static linking} +In order to build static versions of Bacula, in addition +to configuration options that were needed you now must +also add --disable-libtool. Example + +\begin{verbatim} + ./configure --enable-static-client-only --disable-libtool +\end{verbatim} + + \section{Virtual Backup (Vbackup)} \index[general]{Virtual Backup} \index[general]{Vbackup} diff --git a/docs/manuals/en/console/Makefile.in b/docs/manuals/en/console/Makefile.in index 899a3e7e..be059cb2 100644 --- a/docs/manuals/en/console/Makefile.in +++ b/docs/manuals/en/console/Makefile.in @@ -78,7 +78,7 @@ html: latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \ -init_file latex2html-init.pl ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}.html - cp ${IMAGES}/bacula-logo.png ${DOC} + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making html" web: @@ -94,6 +94,7 @@ web: latex2html -split 3 -local_icons -t "Bacula Console and Operators Guide" -long_titles 4 \ -toc_stars -contents_in_nav -init_file latex2html-init.pl -white -notransparent ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}/Bacula_Consol*.html + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making web" show: xdvi ${DOC} diff --git a/docs/manuals/en/console/console.tex b/docs/manuals/en/console/console.tex index 63f3a324..28850d69 100644 --- a/docs/manuals/en/console/console.tex +++ b/docs/manuals/en/console/console.tex @@ -65,10 +65,6 @@ \clearpage \tableofcontents \clearpage -\listoffigures -\clearpage -\listoftables -\clearpage \include{bconsole} \include{gui} diff --git a/docs/manuals/en/developers/Makefile.in b/docs/manuals/en/developers/Makefile.in index 7e069991..b565d792 100644 --- a/docs/manuals/en/developers/Makefile.in +++ b/docs/manuals/en/developers/Makefile.in @@ -55,7 +55,7 @@ html: latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \ ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}.html - cp ${IMAGES}/bacula-logo.png ${DOC} + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @rm -f *.eps *.gif *.jpg *.old web: @@ -79,6 +79,7 @@ web: @rm -f ${DOC}/win32-*.png ${DOC}/wx-console*.png ${DOC}/xp-*.png @rm -f ${DOC}/*.pl ${DOC}/*.log ${DOC}/*.aux ${DOC}/*.idx @rm -f ${DOC}/*.out WARNINGS + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) texcheck: ./check_tex.pl ${DOC}.tex diff --git a/docs/manuals/en/developers/developers.tex b/docs/manuals/en/developers/developers.tex index e390abe9..9fdf26c1 100644 --- a/docs/manuals/en/developers/developers.tex +++ b/docs/manuals/en/developers/developers.tex @@ -1,7 +1,12 @@ %% %% +%% The following characters must be preceded by a backslash +%% to be entered as printable characters: +%% +%% # $ % & ~ _ ^ \ { } +%% -\documentclass[10pt,a4paper]{report} +\documentclass[10pt,a4paper]{book} \topmargin -0.5in \oddsidemargin 0.0in @@ -9,6 +14,7 @@ \textheight 10in \textwidth 6.5in + \usepackage{html} \usepackage{float} \usepackage{graphicx} @@ -18,10 +24,14 @@ \usepackage{index} \usepackage{setspace} \usepackage{hyperref} +% \usepackage[linkcolor=black,colorlinks=true]{hyperref} \usepackage{url} - \makeindex +\newindex{dir}{ddx}{dnd}{Director Index} +\newindex{fd}{fdx}{fnd}{File Daemon Index} +\newindex{sd}{sdx}{snd}{Storage Daemon Index} +\newindex{console}{cdx}{cnd}{Console Index} \newindex{general}{idx}{ind}{General Index} \sloppy @@ -34,7 +44,7 @@ \parindent 0pt \title{\includegraphics{\idir bacula-logo.eps} \\ \bigskip - \Huge{Developers' Guide} + \Huge{Bacula}$^{\normalsize \textregistered}$ \Huge{Developer's Guide} \begin{center} \large{It comes in the night and sucks the essence from your computers. } @@ -44,10 +54,11 @@ \author{Kern Sibbald} \date{\vspace{1.0in}\today \\ - This manual documents Bacula version \input{version} \\ + This manual documents Bacula version \fullversion \\ \vspace{0.2in} - Copyright \copyright 1999-2009, Free Software Foundation Europe + Copyright {\copyright} 1999-2009, Free Software Foundation Europe e.V. \\ + Bacula {\textregistered} is a registered trademark of Kern Sibbald.\\ \vspace{0.2in} 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; @@ -55,16 +66,12 @@ A copy of the license is included in the section entitled "GNU Free Documentation License". } - \maketitle \clearpage +\pagenumbering{roman} \tableofcontents -\clearpage -\listoffigures -\clearpage -\listoftables -\clearpage + \include{generaldevel} \include{platformsupport} diff --git a/docs/manuals/en/developers/generaldevel.tex b/docs/manuals/en/developers/generaldevel.tex index 37d55ee9..098ec143 100644 --- a/docs/manuals/en/developers/generaldevel.tex +++ b/docs/manuals/en/developers/generaldevel.tex @@ -7,25 +7,32 @@ \index{Notes!Bacula Developer} \addcontentsline{toc}{section}{Bacula Developer Notes} -This document is intended mostly for developers and describes the the general +This document is intended mostly for developers and describes how you can +contribute to the Bacula project and the the general framework of making Bacula source changes. \subsection{Contributions} \index{Contributions} \addcontentsline{toc}{subsubsection}{Contributions} -Contributions from programmers are broken into two groups. The first are -contributions that are aids and not essential to Bacula. In general, these -will be scripts or will go into and examples or contributions directory. -For these kinds of non-essential contributions there is no obligation to do -a copyright assignment as described below. However, a copyright assignment -would still be appreciated. +Contributions to the Bacula project come in many forms: ideas, +participation in helping people on the bacula-users email list, +packaging Bacula binaries for the community, helping improve +the documentation, and submitting code. + +Contributions in the form of submissions for inclusion in the project are +broken into two groups. The first are contributions that are aids and not +essential to Bacula. In general, these will be scripts or will go into and +examples or contributions directory. For these kinds of non-essential +contributions there is no obligation to do a copyright assignment as +described below. However, a copyright assignment would still be +appreciated. The second class of contributions are those which will be integrated with -Bacula and become an essential part. Within this class of contributions, there -are two hurdles to surmount. One is getting your patch accepted, and two is -dealing with copyright issues. The following text describes some of the -requirements for such code. +Bacula and become an essential part (code, scripts, documentation, ...) +Within this class of contributions, there are two hurdles to surmount. One +is getting your patch accepted, and two is dealing with copyright issues. +The following text describes some of the requirements for such code. \subsection{Patches} \index{Patches} @@ -33,8 +40,8 @@ requirements for such code. Subject to the copyright assignment described below, your patches should be sent in {\bf diff -u} format relative to the current contents of the Source -Forge SVN, which is the easiest to understand and integrate. -Please be sure to use the Bacula indenting standard (see below). +Forge SVN. The diff -u format is the easiest for us to understand and integrate. +Please be sure to use the Bacula indenting standard (see below) for source code. If you have checked out the source with SVN, you can get a diff using: \begin{verbatim} @@ -44,7 +51,7 @@ svn diff > change.patch If you plan on doing significant development work over a period of time, after having your first patch reviewed and approved, you will be eligible -for having developer SVN access so that you can commit your changes +for having developer SVN write access so that you can commit your changes directly to the SVN repository. To do so, you will need a userid on Source Forge. @@ -61,23 +68,25 @@ November 2004, the code was copyrighted by Kern Sibbald and John Walker. After November 2004, the code was copyrighted by Kern Sibbald, then on the 15th of November 2006, the copyright was transferred to the Free Software Foundation Europe e.V. +In signing the FLA and transferring the copyright, you retain the +right to use the code you have submitted as you want. Your name should be clearly indicated as the author of the code, and you -must be extremely careful not to violate any copyrights or use other +must be extremely careful not to violate any copyrights or patents or use other people's code without acknowledging it. The purpose of this requirement is to avoid future copyright, patent, or intellectual property problems. -Please read the LICENSE agreement in the main source code +Please read the LICENSE agreement in the main Bacula source code directory. When you sign the Fiduciary License Agreement (FLA) and send it in, you are argeeing to the terms of that LICENSE file. -To understand the possible source of future problems, please -examine the difficulties Mozilla is (was?) having finding +If you don't understand what we mean by future problems, please +examine the difficulties Mozilla was having finding previous contributors at \elink{ http://www.mozilla.org/MPL/missing.html} {http://www.mozilla.org/MPL/missing.html}. The other important issue is to -avoid copyright, patent, or intellectual property violations as are currently -(May 2003) being claimed by SCO against IBM. +avoid copyright, patent, or intellectual property violations as was +(May 2003) claimed by SCO against IBM. Although the copyright will be held by the Free Software Foundation Europe e.V., each developer is expected to indicate @@ -104,20 +113,19 @@ explicitly acknowledging that they do so in their first submission. This was sufficient if the developer is independent, or an employee of a not-for-profit organization or a university. However, in an effort to ensure that the Bacula code is really clean, beginning in August 2006, all -previous and future developers with SVN access will be asked to submit a +previous and future developers with SVN write access will be asked to submit a copyright assignment (or Fiduciary License Agreement -- FLA), which means you agree to the LICENSE in the main source directory. It also means that you receive back the right to use the code that you have submitted. Any developer who wants to contribute and is employed by a company should -either list the employer as the owner of the code, or get -explicit permission from him to sign the copyright assignment. -This is because in many -countries, all work that an employee does whether on company time or in the -employee's free time is considered to be Intellectual Property of the -company. Obtaining official approval or an FLA from the company will avoid -misunderstandings between the employee, the company, and the Bacula +either list the employer as the owner of the code, or get explicit +permission from him to sign the copyright assignment. This is because in +many countries, all work that an employee does whether on company time or +in the employee's free time is considered to be Intellectual Property of +the company. Obtaining official approval or an FLA from the company will +avoid misunderstandings between the employee, the company, and the Bacula project. A good number of companies have already followed this procedure. The Fiduciary License Agreement is posted on the Bacula web site at: @@ -137,7 +145,9 @@ It should be filled out, then sent to: Please note that the above address is different from the officially registered office mentioned in the document. When you send in such a -complete document, please notify me: kern at sibbald dot com. +complete document, please notify me: kern at sibbald dot com, and +please add your email address to the FLA so that I can contact you +to confirm reception of the signed FLA. \section{The Development Cycle} @@ -146,27 +156,27 @@ complete document, please notify me: kern at sibbald dot com. \addcontentsline{toc}{subsubsection}{Development Cycle} As I noted in the 1.38 ReleaseNotes, version 1.38 was different from prior -versions because it had a lot more contributions. I expect that this trend -will continue. As a consequence, I am going to modify how I normally do -development, and instead of making a list of all the features that I will -implement in the next version, I will personally sign up for one (maybe -two) projects at a time, and when they are complete, I will release a new +versions because it had a lot more contributions. We expect that this trend +will continue. As a consequence, we have modified how we do +development, and instead of making a list of all the features that we will +implement in the next version, each developer will sign up for one (maybe +two) projects at a time, and when they are complete, we will release a new version. -The difference is that I will have more time to review the new code that is +The difference is that we will have more time to review the new code that is being contributed, and will be able to devote more time to a smaller number -of projects (1.38 had too many new features for me to handle correctly). +of projects (1.38 had too many new features for us to handle correctly). -I expect that future release schedules will be much the same, and the +Future release schedules will be much the same, and the number of new features will also be much the same providing that the contributions continue to come -- and they show no signs of let up :-) \index{Feature Requests} {\bf Feature Requests:} \\ -In addition, I would like to "formalize" the feature requests a bit. +In addition, we would like to "formalize" the feature requests a bit. Instead of me maintaining an informal list of everything I run into -(kernstodo), I would like to maintain a "formal" list of projects. This +(kernstodo), we would like to maintain a "formal" list of projects. This means that all new feature requests, including those recently discussed on the email lists, must be formally submitted and approved. @@ -174,15 +184,15 @@ Formal submission of feature requests will take two forms: \\ 1. non-mandatory, but highly recommended is to discuss proposed new features on the mailing list.\\ 2. Formal submission of an Feature Request in a special format. -I'll give an example of this below, but you can also find it on the web +We'll give an example of this below, but you can also find it on the web site under "Support -\gt{} Feature Requests". Since it takes a bit of time to properly fill out a Feature Request form, you probably should check on the email list first. Once the Feature Request is received by the keeper of the projects list, it -will be sent to me, and I will either accept it, send it back -asking for clarification, send it to the email list asking for opinions, or -reject it. +will be sent to the Bacula project manager (Kern), and he will either +accept it, send it back asking for clarification, send it to the email list +asking for opinions, or reject it. If it is accepted, it will go in the "projects" file (a simple ASCII file) maintained in the main Bacula source directory. @@ -197,11 +207,12 @@ Acceptance of Feature Requests depends on several things: \\ 1. feedback from users. If it is negative, the Feature Request will probably not be accepted. \\ 2. the difficulty of the project. A project that is so -difficult that I cannot imagine finding someone to implement probably won't -be accepted. \\ +difficult that we cannot imagine finding someone to implement probably won't +be accepted. Obviously if you know how to implement it, don't hesitate +to put it in your Feature Request \\ 3. whether or not the Feature Request fits within the current stategy of Bacula (for example an Feature Request that requests changing the -tape to tar format would not be accepted, ...) +tape to tar format probably would not be accepted, ...). {\bf How Feature Requests are prioritized:}\\ Once an Feature Request is accepted, it needs to be implemented. If you @@ -213,13 +224,12 @@ for the next version, and by way of this email, we suggest that you send discuss and send in your Feature Requests for the next release. Please verify that the Feature Request is not in the current list (attached to this email). -Once users have had several weeks to submit Feature Requests, the keeper of the -projects list will -organize them, and request users to vote on them. This will allow fixing -prioritizing the Feature Requests. Having a priority is one thing, but -getting it implement is another thing -- we are hoping that the Bacula -community will take more responsibility for assuring the implementation of -accepted Feature Requests. +Once users have had several weeks to submit Feature Requests, the keeper of +the projects list will organize them, and request users to vote on them. +This will allow fixing prioritizing the Feature Requests. Having a +priority is one thing, but getting it implement is another thing -- we are +hoping that the Bacula community will take more responsibility for assuring +the implementation of accepted Feature Requests. Feature Request format: \begin{verbatim} @@ -286,13 +296,13 @@ Getting code implemented in Bacula works roughly as follows: \item There are growing numbers of contributions (very good). -\item Some contributions come in the form of relatively small patches, +\item Some contributions come in the form of relatively small patches, which Kern reviews, integrates, documents, tests, and maintains. \item All Bacula developers take full - responsibility for writing the code, posting as patches so that I can + responsibility for writing the code, posting as patches so that we can review it as time permits, integrating it at an appropriate time, - responding to my requests for tweaking it (name changes, ...), + responding to our requests for tweaking it (name changes, ...), document it in the code, document it in the manual (even though their mother tongue is not English), test it, develop and commit regression scripts, and answer in a timely fashion all bug reports -- @@ -301,10 +311,10 @@ Getting code implemented in Bacula works roughly as follows: This is a sustainable way of going forward with Bacula, and the direction that the project will be taking more and more. For example, in the past, we have had some very dedicated programmers - who did major projects. However, these + who did major projects. However, some of these programmers due to outside obligations (job responsibilities change of job, school duties, ...) could not continue to maintain the code. In - those cases, the code suffers from lack of maintenance, sometimes I + those cases, the code suffers from lack of maintenance, sometimes we patch it, sometimes not. In the end, the code gets dropped from the project (there are two such contributions that are heading in that direction). When ever possible, we would like to avoid this, and @@ -988,7 +998,7 @@ Code should have some documentation -- not a lot, but enough so that I can understand it. Look at the current code, and you will see that I document more than most, but am definitely not a fanatic. -I prefer simple linear code where possible. Gotos are strongly discouraged +We prefer simple linear code where possible. Gotos are strongly discouraged except for handling an error to either bail out or to retry some code, and such use of gotos can vastly simplify the program. @@ -1066,8 +1076,8 @@ so be conservative in your use of C++ features. \index{Indenting Standards} \addcontentsline{toc}{subsubsection}{Indenting Standards} -I cannot stand code indented 8 columns at a time. This makes the code -unreadable. Even 4 at a time uses a lot of space, so I have adopted indenting +We find it very hard to read code indented 8 columns at a time. +Even 4 at a time uses a lot of space, so we have adopted indenting 3 spaces at every level. Note, indention is the visual appearance of the source on the page, while tabbing is replacing a series of up to 8 spaces from a tab character. @@ -1099,8 +1109,7 @@ avoid generating too many lines, the first brace appears on the first line \end{verbatim} \normalsize -Just follow the convention in the code. Originally I indented case clauses -under a switch(), but now I prefer non-indented cases. +Just follow the convention in the code. For example we I prefer non-indented cases. \footnotesize \begin{verbatim} @@ -1236,6 +1245,11 @@ edit\_uint64()}. For example: \end{verbatim} \normalsize +Note: {\bf \%lld} is now permitted in Bacula code -- we have our +own printf routines which handle it correctly. The edit\_uint64() subroutine +can still be used if you wish, but over time, most of that old style will +be removed. + The edit buffer {\bf ed1} must be at least 27 bytes long to avoid overflow. See src/lib/edit.c for more details. If you look at the code, don't start screaming that I use {\bf lld}. I actually use subtle trick taught to me by @@ -1422,5 +1436,3 @@ the user a tip, but please politely refer him to the manual and the Getting Support page of www.bacula.org. - - diff --git a/docs/manuals/en/install/Makefile.in b/docs/manuals/en/install/Makefile.in index febdfe14..63152755 100644 --- a/docs/manuals/en/install/Makefile.in +++ b/docs/manuals/en/install/Makefile.in @@ -82,7 +82,7 @@ html: latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \ -init_file latex2html-init.pl ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}.html - cp ${IMAGES}/bacula-logo.png ${DOC} + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making html" web: @@ -98,6 +98,7 @@ web: latex2html -split 3 -local_icons -t "Bacula Installation and Configuration Guide" -long_titles 4 \ -toc_stars -contents_in_nav -init_file latex2html-init.pl -white -notransparent ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}/Bacula_Instal_Config_Guide.html + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making web" show: xdvi ${DOC} diff --git a/docs/manuals/en/install/fileset.tex b/docs/manuals/en/install/fileset.tex index 1a232af5..691bf6ee 100644 --- a/docs/manuals/en/install/fileset.tex +++ b/docs/manuals/en/install/fileset.tex @@ -806,6 +806,29 @@ Change: 2005-11-06 12:36:48.000000000 +0100 This option is not implemented in Win32 systems. +\item [DriveType=Windows-drive-type] +\index[dir]{DriveType} +\index[dir]{Directive!DriveType} + This option is effective only on Windows machines and is + somewhat similar to the Unix/Linux {\bf fstype} described + above, except that it allows you to select what Windows + drive types you want to allow. By default all drive + types are accepted. + + The permitted drivetype names are: + + removable, fixed, remote, cdrom, ramdisk + + You may have multiple Driveype directives, and thus permit matching + of multiple drive types within a single Options resource. If + the type specified on the drivetype directive does not match the + filesystem for a particular directive, that directory will not be + backed up. This directive can be used to prevent backing up + non-local filesystems. Normally, when you use this directive, you + would also set {\bf onefs=no} so that Bacula will traverse filesystems. + + This option is not implemented in Unix/Linux systems. + \item [hfsplussupport=yes|no] \index[dir]{hfsplussupport} diff --git a/docs/manuals/en/install/install.tex b/docs/manuals/en/install/install.tex index 18085001..f2c57c9a 100644 --- a/docs/manuals/en/install/install.tex +++ b/docs/manuals/en/install/install.tex @@ -69,10 +69,6 @@ \clearpage \tableofcontents \clearpage -\listoffigures -\clearpage -\listoftables -\clearpage \include{quickstart} \include{installation} diff --git a/docs/manuals/en/problems/Makefile.in b/docs/manuals/en/problems/Makefile.in index 9f91f53c..c2b3f06b 100644 --- a/docs/manuals/en/problems/Makefile.in +++ b/docs/manuals/en/problems/Makefile.in @@ -78,7 +78,7 @@ html: latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \ -init_file latex2html-init.pl ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}.html - cp ${IMAGES}/bacula-logo.png ${DOC} + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making html" web: @@ -94,6 +94,7 @@ web: latex2html -split 3 -local_icons -t "Bacula Problem Resolution Guide" -long_titles 4 \ -toc_stars -contents_in_nav -init_file latex2html-init.pl -white -notransparent ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}/Bacula_Proble*.html + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making web" show: xdvi ${DOC} diff --git a/docs/manuals/en/problems/problems.tex b/docs/manuals/en/problems/problems.tex index 77d146be..2633255c 100644 --- a/docs/manuals/en/problems/problems.tex +++ b/docs/manuals/en/problems/problems.tex @@ -65,10 +65,6 @@ \clearpage \tableofcontents \clearpage -\listoffigures -\clearpage -\listoftables -\clearpage \include{faq} \include{tips} diff --git a/docs/manuals/en/utility/Makefile.in b/docs/manuals/en/utility/Makefile.in index 9b810300..b37abf39 100644 --- a/docs/manuals/en/utility/Makefile.in +++ b/docs/manuals/en/utility/Makefile.in @@ -79,6 +79,7 @@ html: -init_file latex2html-init.pl ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}.html cp ${IMAGES}/bacula-logo.png ${DOC} + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making html" web: @@ -94,6 +95,7 @@ web: latex2html -split 3 -local_icons -t "Bacula Utility Programs" -long_titles 4 \ -toc_stars -contents_in_nav -init_file latex2html-init.pl -white -notransparent ${DOC} >tex.out 2>&1 ./translate_images.pl --to_meaningful_names ${DOC}/Bacula_Utilit*.html + (cd ${DOC}; for i in *.png ; do cp -fp ../${IMAGES}/$${i} .; done) @echo "Done making web" show: xdvi ${DOC} diff --git a/docs/manuals/en/utility/rpm-faq.tex b/docs/manuals/en/utility/rpm-faq.tex index e880efc4..e0d89071 100644 --- a/docs/manuals/en/utility/rpm-faq.tex +++ b/docs/manuals/en/utility/rpm-faq.tex @@ -39,11 +39,18 @@ \item \label{faq1} {\bf How do I build Bacula for platform xxx?} - The bacula spec file contains defines to build for several platforms: - Red Hat 7.x (rh7), Red Hat 8.0 (rh8), Red Hat 9 (rh9), Fedora Core (fc1, - fc3, fc4, fc5, fc6, fc7, fc8), Whitebox Enterprise Linux 3.0 (wb3), Red Hat Enterprise Linux - (rhel3, rhel4, rhel5), Mandrake 10.x (mdk), Mandriva 2006.x (mdv) CentOS (centos3, centos4, centos5) - Scientific Linux (sl3, sl4, sl5) and SuSE (su9, su10, su102, su103, su110). The package build is controlled by a mandatory define set at the beginning of the file. These defines basically just control the dependency information that gets coded into the finished rpm package as well + The bacula spec file contains defines to build for several platforms: \\ + \\ + Red Hat 7.x (rh7), Red Hat 8.0 (rh8), Red Hat 9 (rh9), \\ + Fedora Core (fc1, fc3, fc4, fc5, fc6, fc7, fc8), \\ + Whitebox Enterprise Linux 3.0 (wb3), \\ + Red Hat Enterprise Linux (rhel3, rhel4, rhel5), \\ + Mandrake 10.x (mdk), Mandriva 2006.x (mdv), \\ + CentOS (centos3, centos4, centos5) \\ + Scientific Linux (sl3, sl4, sl5) and \\ + SuSE (su9, su10, su102, su103, su110). \\ + \\ + The package build is controlled by a mandatory define set at the beginning of the file. These defines basically just control the dependency information that gets coded into the finished rpm package as well as any special configure options required. 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 Red Hat 7.x package find the line in the spec file @@ -379,7 +386,7 @@ In general the RPMs, once properly built should install correctly. However, when attempting to run the daemons, a number of problems can occur: \begin{itemize} -\item [Wrong /var/bacula Permissions] +\item Wrong /var/bacula Permissions \\ By default, the Director and Storage daemon do not run with root permission. If the /var/bacula is owned by root, then it is possible that the Director and the Storage daemon will not @@ -390,7 +397,7 @@ can occur: \end{verbatim} Note: as of 1.38.8 /var/bacula is installed root:bacula with permissions 770. -\item [The Storage daemon cannot Access the Tape drive] +\item The Storage daemon cannot Access the Tape drive \\ This can happen in some older RPM releases where the Storage daemon ran under userid bacula, group bacula. There are two ways of fixing this: the best is to modify the /etc/init.d/bacula-sd diff --git a/docs/manuals/en/utility/utility.kilepr b/docs/manuals/en/utility/utility.kilepr index 5f707660..ef877767 100644 --- a/docs/manuals/en/utility/utility.kilepr +++ b/docs/manuals/en/utility/utility.kilepr @@ -3,7 +3,7 @@ img_extIsRegExp=false img_extensions=.eps .jpg .jpeg .png .pdf .ps .fig .gif kileprversion=2 kileversion=2.0 -lastDocument= +lastDocument=utility.tex masterDocument= name=Utility pkg_extIsRegExp=false @@ -17,9 +17,9 @@ QuickBuild= [item:fdl.tex] archive=true -column=110 +column=34 encoding= -highlight= +highlight=LaTeX line=0 open=false order=-1 @@ -53,12 +53,12 @@ order=-1 [item:utility.tex] archive=true -column=36 +column=1 encoding=UTF-8 highlight=LaTeX line=46 -open=false -order=-1 +open=true +order=0 [item:version.tex] archive=true diff --git a/docs/manuals/en/utility/utility.tex b/docs/manuals/en/utility/utility.tex index 0c61b072..0502574e 100644 --- a/docs/manuals/en/utility/utility.tex +++ b/docs/manuals/en/utility/utility.tex @@ -65,10 +65,6 @@ \clearpage \tableofcontents \clearpage -\listoffigures -\clearpage -\listoftables -\clearpage \include{progs} \include{bimagemgr-chapter} -- 2.39.5