![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=948555
http://bugzilla.suse.com/show_bug.cgi?id=948555#c11
--- Comment #11 from Olaf Hering
(In reply to Olaf Hering from comment #9)
(In reply to Michael Chang from comment #8)
Its up to the initrd to do that fsck for us, when nothing is mounted. If one really wants a read-only mount the 'ro' exists for that purpose. Too bad upstream does not understand booting...
I'm confused, in the bootparam for linux kernel that ro was explained as
"The 'ro' option tells the kernel to mount the root filesystem as 'read-only' so that filesystem consistency check programs (fsck) can do their work on a quiescent filesystem. No processes can write to files on the filesystem in question until it is 'remounted' as read/write capable, for example, by 'mount -w -n -o remount /'."
Yes, thats from the time when no initrd was used and the boot scripts expect a readonly mount. Its not the case for us since years, and most likely for everyone else too. -- You are receiving this mail because: You are on the CC list for the bug.