February 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Partitioning_advanced and 9.2
by "Höhle, Jörg" 25 Feb '05

25 Feb '05

Hi, The attachment with logfile was removed from the first mail, the relevant part of the controlfile was: <install> ...... ..... <partitioning_advanced> <fstab> <root_partition>/dev/sda5</root_partition> <use_existing_fstab config:type="boolean">true</use_existing_fstab> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <mount>/local</mount> </partition> </partitions> </fstab> </partitioning_advanced> </install> The same part worked with 9.1 and Sles9 but not with SuSE 9.2 which we need to update our Desktops and some of our servers. Greetings, Jörg Höhle -----Original Message----- From: "Höhle, Jörg" [mailto:hoehle@uni-mainz.de] Sent: Wednesday, February 23, 2005 9:51 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Partitioning_advanced and 9.2 Hi, We used the partitining_advanced feature successfully on 9.1 and sles9 to reuse the existing fstab and keep some local data. On 9.2, with the same Syntax in the controlfile, we coudn't get this to work. According to the logfile the fstab is read correctly but it seems that the configuration Is reset after. Result: ERROR: no proposal! Greetings, Jörg Höhle

1 0

RE: [suse-autoinstall] chroot-scripts not running
by Suffin, Charles 25 Feb '05

25 Feb '05

Actually, I solved the problem by removing the isolinux timeout so that nothing proceeds beyond the "boot:" prompt until someone manually types a valid install target (or just <enter> to get the default). So, if someone leaves the CD in the drive and goes out for lunch, the machine will just be sitting at the prompt when they return. They can just pop out the CD and ctl-alt-del... I like your suggestion Fraser, although I don't quite understand how to specify boot from disk in isolinux.cfg -- the targets that you specify seem to be from the boot medium, in this case the CD. Anyway, thanks! -----Original Message----- From: Campbell, Fraser [mailto:Fraser.Campbell@tdsecurities.com] Sent: Thursday, February 24, 2005 9:17 PM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] chroot-scripts not running Charles Suffin wrote: > The only problem is that if a target PC has the CD drive above the hard disk > (in BIOS boot list), you can get into an infinite loop of reinstalling the > machine on each reboot. Even when I added an "eject" command into my chroot > or pre-install script, these darn drives pull the CD back into the machine > when it resets/reboots! Have the default isolinux option be "boot from harddisk" that way unless someone is there to manually select the desired install method no reinstall can happen ... this is what we do and I agree CD is infinitely less hassle than PXE. Boot from harddisk is the default option on standard SuSE CDs (at least for Enterprise server) so you should be good just copying that config onto your customized install CDs. Fraser -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] chroot-scripts not running
by Campbell, Fraser 25 Feb '05

25 Feb '05

Charles Suffin wrote: > The only problem is that if a target PC has the CD drive above the hard disk > (in BIOS boot list), you can get into an infinite loop of reinstalling the > machine on each reboot. Even when I added an "eject" command into my chroot > or pre-install script, these darn drives pull the CD back into the machine > when it resets/reboots! Have the default isolinux option be "boot from harddisk" that way unless someone is there to manually select the desired install method no reinstall can happen ... this is what we do and I agree CD is infinitely less hassle than PXE. Boot from harddisk is the default option on standard SuSE CDs (at least for Enterprise server) so you should be good just copying that config onto your customized install CDs. Fraser

1 0

RE: [suse-autoinstall] chroot-scripts not running
by Suffin, Charles 25 Feb '05

25 Feb '05

