Hi!
I have one problem left within my autoinstallation process.
When all RPM's are installed, lilo is written into the bootsector. After that
a message pops up with "Sucessfully written into Bootsector [..]". The pop up
needs to be confirmed with a click on the OK button. That's strange to me.
I've read about the default should be show all errors/warnings/messages with
a timeout of 10 seconds even if I don't have a <report> section in my
autoinst.xml. I've also made a <report> section (see below) but without any
postive result.
So, can anybody give me a hint about this prob ?
Btw.: I am using the latest autoyast packages with the latest update image
(y2update.gz) on floppy.
Part of my autoinst.xml:
[..]
<install>
<bootloader>
<activate config:type="boolean">false</activate>
On Tue, 10 Jun 2003, Stefan Weigel wrote:
Hi! I have one problem left within my autoinstallation process. When all RPM's are installed, lilo is written into the bootsector. After that a message pops up with "Sucessfully written into Bootsector [..]". The pop up needs to be confirmed with a click on the OK button. That's strange to me. I've read about the default should be show all errors/warnings/messages with a timeout of 10 seconds even if I don't have a <report> section in my autoinst.xml. I've also made a <report> section (see below) but without any postive result. So, can anybody give me a hint about this prob ?
If the problem occurs also when you omit the <report> section, it is probably a bug where the code is not using the timeout-enabled message function. Please tell us the exact message text (German is ok) so that we can locate it.
Btw.: I am using the latest autoyast packages with the latest update image (y2update.gz) on floppy.
Part of my autoinst.xml:
<report> <messages> <show>true</show> <timeout>5</timeout> <log>true</log> </messages> [...] </report>
This looks like another documentation bug. The boolean values must have a config:type="boolean" attribute and likewise config:type="integer" for the timeout. -- Martin Vidner, developer SuSE CR, s.r.o. e-mail: mvidner@suse.cz Drahobejlova 27 tel:+420-296542373 190 00 Praha 9, Czech Republic http://www.suse.cz
Martin Vidner wrote:
On Tue, 10 Jun 2003, Stefan Weigel wrote:
Btw.: I am using the latest autoyast packages with the latest update image (y2update.gz) on floppy.
Part of my autoinst.xml:
<report> <messages> <show>true</show> <timeout>5</timeout> <log>true</log> </messages> [...] </report>
To avoid the popup, use <messages> <show config:type="boolean">false</show> <timeout config:type="integer">5</timeout> <log config:type="boolean">true</log> </messages>
This looks like another documentation bug. The boolean values must have a config:type="boolean" attribute and likewise config:type="integer" for the timeout.
It is a documentation error, however, it would also work this way in 8.1. Anas
Stefan Weigel wrote:
Hi! I have one problem left within my autoinstallation process. When all RPM's are installed, lilo is written into the bootsector. After that a message pops up with "Sucessfully written into Bootsector [..]". The pop up needs to be confirmed with a click on the OK button. That's strange to me. I've read about the default should be show all errors/warnings/messages with a timeout of 10 seconds even if I don't have a <report> section in my autoinst.xml. I've also made a <report> section (see below) but without any postive result. So, can anybody give me a hint about this prob ?
Something else, why are you getting Lilo in the first place? Do you have LVM or Raid? You should get grub by default. Anas
Best regards
Stefan
participants (3)
-
Anas Nashif
-
Martin Vidner
-
Stefan Weigel