Re: HTML format documentation

2000-08-26 Thread Richard Stallman
Which reminds me: $(sysconfdir) should never include $(prefix). If there's a common need for a configuration directory under $(prefix) then it should be represented by $(localconfdir) or some similarly named variable. This is a question I would like people to discuss more so we

Re: HTML format documentation

2000-08-26 Thread Russ Allbery
Richard Stallman <[EMAIL PROTECTED]> writes: > Which reminds me: $(sysconfdir) should never include $(prefix). If > there's a common need for a configuration directory under $(prefix) > then it should be represented by $(localconfdir) or some similarly > named variable. > This

First Annual Linux User's Training Conference and Awards Presentation

2000-08-26 Thread David Dickson
Title:   To:      [EMAIL PROTECTED]   First Annual Linux Users' Training Conference And Awards Presentation “New Enterprise Solutions Through Linux” October 30, 2000 Ronald Reagan Building and International Trade

First Annual Linux User's Training Conference and Awards Presentation

2000-08-26 Thread David Dickson
Title:   To:      [EMAIL PROTECTED]   First Annual Linux Users' Training Conference And Awards Presentation “New Enterprise Solutions Through Linux” October 30, 2000 Ronald Reagan Building and International Trade

Re: HTML format documentation

2000-08-26 Thread Greg A. Woods
[ On Saturday, August 26, 2000 at 03:42:58 (-0600), Richard Stallman wrote: ] > Subject: Re: HTML format documentation > > Which reminds me: $(sysconfdir) should never include $(prefix). If > there's a common need for a configuration directory under $(prefix) then > it should be repr

Re: HTML format documentation

2000-08-26 Thread Alexandre Oliva
On Aug 26, 2000, Russ Allbery <[EMAIL PROTECTED]> wrote: > Richard Stallman <[EMAIL PROTECTED]> writes: >> Which reminds me: $(sysconfdir) should never include $(prefix). If >> there's a common need for a configuration directory under $(prefix) >> then it should be represented by $(localconfdir

Re: rc and config files - best practices?

2000-08-26 Thread Alexandre Oliva
On Aug 25, 2000, Harlan Stenn <[EMAIL PROTECTED]> wrote: > (Hmmm, I can look at amanda...). Don't, unless you're looking for a good backup solution. Regarding configuration, it's a very bad example of hard-coding too many configuration decisions in compiled files. > - When a process starts up

Re: HTML format documentation

2000-08-26 Thread Greg A. Woods
[ On , August 26, 2000 at 03:07:39 (-0700), Russ Allbery wrote: ] > Subject: Re: HTML format documentation > > Well, I can repeat my standard statement when things like this come up: > Any package which installs parts of itself somewhere other than under > $(prefix) unless it's explicitly configur

Re: HTML format documentation

2000-08-26 Thread Tom Tromey
Greg> For those packages configured with GNU Autoconf I did this by Greg> simply saying "--prefix=/usr" when configuring them Can't you just configure with --sysconfdir=/etc as well? Tom

Re: HTML format documentation

2000-08-26 Thread Alexandre Oliva
On Aug 26, 2000, [EMAIL PROTECTED] (Greg A. Woods) wrote: > This implies that sample configuration files should only be installed to > some place like $(prefix)/share/examples, and that there be an "enable" > procedure (an administrative program separate from "make install", and > installed with

Re: HTML format documentation

2000-08-26 Thread Harlan Stenn
The NTP configuration runtime stuff is slowly moving to /usr/local/etc, as there are a number of sites that NFS mount /usr/local/etc and there are shared configuration files that each host may decide to update. For private information, we're currently saying "make everything visible under /usr/l

Re: rc and config files - best practices?

2000-08-26 Thread Harlan Stenn
OK, amanda is a bad example for how to handle config files. So who can recommend a package that can be used as an example of a *good* way to handle runtime configuration, hopefully for a daemon process that must (reasonably securely) invoke executables as root? H

Re: HTML format documentation

2000-08-26 Thread Peter Eisentraut
Greg A. Woods writes: > However this meant I was either faced with creating a symlink to point > "/usr/etc -> ../etc", or patching all Autoconf'ed packages so that they > did as I suggested above and did not include $(prefix) in $(sysconfdir). Why didn't you just say `configure --prefix=/usr --s

Re: rc and config files - best practices?

2000-08-26 Thread Alexandre Oliva
On Aug 26, 2000, Harlan Stenn <[EMAIL PROTECTED]> wrote: > So who can recommend a package that can be used as an example of a *good* > way to handle runtime configuration I had meant to add it to my message, and ended up forgetting to do so. I think GCC is a good example of that, in the way it

Re: HTML format documentation

2000-08-26 Thread Greg A. Woods
[ On , August 26, 2000 at 14:06:05 (-0600), Tom Tromey wrote: ] > Subject: Re: HTML format documentation > > Greg> For those packages configured with GNU Autoconf I did this by > Greg> simply saying "--prefix=/usr" when configuring them > > Can't you just configure with --sysconfdir=/etc as well?

Re: HTML format documentation

2000-08-26 Thread Greg A. Woods
[ On Saturday, August 26, 2000 at 16:36:41 (-0400), Harlan Stenn wrote: ] > Subject: Re: HTML format documentation > > The NTP configuration runtime stuff is slowly moving to /usr/local/etc, as > there are a number of sites that NFS mount /usr/local/etc and there are > shared configuration files

Re: HTML format documentation

2000-08-26 Thread Alexandre Oliva
On Aug 26, 2000, [EMAIL PROTECTED] (Greg A. Woods) wrote: > In any case if "sysconfdir" means what it says, i.e. "system > configuration directory", Only if you think of a system as a host. I think of a system as a set of hosts on which the same set of policies apply. In this case, a shared co