Re: [Bacula-docs] "as of version 1.37"

[Kern S. <ke...@si...>]

On Thursday 30 October 2008 22:02:54 Thomas wrote:
> Kern Sibbald schrieb:
> > On Thursday 30 October 2008 12:50:37 Thomas wrote:
> >> Hi,
> >>
> >>
> >> isn't it time to remove all the warnings and notes about version 1.3nn?
> >>
> >> e.g.:
> >>
> >> vars.tex:Please note that as of version 1.37, the Variable Expansion
> >>
> >> vars.tex:Currently (version 1.31), it is used only in format labels, but
> >> in the future,
> >>
> >> win32.tex:As of Bacula version 1.39.20 or greater, the installer is
> >> capable
> >>
> >> win32.tex:If you have a previous version Bacula (1.39.20 or lower)
> >>
> >> win32.tex:the new installer (1.39.22 and later) installs the binaries
> >> and dlls in
> >>
> >> win32.tex:example above is the default used in 1.39.22 and later.
> >>
> >> win32.tex:of Bacula (1.34 on, I think), when you start the File daemon
> >> in debug mode it
> >>
> >> win32.tex:know which files were not backed up.  For version 1.37.25 and
> >> greater, see
> >>
> >> win32.tex:In Bacula version 1.31 and later, we use Windows backup API
> >> calls by
> >>
> >> and many many more .....
> >
> > Yes, I have wanted to do so for some time, so if that interests you,
> > please feel free to jump in.  Between:
>
> i can do this for the german version of the manual during the translation,
> but it would be much easier to adopt these changes from the english manual.
>
> an example from disk.tex :
>
> \item To limit the maximum size of each Volume, use:
>
>    {\bf Maximum Volume Bytes = mmmm}.
>
>    Note, if you use disk volumes, with all versions up to and including
>    1.39.28, you should probably limit the Volume size to some reasonable
>    value such as say 5GB. This is because during a restore, Bacula is
>    currently unable to seek to the proper place in a disk volume to restore
>    a file, which means that it must read all records up to where the
>    restore begins. If your Volumes are 50GB, reading half or more of the
>    volume could take quite a bit of time.  Also, if you ever have a partial
>    hard disk failure, you are more likely to be able to recover more data
>    if they are in smaller Volumes.
>
>
> is bacula now able to seek in the file?
> "....Bacula is currently unable to...." for what bacula version is this
> clause written? i dont't know. can i completely erase this from the manual,
> or is it partly still valid?
>
> > Bacula bugs
> > Bacula development for release 3.0.0 at the end of the year
> > Bacula Systems
> > Writing a course for training users in Bacula
> >
> > I don't get much time for cleaning up the manual any more.
> >
> > I watch your commits and try when I can to post it to the web site
> > quickly. If ever you would like to see the results faster, don't hesitate
> > to drop me a little note -- I never get upset by those things.
>
> if i remember right there was a try to find someone who can periodically
> build and upload these files to the homepage.
> just drop me a little note ... :)
>
> > What do you think about the idea of moving all the various subdirectories
> > into only one doc source directory for all the manuals?   We would still
> > keep the separate manuals, but at least *all* the files will be in one
> > place.
>
> i don't see the advantage. maybe (very hypothetical) someday someone
> tries something like "sed -i 's/wrong/right/g' *.tex" to fix a typo in the
> french version of the manual and maybe this command has very bad effects to
> the other languages. (ok, it is not really a problem while using svn)

I had still planned on keeping the translations in separate directories.  The 
main problem I have in having the English manual split into chapters is 
finding the text I want to work on.  I need to search through 7 different 
directories for the file.

>
> very important is keeping all the files like
>
> check_tex.pl
> fix_tex.pl
> latex2html-init.pl
> translate_images.pl

Yes, this is a bit of a problem that I will have to think about.

> ....
>
> unique in the svn.
> but (i think) this should be part of the configure script.
>
>
> another example:
> \begin{verbatim}
>
> in the german manual i use sometimes
>
> \begin{alltt}
>
> with verbatim i am not able to use german umlauts,
> (ok, i have to escape a lot of other signs)
> so the different versions of the manual are partial very different.
> maybe next week someone starts a chinese translation.
> so i think different manuals in different directories is a good idea.
> (as long as as all common scripts are only once in the svn)

Yes, I agree, translations in different directories is critical.  However, my 
proposal, not very well specified, was to combine all the files for a single 
language in one directory.

>
> > I also want to move some more chapters out of the Concepts manual ... for
> > example, the Rescue chapter should either be a manual by itself (maybe
> > later) or at least in the Trouble shooting manual.  And finally, I would
> > like to split the Installation manual into separate Installation and
> > Configuration manuals.
>
> i am currently don't have a complete overview over the whole manual and all
> it chapters. so i am not able to give you any recommendation about how to
> split it.

OK, thanks.

Kern