On Mon, 30 Jun 1997, Oliver Elphick wrote: > Have packages look at /etc as now, but by default have /etc/<package>.conf > be a symbolic link to /usr/etc/<package>.conf. Then the read-only or > site-wide configuration will be in force until theadministrator of > the local machine replaces the symbolic link in /etc with a configuration > specific to that machine. That's not what I said -- I said, leave /etc alone for some packages, because otherwise you'll have to walk through hundreds of computers and add the config files (or symbolic links, for that matter) by hand (or script). And I don't think things like lynx.conf (or emacs conffiles, for that matter) must be different between machines belonging to one site. They must be different between users [excuse me for my bad English], but that's users' problems, aren't they? > This probably should not apply to essential packages, since /usr might not > be mounted when the package was in use. Sure thing. That doesn't apply to aliases, crontab, lilo.conf and such -- they must stay in /etc; but things like screenrc, xearth.markers, emacs/* and lynx.cfg surely belong to /usr. Look how they did it in other Unices -- and they to mount /usr read-only, too! How many times a day you must change global config files? And who is allowed to do it, except for the site admin? BTW, by /usr/local/etc I meant a directory for local config files. As you nay have guessed already. > Make it idiot-proof, and someone will breed a better idiot. Hehe:) Vadik. -- Vadim Vygonets * vadik@cs.huji.ac.il * vadik@debian.org * Unix admin The fish doesn't think, because the fish knows... everything. -- Arizona Dream
Attachment:
pgpFz7HPqBIAt.pgp
Description: PGP signature