Re: Panic on mount with write-locked USB media (umass)

From: Kevin Oberman <oberman_at_es.net>
Date: Tue, 05 Apr 2005 13:18:20 -0700
> From: Charles Swiger <cswiger_at_mac.com>
> 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_at_es.net			Phone: +1 510 486-8634
Received on Tue Apr 05 2005 - 18:18:20 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:31 UTC