Bug 21937

Summary: README File on CD 1 incorrect
Product: [Retired] Red Hat Linux Reporter: Steve Dum <steve_dum>
Component: rhl-ig-alphaAssignee: Ed Bailey <ed>
Status: CLOSED CURRENTRELEASE QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: alpha   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-01-17 21:22:06 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 Steve Dum 2000-12-08 06:32:08 UTC
the README file on CD 1 contains the following text:
------
Once MILO has been installed, you can boot this CD as follows:

    boot -t iso9660 scd0:kernels/generic.gz root=/dev/scd0

where file.gz is the proper kernel for your machine (see kernels/README
for information) and scd0 is the device name of your CDROM drive.
------
I assume that the intent is that generic.gz and file.gz
are supposed to be the same name.
Next, there is no README file in the kernels directory,
much less a vast collection of kernels.  There is only
3 files there vmlinux.gz, vmlinuz.24 and vmlinuz.j

It would be nice to document what these are, and since
it appears that vmlinux.gz is a generic kernel for all
alpha architectures, it would be nice to say that somewhere, 
like in the highlights in RELEASE-NOTES thatthere is now
one generic kernel.

Comment 1 Tammy Fox 2001-01-15 03:46:56 UTC
I don't know how this was assigned to doc (this is not a valid email
address). I have assigned it to Ed because it is related to the Release Notes
and the README file. The Official Red Hat Linux Alpha Installation Guide
contains the correct commands to boot the installation program.

Comment 2 Tammy Fox 2001-01-17 21:22:03 UTC
Somehow this was assigned back to me instead of Ed.

Comment 3 Ed Bailey 2001-05-22 20:07:22 UTC
No longer an issue in the current release.