-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Piesk wrote: | i think upgrading software like bacula clients should be left to | software designed for that. almost every company has such a software | distribution system, especially if we talk about a large number of | installations.
I agree with most opinions out there in that, there's already systems that can handle upgrading the Bacula clients and people should use them. But while everybody mentions these deployment systems I though we should probably document HOW to use them. I know we've had several mailing list posts with different methods (I myself posted my 'push it via SMB/CIFS' scripts and mentioned OCS Inventory NG) but if we had some official documentation, HOWTOs specific to Bacula client deployment, links, etc for people, they might not even need the auto-upgrade feature. Would this be worth dedicating a section of the manual to? And who can create/assemble that documentation? (I could contribute the way I upgrade my Win32 clients with OCS Inventory NG.) Greetings, ~ Michel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) iEYEARECAAYFAkgj+RYACgkQ2Vs+MkscAyXpnwCfckbX2ZNdk8lAfHY3PWvGoUWg fZwAn31htWUThI0zjzuAnZFO7Lz3NlTU =PFXh -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
