Comment # 10 on bug 948555 from Michael Chang

(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 /'."

And eventually the system is remounted as 'rw' in initrd or any other boot
scripts. They dont really a give a ro mounted root and unusable. That's why I
think ro is a safer option to boot than rw to enforce a quiescent mount
initially ..

Thanks.