Author Topic: Kernel Installation  (Read 943 times)

Stryker

  • VIP
  • Member
  • ***
  • Posts: 1,258
  • Kudos: 41
Kernel Installation
« on: 15 October 2002, 21:55 »
Ok, I've recompiled my kernel and have a bzImage file. So I fall down into /boot and see the vmlinuz i expected, but i do not see any other bzImage to replace. What do I do?

voidmain

  • VIP
  • Member
  • ***
  • Posts: 5,605
  • Kudos: 184
    • http://voidmain.is-a-geek.net/
Kernel Installation
« Reply #1 on: 15 October 2002, 11:17 »
A "make install" should place the bzImage file in /boot but named vmlinuz-2.4.x-x just like the default kernel in RedHat. Also, if you make and install new kernel modules you might want to make a new initrd (see "man mkinitrd").

[ October 15, 2002: Message edited by: void main ]

Someone please remove this account. Thanks...

voidmain

  • VIP
  • Member
  • ***
  • Posts: 5,605
  • Kudos: 184
    • http://voidmain.is-a-geek.net/
Kernel Installation
« Reply #2 on: 15 October 2002, 12:22 »
I am always in the habit of making my kernel as modular as possible and also in the habit of making a new initrd even though most if the time it is not necessary. The only real reason for having an initrd is if you have device drivers in module form that are required prior to mounting the root file system (SCSI controller modules). I do work with a lot of SCSI based servers and not creating an initrd has bitten me in the past and the only real reason I am in the habit of creating one whether it's needed or not. You can always compile those necessary drivers statically into the kernel rather than putting them in modules. See step 12 here:

http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/custom-guide/custom-kernel.html

In fact RedHat recommends against the use of an initrd in a custom kernel in most cases. So you can just take my comments on it for what they're worth... Maybe just an awareness of what initrd is.
Someone please remove this account. Thanks...