block device required
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 to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: block device required
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: /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 PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: block device required
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 -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 attached this Flash Card Reader, even after manually kldloaded umass.ko -- only the ugen0 (and .[123]). But that's a different story. Nevertheless the error message is wrong as there are no block devices anymore. Yes, that was my point :) -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: block device required
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: /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:err = ENOTBLK; ./fs/ntfs/ntfs_vfsops.c:err = ENOTBLK; ./i386/ibcs2/ibcs2_errno.c: IBCS2_ENOTBLK, /* 15 */ ./kern/vfs_aio.c: if (error == ENOTBLK) ./kern/vfs_subr.c: *errp = ENOTBLK; ./kern/vfs_subr.c: *errp = ENOTBLK; ./compat/svr4/svr4_sysvec.c:SVR4_ENOTBLK, To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: block device required
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 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 be translated to a different string though... David. ./fs/hpfs/hpfs_vfsops.c:err = ENOTBLK; ./fs/ntfs/ntfs_vfsops.c:err = ENOTBLK; ./i386/ibcs2/ibcs2_errno.c: IBCS2_ENOTBLK, /* 15 */ ./kern/vfs_aio.c: if (error == ENOTBLK) ./kern/vfs_subr.c: *errp = ENOTBLK; ./kern/vfs_subr.c: *errp = ENOTBLK; ./compat/svr4/svr4_sysvec.c:SVR4_ENOTBLK, Just because there is no 'block' device representation in /dev doesn't mean that there aren't block devices. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: block device required
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 representation in /dev doesn't mean that there aren't block devices. Indeed - that's why I said ENOTBLK makes sense in the kernel. Since someone got rid of the classic Not a typewriter message for ENOTTY, maybe we should change the message for ENOTBLK to Inappropriate device for operation. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
