Date: Wed, 3 Jul 1996 22:04:14 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: gpalmer@FreeBSD.ORG (Gary Palmer) Cc: terry@lambert.org, joelh@gnu.ai.mit.edu, jmb@freefall.freebsd.org, tom@sdf.com, jgreco@brasil.moneng.mei.com, root@friday.keanesea.com, hackers@FreeBSD.ORG Subject: Re: What is the best way to setup a drive Message-ID: <199607040504.WAA12377@phaeton.artisoft.com> In-Reply-To: <12468.836455255@palmer.demon.co.uk> from "Gary Palmer" at Jul 4, 96 05:40:55 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > The "/etc" directory is not allowed to be other than on the root file > > system, by definition. That resolves the symlink problem. > > Umm? What was being talked about (if you remember) was having a > read-only root filesystem. Then someone pointed out that that'd stop > you changing passwords, so then a symlink from /etc to a read-write FS > was suggested ... Which makes me wonder where your FS ``improvements'' > fit in? They don't solve the problem of how to figure out where to get > the /etc directory from. I thought that was clear. That /etc has to be writeable is a bogus assumption. The NIS suggestion for "where do I get my passwords from" frees up /etc/passwd. What's left is /etc/fstab (dealt with by mount changes, which aren't the same thing as FS changes), /etc/rc* (bogus) and /etc/sysconfig (also bogus). I really don't see where the problem is: throw out your bogositieis and fix the rest to comply with the design documents, and the problems all fade away. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607040504.WAA12377>