I am sure each individual has their own style for rolling kernels, but on
redhat systems my preference is after running "make config", edit the
Makefile. I tweekt the "EXTRAVERSION" variable towards the top so I can
have multiple kernels/module versions of the same revision (ex 2.2.16-1
2.2.16-2 2.2.16-RAID). Then for the install process run "make install"
instead of make bzImage. This does a nice job of copying the kernel and
System map, then linking it nicely in the /boot directory. The foundation
behind this is the /sbin/installkernel script on your box.
Debian has a nice way where it is very easy to compile the kernel into a
debian package, which can then be installed like any other deb package.
donfede
On Wed, 26 Jul 2000, Bryan Batchelder wrote:
> I've been wanting to mess around with the latest 2.4 kernels and RAID, but
> one thing that I just don't understand/know about the whole compiling the
> kernel is this: How do you manage the System.map file that resides in
> /boot on RedHat systems?
>
> I have no problems configuring/compiling/installing otherwise.
>
> Anyone have a good technique they use when they get to the point where its
> time to copy /usr/src/linux/arch/i386/boot/bzImage >
> /boot/vmlinux-<versionnumber> and copy /usr/src/linux/System.map > /boot and
> edit lilo.conf???
>
> I am curious, and I know that people on this list must be doing it alot :-)
>
> Thanks in advance,
> --b
>
> "A product's only late once, but it can suck
> forever." -- Ben Spees, Ambrosia Software
> --------------------------------------------
> Bryan D. Batchelder
> Palm Wireless/Internet Application Developer
> W: 813.935.7100
> W: 813-936-8844 x 423 (after 5:30PM EST)
> H: 727-547-1322
> M: 727-808-4296
> --------------------------------------------
> ConnectWise, Inc. (www.ConnectWise.com)
> 2803 West Busch Blvd, Suite 204
> Tampa, FL 33618
> --------------------------------------------
>
