Date: Thu, 11 Jan 2001 12:36:23 -0800 From: Jordan Hubbard <jkh@winston.osd.bsdi.com> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: obrien@FreeBSD.org, Doug Barton <dougb@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc crontab rc src/etc/defaults rc.conf src/etc/mtree BSD.root.dist src/libexec Makefile src/libexec/save-entropy Makefile save-entropy.sh Message-ID: <19283.979245383@winston.osd.bsdi.com> In-Reply-To: Message from Sheldon Hearn <sheldonh@uunet.co.za> of "Thu, 11 Jan 2001 20:54:16 %2B0200." <8537.979239256@axl.fw.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm pretty sure that this has all been discussed before, with quite a > bit of consensus (although some might bitch about the period in the > directory name '/.entropy'. Hmmm, if it was then FreeBSD's diskless boot community never weighed in during the discussions and that's a pity. You're well aware, one assumes, of the fact that many of these people habitually use a read-only root? They're not the only ones either - just about all of the embedded folks who boot out of flash also run RO root and usr filesystems. That's one the big reasons for keeping /var a separate filesystem, at least conceptually, in order that that we might mandate a writable filesystem as part of the hierarchy standard. I'll admit that hier(7) is a little vague on that point, but it's certainly been part of the conventional wisdom for as long as I can remember. I also appreciate the arguments for having /var be "too late" in the boot process, at least as things currently stand, but simply assuming that root is writable as your work-around isn't a very safe solution either. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19283.979245383>