Re: -current hangs during boot (UPDATING entry)
Thanks for the updates. A few questions below. -John - Mark Hittinger's Original Message - > > It does look like an updating entry is needed for this badly. > > I did the following things, some of which may not be needed, and now my > -current boxes boot OK. > > 1. update MAKEDEV from /usr/src/etc, run MAKEDEV all > > 2. update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc > > 3. add random_load="YES" to /boot/loader.conf or add the random device to the kernel config file. > 4. update /etc/login.conf from /usr/src/etc I don't remember having to do this... was there a specific reason? > 5. do a "shutdown -r now" which creates the entropy file and reboots > > Now the system boot does not hang at the ldconfig spots. It does look like > there is a lot to do to get back on course, enough to justify adding to > UPDATING. > > Later > > Mark Hittinger > Earthlink > [EMAIL PROTECTED] > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
re: -current hangs during boot (UPDATING entry)
It does look like an updating entry is needed for this badly. I did the following things, some of which may not be needed, and now my -current boxes boot OK. 1. update MAKEDEV from /usr/src/etc, run MAKEDEV all 2. update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc 3. add random_load="YES" to /boot/loader.conf 4. update /etc/login.conf from /usr/src/etc 5. do a "shutdown -r now" which creates the entropy file and reboots Now the system boot does not hang at the ldconfig spots. It does look like there is a lot to do to get back on course, enough to justify adding to UPDATING. Later Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, 23 Oct 2000, John W. De Boskey wrote: > I'm beginning to think we need an updating entry. > > 1. Make sure /dev/random exists 'cd /dev && sh MAKEDEV std' Unless you are using devfs. > 2. Make sure your kernel includes: > > devicerandom # Entropy device Or the appropriate line in /boot/.conf > 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. A better solution would be to increase the granularity of the file system mounts so that the MFS systems were mounted after the entropy gathering. There are a couple of reasons I changed the ordering on the two reseeding attempts, one of the big ones was that for the "manual" reseed (i.e., no entropy file) we want more parts of the system mounted so that we have more potential entropy gathering tools. Rest sounds good... Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
You need to put random_load="YES" into /boot/loader.conf. Optionally, you can load random.ko during the boot process. John W. De Boskey wrote: > It didn't work without the device line when I tested it > last week(Thursday/Friday). > > - David O'Brien's Original Message - > > On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: > > > 2. Make sure your kernel includes: > > > > > > devicerandom # Entropy device > > > > Are you implying the random.ko module is broken? > > -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
It didn't work without the device line when I tested it last week(Thursday/Friday). -John - David O'Brien's Original Message - > On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: > > 2. Make sure your kernel includes: > > > > device random # Entropy device > > Are you implying the random.ko module is broken? > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: > 2. Make sure your kernel includes: > > devicerandom # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: > > 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. You can leave them in, with option "noauto", and mount them later with "mount -a -t mfs". -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
- 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
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? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
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
