Bug 621

Summary: Kernel-Headers-2.0.36-1 rpm
Product: [Retired] Red Hat Linux Reporter: winston2
Component: kernelAssignee: David Lawrence <dkl>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1998-12-30 19:19:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description winston2 1998-12-27 04:12:40 UTC 
When you install this rpm it fails to complete and
apparently does not link the new modules to the proper
directory. You have to do a ln -sf 2.0.36-1 2.0.36 or else
you have a boot up error unable to open 2.0.36 modules.dep
and its down hill from there. I wasted many hours with this
and luckily I found help on usenet.
Comment 1 Aleksey Nogin 1998-12-27 06:34:59 UTC 
Are you sure it was "kernel-headers-2.0.36-1", not "kernel-2.0.36-1"?
Why did you chose Component "rpm" instead of "kernel"?
Comment 2 winston2 1998-12-27 20:54:59 UTC 
I performed the ln -sf 2.0.36-1 2.0.36
in the /lib/modules directory.
I performed the RPM from /tmp.

If I did not do the ln the OS could not find the proper modules.dep
file.
Comment 3 Jeff Johnson 1998-12-30 19:19:59 UTC 
On the next reboot, rc.sysinit should do
	ln -sf /lib/modules/2.0.36-1 /lib/modules/preferred
and then depmod -a will be run on the path /lib/modules/preferred

That's what is supposed to happed with Red Hat (and Red Hat only)
kernel-* rpm's. Please reopen this bug if a reboot does not
create  a /lib/modules/preferred symlink.