"Robin S. Socha" <[EMAIL PROTECTED]> writes:
> man hier should be a lot older than OpenBSD or whatever. I mean, really.

Unix-88 said that this sort of non-vendor provided stuff should go in
/opt/{vendor}/, but SunOS 4.1.x chose not to do that and few others do
even now.  (SunOS 4's HIER(7) suggested /usr/local/ was for "locally
maintained software", and /var/ was "directory of files that tend to
grow or vary in size". The BSD4.4-derived OS's go further and suggest
that /var/ should be solely transient stuff)

Nowadays, I'm tending to build things self contained in
/opt/{product}/ and symlink appropriate things into /usr/local/*/.

For qmail on Solaris, I've been going for:
        /opt/qmail/
                alias/
                bin/
                boot/
                control/
                doc/
                log -> var/log/qmail
                man/
                queue -> var/queue
                sbin/
                supervise/
                users/
                var -> /var/qmail
        /var/qmail/queue/
        /var/log/qmail/
        /usr/local/man/*/* -> /opt/qmail/man/*/*   (to aid use of man)

(as I consider my qmail configurations and binaries non-transient!)

supervise/ is a tricky one though - some bits in there are
configuration and some bits are transient status info. How would
supervise cope if the .../{process}/supervise/ subdirectories were 
symlinks into /var/run/supervise/ ?

(control/ should arguably be in /etc/opt/qmail/..., as should alias/.)

Dan's right that it's a mess, for sure.

James.

Reply via email to