public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  A suggestion for bacula
Date: Fri, 25 Nov 2005 19:47:14 -0600	[thread overview]
Message-ID: <87fypkxjrx.fsf@newsguy.com> (raw)

I've installed bacula from portage ( bacula-1.36.3-r2.ebuild) and
found virtually no documentation with it other than one thin README
and some release notes. Its not as if the documentaion is not
available.  There is quite a large manual for it.

But worse is that the gentoo install has removed things so that even
the available manual doesn't work for a gentoo user.

For example:
In the online manual: http://www.bacula.org/rel-manual/Contents.html

In the section on `Running a job' a gentoo user will not get the right
results because the bacula developers have expected there to be some
of the install of bacula files available for testing.

Bacula goes looking for them in /var/tmp/**bacula* and of course they
are long gone.

So a gentoo user will end up with nothing backed up and wondering what
they did wrong.  Especially if they don't notice the give away
address, and it isn't that obvious because `bconsole' output is pretty
primitive and it will not be on the screen long.  

It also means the restore part is a non starter too since nothing got
backed up.

Apparently someone maybe me needs to go thru the bacula ebuilds and
make them a little more like what bacula devel people expect. Or fix
it so it works for us.


-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2005-11-26  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-26  1:47 Harry Putnam [this message]
2005-11-26  9:37 ` [gentoo-user] Re: A suggestion for bacula Francesco Talamona
2005-11-26 12:46   ` Arturo 'Buanzo' Busleiman
2005-11-26 17:51     ` Francesco Talamona

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fypkxjrx.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox