June 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-sles-e] autoinst.xml for dual boot.
by Ajay Mulwani 24 Jun '05

24 Jun '05

> - you install and configure one laptop manually OK, Windows was already there, installed SLES9. > - you make backup selecting 'save partition info' How? Thanks Alexei. Could you be a little more decscriptive. Ajay

1 0

Configuration of Graphics in Autoyast
by Daniel Spannbauer 24 Jun '05

24 Jun '05

Hello, I'm working with Autoyast under SuSE 9.2 and it works fine. But if I want to configure the Graphics-System all Configuration would be irgnord bei the new System. My Config: <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <max_hsync config:type="integer">65</max_hsync> <max_vsync config:type="integer">78</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">58</min_vsync> </display> <monitor_device>1024X768@70HZ</monitor_device> <monitor_vendor> LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <window_manager>kde</window_manager> </x11> After Installation the Venoder of the Monitor is Unkown, 3D is Enabled. So the X-Server does not start at all. After configuring it with Sax2 the X-Server can start. Is there a Mistake in my Config-File? Can I set the Graphics-Card-Vendor an Type in the Autoyast-File? Greetings 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

1 0

How do I prevent re-install?
by Dave Thacker 23 Jun '05

23 Jun '05

Last year I wrote this: Dave Thacker wrote: > Goal: Unnattended install of SUSE 9.1 using autoyast2. > > I've successfully done a minimal installation using auto-yast on SuSE 9.1. > After the client finished install, it rebooted. It's set to boot from PXE so > it started up the entire install process. and started to install again. > I have > <forceboot config:type="boolean">false</forceboot> set in the config file. > In chapter 4 of the docs it states: > "Change starting from SUSE Linux 9.1/SLES9 > The reboot property in the mode resource was used to force a reboot after > initial system setup and before the system is rebooted for the first time. > Currently after initial installation all systems must reboot, which makes > this option obsolete." > > Given that a reboot is inevitable, how do I stop a perpetual install loop? > DT And Anas was kind enough to offer this solution. > In SLES9 there is a feature which is not documented exactly to solve this problem: <install> ... <pxe> <pxe_localboot config:type="boolean">true</pxe_localboot> <pxelinux-config> DEFAULT linux LABEL linux localboot 0 </pxelinux-config> <tftp-server>192.168.1.1</tftp-server> </pxe> ... </install> This will make YaST upload the contents of <pxelinux-config> to the TFTP server. /tftpboot/pxelinux.cfg has to be world writable. This has not worked. I've checked the /var/log/yaST2 logs to see if the tags "<pxelinux>" show up and are acted upon, but I don't see them being read or seen by autoyast. What can I do to debug this problem? TIA DT

3 4

RE: [suse-autoinstall] autoinstall on s/390
by Stefan Leippert 23 Jun '05

23 Jun '05

Hi ! Thank you very much for your mail ! I will try to use the DASD_Parameters=dasd=xxx now. Maybe this helps. I will post it on the list then. According to SuSE-Documentation (max. 10 lines) my parmfile has 9 lines with a maximum of 77 characters each line. Greetings Stefan Mit freundlichen Grüßen / Best regards Stefan Leippert Praktikant eServer Software System Evaluation and Test IBM Deutschland Entwicklung GmbH Schoenaicher Strasse 220 D-71032 Boeblingen "Smith, Terrance T" <terrance.t.smith To @citigroup.com> Stefan Leippert/Germany/IBM@IBMDE, <suse-autoinstall(a)suse.com> 06/22/2005 04:41 cc PM Subject RE: [suse-autoinstall] autoinstall on s/390 Hi Stefan, I'm having other problems like getting it to properly format my dasd Anyway, I know that you can set autoyast to http but I don't believe that the parmfile allows for you to set install to http. Try setting install to nfs, ftp, as the install protocol The INST_INFO paramter doesn't allow for http and I am deducing that if you can't set INST_INFO to http then you can't set install to http. Regards Terrance Smith zVM / Linux CTI 201-601-7057 -----Original Message----- From: Stefan Leippert [mailto:LEIPPERT@de.ibm.com] Sent: Wednesday, June 22, 2005 9:31 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoinstall on s/390 Hello ! We still have some problems with autoinstallation on our s/390(x)-machines on LPAR: We already have: - start up the machine with the first ramdisk and a modified parmfile. The parmfile contains information like this: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb AUTOINSTALL=yes INST_PASSWORD=xxx IP_HOST=(ownHOSTNAME) IP_ADDR=(ownIP) IP_MTU=1492 IP_INTERFACE=qeth IP_NETMASK=255.255.0.0 IP_GATEWAY=xxx IP_BROADCAST=xxx READ_DEVNO=f618 WRITE_DEVNO=f619 DATA_DEVNO=f61a PORTNAME=OSAPORT INST_INFO=ftp FTPUSER=xxx FTPPASSWORD=xxx INST_IP_ADDR=(IPftpSERVER) INST_SCREEN=SSH IP_DEV=eth0 INST_IP_DIR=SLES-9-s390/SUSE-SLES-Version-9/CD1 autoyast=http://(whereTHEautoinstfileIS)/autoinst.xml install=http://xxx/SUSE-SLES-Version-9/CD1 During the first boot with this parmfile, The machine gets some files by FTP (content, /boot/root, media.l/info.txt, part.info (which is not available), control.xml, driverupdate (which is also not available), products, media, packages, packages.en, packages.en_us, Base-System.sel .....) Now the machine boots with this ramdisk and starts up with an SSH-Server (depending on selection in parmfile) and is reachable in the network. All this worked automatically. >From here everything has to be done by hand: After logging in by SSH, you can start yast. Now yast should get the autoinst.xml from the selected source in parmfile, but yast doesn't. The is no action over the network to get this file, verified by ethereal. There are no Firewall problems because of using private network and already working FTP download. Before starting yast, you can also connect and get the autoinst.xml manually. Yast now askes for alle parameters like DASDs, Package selection, language, partiton... Under installation as VM-guest it works with the same parmfile and the machine gets the autoinst.xml. We already tried a http-source for the autoinst.xml-file, but without success. We cannot use a cdrom or floopy to boot the lpar because we are working via HMC on the machine and only the service element has a floopy or cdrom. We use installservers. Anybody has an idea / hint on how to make the machine getting the autoinst.xml ? Thank you in advance ! Stefan Mit freundlichen Grüßen / Best regards Stefan Leippert Praktikant eServer Software System Evaluation and Test -- 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] How do I prevent re-install?
by Michael Marion 23 Jun '05

23 Jun '05

On 21 Jun, Dave Thacker wrote: > This has not worked. I've checked the /var/log/yaST2 logs to see if the > tags "<pxelinux>" show up and are acted upon, but I don't see them being > read or seen by autoyast. What can I do to debug this problem? Have you tried adding a loghost option to the command line (or info file) to see if it logs there? I seem to see more info in there then in the logs on a host after it jumps. That said... I wrote my own solution to the pxe config setup issue.. I use either mac address config files (01-<mac addr with s/:/-/g and upper case changed to lower>), i.e. host mac 00:02:A5:7F:65:92 becomes 01-00-02-a5-7f-65-92 or, I fall back to Hex value of IP: 192.168.1.1 becomes C0A80101 I also pass a variable of pxe=ethX,Y,Z.Z.Z.Z where X is the ethernet card pxe booted (we did our first pxe boots on a closed net using eth1 even though the host eventually config'd itself on our compute net on eth0). Y is 0 for the NFS source is no on the pxe host and 1 for the NFS install source is on the same pxe host. I wrote a pre.sh in my control files that does: #!/bin/sh echo "In pre-install" if [ -n "`grep pxe= /proc/cmdline`" ] then echo "Need to disable tftpboot config" pxe_ip=`cat /proc/cmdline | sed -e 's/.*pxe=eth.,//g' -e 's/ .*//g'` pxe_ip=`echo $pxe_ip | sed 's/[0-9],//g'` pxe_dev=`cat /proc/cmdline | sed -e 's/.*pxe=$eth.$.*/\1/g'` mkdir /tmp/pxe mount -o rw,nolock ${pxe_ip}:/tftpboot /tmp/pxe /bin/sh -xv /tmp/pxe/fix-pxe.sh $pxe_dev umount /tmp/pxe fi the scripts are: ====== cornholio pxe {894}$ cat fix-pxe.sh #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin if [ ! -x /bin/bash ] then if [ -x /usr/bin/bash ] then ln -s /usr/bin/bash /bin/bash fi fi eth_dev=$1 if [ "x$eth_dev" = "x" ] then eth_dev=eth1 fi MYIP=`ifconfig $eth_dev | awk '/inet addr/{print $2}' | awk -F: '{print $2}'` mycfg=`/tmp/pxe/conv.sh $MYIP` if [ "x$mycfg" = "x" ] then echo "Something happened.. mycfg is blank" exit 1 fi if [ ! -f /tmp/pxe/pxelinux.cfg/$mycfg ] then mycfg=`ifconfig $eth_dev | awk '/HWaddr/{print $NF}' | sed 's/:/-/g' | tr '[:upper:]' '[:lower:]'` mycfg="01-$mycfg" fi if [ ! -f /tmp/pxe/pxelinux.cfg/$mycfg ] then echo "Can't find pxe config file $mycfg" exit 1 fi mv -f /tmp/pxe/pxelinux.cfg/$mycfg /tmp/pxe/pxelinux.cfg/${mycfg}.orig sed -e 's/^DEFAULT/#DEFAULT/g' -e 's/^#$DEFAULT disk$/\1/g' /tmp/pxe/pxelinux.cfg/${mycfg}.orig > /tmp/pxe/pxelinux.cfg/$mycfg chmod 666 /tmp/pxe/pxelinux.cfg/$mycfg ========= and cornholio pxe {895}$ cat conv.sh #!/bin/bash if [ $# -ne 1 ] then echo Usage: conv.sh $ip exit 1 fi hex () { if [ $1 -lt 10 ] then echo $1 elif [ $1 = 10 ] then echo A elif [ $1 = 11 ] then echo B elif [ $1 = 12 ] then echo C elif [ $1 = 13 ] then echo D elif [ $1 = 14 ] then echo E elif [ $1 = 15 ] then echo F fi } IP=$1 for block in `echo $IP | sed 's/\./ /g'` do if [ $block -lt 10 ] then echo -n 0$block else let div=$block/16 let mult=$div*16 let rem=$block-$mult echo -n `hex $div``hex $rem` fi done echo "" ================== So far, this has worked like a charm from sles8 through sles9-sp1. The only negative is if the pre.sh runs, but the install has a problem later for some reason. You have to go back and reset the config to pxe boot the installer again instead of booting locally. Of course, /tftpboot on the pxe/tftp server has to be exported root writeable to all. We're doing pxe installs in our subnets now where our dns/dhcp system hands out the pxe data, and a linux box serves as the pxe config box by running tftp and exporting /tftpboot open for root. Of course, you have to know the mac address and IP of a host before you can jump it in this setup. We don't use a default. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Marge: "Homer, we'd like to talk to you." Homer: "But then I wouldn't be watching TV. You can see the bind I'm in." ==> Simpsons

1 0

Users not being added
by Curt Blank 22 Jun '05

22 Jun '05

The install is not adding any users I have defined but it does create their home directories. This is an example of one that is not being created, any help as to why this is not working would be appreciated. <user> <encrypted config:type="boolean">true</encrypted> <fullname>Test Account</fullname> <gid>100</gid> <home>/home/testacct</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1000</uid> <user_password>$2a$05$r9Z05Brkvb4A2KIdhNLadOKO7vxAh2R3mIOX7B0YCbkdqrjl2Et16</user_password> <username>testacct</username> </user>

3 2

RE: [suse-autoinstall] autoinstall on s/390
by Smith, Terrance T 22 Jun '05

22 Jun '05

Hi Stefan, I'm having other problems like getting it to properly format my dasd Anyway, I know that you can set autoyast to http but I don't believe that the parmfile allows for you to set install to http. Try setting install to nfs, ftp, as the install protocol The INST_INFO paramter doesn't allow for http and I am deducing that if you can't set INST_INFO to http then you can't set install to http. Regards Terrance Smith zVM / Linux CTI 201-601-7057 -----Original Message----- From: Stefan Leippert [mailto:LEIPPERT@de.ibm.com] Sent: Wednesday, June 22, 2005 9:31 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoinstall on s/390 Hello ! We still have some problems with autoinstallation on our s/390(x)-machines on LPAR: We already have: - start up the machine with the first ramdisk and a modified parmfile. The parmfile contains information like this: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb AUTOINSTALL=yes INST_PASSWORD=xxx IP_HOST=(ownHOSTNAME) IP_ADDR=(ownIP) IP_MTU=1492 IP_INTERFACE=qeth IP_NETMASK=255.255.0.0 IP_GATEWAY=xxx IP_BROADCAST=xxx READ_DEVNO=f618 WRITE_DEVNO=f619 DATA_DEVNO=f61a PORTNAME=OSAPORT INST_INFO=ftp FTPUSER=xxx FTPPASSWORD=xxx INST_IP_ADDR=(IPftpSERVER) INST_SCREEN=SSH IP_DEV=eth0 INST_IP_DIR=SLES-9-s390/SUSE-SLES-Version-9/CD1 autoyast=http://(whereTHEautoinstfileIS)/autoinst.xml install=http://xxx/SUSE-SLES-Version-9/CD1 During the first boot with this parmfile, The machine gets some files by FTP (content, /boot/root, media.l/info.txt, part.info (which is not available), control.xml, driverupdate (which is also not available), products, media, packages, packages.en, packages.en_us, Base-System.sel .....) Now the machine boots with this ramdisk and starts up with an SSH-Server (depending on selection in parmfile) and is reachable in the network. All this worked automatically. >From here everything has to be done by hand: After logging in by SSH, you can start yast. Now yast should get the autoinst.xml from the selected source in parmfile, but yast doesn't. The is no action over the network to get this file, verified by ethereal. There are no Firewall problems because of using private network and already working FTP download. Before starting yast, you can also connect and get the autoinst.xml manually. Yast now askes for alle parameters like DASDs, Package selection, language, partiton... Under installation as VM-guest it works with the same parmfile and the machine gets the autoinst.xml. We already tried a http-source for the autoinst.xml-file, but without success. We cannot use a cdrom or floopy to boot the lpar because we are working via HMC on the machine and only the service element has a floopy or cdrom. We use installservers. Anybody has an idea / hint on how to make the machine getting the autoinst.xml ? Thank you in advance ! Stefan Mit freundlichen Grüßen / Best regards Stefan Leippert Praktikant eServer Software System Evaluation and Test -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

autoinstall on s/390
by Stefan Leippert 22 Jun '05

22 Jun '05

Hello ! We still have some problems with autoinstallation on our s/390(x)-machines on LPAR: We already have: - start up the machine with the first ramdisk and a modified parmfile. The parmfile contains information like this: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb AUTOINSTALL=yes INST_PASSWORD=xxx IP_HOST=(ownHOSTNAME) IP_ADDR=(ownIP) IP_MTU=1492 IP_INTERFACE=qeth IP_NETMASK=255.255.0.0 IP_GATEWAY=xxx IP_BROADCAST=xxx READ_DEVNO=f618 WRITE_DEVNO=f619 DATA_DEVNO=f61a PORTNAME=OSAPORT INST_INFO=ftp FTPUSER=xxx FTPPASSWORD=xxx INST_IP_ADDR=(IPftpSERVER) INST_SCREEN=SSH IP_DEV=eth0 INST_IP_DIR=SLES-9-s390/SUSE-SLES-Version-9/CD1 autoyast=http://(whereTHEautoinstfileIS)/autoinst.xml install=http://xxx/SUSE-SLES-Version-9/CD1 During the first boot with this parmfile, The machine gets some files by FTP (content, /boot/root, media.l/info.txt, part.info (which is not available), control.xml, driverupdate (which is also not available), products, media, packages, packages.en, packages.en_us, Base-System.sel .....) Now the machine boots with this ramdisk and starts up with an SSH-Server (depending on selection in parmfile) and is reachable in the network. All this worked automatically. >From here everything has to be done by hand: After logging in by SSH, you can start yast. Now yast should get the autoinst.xml from the selected source in parmfile, but yast doesn't. The is no action over the network to get this file, verified by ethereal. There are no Firewall problems because of using private network and already working FTP download. Before starting yast, you can also connect and get the autoinst.xml manually. Yast now askes for alle parameters like DASDs, Package selection, language, partiton... Under installation as VM-guest it works with the same parmfile and the machine gets the autoinst.xml. We already tried a http-source for the autoinst.xml-file, but without success. We cannot use a cdrom or floopy to boot the lpar because we are working via HMC on the machine and only the service element has a floopy or cdrom. We use installservers. Anybody has an idea / hint on how to make the machine getting the autoinst.xml ? Thank you in advance ! Stefan Mit freundlichen Grüßen / Best regards Stefan Leippert Praktikant eServer Software System Evaluation and Test

1 0

Re: [suse-autoinstall] Dynamic changes in autoYast control file (Not through rules)
by Michael Marion 21 Jun '05

21 Jun '05

On 20 Jun, Alexander Dubinin wrote: > Idea is to generate swap partition size automatically, using script. > Does I have possibility to start some script _before_ autoyast config > file is processed? The pre scripts are run after the xml file has already been assembled AFAIK. > Preferable is a way, similar to used in RedHat KickStart - run > pre-configuration script, generate partition layout and pass this > layout to AutoYast like "include" in KickStart. You can already do this using rules and classes instead of specific xml files. See http://yast.suse.com/autoinstall/9.1/html/rulesandclass.html example of what I'm doing... <rule> <disksize> <match>/dev/hda 10000</match> <match_type>greater</match_type> </disksize> <disksize> <match>/dev/hdb 10000</match> <match_type>greater</match_type> </disksize> <result> <profile>dideab.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> That rule matches dual IDE disks, installed as hda and hdb (I have a similar rule for hda and hdc). Then the dideab.xml (or dideac.xml if hda and hdc) file is just the partitioning bit. A custom example is... <rule> <custom1> <script> <![CDATA[ #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin if [ -n "`grep site= /proc/cmdline`" ] then echo -n `cat /proc/cmdline | sed -e 's/.*site=//g' -e 's/ .*//g'` else echo -n sandiego fi ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> This allows us to pass a site (for remote offices) on the boot line and load the file <site>.xml. In that file, we have the pre/chroot/post install scripts for looking at the local site's NFS installation path. Then we have a generic file that lists all the packages to install, which is the same for everyone.. It's a little confusing at first, but once you get how the rules/classes work, it's pretty slick. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Jimmy: "The job market is very competitive right now for someone with my skills! ...There are a whole lot of kids on summer vacation." -- The PJs.

3 3

Much information custom rules
by Pavlin Maslyankov 21 Jun '05

21 Jun '05

Hi , I didn't manage to find much information about the custom rules in the autoyast file. How they have to be written? I saw that they are shell scripts but what do they have to return ( as a return value of the process ) and actually does it matter . I saw in modules/AutoInstallRules.ycp that they use the stdout for communication with the parent process but what exactly it they have to write on it. I am not very good in this YCP so I am not sure whether I understood everything very well. So does someone have experience with custom rules and have few minutes to explain me. Thanks in advance. I forgot to mention that I use SLES 9 if it does matter. Regards, Pavlin Maslyankov "Tumbleweed E-mail Firewall <tumbleweed.com>" made the following annotations on 06/03/05 02:05:37 ------------------------------------------------------------------------------ This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ==============================================================================

3 2