From owner-freebsd-current Sun Oct 22 16:35:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id E376437B4C5; Sun, 22 Oct 2000 16:35:44 -0700 (PDT) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.0/8.11.0) id e9MNZes38477; Sun, 22 Oct 2000 19:35:40 -0400 (EDT) (envelope-from jwd) Date: Sun, 22 Oct 2000 19:35:39 -0400 From: "John W. De Boskey" To: "David O'Brien" Cc: Donny Lee , Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: -current hangs during boot Message-ID: <20001022193539.A38460@bsdwins.com> References: <39F2A1D0.2FC92123@CoreBit.com> <20001022154231.C4742@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001022154231.C4742@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sun, Oct 22, 2000 at 03:42:31PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- David O'Brien's Original Message ----- > On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: > > with the mfs enable, it hangs there right after FILESYSTEM > > checking, and with random_load set to YES, it hangs at ldconfig. > > mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. I saw this the other day... I've been examining the mfs code, and I'm not really sure why it needs to use random values... Anyone know the history on the '#ifdef FSIRAND' code? -john ps: break out of the boot sequence, 'ls -al /etc/ > /dev/random' and then 'exit' will get around this and other problems, but requires hands on reboots. > > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message