March 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] post-install scripts
by Ness, Todd 02 Mar '05

02 Mar '05

I am doing http installs i.e. install=http://1.1.1.1/directory/CD1 autoyast=http://1.1.1.1/install/autoinstall.xml Either in the info file or on the boot cd command line. -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 9:26 AM To: 'Andreas.Matthieu(a)tfa.brandenburg.de'; Suffin, Charles; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts What you're saying is great, guys (thanks!), but Todd's post-install script in his XML fragment does not do network initialization (I think) before executing wget. I do not understand why his script works... Thanks! -- Charlie p.s./ I didn't mean to rathole Mitko's original email! I am shutting up now! :) -----Original Message----- From: Andreas.Matthieu(a)tfa.brandenburg.de [mailto:Andreas.Matthieu@tfa.brandenburg.de] Sent: Thursday, February 24, 2005 11:21 AM To: Charles.Suffin(a)stratus.com; suse-autoinstall(a)lists.suse.com Subject: AW: [suse-autoinstall] post-install scripts 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Creation of ISO in one minute ;)
by Pierre Allix 02 Mar '05

02 Mar '05

Hello, I wrote some scripts for easily creating AutoYaST ISOs. With few modifications in the configuration you can use them too. There is a cache system and others tips, so it is really fast (less than one minute on a good machine). You can customize your installation with pre and post scripts. You can also add any files, binaries that are not RPMS for instance, they'll be available in the final root system. It only creates ISOs for the equivalent of 'Minimal' installation but you can change this by modifying one file. You can find the scripts here : http://kototama.free.fr/perl/suse/suse3.tgz They are released under the GPL license version 2. You'll also need these files : http://kototama.free.fr/perl/suse/root http://kototama.free.fr/perl/suse/rescue Installation instructions : $ export HTTP_PROXY=proxy:3128 $ wget http://kototama.free.fr/perl/suse/root (set HTTP_PROXY according to your network) $ wget http://kototama.free.fr/perl/suse/rescue $ wget http://kototama.free.fr/perl/suse/suse3.tgz $ tar xzf suse3.tgz $ mv root rescue suse3/autoyast/suse_data/iso_tree/boot/ $ cd suse3/autoyast $ less README Sorry for not just making one archive but I can't upload big files on this ftp. It is usefull for me, I hope it'll be usefull for you. Feedback is welcome. Pierre

1 0

specify install-server in the xml-file?
by suselist＠nlsn.nu 02 Mar '05

02 Mar '05

Hi, Im a novice with autoyast, but have used kickstart for several years. I have install-server (http) for installing NLD9 clients. I boot the machine with CD1 of NLD9 and enter "autoyast=http://server/profiles/profile1.xml install=http://server/image/NLD9/i386" and everything works. But, I want to embed the "install=" in the xml, is that possible? ( kickstart has url of image in the kickstart-profile ) I have tried with linuxrc but it doesnt work. Any pointers? Regards Daniel

2 2

dual boot problems
by mspark 02 Mar '05

02 Mar '05

I'm getting ready to install SUSE 9.2 I am doing a dual boot system with XP on the first primary partition and SUSE on the second primary partition. What do I need to know about before installation as far as partition problems. Currently I have 9.1 and my XP isn't accessable and I understand it is from "hidden NTFS' partitions. A problem that Yast causes in the boot partition table or something. Is this problem corrected in 9.2 or is there more fixes?? Thanks! __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

2 1

SSH access during automated install?
by Daniel 02 Mar '05

02 Mar '05

Hi list, I successfully installed my suse 9.2 servers via PXE boot, autoyast and an XML file. Now one of the machines seems to have trouble during the install - it just hangs (perhaps a bug in my test xml file). To avoid this in situations where I have no physical access to the machine I tried: usessh=1 and sshpassword=password as kernel parameters. (just to have a "backdoor" to reset the machine if it hangs...) When I now start an automated install the machine boots but WAITS for the ssh user to log on and start yast by hand, which isn´t quite practically during automated install ;-) How do I get access via SSH during install and still have fully automatic install? Thanks for your help! Daniel

2 1

