RE: [suse-autoinstall] Scripting troubles
Strangely enough, when I removed the extra path stuff, it worked. ;-) It also worked fine w/o the terminal definitions, etc. It came up during the last stage of the install, when it was already in a (frame-based?) graphical install mode. Seemed to go OK, except for the x11 one. It apparently hadn't yet installed a number of the base XFree packages it needed to do 'yast2 x11'. I'll keep your text in mind. Do the scripts execute in the order I enter them in autoyast? If so, I may need to re-order things. --Jon Robison -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tue 9/30/2003 8:13 PM To: Robison, Jonathon (M.) Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Scripting troubles Robison, Jonathon (M.) wrote:
Strangely enough, /var/adm/autoinstall has nothing but empty directories in it, with the exception of ./cache/installedSystem.xml
Script name has to be without any additional path information, only a file name, and nothing else. You scripts wont work, as you are executing some gui stuff in a script. I have made a small test and it can work if you change the virtual terminal, for example, this would work: /bin/chvt 3 exec < /dev/tty3 > /dev/tty3 exec /sbin/yast2 proxy /bin/chvt 1 This would bring up the proxy configuration in text mode on the 3rd terminal. This can be used with other yast2 modules I guess.. Anas
--Jon Robison
On Tue, 2003-09-30 at 10:44, damien.selles@eu.effem.com wrote:
Hi,
Did you check the logs generated by your chroot scripts?
after the installation you should be able to access them here -> /var/adm/autoinstall/logs/
and another question: why do you use /tmp/ in your filename? Maybe you should try without the /tmp/ before the filename.
Regards
--------------------------------------------------------------- Damien Selles
"Robison, Jonathon (M.)" <jrobiso2@ford.com> ford.com
30/09/2003 15:29
To: suse-autoinstall@suse.com cc:
Subject: [suse-autoinstall] Scripting troubles
I have added a number of scripts to my xml file, and yet they never get executed. I have tried pre, chroot, and post.
These scripts are rather important, as they are intended to run parts of yast2 after the install and help the user set up printing, etc. and most especially, set suid on /usr/bin/smbmnt (otherwise users cannot mount their windows shares themselves).
Is there some known problem with the scripting? I've attached my XML file just in case.
Robison, Jonathon (M.) wrote:
Strangely enough, when I removed the extra path stuff, it worked. ;-)
It also worked fine w/o the terminal definitions, etc. It came up during the last stage of the install, when it was already in a (frame-based?) graphical install mode. Seemed to go OK, except for the x11 one. It apparently hadn't yet installed a number of the base XFree packages it needed to do 'yast2 x11'.
I'll keep your text in mind. Do the scripts execute in the order I enter them in autoyast? If so, I may need to re-order things.
Yes, and I would only run things in post scripts and not in chroot scripts. Anas
--Jon Robison
-----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tue 9/30/2003 8:13 PM To: Robison, Jonathon (M.) Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Scripting troubles
Robison, Jonathon (M.) wrote:
Strangely enough, /var/adm/autoinstall has nothing but empty directories in it, with the exception of ./cache/installedSystem.xml
Script name has to be without any additional path information, only a file name, and nothing else.
You scripts wont work, as you are executing some gui stuff in a script. I have made a small test and it can work if you change the virtual terminal, for example, this would work:
/bin/chvt 3 exec < /dev/tty3 > /dev/tty3 exec /sbin/yast2 proxy /bin/chvt 1
This would bring up the proxy configuration in text mode on the 3rd terminal. This can be used with other yast2 modules I guess..
Anas
--Jon Robison
On Tue, 2003-09-30 at 10:44, damien.selles@eu.effem.com wrote:
Hi,
Did you check the logs generated by your chroot scripts?
after the installation you should be able to access them here -> /var/adm/autoinstall/logs/
and another question: why do you use /tmp/ in your filename? Maybe you should try without the /tmp/ before the filename.
Regards
--------------------------------------------------------------- Damien Selles
"Robison, Jonathon (M.)" <jrobiso2@ford.com> ford.com
30/09/2003 15:29
To: suse-autoinstall@suse.com cc:
Subject: [suse-autoinstall] Scripting troubles
I have added a number of scripts to my xml file, and yet they never get executed. I have tried pre, chroot, and post.
These scripts are rather important, as they are intended to run parts of yast2 after the install and help the user set up printing, etc. and most especially, set suid on /usr/bin/smbmnt (otherwise users cannot mount their windows shares themselves).
Is there some known problem with the scripting? I've attached my XML file just in case.
participants (2)
-
Anas Nashif -
Robison, Jonathon (M.)