Before I reboot with the corrected boot loader. I wanted to summarize
what make rpm does. After you make your config file, it goes through and
compiles the kernel and modules.
If the build process is successful. Like, in my case, it was. It will
rename the bzImage vmlinuz-2.5.xx and copy the config, system.map over
to a directory called
/var/tmp/kernel-2.5.70-root/boot
the actual file names will be called the below:
config-2.5.70 System.map-2.5.70 vmlinuz-2.5.70
It will also locate the modules in the below directory. I'm not sure how
rpm uses these, but I assume that it will package them up and locate
them in /lib/modules/2.5.70 upon installing a successful rpm.
/var/tmp/kernel-2.5.70-root/lib/modules/2.5.70
I simply compared the modules directory with my other modules version.
The directories looked the same, in structure. I just copied the 2.5.70
directory over to /lib/modules. I renamed the other kernel modules first
though.
Next try without the debugging information and using rpmbuild might go
through the whole process. I like the process so far. It does save alot
of steps and will make installing and upgrading kernels a bit easier and
opens up customization and automation.
Try it, it is interesting.
Jim
--
"Marriage is like a cage; one sees the birds outside desperate to get
in, and
those inside desperate to get out."
-- Montaigne
