Date: 24 Oct 1996 10:55:50 +0100 From: Paul Richards <p.richards@elsevier.co.uk> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers), danny@panda.hilink.com.au (Daniel O'Callaghan) Subject: Re: root only: (was Re: comments on this change please.) Message-ID: <57g234vg7t.fsf@tees.elsevier.co.uk> In-Reply-To: J Wunsch's message of Thu, 24 Oct 1996 10:17:23 %2B0200 (MET DST) References: <199610240817.KAA02470@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
J Wunsch <j@uriah.heep.sax.de> writes: I'm very much in the ro / camp. When we originally discussed sysconfig the idea was to have a single stop configuration file that was designed in such a way that it would be easy to build admin tools on top of while still using a flat file for people to fix with vi. Now, that goal perhaps needs re-visiting but the basic premise, that all the /etc stuff is read-only still stands I think. I put all my dynamic files in /var, things like /etc/rc should never change, there's ino reaons why the password databases can't be moved to /var since they are already modified by applications rather than by hand. It's only conservatism that's impeding progress here. As a transition measure there's this wonderful concept of symlinks that seems to be perfectly acceptable everywhere else and in any case a simple # This file has been moved to /var/foo would serve just as well in the interim to tell people they're editing the wrong file. I think in general the goal should remain and incremental steps made to achieve it. Jordan, I think a golden opportunity was missed by not putting sysconfig into /var from the beginning. -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57g234vg7t.fsf>