Re: mount & umount read-only floppy: unmount failed: Input/output error ??

From: Rob (listone_at_deathbeforedecaf.net)
Date: 06/30/03

  • Next message: Rob Lahaye: "Re: mount & umount read-only floppy: unmount failed: Input/output error ??"
    To: "Rob Lahaye" <lahaye@users.sourceforge.net>, <freebsd-questions@freebsd.org>
    Date: Mon, 30 Jun 2003 19:41:50 +0930
    
    

    That's strange - I get errors as soon as I try and do this, before the
    filesystem is even available.

    Perhaps the updates from mounting the floppy aren't being written out to
    the actual media until you try to unmount it - some kind of caching
    issue?

    What happens if you try to touch a file on the (incorrectly) writeable
    floppy?

    ----- Original Message -----
    From: "Rob Lahaye" <lahaye@users.sourceforge.net>
    Subject: Re: mount & umount read-only floppy: unmount failed:
    Input/output error ??

    >
    > Rob <listone@deathbeforedecaf.net> wrote:
    > > So did you put a write-protected floppy in, and try and mount it
    > > read/write?
    > >
    > > That's not going to work....
    >
    > I would agree, if the mount didn't work. But that's what I
    > tried to point out.
    >
    > As it is now, the trouble arises from the fact that you actually
    > CAN read/write mount a read/only-floppy. No complaints from the
    > mount command.
    >
    > However, you can't umount it anymore! So you're stuck and it
    > is mounted for-ever! Unless, you take the floppy out, change it
    > to read/write, put it back in the drive and do the umount again.
    >
    > Why does mount not check the read/write of the floppy?
    > And if it doesn't, for some reason, why then all of a sudden
    > umount does check for the read/write thing?
    >
    > Rob.
    >
    > PS: this is with FreeBSD 4.8
    >
    > _______________________________________________
    > freebsd-questions@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > To unsubscribe, send any mail to
    "freebsd-questions-unsubscribe@freebsd.org"
    >

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Rob Lahaye: "Re: mount & umount read-only floppy: unmount failed: Input/output error ??"

    Relevant Pages

    • Re: Locking Down a Linux Box
      ... I'm new to this list, but we were talking about network security, ... It currently doesn't use (mount) any hard drive ... > can be write protected so not having floppy support in your kernel only ...
      (Focus-Linux)
    • Re: Locking Down a Linux Box
      ... > routers/firewalls on a floppy. ... changes -- there would be no mount or modprobe program left by the ... > administration on this host anymore, but an attacker could ... > then leave the filesystem readonly. ...
      (Focus-Linux)
    • Re: Locking Down a Linux Box
      ... Mine will be a firewall, ... There are several linux routers/firewalls on a floppy. ... It currently doesn't use (mount) any hard drive ... > The permissions on the filesystem are stripped to bare minimums, ...
      (Focus-Linux)
    • Re: mount & umount read-only floppy: unmount failed: Input/output error ??
      ... Rob wrote: ... if the mount didn't work. ... CAN read/write mount a read/only-floppy. ... Unless, you take the floppy out, change it ...
      (freebsd-questions)
    • Re: Card Reader
      ... on the mount of a fat32 filesystem, but native Unix filesystems do a little interlocking-inodes dance during a mount, and the filesystem can only be unmounted if the media is present so the dance can be reversed. ... any write activity has been seen on the hardware, pulling the card out won't harm anything at all. ... When the floppy activity has stopped, pull the disk from the drive. ...
      (rec.photo.digital)