Re: [suse-autoinstall] initrd module load order not following info file
Jiri Srain wrote:
Hi Mike!
Dne pondělí 30 květen 2005 10:26 jste napsal(a):
Jiri Srain wrote:
Dne pondělí 30 květen 2005 09:59 jste napsal(a):
SLES10 seems a bit too far on the horizon. This is the first system we're trying to install using autoyast with SLES9.
It is not issue of autoinstallatino only - plain installatino is affected as well.
but there at least you have the option of checking the initrd before you boot. I tried with adding "boot confirm true" (can't remember the exact syntax) in autoinst.xml but that option didn't seem to have any effect as the machine booted automatically right after installation finished.
Don't know, pass the question to the list.
I would be happy if I had the chance to alter the MKINITRD and create a correct initrd _before_ the initial reboot, as we're not really looking for fully-automated setups. Any idea on why this might not work?
No, no idea. I didn't know about this option before.
That's (or rather was) the option in autoinst.xml: <install> <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> </mode> According to autoyast documentation here http://www.suse.de/~nashif/autoinstall/9.1/autoyast.pdf it has been dropped for SuSE9.1/SLES9.
It is not possible to add all modules which are in info file to initrd - because it would put there a lot of modules which are not needed.
Where does the MKINITRD variable get set? Which file would I have to look into to tweak it myself?
/usr/share/YaST2/modules/Initrd.ycp, after modifying it needs to be recompiled by 'ycpc -c Initrd.ycp'.
thanks for the pointer. I'll look into it tomorrow when I'm on site.
If you just want to update sysconfig and recreated initrd before the reboot, the probably easiest would be to add to /usr/share/YaST2/clients/inst_finish just after bootloader is installed eg.
Popup::Message (_("Update the inirdd now"));
This will show you message after bootloader is saved and you can switch to the console to change anything you want to.
Just remember that you have to change the file in the installation system (which is stored on CD1 in /boot/root). It is cramfs image.
that sounds like a good workaround, thanks.
Hi, I have a working SLES9-SP1 autoyast setup. But, In my post-install scripts I upgrade the kernel to a custom one with rpm. The problem is that after install the machine needs a reboot for the new kernel to work. I have read the docs and found information about "forceboot": <install> <general> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> </mode> But, it doesnt work for SLES9-SP1. How do I get a reboot to activate the new kernel? Regards Daniel
On Wednesday 15 June 2005 20:10, suselist@nlsn.nu wrote:
I have a working SLES9-SP1 autoyast setup. But, In my post-install scripts I upgrade the kernel to a custom one with rpm.
The problem is that after install the machine needs a reboot for the new kernel to work.
I have read the docs and found information about "forceboot":
The reboot property in the mode resource was used to force a reboot after initial system setup and before the system is booted for the first time. Currently after initial installation all systems must boot, which makes this option obsolete.
How do I get a reboot to activate the new kernel?
either update your installation source with the new kernel, so it's getting installed in the first place or, if that is not possible, try to do an update of the kernel in a chroot-script with: <chrooted config:type="boolean">true</chrooted> and not in a post-script. You are in the chrooted in the installed system then and you are very short before the first reboot happens. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
participants (3)
-
Michael Steinmann -
suselist＠nlsn.nu -
Uwe Gansert