Bug 53122 - Problem at Startup with mkkerneldoth call in rc.sysinit
Summary: Problem at Startup with mkkerneldoth call in rc.sysinit
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: initscripts
Version: roswell
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-04 03:45 UTC by Adam McCarthy
Modified: 2014-03-17 02:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-09-04 03:45:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam McCarthy 2001-09-04 03:45:18 UTC
Description of Problem: 

Using the RedHat Public Beta of Roswell, boot up would hang at the use of
mkkerneldoth to generate kernel definition header(system stopped at
"Enabling Swap Space [OK]"). The odd thing was that this happened out of
nowhere after installation. In all honesty, the only thing that was being
done (user end) to the system was the repeated power cycles of the server
(I was marveling at using ext3). I was able to correct the issue of the
system hanging at the boot up by commenting out the call to mkkerneldoth in
rc.sysinit.  I figured I should report this as a
bug, and I guess hopefully learn a little bit more about the
function/importance of mkkerneldoth as I am ignorant about this script.
Thanks.

Version-Release number of selected component (if applicable):

roswell public beta

How Reproducible:
not sure exactly.

Steps to Reproduce:
1. Install RedHat 
2. wait for problem?
3. whine about problem?

Actual Results:
described above

Expected Results:
do not know, have only had this happen once on one box...other beta
installations have not had this happen yet...

Additional Information:
	
I hope that this is actually enough information.

Comment 1 Bill Nottingham 2001-09-04 03:55:06 UTC
fixed in later initscripts. remove /var/lib/rpm/__db*, and your system will boot
fine.


Note You need to log in before you can comment on or make changes to this bug.