Re: /sbin/installkernel bug workaround?

[Adam Holisky <development buickfiles org>]

Well, I'm running RH 7.2, and I don't use lilo/grub or anything.  For me 
it's a good old' boot disk.  I update kernels quite a bit (as late as last 
night).  Are you working with the kernel as root when making the modules?  
That might be it..  Also, the only install command I do is 'make 
modules_install' (that works fine for me).

I did use grub for a week with 7.1 - and I never had this 
problem. However, upon closer examination of /sbin/installkernel (in RH 
7.2), it turns up to be a bash script.  Try removing the last line of the 
script, which makes reference to lilo.  If lilo exits, then the script will
run it, updating the boot record.  Or better yet: Since you have grub, you 
should be able to just replace "lilo" with "grub" and it should work 
(include any options you need to have grub update itself, i'm ignorent when
it comes to grub since i've used lilo 99% of the time).

Hope that help,

Adam



On Mon, 25 Feb 2002, Brian K. Jones wrote:

> Hi,
> 
> Trying to upgrade to kernel 2.4.17 on a Redhat 7.2 system with grub 
> as the bootloader.  'make modules install' and 'modules_install' both 
> fail, because the process calls /sbin/installkernel, which apparently 
> is dependent on lilo (?).  Seems strange that Redhat would make 
> something really important dependent on something that, in a default 
> install, doesn't exist.  I must be missing something.  Anyone know a 
> workaround?  How is everyone running RH 7.2 w/ grub performing kernel 
> installs?  Please excuse my ignorance - I've not used a grub based 
> system before this. (I'm tempted not to again, given this experience 
> :(  )
> 
> Thanks
>