> As suggested, if the correct root device can't be found, the boot
> _should_ offer you a choice of running off others that appear to be
> bootable.
The "appear to be bootable" criterion is almost impossible (and unsafe to
attempt) to determine.
Also, I certainly can see instances
Matthew Jacob <[EMAIL PROTECTED]> writes:
>> > My FreeBSD-alpha PC164 lost it's IDE disk for 4.2 somehow- which I'd
>> > just loaded the 4.2 kernel from- so it decided to run off of da0
>> > instead, which was -current. Truly a startling turn of
>> > events. Shouldn't one stop and ask if the root
On Sun, Mar 04, 2001 at 01:13:36PM -0800, Matthew Jacob wrote:
> This might also be the source of the 'going nowhere without my init' install
> failures that so plague alphas?
No it is libdisk doing *err()* calls!! A library should *NOT* be
exiting on its own.
--
-- David ([EMAIL PROTECTED])
> > There are two schools of thought here. One says "you should try very
> > hard to find a root device", the other says "you should boot only from
> > the exactly correct root device and complain otherwise". I took the
> > first approach because its advocates shouted more loudly than those o
On Sun, 4 Mar 2001, Mike Smith wrote:
> >
> > This happened to me yesterday, and, haha, I didn't notice until I started to
> > see RSA stuff not working:
> >
> > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing
> > Enabled
> > da0: 4340MB (924 512 byte sectors: 255H
>
> This happened to me yesterday, and, haha, I didn't notice until I started to
> see RSA stuff not working:
>
> da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing
> Enabled
> da0: 4340MB (924 512 byte sectors: 255H 63S/T 553C)
> Mounting root from ufs:/dev/ad0a
> no su
This happened to me yesterday, and, haha, I didn't notice until I started to
see RSA stuff not working:
da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing
Enabled
da0: 4340MB (924 512 byte sectors: 255H 63S/T 553C)
Mounting root from ufs:/dev/ad0a
no such device 'ad'
set
