From owner-freebsd-hackers Fri Feb 9 8:31:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winnie.fit.edu (fit.edu [163.118.5.1]) by hub.freebsd.org (Postfix) with ESMTP id 99DA537B980 for ; Fri, 9 Feb 2001 08:09:04 -0800 (PST) Received: from netzero.net (rm305w-b.campbell.fit.edu [163.118.216.112]) by winnie.fit.edu (8.9.1/8.9.1) with ESMTP id LAA11539 for ; Fri, 9 Feb 2001 11:09:50 -0500 (EST) Message-ID: <3A841662.B061A317@netzero.net> Date: Fri, 09 Feb 2001 11:10:10 -0500 From: Kevin Brunelle X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: mount checking for read-only media References: <3A837A0A.DAB3520A@columbus.rr.com> <20010209181342S.non@ever.sanda.gr.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's not system call but `od' driver does check if the medium is > writable or not. It returns EACCESS when the mount option is -rw and > the medium is read-only. `od' is drived from `da' so quick hack will > do the trick. This is all for scsi drives. I may not know everything, but I know most floppies aren't scsi! But, I am sure the problem exists for both. I know from experience that is exists or did exist for ata drives. I think he would be more likely to find the code for his problem in the 'ad' driver files. I could be wrong about this... but I know I had this happen to me on a computer without scsi equipment before. Of course, if he has a scsi zip drive as well, then both need to get fixed. ;-) Kevin Brunelle -- "Do not meddle in the affairs of sysadmins, for they are subtle and quick to anger." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message