Bug 10252

Summary:	Need /boot/README about System.map, etc.
Product:	[Retired] Red Hat Linux	Reporter:	swear
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	kenneth_porter
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:38:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description swear 2000-03-19 20:24:43 UTC

Actually, the kernel-source RPM, but that was rejected.

The /usr/src/linux/README kernel-building info doesn't say what to do
about the links /boot/System.man and /boot/module-info like where do I
get the real files after a kernel build.  Since you probably can't
convince the kernel guys to change their README, I suggest you put some
notes in /boot/READEM.  Those links have been a long-standing gripe I've
had with the several RHL versions; such a file would have reduced my grief.

It probably ought to be in the "filesystem" RPM or something because many
people don't bother with "kernel-sources", getting the kernel from a
non-Red-Hat source.

Comment 1 kenneth_porter 2000-03-22 06:59:59 UTC

Amen! Actually, the link for System.map should be set in /etc/rc.d/rc.sysinit,
at the same time the module directory is selected. ("ln -sf
/boot/System.map-$mver /boot/System.map") That means the initscripts package
needs to be fixed. (Perhaps this bug should be reassigned to that component.)

(See my related gripe on the RH-specific undocumented .rhkvmtag in bug# 10299.)

Comment 2 Bugzilla owner 2004-09-30 15:38:46 UTC

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/