I don't see any possible scenario where FSCKFIX=no makes sense as a default. We don't debug broken filesystems with disk editors anymore; either fsck works, or we restore files from backup (or from Debian packages after running debsums). Filesystem developers might want to set FSCKFIX=no, or ask others to temporarily do so to reproduce a problem, but as a default I think it makes sense to use FSCKFIX=yes on all types of systems.
When fsck hits an error and offers to drop into a root shell, who does anything other than just running fsck again and saying "go ahead and fix it"? Let's remove the intermediate step. - Josh Triplett _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
