Bug 118554 - mkinitrd fails when no System.map is found
Summary: mkinitrd fails when no System.map is found
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: RC 4
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Hannes Reinecke
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-23 09:34 UTC by Takashi Iwai
Modified: 2005-12-05 14:57 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
mkinitrd (64.97 KB, text/plain)
2005-12-05 14:56 UTC, Hannes Reinecke 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Takashi Iwai 2005-09-23 09:34:25 UTC 
The recent mkinitrd requires System.map (or the one with the version suffix) on
/boot.  If not exists, however, it still creats initrd file which is unusable
because of lack of modules.dep.

mkinitrd should check the existence of System.map and doesn't pass -F option if
not there, or completely fail.  Better would be to have another option to
specify System.map explicitly like -k or -i.
Comment 1 Hannes Reinecke 2005-12-05 14:53:37 UTC 
Added a switch '-M' to mkinitrd to specify a System.map file to use. Abort if no useable file has been found.
Comment 2 Hannes Reinecke 2005-12-05 14:56:36 UTC 
Created attachment 59829 [details]
mkinitrd

New /sbin/mkinitrd.
Comment 3 Hannes Reinecke 2005-12-05 14:57:03 UTC 
Will be submitting the new mkinitrd for the next Alpha release.