From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: stoffel@casc.com (John Stoffel),
esr@thyrsus.com, cate@dplanet.ch,
linux-kernel@vger.kernel.org (CML2),
kbuild-devel@lists.sourceforge.net
Subject: Re: Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...]
Date: Thu, 03 May 2001 09:24:40 -0400 [thread overview]
Message-ID: <200105031324.f43DOeaA030953@pincoya.inf.utfsm.cl> (raw)
In-Reply-To: Message from Alan Cox <alan@lxorguk.ukuu.org.uk> of "Thu, 03 May 2001 13:47:25 +0100." <E14vIW2-0005US-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> said:
> In-Reply-To: <200105031232.f43CW7aA009990@pincoya.inf.utfsm.cl> from "Horst von
> *** Brand" at May 03, 2001 08:32:07 AM
> > > No, we're just asking you to make the CML2 parser more tolerant of old
> > > and possibly broken configs.
> > It is _much_ easier on everybody involved to just bail out and ask the
> > user (once!) to rebuild the configuration from scratch starting from
> > the defaults.
> No. Every new kernel changes the constraints so every new kernel you have
> to reconfigure from scratch. That also makes it very hard to be sure you got
> the results right.
Really? I've mostly seen symbols added, very rarely did I see constraints
changed. But that might be just my narrow view on the matter...
> oldconfig has a simple algorithm that works well for current cases
>
> Start at the top of the symbols in file order. If a symbol is new ask the
> user. If a symbol is now violating a constraint it gets set according to
> existing constraints if not it gets set to its old value.
I understand that to mean: "If it is new and (at least somewhat)
unconstrained, ask the user. If fully constrained, take that value
unconditionally." This is a _very_ different case from a broken
configuration as a starting point, in which constraints are violated with
the values as set.
Hell, I had to rebuild my .config files from scratch a few times already
because of wild changes in the hardware on which the resulting kernels
would have to run, its not _that_ big a deal to have to perhaps have to do
it once each time a new stable kernel series starts or so.
People, remember that doing certain things in software is just not worth
the effort.
--
Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
next prev parent reply other threads:[~2001-05-03 13:26 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 23:35 CML2 1.3.1, aka "I stick my neck out a mile..." Eric S. Raymond
2001-04-29 15:12 ` John Stoffel
2001-04-29 22:35 ` Eric S. Raymond
2001-04-29 22:43 ` [kbuild-devel] " Eric S. Raymond
2001-04-30 7:52 ` Anton Altaparmakov
2001-04-30 8:03 ` Eric S. Raymond
2001-04-30 16:17 ` volodya
2001-04-30 16:28 ` John Stoffel
2001-04-30 17:39 ` Eric S. Raymond
2001-04-30 19:16 ` Peter Samuelson
2001-04-30 19:25 ` Eric S. Raymond
2001-05-01 9:23 ` Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...] Giacomo A. Catenazzi
2001-05-01 16:31 ` Eric S. Raymond
2001-05-01 21:35 ` Olivier Galibert
2001-05-01 22:26 ` Tom Rini
2001-05-02 13:32 ` Giacomo Catenazzi
2001-05-02 17:49 ` Eric S. Raymond
[not found] ` <200 <3AF00C53.5EEE8E01@math.ethz.ch>
2001-05-02 20:12 ` John Stoffel
2001-05-03 7:04 ` Hierarchy doesn't solve the problem Eric S. Raymond
2001-05-03 7:34 ` Urban Widmark
2001-05-03 7:46 ` Eric S. Raymond
2001-05-03 14:33 ` Juan Quintela
2001-05-03 16:16 ` Eric S. Raymond
2001-05-03 22:20 ` Mike Castle
2001-05-03 12:32 ` Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...] Horst von Brand
2001-05-03 12:47 ` Alan Cox
2001-05-03 13:24 ` Horst von Brand [this message]
2001-05-03 14:40 ` Juan Quintela
2001-05-03 16:07 ` Eric S. Raymond
2001-05-03 16:04 ` Eric S. Raymond
2001-05-03 17:36 ` Alan Cox
[not found] ` <15084.12830.973535.153706@gargle.gargle.HOWL>
2001-04-29 22:41 ` CML2 1.3.1, aka "I stick my neck out a mile..." Eric S. Raymond
2001-04-30 1:36 ` Anton Altaparmakov
2001-04-30 1:41 ` Eric S. Raymond
2001-04-30 2:13 ` [kbuild-devel] " John Cowan
2001-04-30 2:24 ` Alexander Viro
2001-04-30 5:41 ` David Emory Watson
2001-04-30 5:50 ` Alexander Viro
2001-04-30 6:12 ` David Emory Watson
2001-04-30 6:53 ` Eric S. Raymond
2001-04-30 7:11 ` [OT] " Jeff Garzik
2001-04-30 7:17 ` Alexander Viro
2001-04-30 15:54 ` [kbuild-devel] " Eric S. Raymond
2001-04-30 10:57 ` John Cowan
2001-04-30 14:25 ` Kai Henningsen
2001-04-30 13:30 ` David Woodhouse
2001-04-30 13:29 ` David Woodhouse
2001-04-30 7:05 ` volodya
2001-04-30 7:23 ` Alexander Viro
2001-04-30 7:40 ` Eric S. Raymond
2001-04-30 9:09 ` [Moving rapidly offtopic] " Henning P. Schmiedehausen
2001-04-30 16:16 ` nick
2001-04-30 17:12 ` [kbuild-devel] " Eric S. Raymond
2001-04-30 17:20 ` [OT] " Jeff Garzik
2001-04-30 17:25 ` Rik van Riel
2001-04-30 19:44 ` [kbuild-devel] " Gerhard Mack
2001-04-30 19:47 ` nick
2001-04-30 3:26 ` volodya
2001-04-30 8:13 ` Anton Altaparmakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200105031324.f43DOeaA030953@pincoya.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cate@dplanet.ch \
--cc=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stoffel@casc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®