[lkml]   [2001]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why recovering from broken configs is too hard
David Mansfield <>:
> 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="">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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.076 / U:0.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site