From owner-freebsd-scsi Thu Nov 30 17:46:28 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA12318 for freebsd-scsi-outgoing; Thu, 30 Nov 1995 17:46:28 -0800 Received: from tcptest.psc.edu (tcptest.psc.edu [128.182.61.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA12312 for ; Thu, 30 Nov 1995 17:46:26 -0800 Received: (from peterb@localhost) by tcptest.psc.edu (8.7.1/8.7.1) id UAA19782; Thu, 30 Nov 1995 20:53:57 -0500 (EST) Date: Thu, 30 Nov 1995 20:53:57 -0500 (EST) Message-Id: <199512010153.UAA19782@tcptest.psc.edu> From: Peter Berger To: julian@ref.tfs.com CC: freebsd-scsi@freebsd.org In-reply-to: <199512010133.RAA13235@ref.tfs.com> (message from Julian Elischer on Thu, 30 Nov 1995 17:33:46 -3200 (PST)) Subject: Re: question: Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > From: Julian Elischer > Date: Thu, 30 Nov 1995 17:33:46 -3200 (PST) > Cc: freebsd-scsi@freebsd.org > X-Mailer: ELM [version 2.4 PL24] > Content-Type: text > > The ioctls can do things like 'format device' > (what do you mean 'mounted' read only) > you shouldn't be accessing a device for ioctls when it's 'mounted' > (as in mounting a disk partition). I mis-spoke; I meant "opened" read only. Is this a standard 4.4BSD Lite feature, or a specific FreeBSD-ism? > > > > > > what's the rationale for returning EACCES when trying to ioctl a > > device mounted read-only? inquiring minds want to know. > > > > (I encountered this problem with xmcd, which was failing because of > > it. I decided it was easier to change the kernel than to compile > > Motif, so....) > > > >