I'm beginning to think we need an updating entry.
1. Make sure /dev/random exists 'cd /dev && sh MAKEDEV std'
2. Make sure your kernel includes:
device random # Entropy device
3. Make sure /etc/rc is at rev 1.237 or higher.
4. Make sure /etc/rc.shutdown is at rev 1.13 or 1.15
5. At this time, remove ALL MFS filesystems from /etc/fstab.
They can be hand mounted after bootup or via a local rc
startup script.
6. Reboot your system via 'init 6' or 'shutdown -r now' (or similar).
Do not use 'reboot'.
7. If at any time during the boot process a 'cntrl-t' shows a
process hung in 'rndblk', hit 'cntrl-\', 'ls -al /etc > /dev/random',
and then 'exit'. This should get your machine to boot for this
session until you figure out which of the above are not done.
-John
----- Brian O'Shea's Original Message -----
> On Sun, Oct 22, 2000 at 07:35:39PM -0400, John W. De Boskey wrote:
> > ----- 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...
>
> When ldconfig hangs, it is in a mkstemp() call. The mkstemp()
> function probably uses random numbers to generate unique file names:
>
> #0 0x8054340 in read ()
> #1 0x804c966 in mktemp ()
> #2 0x804ca33 in arc4random_stir ()
> #3 0x804cad9 in arc4random ()
> #4 0x804c791 in mktemp ()
> #5 0x804c692 in mkstemp ()
> #6 0x804886a in write_elf_hints ()
> #7 0x8048818 in update_elf_hints ()
> #8 0x8048c61 in main ()
> #9 0x8048139 in _start ()
>
>
> -brian
>
> --
> Brian O'Shea
> [EMAIL PROTECTED]
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
