Date: Mon, 23 Oct 2000 21:33:44 -0400 From: "John W. De Boskey" <jwd@bsdwins.com> To: Makoto MATSUSHITA <matusita@jp.FreeBSD.org> Cc: "David O'Brien" <obrien@FreeBSD.ORG>, Donny Lee <donny@CoreBit.com>, Leif Neland <leifn@neland.dk>, freebsd-current@FreeBSD.ORG Subject: Re: -current hangs during boot (UPDATING entry) Message-ID: <20001023213344.A46608@bsdwins.com> In-Reply-To: <20001024102350E.matusita@jp.FreeBSD.org>; from matusita@jp.FreeBSD.org on Tue, Oct 24, 2000 at 10:23:50AM %2B0900 References: <20001023141405.Z622@beastie.localdomain> <20001023141405.Z622@beastie.localdomain> <20001023183029.A45262@bsdwins.com> <20001024102350E.matusita@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Makoto MATSUSHITA's Original Message ----- > > jwd> 5. At this time, remove ALL MFS filesystems from /etc/fstab. > jwd> They can be hand mounted after bootup or via a local rc > jwd> startup script. > > Is there any chance to mount MFS filesystem listed in /etc/fstab just > after the /dev/random reseeding is done ? I cannot put up with that we > cannot put 'mfs' line to /etc/fstab forever. Moreover, /tmp (common > MFS candidate) is already used by X server after rebooting; you may > not want to mount /tmp at hand later. > > Or, it's only for upgrading procedure, and we can put 'mfs' lines back? #5 above represents a bug in the current code. It needs to be fixed, but I don't know what the 'correct' thing to do is just yet. Does the FSIRAND code in mfs require crypto strength randomness? -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001023213344.A46608>