SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
[Bacula-devel] Questions for Bacula Windowsusers ...
Author Message
Post [Bacula-devel] Questions for Bacula Windowsusers ... 
1. I am considering to change the default installation location for
Bacula on
Windows to be the same as it was previously -- that is the \bacula
directory
on the main disk. The current installation places files in the
"standard"
Windows locations, but IMO, it is very inconvenient because they are
extremely long names with spaces that are very hard to remember, and
are
sprayed all over the disk.

Please don't change this. I talked to the Windows guys here (who are
fairly reasonable sorts) and they expect packages that go into their
environment to comply with the manufacturer's recommended packaging and
location strategy. Putting things in the root directory (aka the "old"
way) messes up their management plans and the way they do builds, and
makes them grumpy. Grumpy Windows admins is bad, particularly if you
want companies to pick up Bacula into the mainstream.=20

Keep in mind that for those whose only experience is with Windows, this
is the way things are supposed to work. They don't know any better, and
things that make them think are difficult, and thus bad.=20

Personally, I want it in SYS1.PARMLIB, but the LKED and IEBLIBR steps
just don't want to happen for me...8-)

-- db

Post [Bacula-devel] Questions for Bacula Windowsusers ... 
On Friday 15 June 2007 13:54, David Boyes wrote:
1. I am considering to change the default installation location for
Bacula on
Windows to be the same as it was previously -- that is the \bacula
directory
on the main disk. The current installation places files in the
"standard"
Windows locations, but IMO, it is very inconvenient because they are
extremely long names with spaces that are very hard to remember, and
are
sprayed all over the disk.

Please don't change this. I talked to the Windows guys here (who are
fairly reasonable sorts) and they expect packages that go into their
environment to comply with the manufacturer's recommended packaging and
location strategy. Putting things in the root directory (aka the "old"
way) messes up their management plans and the way they do builds, and
makes them grumpy. Grumpy Windows admins is bad, particularly if you
want companies to pick up Bacula into the mainstream.

OK, it is not going away, but there will probably be some additional options
or a different default.


Keep in mind that for those whose only experience is with Windows, this
is the way things are supposed to work. They don't know any better, and
things that make them think are difficult, and thus bad.

Personally, I want it in SYS1.PARMLIB, but the LKED and IEBLIBR steps
just don't want to happen for me...8-)

-- db

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-devel mailing list
Bacula-devel < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-devel


Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB