Bug 119623 - GRUB YaST module only allow one map statement
Summary: GRUB YaST module only allow one map statement
Status: RESOLVED DUPLICATE of bug 119174
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: i686 SuSE Pro 9.3
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Olaf Dabrunz
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords: Bad_Design
Depends on:
Blocks:
 
Reported: 2005-09-30 10:43 UTC by Tomas Jensen
Modified: 2007-05-10 13:40 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Jensen 2005-09-30 10:43:08 UTC 
When adding another hd to boot Windows XP from only one map statement is 
allowed even if you need two. Eg. :

title Windows XP
  map (hd0) (hd1)
  map (hd1) (hd0)
  chainloader (hd1,0)+1

the last map state has to be entered by hand. The GUI do not allow it.
Comment 1 Danny Al-Gaaf 2005-10-14 16:07:52 UTC 
please report bugs for openSUSE against SUSE 10.0 and take a look at:  http://
www.opensuse.org/index.php/Submit_a_bug befor report a bug.
Comment 2 Michael Gross 2005-10-17 06:19:08 UTC 
To me this looks like an enhancement.
Jiri: Please decide if this makes sense.
Comment 3 Jiri Srain 2005-10-21 10:45:28 UTC 
Do you really report the bug against 10.0? Which dialog do you mean?

Could you, please, attach the logs (see comment #2)?
Comment 4 Jiri Srain 2005-12-15 12:14:25 UTC 
Reasigning to new maintainer
Comment 5 Alexander Osthof 2007-05-10 13:20:20 UTC 
Is it possible that this feature (adding a "map to from" line) isn't available anymore at all? I've tried to add such a line by the yast2 bootloader gui (in openSUSE 10.2), but there's no such option.

I would recommend to close this bug INVALID.
Comment 6 Alexander Osthof 2007-05-10 13:40:52 UTC 

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