On Fri, Nov 16, 2012 at 11:53:56AM +0100, Ruediger Meier wrote:
On Friday 16 November 2012, Dr. Werner Fink wrote:
On Thu, Nov 15, 2012 at 01:10:29PM -0800, Linda Walsh wrote:
The most optimal way for deficient file systems that need fsck is likely to use an initrd if it is needed that often. The alternative is to pick an advanced journaling file system rather than a modern one that, for me, has only needed a real 'fsck', only *once* in the past 12 years of constant usage.
In other words: as this had worked for you the last 12 years due luck you want that all other users may risk data loose?
The initrd lives also on a filesystem which can't be checked before mounting it (at least using grub). And moreover the initrd can be broken itself. From my practical expirience I had more often a broken initrd than a broken root file system. Also repairing a file system is IMO usually more easy than repairing a broken initrd, specially since the initrd got more and more complicated.
/suse/werner> mount | grep /boot /dev/sdb1 on /boot type ext2 (rw,acl,user_xattr)
Anyway, having the possibility of booting without initrd does not force any user to do it. But removing that possibility is one more step to reach the final goal to have a non-configurable system ...
What does mean broken initrd? The only case I'm remembering is compiling and installing a kernel and then forgot to run mkinitrd. But I'm also remembering on some power outages which had lead to a fsck/repair of the root file system. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org