Hi everybody, some time ago I started creating my own sles9 cds. I have a sles9 where the install server runs and a sles9 machine where patch server runs. On the install server I use CD Creator to create my cds (at least the install tree, the iso images and the burning I do with a script). I also have some XML files for autoyast, with a post-install script where the user can choose some install options. All this works fine. Now I want to do the same with sles10. I managed to setup an install server on the sles9 machine. I also created some XML files for autoyast, but I have problems with the interactiv post-install script. Now some questions: 1) Can I use CD Creator from sles9 to create sles10 cds (just the install tree) ? 2) Can I use sles9 as patch server for sles10 ? 3) What's the best way to create an interactiv postinstall script ? I tried the init-script option, but the script runs in parallel with other scripts an never gets the hold of the console. In sles9 I had a post-install script which dropped a S00setup file in rc5.d, but in sles10 this files is ignored. Any ideas ? Thank you very much for your help. Sincerely Bernhard
Bernhard Dübi wrote:
Hi everybody, ... 3) What's the best way to create an interactiv postinstall script ? I tried the init-script option, but the script runs in parallel with other scripts an never gets the hold of the console. In sles9 I had a post-install script which dropped a S00setup file in rc5.d, but in sles10 this files is ignored. Any ideas ?
for some interactiveness, you could try switching terminal, for example : /bin/chvt 9 exec < /dev/tty9 > /dev/tty9 you would lose stderr with this syntax, but for simple scripts it should be ok. as for being run in parallel, you could try using chroot scripts to either add all required stuff to Required-Start for /etc/init.d/autoyast, or do as uwe suggested some time ago - "Have you tried to turn off the RUN_PARALLEL in /etc/sysconfig/boot?" if these solutions do not help you, maybe executing a chroot script which adds your own service to be run upon boot helps... you could look at autoyast init script for hints.
Thank you very much for your help.
Sincerely Bernhard -- Rich
On Thu, 2006-10-26 at 11:46 +0300, Rich wrote:
Bernhard Dübi wrote:
Hi everybody, ... 3) What's the best way to create an interactiv postinstall script ? I tried the init-script option, but the script runs in parallel with other scripts an never gets the hold of the console. In sles9 I had a post-install script which dropped a S00setup file in rc5.d, but in sles10 this files is ignored. Any ideas ?
for some interactiveness, you could try switching terminal, for example :
/bin/chvt 9 exec < /dev/tty9 > /dev/tty9
I have now 2 versions, one as init-script and one as a post-script. With the init-script the machine boots up to the xdm login screen and the chvt changes then to another console (8 in my case). The post-script installs a script in /etc/init.d and activates it with chkconfig. This has the advantage that I can place the script more precisely in the boot process and the machine stops booting at some point. My problem is that YaST comes up all messed up. It looks like YaST draws the screen correctly. But then it activates the input fields with wrong offsets. My Script looks like this (the real script is much larger, but this is essentially what I do to start YaST): <init-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <filename>sysetup.sh</filename> <location></location> <source><![CDATA[#!/bin/bash chvt 8 exec 0<> /dev/tty8 1>&0 2>&0 REDIRECT="`showconsole 2>/dev/null`" export REDIRECT set -- $(stty size < $REDIRECT) LINES=$1 COLUMNS=$2 if test $COLUMNS -eq 0 ; then LINES=24 COLUMNS=80 test "$TERM" = "linux" -o -z "$TERM" && TERM=vt102 fi export LINES COLUMNS yast2 lan ]]></source> </script> </init-scripts> Any idea how I can make YaST look clean and easy ? Sincerely Bernhard
On Tue, 2006-10-31 at 21:15 +0100, Bernhard Dübi wrote:
On Thu, 2006-10-26 at 11:46 +0300, Rich wrote:
Bernhard Dübi wrote:
Hi everybody, ... 3) What's the best way to create an interactiv postinstall script ? I tried the init-script option, but the script runs in parallel with other scripts an never gets the hold of the console. In sles9 I had a post-install script which dropped a S00setup file in rc5.d, but in sles10 this files is ignored. Any ideas ?
for some interactiveness, you could try switching terminal, for example :
/bin/chvt 9 exec < /dev/tty9 > /dev/tty9
I have now 2 versions, one as init-script and one as a post-script.
New strategy, instead of installing an init script with chkconfig I add a bootwait entry in inittab, just like the yast initial config. In this mode, my scripts work like the init scripts in sles9. Problem solved. Thank you very much for your help. Sincerely Bernhard
something else you might want to look at that we started looking at is yast2-firstboot. you can put scripts into it and give the user yast2 modules to interact with. very simple to use as well. -----Original Message----- From: Bernhard Dübi [mailto:bduebi@solnet.ch] Sent: Thursday, November 02, 2006 10:22 PM To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Interactiv post-install script On Tue, 2006-10-31 at 21:15 +0100, Bernhard Dübi wrote:
On Thu, 2006-10-26 at 11:46 +0300, Rich wrote:
Bernhard Dübi wrote:
Hi everybody, ... 3) What's the best way to create an interactiv postinstall script ? I tried the init-script option, but the script runs in parallel with other scripts an never gets the hold of the console. In sles9 I had a post-install script which dropped a S00setup file in rc5.d, but in sles10 this files is ignored. Any ideas ?
for some interactiveness, you could try switching terminal, for example :
/bin/chvt 9 exec < /dev/tty9 > /dev/tty9
I have now 2 versions, one as init-script and one as a post-script.
New strategy, instead of installing an init script with chkconfig I add a bootwait entry in inittab, just like the yast initial config. In this mode, my scripts work like the init scripts in sles9. Problem solved. Thank you very much for your help. Sincerely Bernhard -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
participants (3)
-
Bernhard Dübi -
Ness, Todd -
Rich