In the last episode (Dec 28), Peter Pentchev said:
> On Thu, Dec 28, 2000 at 03:31:55PM +0100, Poul-Henning Kamp wrote:
> > In message <[EMAIL PROTECTED]>, "Walter W. Hop"
>writes:
> > > 2. Automatic file system checks
> > > In case of a powercycle or crash, it could be that a filesystem
> > > needs fixing. Now I don't know much about fs internals, but I
> > > guess that in most cases just answering 'Y' to fsck's questions
> > > will fix things. I would appreciate an option where an
> > > inconsistency would start up fsck in an "automatic" repair mode,
> > > with all actions logged and "undo" data being saved (in case
> > > manual review is needed).
> >
> > Alternatively it might be worth considering adding a
> > "remote-single-user" capability:
> >
> > If an fsck fails, ifconfig the interfaces and start an sshd so
> > people can get in remotely and fsck...
>
> What if an fsck on /usr fails? Other than that, I love the idea!
Force-mount it read-only if necessary, or simply copy a static sshd
into /sbin. Runnning fsck -y is the wrong solution, since if fsck
can't fix an error automatically, something pretty bad has happened
(physical media error, someone dd'ing onto the raw disk, etc)..
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
