[lug] Re lpc status and sh

[Nate Duehr]

I think RedHat's doing this by default in their kernel-source RPM's now,
using "-custom", but I haven't checked that to be sure.  It just acted
that way the other day when I was doing a kernel build on a 7.2 box.

On Tue, Nov 13, 2001 at 02:40:26PM -0700, D. Stimits wrote:
> Nate Duehr wrote:
> > 
> > On Sat, Nov 10, 2001 at 11:42:08PM -0500, John Karns wrote:
> > > On Fri, 9 Nov 2001, J. Wayde Allen said:
> > > make menuconfig
> > > make dep
> > > make bzImage
> > > make modules
> > 
> > Don't forget :
> > 
> > make modules-dep (although I think the make dep takes care of this)
> > ... before building modules
> > 
> > and...
> > make modules-install
> > ...after building modules
> > 
> > And it's always a good idea to
> > 
> > make mrproper
> > and/or..
> > make clean
> > 
> > Before starting.
> 
> One of my favorite tips is to choose a new "EXTRAVERSION" in the
> Makefile before starting. When you run "uname -r", and get back
> something like 2.4.9-15smp, the "-15smp" is the EXTRAVERSION. This stops
> your original kernel and modules from being overwritten during the
> install, and it can be used to append to your System.map file as an aid
> there too (anyone seen unresolved symbols while loading modules?). E.G.,
> edit /usr/src/linux/Makefile, find the EXTRAVERSION line, and do
> something like:
> EXTRAVERSION =-TestRun
> (note that there is no space between the "=" and the "-")
> 
> Assuming your kernel source is 2.4.15, then you'd copy your bzImage to
> /boot/bzImage-2.4.15-TestRun, and your System.map to
> /boot/System.map-2.4.15-TestRun. Doing a make modules-install would then
> write modules to a new directory /lib/modules/2.4.15-TestRun/, rather
> than overwriting or getting mixed up with prior modules. It's a very
> good idea to then save a working .config file from
> /usr/src/linux/.config based on that name in some protected location,
> e.g., "cp /usr/src/linux/.config
> /root/archive/kernel/config-2.4.15-TestRun".
> 
> And if you create an initial ramdisk with mkinitrd, you should also name
> the ramdisk this way, e.g., "/boot/initrd-2.4.15-TestRun". No matter
> what minor change you make to the configuration, it should be serialized
> or named differently each time you decide to keep the configuration,
> you'll always be able to go back and compare changes or reproduce exact
> kernels later.
> 
> Now each time you run lilo and set a new kernel, your old ones can be
> left in as backup until certain you don't want them anymore. Then you
> can delete the old kernels, modules, System.map's, and initial ramdisks
> without losing the history (never erase old config's kept in archive).
> It's also a very good idea to cross-save config's on different machines
> so you can figure out what you have from a working one when something
> dies.
> 
> D. Stimits, stimits at idcomm.com
> 
> > 
> > --
> > Nate Duehr <nate at natetech.com>
> > 
> > GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
> > Public Key available upon request, or at wwwkeys.pgp.net and others.
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.