On Mon, Feb 07, 2000 at 04:40:21PM +0100, Martin Cracauer wrote: > > > > I don't have it in /var/log/messages, but I can reboot my machine > > (that has this problem) and copy down what I see. > > If it has been thrown out by newer kernel messages, try > /var/run/dmesg.boot That wouldn't even be written if /etc/fstab can't be found to write /var, would it? (all I see is the most recent boot there, after I re-IDed the disks to boot successfully) I can't remember if the panic was not finding init, or not being able to mount root or whatever, I'll find that out in a bit... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Hardwiring SCSI device ID broken? Martin Cracauer
- Re: Hardwiring SCSI device ID broken? Peter Wemm
- Re: Hardwiring SCSI device ID broken? Igor Timkin
- Re: Hardwiring SCSI device ID brok... Peter Wemm
- Re: Hardwiring SCSI device ID ... Martin Cracauer
- Re: Hardwiring SCSI device ID ... Igor Timkin
- Re: Hardwiring SCSI device ID broken? tele danmarQ kvindeservice
- Re: Hardwiring SCSI device ID broken? Martin Cracauer
- Re: Hardwiring SCSI device ID brok... Barry Bouwsma
- Re: Hardwiring SCSI device ID brok... Barry Bouwsma
- Re: Hardwiring SCSI device ID ... Peter Wemm
- Re: Hardwiring SCSI devic... Barry Bouwsma
- Re: Hardwiring SCSI device ID broken? tele danmarQ kvindeservice
- Re: Hardwiring SCSI device ID broken? Matthew Sean Thyer
- Re: Hardwiring SCSI device ID broken? Kun Limfjordsporter