If I change the bootloader kernel paramter line from ro to rw, and simply wipe out the roofs entry from fstab, I still have a bootable system. Is there a good reason why rootfs on btrfs should initially mount ro? It seems the legacy reason for this is so rootfs is available, yet can still have fsck run on it, after which it's remounted rw. None of that applies to btrfs does it? In which case we're slightly faster booting rw from the start, which is a bootloader configuration change. And then having installers exclude / from fstab. (Already systemd is mounting rootfs rw anyway, and, using special GPT partitiontypeguids, it's automounting swap and /home even if they're not listed in fstab.) Any comments on the efficacy of initial ro state when / is on Btrfs? Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
