Building new 2.4.1x kernels.
Kurt Wall
kwall
Mon May 17 11:43:18 PDT 2004
On Tue, Jan 21, 2003 at 09:17:36AM -0700, Collins Richey wrote:
> On Tue, 21 Jan 2003 08:19:57 -0500
> "David A. Bandel" <david at pananix.com> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Mon, 20 Jan 2003 20:12:05 -0500
> > begin kbb0927 at cs.com spewed forth:
> >
>
> > > Thanks. I clicked on the link on the main page. I knew there had to
> > > be tarballs of the complete kernel somewhere.
> >
> > I find it hard to believe that anyone on this list would waste
> > bandwidth to d/l 25Mb when one or two 1Mb d/l will do the same thing.
> > Patching is not hard. If there's no SxS on patching, ...
>
> My sxs on patching is still on the site.
>
> > It's brain dead simple and allows you to use your old
> > .config (as in `make oldoconfig`) and only decide to incorporate or no
> > the new stuff.
> >
>
> Just a side note, my experience with 'make oldconfig' has been less than
> stellar. I found out the hard way that 'make oldconfig' would change
> kernel options silently (sometimes built-in to modules, as I remember),
> so I only use 'make oldconfig' to point out changes. After getting
> burnt once, I now always save my existing config, use 'make menuconfig',
> load the old version, make changes, save my changes in the old place,
> then save the .config.
That's precisely what "make oldconfig" is *supposed* to do, remember existing
kernel options silently and only point out new configuration changes.
Kurt
More information about the Linux-users
mailing list