> On Tue, 30 Dec 2003 linuxproject@xxxxxxxxxx wrote:
>
>> First off I would like to say how much I enjoy Fedora, and I
>> think it is an awesome distro. The question I have is, how exactly
>> do you configure the kernel to work on other machines in the rpm.
>
> Take a peek at the runtime scripts:
>
> rpm -q --scripts kernel # kernel-smp, if necessary
>
> In particular, you'll be interested in the postinstall scriptlet.
>
> --Paul Heinlein <heinlein@xxxxxxxxxx>
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list@xxxxxxxxxx
> http://www.redhat.com/mailman/listinfo/fedora-devel-list
>
Ok, I ran rpm =q --scripts kernel and this is what it came up with for the
postinstall scriptlet:
postinstall scriptlet (using /bin/sh):
cd /boot
ln -sf vmlinuz-2.4.22-1.2135.nptl vmlinuz
ln -sf System.map-2.4.22-1.2135.nptl System.map
[ -x /usr/sbin/module_upgrade ] && /usr/sbin/module_upgrade
[ -x /sbin/mkkerneldoth ] && /sbin/mkkerneldoth
[ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --mkinitrd --depmod
--install 2.4.22-1.2135.nptl
>From what I understand, this changes directory to /boot, then create some
type of link (symbolic?) from vmlinuz-2.4.22-1.2135.nptl to vmlinuz and
the same for System.map, then it upgrades the modules, and I'm not sure
waht mkkernewldoth does, and then the new-kernel-pkg is what creates the
initrd image and runs depmod to look for dependencies and finally installs
the new kernel. However, I'm still not quite sure of how you setup your
kernel that is used on the install cds during the installation to work on
different machines. This scriptlet shows how it is installed, but I am
mainly wondering how kernel is setup to be so versatile that it will work
on different systems.
Thanks,
Casey Price
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-devel-list
|
