lkml.org 
[lkml]   [2001]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Why recovering from broken configs is too hard


On Thu, 3 May 2001, Eric S. Raymond wrote:

> The obvious thing to try is to start with the configuration you have
> and try mutating the variables that occur in the broken constraint(s).
> Of course, there are 3^n of these where n is the number of distinct
> variables, so this is going to blow up really fast; 3, 9, 27, 81, 243
> and we ain't even to six symbols yet. By the time we get to the
> twelve variables that could be linked by just *one* constraint, there
> are 531,441. Even if you can check 500 configurations a second it's
> going to take 16 minutes just to get a candidate list.
>
> But wait! There's more! If some of the variables participate
> in multiple constraints, the numbers get *really* large. Worst-case
> you wind up having to filter 3^1976 or

<DSW>
I see your 3^1976 and raise "unsolvable". It's a special case
of termination problem, dontcha see.
</DSW>

Yes, generic problem is damn hard. The thing being, _this_ problem is
damn far from generic.

-
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/

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