At Stratus, I tried the PXE approach and instead chose to create an isolinux-based CD with a few boot label targets to specify the variety of XML files we need... At our place, the developers do not control the DHCP server for the corporation, and so it was painful to get PXE to work -- private LAN and/or hacking the DHCP server for a subnet only (to respond to PXE)... The CD approach has been hugely successful and flexible. It eliminates the need to muck with DHCP/PXE, and you only have to set up an installation source (we use http:). The only problem is that if a target PC has the CD drive above the hard disk (in BIOS boot list), you can get into an infinite loop of reinstalling the machine on each reboot. Even when I added an "eject" command into my chroot or pre-install script, these darn drives pull the CD back into the machine when it resets/reboots! (anyone remember the "infinite mirrors" from the 1970s? :) :) ) -----Original Message----- From: Campbell, Fraser [mailto:Fraser.Campbell@tdsecurities.com] Sent: Thursday, February 24, 2005 8:42 PM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] chroot-scripts not running Anas Nashif wrote: >>> As part of my auto-install I have a <chroot-scripts> script which >>> notifies a server to remove the PXE boot file from the tftp server >>> (that way, next time I boot the new machine, it won't try to run >>> the install again). The chroot-script is the following: >> >> A normal boot with dhcp enabled will not trigger a PXE install, why >> are you PXE booting your machine after the initial install? > >It will reuse the same dhcp configuration it got for the installation, >so it restarts installation. This is a well known problem with >autoinstallation in general. Ahhh. On my servers I specifically select a one-time network boot (I press F12) to do the PXE install, after that first install the server boots from local disk (automatically, no intervention). If your machines don't let you do the one-time network boot then yes that would be a pain :-( Fraser -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] chroot-scripts not running
by Campbell, Fraser 25 Feb '05

25 Feb '05

Anas Nashif wrote: >>> As part of my auto-install I have a <chroot-scripts> script which >>> notifies a server to remove the PXE boot file from the tftp server >>> (that way, next time I boot the new machine, it won't try to run >>> the install again). The chroot-script is the following: >> >> A normal boot with dhcp enabled will not trigger a PXE install, why >> are you PXE booting your machine after the initial install? > >It will reuse the same dhcp configuration it got for the installation, >so it restarts installation. This is a well known problem with >autoinstallation in general. Ahhh. On my servers I specifically select a one-time network boot (I press F12) to do the PXE install, after that first install the server boots from local disk (automatically, no intervention). If your machines don't let you do the one-time network boot then yes that would be a pain :-( Fraser

1 0

RE: [suse-autoinstall] chroot-scripts not running
by Campbell, Fraser 25 Feb '05

25 Feb '05

Mitko Haralanov wrote: > As part of my auto-install I have a <chroot-scripts> script > which notifies a server to remove the PXE boot file from the tftp server > (that way, next time I boot the new machine, it won't try to run the > install again). The chroot-script is the following: A normal boot with dhcp enabled will not trigger a PXE install, why are you PXE booting your machine after the initial install? Fraser

2 1

RE: [suse-autoinstall] installing a lot of perl modules
by Campbell, Fraser 25 Feb '05

25 Feb '05

Ryan Allen wrote: > Does anybody have recommendations for installing a bunch of perl modules > that aren't in RPM? Make RPMs. Debian has dh-make-perl package which will builds Debian perl packages, it works fine. For RPM there is an equivalent helper called perl-Module-Build ... not certain how well it works or if it works on SuSE but you may want to check it out. Fraser

1 0

chroot-scripts not running
by Mitko Haralanov 25 Feb '05

25 Feb '05

I did not really expect to have some many problems with this but I was wrong... As part of my auto-install I have a <chroot-scripts> script which notifies a server to remove the PXE boot file from the tftp server (that way, next time I boot the new machine, it won't try to run the install again). The chroot-script is the following: <chroot-scripts> <script> <filename>done-install</filename> <interpreter>shell</interpreter> <source> <![CDATA[# # Tell the install server we are done. # THIS MUST REMAIN THE LAST COMMAND. echo "We are running" > /root/blah wget http://1.2.3.4/cgi-bin/install-done.cgi ]]> </source> </script> </chroot-scripts> However, it does not seem to be running at all. The "echo" line does not produce anything and there is no sign of the wget in the http server logs. How can I verify that the script is running and the wget is doing what it is supposed to? Thanx -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== Hackers are just a migratory lifeform with a tropism for computers.

2 1

RE: [suse-autoinstall] chroot-scripts not running
by Suffin, Charles 25 Feb '05

25 Feb '05

Mitko, This stuff is a little intricate, so don't be discouraged. It took me a couple of weeks to get my install working perfectly (and I was a novice). I don't think that's too bad. Anyway, do you want this .cgi file to exist after the system reboots? I am guessing that your problem is that you are not in the right directory to do the wget. Please note that the root filesystem on disk is mounted (as /mnt) during the chroot script execution. If you want to put anything on disk, you need to cd into /mnt (which becomes the root after the reboot), or some subdirectory, and *then* do the wget. A trick I have used during the scripting environments is to put an "exec /bin/bash" into the script. This essentially halts the script at that moment and it will not proceed until you terminate the bash shell. What you can do when the script stops is use ctl-alt-<f2> to switch to a tty shell and then poke around to see what's going on. Then you can use ps -ef to find the shell that you started, kill -9 it, and then the install proceeds. I hope this helps. It is definitely true that you will not see standard output from a script during its execution, and your file (/root/blah) will be lost because you are not writing it to disk. If you wrote to /mnt/blah, you'd see /blah on the reboot. -- Charlie -----Original Message----- From: Mitko Haralanov [mailto:mitko@pathscale.com] Sent: Thursday, February 24, 2005 6:47 PM To: suse-autoinstall(a)lists.suse.com Subject: [suse-autoinstall] chroot-scripts not running I did not really expect to have some many problems with this but I was wrong... As part of my auto-install I have a <chroot-scripts> script which notifies a server to remove the PXE boot file from the tftp server (that way, next time I boot the new machine, it won't try to run the install again). The chroot-script is the following: <chroot-scripts> <script> <filename>done-install</filename> <interpreter>shell</interpreter> <source> <![CDATA[# # Tell the install server we are done. # THIS MUST REMAIN THE LAST COMMAND. echo "We are running" > /root/blah wget http://1.2.3.4/cgi-bin/install-done.cgi ]]> </source> </script> </chroot-scripts> However, it does not seem to be running at all. The "echo" line does not produce anything and there is no sign of the wget in the http server logs. How can I verify that the script is running and the wget is doing what it is supposed to? Thanx -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== Hackers are just a migratory lifeform with a tropism for computers. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

AW: [suse-autoinstall] post-install scripts
by Andreas.Matthieu＠tfa.brandenburg.de 24 Feb '05

24 Feb '05

Hi Charles, at postinstall step network are not running [SLES9: AY boot, setup network, install packages (second step), stop network, configure network (but let it down), start postscripts, continue boot with startup network]. Try "ifconfig ethX up" in postscript before use network. Regards, Andreas -----Ursprüngliche Nachricht----- Von: Charles.Suffin(a)stratus.com [SMTP:Charles.Suffin@stratus.com] Gesendet am: Donnerstag, 24. Februar 2005 16:41 An: todd.ness(a)eds.com; suse-autoinstall(a)lists.suse.com Betreff: RE: [suse-autoinstall] post-install scripts Hmm... OK, I'd swear I was unable to use http: during my post-install scripts (when I did my testing), but maybe I goofed. Thanks! -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 10:36 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts This happens during the post-scripts section of the auto install process. Also, I am doing network builds so the networking has to be up and running. So, I download one script that downloads and executes the rest of the scripts. <scripts> <pre-scripts config:type="list"> </pre-scripts> <post-scripts config:type="list"> <script> <filename>cleanup</filename> <interpreter>shell</interpreter> <source> <![CDATA[ echo writing profile echo "d-default" > /etc/MSDprofile echo getting scripts /usr/bin/wget http://1.2.3.4/install/postinst.sh -O /tmp/postinst.sh chmod 555 /tmp/postinst.sh /tmp/postinst.sh exit 0]]> </source> </script> </post-scripts> </scripts> -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 7:38 AM To: Ness, Todd; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Guys, quick question... I found that the post-install scripting environment -- which runs after the reboot -- didn't have networking set up yet (whereas chroot scripts run before the reboot and have the network running). Do you guys (Todd) do some magic to enable the network for the operation of post-install scripts so you could use wget? What I do is use wget during chroot scripts and store the files in /mnt/... (which gets mounted as root after the reboot). -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 9:31 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Just a thought, I wrote a post-install wrapper that gets scripts via wget and those scripts are S01name.. S20name and then executes them serially similar to rc startup scripts. -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, February 24, 2005 7:15 AM To: Mitko Haralanov Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] post-install scripts They are executed in the order they appear in the XMl file. Anas Mitko Haralanov wrote: > I have recently started working on a autoyast configuration file for > SuSE9.1. In the process of generating the file, I have created several > post-install scripts which configure different parts of the system. > The question that I have is: what is the order in which the scripts > are going to be executed? Currently some of the post-install scripts > depend on others and I need to be sure in what order they will be > executed. > > Thanx > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1