2014/12/11 3:48 "Brian" <a...@cityscape.co.uk>: > > On Wed 10 Dec 2014 at 19:23:07 +0300, tv.deb...@googlemail.com wrote: > > > On 10/12/2014 14:04, Andrei POPESCU wrote: > > > > > >Of course, there's also the option of completely disabling automatic > > >fsck (there are several ways to do this), as I understand is the default > > >for new enough filesystems. This would make more sense for me on systems > > >with bad power (you'd still get the "bad shutdown" check). > > > > Yes, disabling and doing manual checks from time to time is a > > possibility, but you'd have to convince all users to hand their > > gears to an admin outside of business hours. The said admin (who > > might just bee a teacher in fact) might not be happy with the idea > > of a week-end spent at fsck'ing the world out of the compulab, just > > because of systemd. With the conditions I mentioned earlier running > > a fsck regularly is a good thing, just not being able to interrupt > > it in case of emergency isn't. > > Ever since Wheezy automatic fsck has been disabled on new installs. [...]
Odd. The last time I booted my wheezy-by-install system, it did an automatic fsck. I did nothing in particular to enable that. I think you are reading things into the documentation that you want to be there. -- Joel Rees