[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
Jeff Garzik <>:
> "Eric S. Raymond" wrote:
> > OK, so you want CML2's "make oldconfig" to do something more graceful than
> > simply say "Foo! You violated this constraint! Go fix it!"
> [...]
> > Have I got the point across yet? There are *no* good solutions
> > to this problem. There aren't even any clean ways to separate
> > easy cases from hard ones.
> No good solutions? Then how come I use "make oldconfig" every day...

You fix broken configs by hand. That's what you'll do in the new
system, too.

> IMHO "make oldconfig" must stay.

There was never any risk it would go away.
<a href="">Eric S. Raymond</a>

Everything you know is wrong. But some of it is a useful first approximation.
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.106 / U:0.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site