Re: Why recovering from broken configs is too hard

From: Eric S. Raymond (esr@thyrsus.com)
Date: Thu May 03 2001 - 10:58:48 EST


David Mansfield <lkml@dm.ultramaster.com>:
> If so, given the above ruleset involving symbols A, B and C, and given
> that such a ruleset is violated for some reason (you don't even care
> why), use the following approach:
>
> set C to 'n' -> are we ok?
> set B to 'n' -> are we ok?
> set A to 'n' -> are we ok?
>
> Inform the user of each change. In a massively broken configuration you
> could end up with a lot of stuff set to 'n' ultimately, but I think that
> this generally would just end up shutting off troublesome configuration
> settings, and requiring that the user then reset them manually.

Actually this is the best idea I've seen yet, because the single "known-good"
configuration is almost all n values.

-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

Let us hope our weapons are never needed --but do not forget what the common people knew when they demanded the Bill of Rights: An armed citizenry is the first defense, the best defense, and the final defense against tyranny. If guns are outlawed, only the government will have guns. Only the police, the secret police, the military, the hired servants of our rulers. Only the government -- and a few outlaws. I intend to be among the outlaws. -- Edward Abbey, "Abbey's Road", 1979 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon May 07 2001 - 21:00:17 EST