Bug 432250 - Feature request: allow same kernels for different archs te be installed simultaniously
Summary: Feature request: allow same kernels for different archs te be installed simul...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-10 13:14 UTC by Rolf Fokkens
Modified: 2008-08-21 20:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-08-21 20:10:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rolf Fokkens 2008-02-10 13:14:53 UTC
Description of problem:
1) A single grub config for F8 can be used for both an i386 and an x86_64
install on the same machine, but both installs write conflicting kernel info in
shared config when the kernel is upgraded, becaus of the same image naming. As
to why both a i386 and a x86_64 are installed: te investigate game issues on
x86_64 for 32bit games - Return to Castle Wolfenstein has an issue for example.
2) Potential future use: run a 32bit F8 install on a x86_64 kernel as an option.
during boot the user may choose the 32bit kernel or the 64bit kernel. This may
help to intensify the x86_64 kernel use. Agreed: modutils needs to be changed
for this.
3) livna provides nvidia kernel modules for i586, which forces me to use a i586
kernel though I would like to keep my i686 kernel as well. This however is not
possible.

This suggestion may have been posted and/or discussed before, but I wasn't able
to find it.

Comment 1 Bug Zapper 2008-05-14 05:07:15 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Rolf Fokkens 2008-08-21 20:10:08 UTC
Fedora 9 surprisingly has my requested feature. So the request is now opsolete.


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