Thanks for the hint with the chrooted script. Unfortunatley this does not work either. The chrooted script is simply ignored. I looked at the menu.lst autoyast has created (using the recovery system) It looks like this: # Modified by YaST2. Last modification on Wed Jun 28 17:57:10 UTC 2006 color white/blue black/light-gray default timeout <NULL> ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 10.0 root (hd0,0) kernel /boot/vmlinuz root=/dev/sda1 selinux=0 resume=/dev/sda2 splash=silent showopts initrd /boot/initrd ...snap As you can see there is NULL (pointer) were there should be a number >0) I wrote this chrooted script: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <feedback config:type="boolean">true</feedback> <filename>fixboot.0</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/sh # Dies fixt ein autoyast2 problem mit dem initial /boot/grub/menu.lst echo "Substitute <NULL> in /boot/grub/menus.lst by 17" FILE=/boot/grub/menu.lst echo "-----------------------" echo "$FILE Before fix" cat $FILE echo "-----------------------" if [ -f "$FILE" ];then cp $FILE /tmp/menu cat /tmp/menu | sed 's/<NULL>/17/' >$FILE fi echo "-----------------------" echo "$FILE After fix" cat $FILE echo "-----------------------" ]]></source> </script> </chroot-scripts> </profile> The script is read in correctly, I can see it in the /tmp/autoinstall.xml, if I look into the system to be installed, by ALT <F2> terminal, when waiting for ACCEPT to autoinstall. fixboot.0 is also mentioned in /var/log/messages/YaST2/y2log in the final system. But no logs in /var/adm/autoinstall/logs (only a later postscript is logged). When I accept, all packages are installed the bootmanager is set up (wrong) and the system tries to boot. But there is no POP-UP as it should be (<feedback config:type="boolean">true</feedback>!). The fixboot script is obviously completly ignored! I have no logs whatsoever, since the logs are in Ramdisk, which are lost as soon as the system boots! I can only guess, that the Bug which makes the <NULL> also prevents my fixboot script from running!. Any further hints? Uwe Gansert wrote:

On Monday 26 June 2006 11:47, Folkhard Mueller wrote:

...

I use SuSE Linux 10.0's autoyast.

All is fine but after all packages are installed the system is prepared for the first initial boot. In this step there is obvioulsy the boot timeout set to 0 which means the system waits forever to boot. One Return plugged in on the Keyboard is enough and ibooting occurs successfully.

hmm. I never had such a problem but if you need, you can workaround it with a chroot-script with true</chrooted> http://www.suse.de/~ug/autoyast_doc/createprofile.scripts.html#chroot.script... modify the /boot/grub/menu.lst to your need with that script

-- |\ _,,,---,,_ ZZZzz /,`.-'`' -. ;-;;,_ _______|,4- ) )-,_. ,\ (____-'_________________________________________ '---''(_/--' `-'\_) Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD CAD P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller@epcos.com Web: http://www.epcos.com

On Monday 26 June 2006 07:18, Uwe Gansert wrote:

On Monday 26 June 2006 11:47, Folkhard Mueller wrote:

...

I use SuSE Linux 10.0's autoyast.

All is fine but after all packages are installed the system is prepared for the first initial boot. In this step there is obvioulsy the boot timeout set to 0 which means the system waits forever to boot. One Return plugged in on the Keyboard is enough and ibooting occurs successfully.

hmm. I never had such a problem but if you need, you can workaround it with a chroot-script with true</chrooted> http://www.suse.de/~ug/autoyast_doc/createprofile.scripts.html#chroot.scrip ts modify the /boot/grub/menu.lst to your need with that script

Looks like bug 183051 which I already reported. I saw that first in 10.0 but because we skipped 10.0 I didn't report it. It's still there in 10.1. I didn't try the chroot-script workaround yet. Karsten.

Nice to hear that I am not the only one finding some bugs in yast's autoinstall! (I found more, but I do not report if I find some solution which works!). The chroot-script I wrote worked arround successfully (after adding the missing tag <scripts>)! Karsten Künne wrote:

On Monday 26 June 2006 07:18, Uwe Gansert wrote:

...

On Monday 26 June 2006 11:47, Folkhard Mueller wrote:

...

I use SuSE Linux 10.0's autoyast.

All is fine but after all packages are installed the system is prepared for the first initial boot. In this step there is obvioulsy the boot timeout set to 0 which means the system waits forever to boot. One Return plugged in on the Keyboard is enough and ibooting occurs successfully.

hmm. I never had such a problem but if you need, you can workaround it with a chroot-script with true</chrooted> http://www.suse.de/~ug/autoyast_doc/createprofile.scripts.html#chroot.scrip ts modify the /boot/grub/menu.lst to your need with that script

Looks like bug 183051 which I already reported. I saw that first in 10.0 but because we skipped 10.0 I didn't report it. It's still there in 10.1. I didn't try the chroot-script workaround yet.

Karsten.

-- |\ _,,,---,,_ ZZZzz /,`.-'`' -. ;-;;,_ _______|,4- ) )-,_. ,\ (____-'_________________________________________ '---''(_/--' `-'\_) Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD CAD P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller@epcos.com Web: http://www.epcos.com