WG: [suse-autoinstall] reboot after install
![](https://seccdn.libravatar.org/avatar/c3305251101a760db670ad7091390b33.jpg?s=120&d=mm&r=g)
Hello Simon, forceboot only forces the boot :) the reboot is done by: <reboot config:type="boolean">true</reboot> andreas ________________________________ Von: Simon Crute [mailto:scrute@novell.com] Gesendet: Do 07.09.2006 14:12 An: suse-autoinstall@suse.com Betreff: [suse-autoinstall] reboot after install Hi, I'm trying to get my autoyast setup to reboot after the install has finished, and then run the initscript scripts after the first boot. I've got the following section. <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">true</forceboot> <second_stage config:type="boolean">true</second_stage> </mode> <mouse/> ... </general> but it's still not rebooting after an install. This causes me problems because the install kernel is a -default one, but I'm building -smp systems, so the initscrupt (which configures the sound card, and the display) fails cos there are no -default modules there, only -smp ones -- Simon Crute IS&T Bracknell Novell UK Ltd -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
![](https://seccdn.libravatar.org/avatar/db22781459847f0f5ff588e09a58b943.jpg?s=120&d=mm&r=g)
On Thursday 07 September 2006 13:28, Maurer, Andreas wrote:
Hello Simon,
forceboot only forces the boot :)
the reboot is done by: <reboot config:type="boolean">true</reboot>
andreas
I thought the docs said this option was obsoleted, but I tried it, and it's not working either. From the docs. ----------------- 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. -------------------- Well, my systems are very NOT rebooting after they compleat the install. Uwe ? -- Simon Crute IS&T Bracknell Novell UK Ltd
![](https://seccdn.libravatar.org/avatar/43d28c61e1e0659972b2e139c34792d5.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 10:39, Simon Crute wrote:
Well, my systems are very NOT rebooting after they compleat the install.
I don't understand where exactly you want the machine to reboot? The reboot property is useless now, because it triggers a reboot after the package installation. Since SLES9 that happens anyway. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing mind.in.a.box - You Will See
![](https://seccdn.libravatar.org/avatar/db22781459847f0f5ff588e09a58b943.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 09:50, Uwe Gansert wrote:
On Friday 08 September 2006 10:39, Simon Crute wrote:
Well, my systems are very NOT rebooting after they compleat the install.
I don't understand where exactly you want the machine to reboot? The reboot property is useless now, because it triggers a reboot after the package installation. Since SLES9 that happens anyway.
Well, I want a reboot after the post-install scripts have ran, and it doesn't look like I'm getting that. After I install a dual CPU machine, if I run a uname -a it shows it's running a -default kernel. If I reboot the machine manually, it is then running the -smp kernel. This is why I think it's not rebooting at all during the install process. I've just double checked, and it doesn't reboot during the install at all. -- Simon Crute IS&T Bracknell Novell UK Ltd
![](https://seccdn.libravatar.org/avatar/43d28c61e1e0659972b2e139c34792d5.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 12:35, Simon Crute wrote:
Well, I want a reboot after the post-install scripts have ran, and it doesn't look like I'm getting that.
hm? That has never worked. At least I don't know of any mechanism that triggered a reboot in the middle of stage 2.
I've just double checked, and it doesn't reboot during the install at all.
that's very strange. What do you install btw? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing ROTERSAND - dare to live
![](https://seccdn.libravatar.org/avatar/db22781459847f0f5ff588e09a58b943.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 11:52, Uwe Gansert wrote:
On Friday 08 September 2006 12:35, Simon Crute wrote:
Well, I want a reboot after the post-install scripts have ran, and it doesn't look like I'm getting that.
hm? That has never worked. At least I don't know of any mechanism that triggered a reboot in the middle of stage 2.
Basically a reboot at any point will sort me out.
I've just double checked, and it doesn't reboot during the install at all.
that's very strange. What do you install btw?
I'm installing SLED10 + the ODE addon. -- Simon Crute IS&T Bracknell Novell UK Ltd
![](https://seccdn.libravatar.org/avatar/43d28c61e1e0659972b2e139c34792d5.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 13:11, Simon Crute wrote:
I'm installing SLED10 + the ODE addon.
weird. Have you tried to remove "forceboot" and "reboot" from your general section? So that just signature stuff and maybe "confirm" is left? The machine should reboot after stage 1 per default. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing ROTERSAND - by the waters
![](https://seccdn.libravatar.org/avatar/696eaeb2f94b44f338a3e92c1c5ed649.jpg?s=120&d=mm&r=g)
Is there an option to have it reboot or shutdown after stage 2? -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Friday, September 08, 2006 6:19 AM To: suse-autoinstall@suse.com Subject: Re: WG: [suse-autoinstall] reboot after install On Friday 08 September 2006 13:11, Simon Crute wrote:
I'm installing SLED10 + the ODE addon.
weird. Have you tried to remove "forceboot" and "reboot" from your general section? So that just signature stuff and maybe "confirm" is left? The machine should reboot after stage 1 per default. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing ROTERSAND - by the waters -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
![](https://seccdn.libravatar.org/avatar/43d28c61e1e0659972b2e139c34792d5.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 14:21, Stephens, Bill {PBSG} wrote:
Is there an option to have it reboot or shutdown after stage 2?
only with an init-script like this for example: <scripts> <init-scripts config:type="list"> <script> <source><![CDATA[ /sbin/shutdown -h now ]]> </source> </script> </init-scripts> </scripts> -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing mind.in.a.box - Out Of Time
![](https://seccdn.libravatar.org/avatar/db22781459847f0f5ff588e09a58b943.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 12:18, Uwe Gansert wrote:
On Friday 08 September 2006 13:11, Simon Crute wrote:
I'm installing SLED10 + the ODE addon.
weird. Have you tried to remove "forceboot" and "reboot" from your general section? So that just signature stuff and maybe "confirm" is left? The machine should reboot after stage 1 per default.
I've remove the foceboot and reboot, and now it is rebooting after the RPM install, and before doing the configuration. So, what am I missunderstanding with the forceboot option then ? -- Simon Crute IS&T Bracknell Novell UK Ltd
![](https://seccdn.libravatar.org/avatar/43d28c61e1e0659972b2e139c34792d5.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 15:11, Simon Crute wrote:
I've remove the foceboot and reboot, and now it is rebooting after the RPM install, and before doing the configuration.
So, what am I missunderstanding with the forceboot option then ?
the forceboot option is (like the reboot option) useless and not supported anymore. The default of yast is to reboot the machine after the package installation. forceboot overwrites that default with a new value. I'm pretty sure that I tried that option too a while ago and my machine still rebooted. That's why I kept it and thought: "well useless, but can't hurt.". It looks like I was wrong because in your case, it changes the default behaviour to "not booting". I need to take a closer look why that happened and why it's different on your hardware than on mine but I'll drop the "forceboot" code now anyway. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing The Retrosic - The Storm
![](https://seccdn.libravatar.org/avatar/696eaeb2f94b44f338a3e92c1c5ed649.jpg?s=120&d=mm&r=g)
It sure would be nice to use the option to reboot after stage 2. Like Simon, it's the only way I can ensure some of my changes are updated, so right now I'm using the "duct tape and bailing wire" method of injecting my own code to force a reboot. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Friday, September 08, 2006 8:27 AM To: suse-autoinstall@suse.com Subject: Re: WG: [suse-autoinstall] reboot after install On Friday 08 September 2006 15:11, Simon Crute wrote:
I've remove the foceboot and reboot, and now it is rebooting after the RPM install, and before doing the configuration.
So, what am I missunderstanding with the forceboot option then ?
the forceboot option is (like the reboot option) useless and not supported anymore. The default of yast is to reboot the machine after the package installation. forceboot overwrites that default with a new value. I'm pretty sure that I tried that option too a while ago and my machine still rebooted. That's why I kept it and thought: "well useless, but can't hurt.". It looks like I was wrong because in your case, it changes the default behaviour to "not booting". I need to take a closer look why that happened and why it's different on your hardware than on mine but I'll drop the "forceboot" code now anyway. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing The Retrosic - The Storm -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
![](https://seccdn.libravatar.org/avatar/43d28c61e1e0659972b2e139c34792d5.jpg?s=120&d=mm&r=g)
On Friday 08 September 2006 15:37, Stephens, Bill {PBSG} wrote:
It sure would be nice to use the option to reboot after stage 2. Like Simon, it's the only way I can ensure some of my changes are updated, so right now I'm using the "duct tape and bailing wire" method of injecting my own code to force a reboot.
I'll think about that but at the end, it will be a similar (just automated) solution like the init-script version I already suggested. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing :Wumpscut: - Bunkertor 7 [German Texture]
participants (4)
-
Maurer, Andreas
-
Simon Crute
-
Stephens, Bill {PBSG}
-
Uwe Gansert