Bug 145516 - U6 does not include the boot.iso
Summary: U6 does not include the boot.iso
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: anaconda
Version: 2.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-19 07:51 UTC by Daniel Lindh
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2007-10-19 19:20:57 UTC


Attachments (Terms of Use)

Description Daniel Lindh 2005-01-19 07:51:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
CD1 of 2.1ES-U6 does not contain the boot.iso needed for kickstart
installations among other things. The /image/ directory is there but
the boot.iso is missing. I checked the others cds aswell but its
nowhere to be found

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

How reproducible:
Always

Steps to Reproduce:
1. Download the image
2. Burn och mount 
3. Check for boot.iso
    

Additional info:

Comment 1 Daniel Lindh 2005-01-21 07:45:04 UTC
Reproduce should be 
2. Burn or mount :-)

Comment 2 Shafer Stockton 2005-11-03 02:43:21 UTC
I'm quite curious where this handy file wandered off to also. :)

Comment 3 RHEL Product and Program Management 2007-10-19 19:20:57 UTC
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.


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