Bug 21937 - README File on CD 1 incorrect
Summary: README File on CD 1 incorrect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rhl-ig-alpha
Version: 7.0
Hardware: alpha
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ed Bailey
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-08 06:32 UTC by Steve Dum
Modified: 2007-04-18 16:30 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-01-17 21:22:06 UTC
Embargoed:


Attachments (Terms of Use)

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.


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