Installing the new kernel

[jabr at blu.org (John Abreau)]

jbk <jbk at mail2.gis.net> writes:

> In the past (RH7.0) I did not use 'make install'
> to insert my custom kernel, instead I copied
> '.../arch/boot/bzImage /boot/vmlinuz-myversion'
> and also I copied '.../arch/boot/System.map
> /boot/System.mapmyversion' . There no longer seems
> to be the file System.map and the latest RH7.2
> guides to not mention this method any more.
> WHat is new about the boot process that has
> changed since the 2.2 kernel?

Last time I did a kernel upgrade, I examined the sources and discovered
the "rpm" ruleset. I don't know how "new" this is, just that I hadn't
noticed it before. This was for 2.4.17, which has worked great for me;
this was the first one where I was able to get kino working properly
with my firewire card for video capture and editing. This was using
Redhat 7.2.

Basically, I did a "make xconfig", then loaded the kernel config from
"/usr/src/linux-2.4.9-13/configs/kernel-2.4.9-i386.config" and saved 
it as the default .config, then did a "make rpm", then dug the new 
rpm out of /usr/src/redhat/RPMS and installed it.

Everything worked like a charm.


-- 
John Abreau / Executive Director, Boston Linux & Unix 
ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 344 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20020120/4f957651/attachment.sig>