> > > msdosfs: /dev/ugen0: Block device required
> >
> > This is caused by the kernel returning ENOTBLK, which I think still
> > makes sense in the kernel. It's possible that the errno should be
> > translated to a different string though...
> Just because there is no 'block' device representa
On Sat, 18 Aug 2001, David Malone wrote:
> On Sat, Aug 18, 2001 at 11:02:04AM -0400, Mikhail Teterin wrote:
> > Now, this may be the wrong way to do it:
> >
> > # mount -oro -t msdos /dev/ugen0 /mnt
> >
> > But the error message is certainly misleading. Especially,
> > since the are no blo
On Sat, Aug 18, 2001 at 11:02:04AM -0400, Mikhail Teterin wrote:
> Now, this may be the wrong way to do it:
>
> # mount -oro -t msdos /dev/ugen0 /mnt
>
> But the error message is certainly misleading. Especially,
> since the are no block devices in -current any more :)
>
> msdosfs:
On 18 Aug, Bernd Walter wrote:
> On Sat, Aug 18, 2001 at 11:02:04AM -0400, Mikhail Teterin wrote:
>> Now, this may be the wrong way to do it:
>>
>> # mount -oro -t msdos /dev/ugen0 /mnt
>>
>> But the error message is certainly misleading. Especially, since the
>> are no block devices in -c
On Sat, Aug 18, 2001 at 11:02:04AM -0400, Mikhail Teterin wrote:
> Now, this may be the wrong way to do it:
>
> # mount -oro -t msdos /dev/ugen0 /mnt
>
> But the error message is certainly misleading. Especially,
> since the are no block devices in -current any more :)
>
> msdosfs: