Mailinglist Archive: opensuse-bugs (19685 mails)

< Previous Next >
[Bug 390659] New: autoyast bootloader config: empty settings are ignored ( impossible to entry w/o initrd)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 15 May 2008 03:33:04 -0600 (MDT)
  • Message-id: <bug-390659-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=390659


Summary: autoyast bootloader config: empty settings are ignored
(impossible to entry w/o initrd)
Product: openSUSE 11.0
Version: Beta 1
Platform: x86-64
OS/Version: openSUSE 11.0
Status: NEW
Severity: Normal
Priority: P5 - None
Component: AutoYaST
AssignedTo: ug@xxxxxxxxxx
ReportedBy: gernot@xxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---


I'm trying to auto-install a system with memtest. Memtest doesn't seem to work
when GRUB loads some initrd.

So I simply want YaST to create the following entry in menu.lst:

title Memtest
root (hd0,0)
kernel /boot/memtest.bin

However, it seems to be impossible to specify empty settings in autoinst.xml.

When I e.g. try the following section:

<section>
<image>/boot/memtest.bin</image>
<name>Memtest</name>
<type>image</type>
</section>

Then I end up with something like

title Memtest
root (hd0,0)
kernel /boot/memtest.bin root=/dev/disk/... ... a lot of other params ...
initrd /boot/initrd-2.6.25-rc9-17-default

Specifying empty settings like <append></append>, <initrd></initrd> doesn't
change anything. Then only workaround which comes close to what I want is using

<section>
<append> </append>
<image>/boot/memtest.bin</image>
<kernel>/boot/memtest.bin</kernel>
<initrd> </initrd>
<name>Memtest</name>
<root> </root>
<type>image</type>
</section>

which gives me the (invalid) bootloader entry

title Memtest
root (hd0,0)
kernel /boot/memtest.bin root=
initrd

But - whatever I tried, I didn't find a way to disable writing the "initrd"
line (the weird root= parameter isn't nice, but it doesn't hurt memtest at
least).


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups