On Monday 02 January 2006 16:18, Paul wrote:
On Monday 02 January 2006 02:26, Gene Heskett wrote:
Really, once the initial config to a working kernel has been achieved, building new ones is pretty simple.
The real, bites everybody behind the short hair problem is that the distros do not make it the least bit easy to discover the .config that built the kernel thats actually running.
Double checked Fedora, and they, like Debian, install a config-<KVER> in /boot along with the vmlinuz image. The only difficulty is weeding out the multitude of drivers that are not needed.. Even patching is painless as long as you follw the advice of using a virgin tarball from kernel.org. I think the one thing that does trip people up when it comes to patching with RTAI is one or two of the config options. The favorite one is to enable APM and then blame EMC for a ragged output.
Don't know about Fedora, but Debian has a make-kpkg script that will clean, configure, and build the kernel, and serve it up as a deb package. A great little tool if you are concerned about being able to purge a kernel image from the system in the future.
One can use mc for the housecleaning if required, and probably quicker. And totally legal in the case of a kernel.org kernel built and installed locally, just delete them from /boot, /lib/modules, and that entry in menu.lst or grub.conf (for rh flavored stuff) menu.lst or grub.conf, depending on your favorite poison, is a text file that doesn't take a rocket scientist to edit. The only thing confusing is that the use of the word 'root' means 2 different things depending on where it is in the file. Lets see if I can clarify this and take a bit of the obtuseness out of this mystery file called menu.lst or grub.conf. Here is the entry I'm presently booted to, out of 24 choices in my grub.conf: --------------- # grub.conf generated by anaconda (yeah sure, years ago) # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img # boot=/dev/hda1 default=5 fallback=4 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz # 5 The above line is a comment, added by me purely for me to keep track of the current position in the list. See the default and fallback entries above. title Fedora Core 2 Linux (2.6.15-rc7) root (hd0,0) The word root (hd0,0) above, means the first drive on the first controller channel. Search its mbr for partition info. kernel /vmlinuz-2.6.15-rc7 ro root=/dev/hda7 elevator=cfq The word root= above means the / partition, in this case, the first drive, 7th partition. It could, and I have done it, point to a different drive for dual boot lashups, as in /dev/hdd3 or whatever, which would be the last (4th) drive on the first controllers second channel, 3rd partition in, is the partition to be mounted as /. initrd /initrd-2.6.15-rc7.img Self explanatory. End of that particular entry. Does this help explain that? Or am I carrying coals to Newcastle. :-)
Regards, Paul.
-- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.