Fsck should run from cron (not at boot) and report errors

Fsck runs by default every 30 mounts for the root filesystem. Inevitably, this happens when you most need the computer to boot quickly. A proper alternative should work like this: fsck runs once a week as a cron job but only _checks_ the filesystem for errors (this way it is ok to run the check while the filesystem is mounted). If there are errors, then the user is prompted to repair the filesystem, hopefully through some relatively easy process that does not involve manually booting to single user mode. This may involve making changes to fsck since to my knowledge it does not have a "read only" mode.