From owner-freebsd-current@FreeBSD.ORG Tue Apr 5 19:47:09 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 383ED16A4CE for ; Tue, 5 Apr 2005 19:47:09 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12AD943D5A for ; Tue, 5 Apr 2005 19:47:09 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) id j35Jl56g002455; Tue, 5 Apr 2005 12:47:06 -0700 (PDT) Received: from [10.1.1.245] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)j35Jl4va000232; Tue, 5 Apr 2005 12:47:05 -0700 (PDT) In-Reply-To: <20050405193652.0434F5D08@ptavv.es.net> References: <20050405193652.0434F5D08@ptavv.es.net> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <64913bc58ab8884979cc81a0529df142@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 5 Apr 2005 15:47:03 -0400 To: Kevin Oberman X-Mailer: Apple Mail (2.619.2) cc: current@freebsd.org Subject: Re: Panic on mount with write-locked USB media (umass) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2005 19:47:09 -0000 On Apr 5, 2005, at 3:36 PM, Kevin Oberman wrote: > Then I plugged it in with the write lock switch on and tried to mount > it. "mount_msdosfs: /dev/da0s1: Permission denied" Hey! I'm root! This > is supposed to work. Sounds like the partitioning and GEOM foot > shooting > thread. Oh, well, but this really could be handled better. What happens if you try to mount a read-only NFS volume as read-write? Being root gives one superhuman powers over the local machine, but it does not make a device which is write-protected by hardware writeable. It would be useful if mount was smart enough to notice when it is dealing with a read-only device, and try to mount such things read-only, rather than trying to mount things read-write by default and failing. Of course, the system shouldn't panic, either. :-) -- -Chuck