"Dampure, Pierre Y." wrote:
>
> Apologies to all, this was a pilot error. /boot/defaults/loader.conf was
> referencing disk1s1a -- it should have been disk2s1a (I forgot the
> floppy was included in the unit count).
For the record, this _cannot_ be the cause of the problem you had.
I'd rather b
Apologies to all, this was a pilot error. /boot/defaults/loader.conf was
referencing disk1s1a -- it should have been disk2s1a (I forgot the
floppy was included in the unit count).
After a few interesting floppy boots / fdisk / disklabel sessions, I got
the thingie to work.
One point, though: th
"Dampure, Pierre Y." wrote:
>
> Apologies if this ought to be in -questions rather than -current, but
> since I first noticed the problem on 5.0-2621-CURRENT...
>
> The above snapshot was installed on a brand new system (OR840, 2x733EB,
> 512MB RDRAM, 1xAHA2940UW, 4x9.1Gb Barracuda). The dis
Apologies if this ought to be in -questions rather than -current, but
since I first noticed the problem on 5.0-2621-CURRENT...
The above snapshot was installed on a brand new system (OR840, 2x733EB,
512MB RDRAM, 1xAHA2940UW, 4x9.1Gb Barracuda). The disk organisation is
as follows:
d
