Here are my kernel RPMs built from 2.2.18pre17 with several patches from the RedHat kernel source. Release 0_biscuit_3 has only been tested on my laptop (the i586 kernel). I am holding off until I fix a couple minor bugs from 3 and redo the spec a little bit to make release 4.
The spec file is essentially the same for all of these kernels. There is a set of defines at the top that decide which type of kernel to build. Currently only normal and win4lin are implemented, but I will get around to doing more later. Also, the spec from the win4lin kernel is slightly newer than that of the normal kernel, but when building a normal kernel, they should function identically.
It should be noted that there is a small bug with the kernel configuration scripts that makes it necessary to answer "No" to a configuration question even though the option is properly defined in the config file.
When building RPMs, it is usually better to not build as root. Building as root gives all of the scripts control over the system and is a really bad idea. To build as a normal user you must set up a ~/.rpmmacros file with the following line in it:
%_topdir /home/{YOURUSERNAME}/RPM
Then create the RPM directory and the BUILD, RPMS, SOURCES, SPECS, and SRPMS subdirectories, and in the RPMS directory create the i386, i586, i686, and noarch directories. From then on it should be possible to install source RPMs as yourself and then build them as yourself.
In fact, one of the advantages of my kernel RPMs versus RedHat's is that you actually can build as a normal user. RedHat's spec makes use of the mknod command to create device files for ibcs and therefore can not be built as a normal user
Please note that I am not building iBCS, but I am building pcmcia support. If anybody actually wants iBCS I'll build that too, or I might do it anyway if I feel like it. So lemme know if it's important to you.
To install the kernel, simply do the usual rpm -ivh or use your favorite graphical rpm installer. The post install script will create the appropriate vmlinu[xz] and System.map symlinks in /boot. The script then runs mkinitrd for the new kernel and creates a symlink to it. The script then prints a message reminding you to reconfigure your bootloader. It is strongly recommended that you configure your boot loader so that you can still boot your current kernel in the event that this new kernel does not work for you. To do that, create an entry pointing to the appropriate vmlinuz and optionally initrd.img files that otherwise matches your current entry pointing to vmlinuz and initrd.img.
NOTE: Your browser either does not support frames, or is configured to display unframed content. To navigate the site you should visit the navigation page.