Bug 181750 - enabling xen group should still install non-xen kernel
Summary: enabling xen group should still install non-xen kernel
Keywords:
Status: CLOSED DUPLICATE of bug 181618
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-16 06:49 UTC by Alexandre Oliva
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-20 20:28:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alexandre Oliva 2006-02-16 06:49:00 UTC
Description of problem:
If you select the xen package group, you end up without a non-xen kernel to boot
from.  I don't think this is appropriate; I'd rather get both to choose from,
lest the xen kernel not be able to boot at all, while a subsequent update might.

I'm not even sure the xen-hypervisor kernel should boot up by default.

Version-Release number of selected component (if applicable):
anaconda-10.92.4-1

How reproducible:
Every time

Steps to Reproduce:
1.Select the `xen' package group in the installer
2.Install
3.Try another install, with kickstart, and request the `kernel' package
  
Actual results:
After 2., the non-xen kernel was not even installed.  After 3, it is, but is not
the default.

Expected results:
Non-xen kernel should probably be installed, and should still be the default
unless requested otherwise.

Additional info:

Comment 1 Jeremy Katz 2006-02-20 20:28:44 UTC

*** This bug has been marked as a duplicate of 181618 ***


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