> > > 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...
>
Especially,
> > since the are no block devices in -current any more :)
> >
> > 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
>
> 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...
David.
./fs/hpfs/hpfs_vfsops.c:
ce the
>> are no block devices in -current any more :)
>>
>> msdosfs: /dev/ugen0: Block device required
>
> ugen is a generic usb device and not a disk What you need is umass .
Yes, I figured that by now. For some reason, the umass0 was NOT created,
when I attache
>
> msdosfs: /dev/ugen0: Block device required
ugen is a generic usb device and not a disk.
What you need is umass.
Nevertheless the error message is wrong as there a no block devices
anymore.
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROT
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: /dev/ugen0: Block device required
-mi
To Unsubscribe: send mail
