On 03/08/10 08:07, [email protected] wrote: > Hello :-) > > The 5.0.1 Release Notes strongly recommends installing into a single > directory, preferably /opt/bacula and invites questions in this mailing list > (full text below sig). > > Presumably the Bacula project has encountered problems with installing to > the prevalent /usr/(local/)bin, /usr/share/* et cetera directories, maybe > for reasons given in the Linux Filesystem Hierarchy (LFH) documentation > (http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/foreward.html and > http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/opt.html). > > But the single directory recommendation is contrary to LFH. Does the > project specifically recommend against following LFH by installing to: > > /opt/bacula (executables) > /etc/opt/bacula (configuration files) > /var/opt/bacula (data)
Bacula does indeed recommend the single-heirarchy installation over LFH, not least because it greatly simplifies life in the case of the disaster-recovery scenario, particularly in the case of a statically compiled Bacula installation. It becomes a simple matter to copy the complete client installation off onto a CD or even a USB flash memory stick. One can then boot a crashed machine from a liveCD, format and partition the disk, plug in the USB stick, start up the static client, and begin restoring. Kern can undoubtedly provide further reasons. > Ironically one of the LFH rationales is to ease backup: executables change > rarely so do not need to be backed up as frequently as data. I have to admit this is one of several rationales I have never thought made any sense. Any backup system worth its salt only backs up changed files anyway unless doing a full backup, and backs up all changed files that it has not been told to ignore. Is the idea behind this rationale to only even *scan* executable directories at infrequent intervals and thus risk missing changes? -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 [email protected] [email protected] [email protected] Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
