From owner-freebsd-current Sat Mar 30 12:01:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA05509 for current-outgoing; Sat, 30 Mar 1996 12:01:41 -0800 (PST) Received: from sxt2.space.lockheed.com (sxt2.space.lockheed.com [192.68.162.109]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA05499 for ; Sat, 30 Mar 1996 12:01:37 -0800 (PST) Received: by sxt2.space.lockheed.com (5.65/DEC-Ultrix/4.3) id AA05238; Sat, 30 Mar 1996 11:55:44 -0800 Date: Sat, 30 Mar 1996 11:55:44 -0800 (PST) From: "Brian N. Handy" To: Joerg Wunsch Cc: FreeBSD-current users Subject: Re: Fixit Floppy Broken? In-Reply-To: <199603300804.JAA03375@uriah.heep.sax.de> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I wrote: > > > I complained earlier about 'ls' not working on the floppy drive...but I > Joerg responded: > I've read it, but your description is too vague. I cannot reproduce > the problem (it seems like some FS-related vnode locking, i don't > think this is particularly dependant on happening on the floppy drive > itself), and seriously, about nobody really uses file systems on > floppies... Well...I usually don't either. A colleage had blown away his libc.so.3.0, and needed a new copy so I figured this would be simple. I've figured out the problem, though. This should have occured to me but I'm an idiot. I had set the 'write-protect' tab, then mounted the drive read-write. FreeBSD didn't like that at all. So, as I see it, there are two ways to look at this: (1) I deserved it, or... (2) Maybe the mount routine should complain and die if it tried to mount the floppy read-write when the floppy is write-protected. Regards, Brian