From owner-freebsd-current  Sun Mar 31 09:38:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA06902
          for current-outgoing; Sun, 31 Mar 1996 09:38:54 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA06897
          for <freebsd-current@FreeBSD.org>; Sun, 31 Mar 1996 09:38:52 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id JAA13197; Sun, 31 Mar 1996 09:38:10 -0800 (PST)
Message-Id: <199603311738.JAA13197@precipice.shockwave.com>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-current@FreeBSD.org (FreeBSD-current users),
        handy@sxt2.space.lockheed.com (Brian N. Handy)
Subject: Re: Fixit Floppy Broken? 
In-reply-to: Your message of "Sun, 31 Mar 1996 11:46:00 +0200."
             <199603310946.LAA10060@uriah.heep.sax.de> 
Date: Sun, 31 Mar 1996 09:38:10 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


  From: J Wunsch <j@uriah.heep.sax.de>
  Subject: Re: Fixit Floppy Broken?
  As Brian N. Handy wrote:
  
  > > ..., 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.
  
  Why didn't you do what everybody else does: create a tar floppy?
  
  (Mount a r/o medium read-write.)
  
  > (2)  Maybe the mount routine should complain and die if it tried to mount 
  >      the floppy read-write when the floppy is write-protected.  
  
  Our floppy driver is not smart enough about write-protected media at
  open(2) time.

That is a bug.  Please file a PR