At 9:13 AM -0800 2000/3/27, Julian Elischer wrote:
> in a 4.0 kernel, teh block device doesn't exist, you always use the
> character device,
> so it was renamed so that /dev/da0s1a is teh name for the char device
> but if you are using a device on a 3.4 disk it refers toi the block device
>
in a 4.0 kernel, teh block device doesn't exist, you always use the
character device,
so it was renamed so that /dev/da0s1a is teh name for the char device
but if you are using a device on a 3.4 disk it refers toi the block device
(which isn't in a 4.0 kernel)
On Mon, 27 Mar 2000, Brad Knowles
At 7:33 PM -0800 2000/3/25, Doug Barton wrote:
> 'fsck -y /dev/da0s1a'
I had tried that already, but I'll do it again and let you see
what happens:
$ fsck -y /dev/da0s1a
Can't open /dev/da0s1a: Invalid argument
--
These are my opinions -- not t
Brad Knowles wrote:
> When I try to mount my 3.4-STABLE root filesystem on /old, here's
> what I get:
>
> $ mount /old
> mount: /dev/da0s1a on /old: incorrect super block
'fsck -y /dev/da0s1a'
--
"So, the cows were part of a dream that dream
At 10:18 AM +1000 2000/3/26, Tony Maher wrote:
> No, sd is deprecated.
> AFAIK its da only in 4.0, and only character devices.
> 3.4 has sd compatability and has block devices.
Hmm. Okay, well I note that what's being used right now is
da1s1a through da1s1h, and I had copied these e
