Re: [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk

Rob Landley wrote:

But yeah, we're sticklers for correct behavior, and only attempt to remount readonly if we get EACCES or EROFS, not _just_ because we attempted a read/write mount and it failed.

BTW, busybox doesn't agree to do just mount -o remount,... /mountpoint, it wants also either the device name passed or the entry be present in fstab.

Regards,

Evgeny
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk
    • From: Rob Landley <[email protected]>

• References:
  • [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk
    • From: Jon Masters <[email protected]>
  • Re: [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk
    • From: Evgeny Stambulchik <[email protected]>
  • Re: [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk
    • From: Rob Landley <[email protected]>

• Prev by Date: Re: ext3 corruption: "JBD: no valid journal superblock found"
• Next by Date: Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
• Previous by thread: Re: [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk
• Next by thread: Re: [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]