Date: Sat, 4 Nov 1995 09:41:57 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: bde@zeta.org.au Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: kern/810: Some I/O attempts to CD-ROMs hang at isoilk FDIV038 Message-ID: <199511040841.JAA06837@uriah.heep.sax.de> In-Reply-To: <199511030940.BAA01604@freefall.freebsd.org> from "Bruce Evans" at Nov 3, 95 01:40:02 am
next in thread | previous in thread | raw e-mail | index | archive | help
As Bruce Evans wrote: > > ENODEV might be a better errno. EOPNOTSUPP only applies to networking > according to the comment in errno.h :-). EROFS isn't quite right for > file systems on devices that are inherently readonly. OTOH, cd9660 > isn't inherently readonly. The current implementation just doesn't > suppport writing, so EOPNOTSUPP is reasonable. If writing was supported > then EROFS would be the natural errno. I think you can currently only mount cd9660 read/only, so EROFS *is* okay (but should not be generated by the cd9660 code itself, but by the upper file system layers). The devices where cd9660 is currently applied to do not allow writing, so either open routine should return ENODEV for an open with write intent. This would prevent one from mounting a CD read/write on a CD reader, even when the cd9660 code does understand how to write something. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511040841.JAA06837>