From owner-cvs-all Thu Jan 11 12:43:50 2001 Delivered-To: cvs-all@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id DC33C37B400; Thu, 11 Jan 2001 12:43:18 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0BKgqI10456; Thu, 11 Jan 2001 22:42:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101112042.f0BKgqI10456@gratis.grondar.za> To: Jordan Hubbard Cc: Sheldon Hearn , obrien@FreeBSD.org, Doug Barton , 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 References: <19283.979245383@winston.osd.bsdi.com> In-Reply-To: <19283.979245383@winston.osd.bsdi.com> ; from Jordan Hubbard "Thu, 11 Jan 2001 12:36:23 PST." Date: Thu, 11 Jan 2001 22:42:50 +0200 From: Mark Murray Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Agreed with all the below. Matt has already said that untangling the randomness requirements from mount(_nfs?) was easy; I await his contributions. If we can unsnarl one dependancy loop, I will be delighted :-). M > > 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 > > -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message