On Mon, Jul 9, 2012 at 9:00 PM, Nate Duehr <denverpi...@me.com> wrote: > > > He's not asking what to type at that point, he's asking how to keep the > kernel from stopping at that point and just do the (possibly destructive, but > often-times all that gets damaged/moved to lost+found, is open logs that were > open when the system went down) fsck. > > (Unfortunately I do not know the answer as to how to tell the initial fsck > just to go ahead and do the destructive fsck pass, without human > intervention, as I wouldn't want it to do that, but I see where the > communication misunderstanding is happening in the e-mail chain.) > > He's saying the desktop machines are "throwaway" and he doesn't want to take > the time to go over and look... do the fsck and if it trashes the filesystem, > he'll just re-image the machine later. Meanwhile, the user isn't confused by > the fsck message or interrupted by it, if the machine finds filesystem > problems at boot time. > > I would assume this is often a desired behavior on machines that have poor AC > power at remote sites. Give the fsck a try if I'm not there.
Answered a while back on the list: http://lists.centos.org/pipermail/centos/2012-January/122777.html -- Les Mikesell lesmikes...@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
