Bug 114451 - Cannot configure bootloader for booting kernels from other partitions during installation
Summary: Cannot configure bootloader for booting kernels from other partitions during ...
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 4
Hardware: Other All
: P5 - None : Major
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 15:43 UTC by Matthias Hopf
Modified: 2005-09-02 07:34 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Hopf 2005-08-31 15:43:59 UTC
When configuring grub I want to add the kernel of another partition (e.g. a
SL9.3 partition) that hasn't been automatically detected.

Example: I install on /dev/hda6, I want to add a kernel from /dev/hda7.
I can only change the root of the configuration, but not the kernel location.
I.e. the grub configuration will look like this:

root (hd0,5)
kernel /boot/vmlinuz root=/dev/hda7 ...
initrd /boot/initrd

... instead of root (hd0,6).
The according overview line in the grub configuration screen will look like
(/dev/hda6, root=/dev/hda7).

I can change this in the config file, but I'm missing a configuration field for
the partition the kernel is located on (or the root partition should be used for
that, not the current boot partition).
Comment 1 Jiri Srain 2005-09-02 07:34:04 UTC
well, this is the lowlight of the changed dialog design - you add paths in 
your system. You have two ways to do it: 
 
1. Mount the other partition somewhere and add the kernel/initrd as 
eg. /mnt/boot/vmlinuz 
 
2. Add the kernel/initrd in the GRUB syntax (hd0,6)/boot/vmlinuz for /dev/hda7