-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I haven't looked at how it actually works yet, but the idea of being able to check the filesystem and/or blocks read-only while the system is running and only warn on error sounds fairly appealing. I imagine the implementation could look something like the notification for a needed reboot after a kernel upgrade, or the one for restarting firefox after an update, with a little "I have important information for you!" lightbulb in the notification area that would explain what's going on, and warn that the process could take a significant amount of time (if possible, an estimate based on disk size?). Note that we need to make sure the check in the background uses only idle CPU time, not running immediately after you boot (making your login annoyingly slow), or at a scheduled time jumping on it 100% (see Beagle).
I don't for one minute buy the argument that "Windows manages without disk checks" being a valid point against us do it - I would be very upset if we did everything like Windows, as there is a reason I switched. I think both fsck and badblocks are useful tools, and definitely see the advantage to running them on a regular basis. The discussion here shouldn't be about *whether* to check for disk and filesystem errors, but *how* and *when* we could do so in a more effective and less intrusive manner, with more explanation of what is happening and warning of when time-consuming processes will be necessary. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHAPdqKlAIzV4ebxoRAuwtAKCwrk6NF9UpdGpHl+Gd8oXAxwDd+gCfe5oj QdXiEETFEHjWTQXXVOIPF8o= =ywTF -----END PGP SIGNATURE----- -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
