From owner-freebsd-current@FreeBSD.ORG Tue Apr 5 20:18:20 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 AB63416A4CE for ; Tue, 5 Apr 2005 20:18:20 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AF5343D58 for ; Tue, 5 Apr 2005 20:18:20 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Tue, 05 Apr 2005 13:18:20 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 042685D07; Tue, 5 Apr 2005 13:18:20 -0700 (PDT) To: Charles Swiger In-reply-to: Your message of "Tue, 05 Apr 2005 15:47:03 EDT." <64913bc58ab8884979cc81a0529df142@mac.com> Date: Tue, 05 Apr 2005 13:18:20 -0700 From: "Kevin Oberman" Message-Id: <20050405201820.042685D07@ptavv.es.net> 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 20:18:20 -0000 > From: Charles Swiger > Date: Tue, 5 Apr 2005 15:47:03 -0400 > > 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. :-) I think that is what I said. I am almost sure that this is how it used to work. I'm not sure whether the change was caused by something in msdosfs or GEOM (or somewhere else), but I sure preferred it when the RO device mounted RO. CDs still do this (thankfully). This makes me suspect msdosfs is the culprit. But the real concern on my part was the panic. The other issue is just POLA and annoyance. Panics should NEVER happen (although they always will). -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634