auto-installing with patched OS
by Mark Acosta 02 Mar '05

02 Mar '05

I need to autoinstall a patched 2.6.8-24.11-default kernel (including patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, but I can't find out how to patch/update to 2.6.8-24.11-default. How is the best accomplished? thanks, Mark

3 2

RE: [suse-autoinstall] chroot-scripts not running
by Schumacher, Gordon 01 Mar '05

01 Mar '05

Take a look at "isolinux.cfg" on the standard SuSE CD (or DVD) 1. That should show you how it needs to look. -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 8:22 PM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] chroot-scripts not running 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 -- 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] netsetup
by Schumacher, Gordon 01 Mar '05

01 Mar '05

I've had good luck with using this for user interaction (this is a fragment of a script which constructs a user account according to the user's input): #!/bin/sh /bin/chvt 9 exec < /dev/tty9 > /dev/tty9 ### BEGIN USER INTERACTION HERE ### ans="n" while [ 1 ] do echo Please enter your first and last name. You may enter a middle name echo or initial if you wish. read fullname while [ 0 ] do echo Is "$fullname" right $Y/N$?\ read ans if [[ "$ans" == "y" || "$ans" == "n" || "$ans" == "Y" || "$ans" == "N" ]] then break fi done if [[ "$ans" == "y" || "$ans" == "Y" ]] then break fi done ### END USER INTERACTION HERE ### /bin/chvt 7 -----Original Message----- From: Pierre Allix [mailto:pierre.allix@idealx.com] Sent: Wednesday, February 23, 2005 9:34 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] netsetup >That parameter only affects the very first setup of networking that >is used for installing packages. You have to set up the rest in >(auto)yast. > > > Ok, thanks. I suppose autoyast can't ask the user for this information (and only for these) or not ? I think I have to create a rc script. -- 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] Installing Additional Software
by Schumacher, Gordon 01 Mar '05

01 Mar '05

Try looking at section 4.5 in the AutoYaST manual; hopefully this will help. -----Original Message----- From: Daniel Spannbauer [mailto:ds@marco.de] Sent: Wednesday, February 23, 2005 8:45 AM To: suse-autoinstall(a)lists.suse.com Subject: [suse-autoinstall] Installing Additional Software Hello, i'm working under SuSE 9.2. I've made a Config-File with Yast2, started an DHCP-Server, NFS-Server und TFTP-Server. I run Autoyast with PXE-Boot and it works very well. But now I wan't to install a Not-SuSE-Package auomaticaly after the SuSE-Installation is done. The rpm-File is at the same Path as the Suse-RPMs are (on a NFS-Share) How do I setup up this? Can I do this in Yast too? I'm not good in XML so a graphical Solution would be nice. Thanks Daniel -- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds(a)marco.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

More mysteries: LDAP
by Ole Streicher 01 Mar '05

01 Mar '05

Hi group again, my fiddling with the autoyast configuration options continues. I have the following entry in my xml file: <ldap> <base_config_dn>dc=mydomain,dc=de</base_config_dn> <create_ldap config:type="boolean">true</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>dc=mydomain,dc=de</ldap_domain> <ldap_server>ldap</ldap_server> <ldap_tls config:type="boolean">false</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <member_attribute>member</member_attribute> <pam_password>crypt</pam_password> <start_ldap config:type="boolean">true</start_ldap> </ldap> The server "ldap" is resolvable via our DNS server. Autoyast triggers the "ldap" authentication (/etc/nsswitch.conf contains a "passwd_compat: ldap" line), but the ldap configuration itself is done just half-way. The file /etc/ldap.conf is created with follwing contents (comment lines removed): host 127.0.0.1 base dc=example,dc=com ldap_version 3 pam_password crypt ssl start_tls pam_filter objectclass=posixAccount nss_base_passwd dc=mydomain,dc=de nss_base_shadow dc=mydomain,dc=de nss_base_group dc=mydomain,dc=de >From the last three lines I can see that there is "something" configured in the file, but why are the "host" and "base" lines kept unusable? They are clearly defined in my XML config. Is this something I did wrong or is it just one more bug of autoyast? Best regards Ole -- DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl

3 2