I agree with Jesse that this is almost a packaging issue. However, I do
think that certain files should be moved.
Specifically:
All daemons should go in "$(sbindir)".
The sd tools, bconsole, and any other gui console or monitoring program
should go in "$(bindir)".
The bsmtp tool, the mtx-changer script, and any future tools which would be
run by bacula but not by the user should go in "$(libexecdir)/bacula".
All of the extra scripts such as updatedb/* and the db creation scripts
should go in "$(datadir)/bacula" or at least "$(sysconfdir)/bacula/scripts"
or something where they don't clutter the top-level config directory so
much.
I'm not trying to be a FHS nazi here, but currently /etc/bacula gets kind of
cluttered without significant packaging modifications. I also think that
some of the extra scripts like the various db creation/deletion/mangling
series should be installed by default. It's not a lot of work from a
packaging point of view, but why write 'cp -p <path>/updatedb /etc/bacula/'
or simliar into the distro end when it's likely that a user may need these
scripts but the package manager deleted the source tree after installation?
Switching gears for a moment...
Jesse also brought up another subject which has occurred to me as well. For
the daemons I completely agree with keeping the config files in /etc/bacula
but for console and gui programs it makes sense to me that these programs
should look for config files in a hierarchial fashion the way other user
programs do: look for the file specified with by -c, then
"${HOME}/.bacula/bconsole.conf". then "$(sysconfdir)/bacula/bconsole.conf".
Having a "${HOME}/.bacula/" might seem unnecessary at this point, but I've
also been thinking that some operators might like to tweak their own console
config especially if the console program(s) ever implement certain config
options which have been mentioned before such as "Autodisplay = on" or
having multiple console levels in the same config file and maybe switching
between them within the console. Plus, if any of the gui projects ever
become sophisticated enough to need a complicated set of options stored in
their config, this would be a good place for them if an operator/admin
wanted to change gui options without affecting the default (/etc/bacula) gui
options.
I think that about covers my 2cts on the matter. ;-)
Thanks,
Chris
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Kern Sibbald
> Sent: Thursday, 18 August, 2005 10:59
> To: bacula-users@lists.sourceforge.net
> Subject: [Bacula-users] Fwd: [Bacula-devel] Proposal for
> location of gnome-console
>
> Hello,
>
> Are there any comments on this proposal?
>
> To be consistent, I would imagine we would need to include bconsole,
> wxconsole, and possibly a number of other files in /usr/bin
> as well. I can
> understand Daniel's point, but probably prefer to let the
> user move or link
> the file to where he wants.
>
> ---------- Forwarded Message ----------
>
> Subject: [Bacula-devel] Proposal for location of gnome-console
> Date: Thursday 11 August 2005 10:35
> From: Daniel Bloemer <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
>
> Hello,
>
> I am using bacula for a while now, and it works pretty fine.
> I have just upgraded from 1.36.1 tp 1.36.3 (SuSE-9.2-RPMs) and have
> stumbled (again) across a minor inconvenience:
>
> The gnome-console is located under /usr/sbin and is equipped with the
> user rights 754. Since I usually do my daywork with a non-proviliged
> user, I cannot start the console directly.
> Maybe it would be better if the gnome-console would be located in
> /usr/bin and is executable for any user. The user still needs the
> configuration containing the password for accessing the bacula-system.
>
> Best Regards
>
> Daniel Blömer - Bonn, Germany
> --
> Daniel Bloemer - BusinessCoDe GmbH
> Systemadministration and Support
> Phone: +49 (0)228 / 28925-43
> http://www.business-code.de
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development
> Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *
> Testing & QA
> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Bacula-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/bacula-devel
>
> -------------------------------------------------------
>
> --
> Best regards,
>
> Kern
>
> (">
> /\
> V_V
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development
> Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *
> Testing & QA
> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
