June 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] Additional Package & Silent install
by Michael Marion 01 Jul '05

01 Jul '05

On 30 Jun, Jan Kalcic wrote: > 1) I'm looking for a clear way to add additional packages to the installation server. I found a solution using the post script (wget && rpm) but it would really better and more handy to have them direclty into the AutoYaST software package database. Sort of difficult to get working.. but once you do, easy to keep updated and very slick integration. >From a previous answer I posted to the same question before: Look in the archives of this list for many threads on this, i.e. subjs: [suse-autoinstall] Custom install source for yast in SLES9 [suse-autoinstall] How can I regularly update the install repository? I should document my setup when I have a chance.. this comes up so often. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Joe: "I don't know, one minute we're spanking each other with meat, the next minute it got weird." --Wings

2 1

RE: [suse-autoinstall] Additional Package & Silent install
by Ness, Todd 30 Jun '05

30 Jun '05

1. requires the use of /usr/lib/YaST2/bin/create_package_descr you also have to edit selection files, md5sum files, selections, and directory.yast in the /pathtoinst/suse/setup/descr directory. 2. in the install section of your file there is a mode section set it to false <confirm config:type="boolean">false</confirm> -----Original Message----- From: Jan Kalcic [mailto:jkalcic@novell.com] Sent: Thursday, June 30, 2005 2:54 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Additional Package & Silent install Hi all, Few question about AutoYaST: 1) I'm looking for a clear way to add additional packages to the installation server. I found a solution using the post script (wget && rpm) but it would really better and more handy to have them direclty into the AutoYaST software package database. 2) During the installation on the target sysstem it's always asked to prompt yes to load the modules. Is there a way to make it silent? TIA, Jan Kalcic CNE, CLE, LPIC I Primary Support Engineer Novell Italy, Milan. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Additional Package & Silent install
by Jan Kalcic 30 Jun '05

30 Jun '05

Hi all, Few question about AutoYaST: 1) I'm looking for a clear way to add additional packages to the installation server. I found a solution using the post script (wget && rpm) but it would really better and more handy to have them direclty into the AutoYaST software package database. 2) During the installation on the target sysstem it's always asked to prompt yes to load the modules. Is there a way to make it silent? TIA, Jan Kalcic CNE, CLE, LPIC I Primary Support Engineer Novell Italy, Milan.

1 0

AW: [suse-autoinstall] 9.3 Pro can´t get autoinst.xml from floppy
by Götz Rieger 29 Jun '05

29 Jun '05

Hi Uwe, again thanks your high-speed responses. Goetz > -----Ursprüngliche Nachricht----- > Von: Uwe Gansert [mailto:ug@suse.de] > Gesendet: Dienstag, 28. Juni 2005 17:20 > An: suse-autoinstall(a)suse.com > Betreff: Re: [suse-autoinstall] 9.3 Pro can´t get autoinst.xml from > floppy > > > On Tuesday 28 June 2005 17:07, Götz Rieger wrote: > > > I´m trying to autoinstall a 9.3 Professional. The > > control file is named autoinst.xml and resides on a > > floppy, > > that's a bug. Use device://fd0/autoinst.xml instead. > > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

9.3 Pro can´t get autoinst.xml from floppy
by Götz Rieger 28 Jun '05

28 Jun '05

Hi all, I´m trying to autoinstall a 9.3 Professional. The control file is named autoinst.xml and resides on a floppy, the boot medium is CD1. The whole setup works well with the 9.2 installation medium. When I use the 9.3 CD or DVD, I get the error "A profile for this maschine could not be found..." from YaST. And /var/log/YaST2/y2log shows many complaints about "mount point /media/floppy does not exist" or "[YCP] autoinstall/io.ycp:184 file /media/floppy/ autoinst.xml can´t be retrieved". Hm. If I watch the same autoinstall on 9.2, /media/floppy is created automagically, I would assume by some YaST-Modul... and /media/floppy/ autoinst.xml is found... Any ideas? Regards, Goetz

2 1

s390 / activating DASD
by Stefan Leippert 28 Jun '05

28 Jun '05

Hello list, autoinstall on LPAR is now working, but we still have one problem: We have to activate and select the target-DASD (direct access storage device) manually by yast, so a "complete without user input" install is only possible after selecting, activating and formating the dasd. The autoinst.xml-file will be loadad AFTER the DASD-configuration by yast, so there might be a way with a parameter into the parmfile. The parameter "DASD_Parameter=dasd=0.0.5f07" or "DASD_Parameter=dasd=5f07" didn't change anything. 5f07 is the ID of the DASD. Are there any other secret parameters for the parmfile to make them activate the DASD ? In all threads found in the internet this parameter is written like "DASD_Parameter=dasd=100-103" where I don't understand the "100-103". Any hint ? Maybe I only use a wrong ID or syntax. The next thing is the installed SSH-Server - There is no password for root set, the SSH-Access isn't possible until I logged in by HMC and set it by hand. I have already tried following lines in the autoinst.xml: <users config:type="list"> <user> <username>root</username> <user_password>XXXXX</user_password> <encrypted config:type="boolean">false</encrypted> </user> </users> But that didn't solve the problem. Thank you in advance ! 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 mailto:leippert@de.ibm.com

1 0

Problems with YOU using a SLES9 Custom CD
by Fabiano Felix 27 Jun '05

27 Jun '05

Hi All, I make a Custom CD using SLES9, where I create new package description using only my package selection. I also updated kernel image that is used at installation process, using the same that are at SP1. All process works fine, and all services functions without any problem... but, when I try to do an On-line Update, I only can see SUSE-SLES packages. The most important packages are at SUSE-CORE selection (probably an inheritance from UnitedLinux CD's model...). I tried to add this update option using YaST2 (and copying from a "normal" SLES9 install), but I can't have success... Two questions: - Someone has some idea to correct this? - What's the best form to customize SLES9 CD's and don't have this problem again? (I believe that it have some relation with "media.N", "yast dir at CD root" and "contents" file...) With best regards, Fabiano Felix

1 0

Mounted paths under post-install script?
by Thorbjorn Jemander 27 Jun '05

27 Jun '05

Hi, I am doing a custom SuSE install DVD and I have included some extra software that needs to be installed during the post-install stage. However, what can I assume about mounts during the post-install script? Will the DVD be mounted, and if so, what is the mounting point? /media/dvd? I'm using SuSE Professional 9.3. Thanks in advance, ________________________________________________ Dr. Thorbjörn Jemander, Senior/RT Systems Expert Enea Epact AB, Teknikringen 8, Linköping, Sweden thje(a)epact.se, +46 13 465 58 67, www.epact.se

1 0

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

24 Jun '05

For those who wanna try this also - Put the AUTOYAST-Paramter into the first line and yast gets the autoinst.xml-file or query for it, if it cannot get it on the given path. My parmfile: AUTOYAST=nfs://10.30.10.32:stefan/autoinst.xml ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb IP_INTERFACE=qeth IP_ADDR=10.30.53.24 IP_NETMASK=255.255.0.0 IP_BROADCAST=10.30.255.255 IP_MTU=1500 IP_GATEWAY=10.30.10.32 IP_HOST=xxx READ_DEVNO=f618 WRITE_DEVNO=f619 DATA_DEVNO=f61a DASD_Parameter=dasd=5f07 INST_INFO=nfs INST_IP_ADDR=10.30.10.32 INST_IP_DIR=/distros/suse/SLES-9-s390/SUSE-SLES-Version-9/CD1 INST_PASSWORD=xxxx AUTOINSTALL=yes INST_SCREEN=VNC VNC_PASSWORD=xxxx Connection by VNC through SSH-Tunnel. Yast now just queries the DASD, and then runs in a loop in "Preparing System for automated installation". I think I have to check the autoinst.xml-file now, yast runs till "Preparing your harddisk" and then starts again with "Preparing System for automated installation". 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 mailto:leippert@de.ibm.com

1 0

SLES9 autoinstall stops "Creating initrd ..."
by Djeezus 24 Jun '05

24 Jun '05

Hy all, I've seen this question posted before, I found some relates articles / posts on the web, but none with a proper solution ... everything goes fine up to the point where it's trying to create the "initrd" image on the client... The y2log doesn't show any errors related to "initrd" and I've double/tripple checked the autoinstall.pdf and made sure the nfs directory tree is OK ... I found some articles on the web about "Creating initrd ... " failures, but they stated this was an old SLES9 beta problem, which should be resolved by now. - The autoyast server : autoyast:~ # SPident CONCLUSION: ServicePack Level: SLES-9-i386-SP1 + "updates" => up-to-date autoyast:~ # ls -l /data/Sles9/ total 0 drwxr-xr-x 5 root root 240 May 12 15:22 . drwxr-xr-x 10 root root 232 Jun 23 00:19 .. lrwxrwxrwx 1 root root 19 May 12 15:21 boot -> sles9-i386/CD1/boot lrwxrwxrwx 1 root root 22 May 12 15:21 content -> sles9-i386/CD1/content lrwxrwxrwx 1 root root 26 May 12 15:21 control.xml -> sles9-i386/CD1/control.xml drwxr-xr-x 7 root root 168 May 12 15:17 core9-i386 lrwxrwxrwx 1 root root 22 May 12 15:21 media.1 -> sles9-i386/CD1/media.1 drwxr-xr-x 3 root root 72 May 12 15:17 sles9-i386 drwxr-xr-x 2 root root 104 Jun 22 12:08 yast Any thoughts / comments much appreciated; Bye, Gert PS : the same server also acts as YOU server for the other SLES9 installs (which were manually installed), and this works fine ...

1 0

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

AW: AW: [suse-autoinstall] Problem Creating Logical Partitions
by Götz Rieger 21 Jun '05

21 Jun '05

Bjoern, Uwe, thank you for your help. Removing the extended partition and declaring the primary partitions solves the problem. Regards, Goetz > -----Ursprüngliche Nachricht----- > Von: Uwe Gansert [mailto:ug@suse.de] > Gesendet: Dienstag, 21. Juni 2005 13:14 > An: suse-autoinstall(a)suse.com > Betreff: Re: AW: [suse-autoinstall] Problem Creating Logical > Partitions > > > On Tuesday 21 June 2005 13:04, Götz Rieger wrote: > > > Does AutoYaST realize automatically that he would need > > an extended partition to create 5 partitions? > > yes. Remove the extended partition from your profile and you > get what you > want. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

AW: [suse-autoinstall] Problem Creating Logical Partitions
by Götz Rieger 21 Jun '05

21 Jun '05

Hi Bjoern, thanks for your answer. But if your file works this way, I have a real problem understanding how AutoYaST handles things... ;-) Your partitions all have mountpoints and partition_id=131, whereas in my opinion extended partitions should have 15 and no mountpoint. Does AutoYaST realize automatically that he would need an extended partition to create 5 partitions? I am a bit lost here... Any help? Regards, Goetz > -----Ursprüngliche Nachricht----- > Von: Bjoern Lotz [mailto:blotz@suse.de] > Gesendet: Dienstag, 21. Juni 2005 12:38 > An: suse-autoinstall(a)suse.com > Betreff: Re: [suse-autoinstall] Problem Creating Logical Partitions > > > Hello, > > The following works for me (SLES9), creating two primary > partitions, one > extended and logical partitions within the extended: > > <partitioning config:type="list"> > <drive> > <device>/dev/hda</device> > <initialize config:type="boolean">true</initialize> > <partitions config:type="list"> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>swap</mount> > <partition_id config:type="integer">130</partition_id> > <partition_type>primary</partition_type> > <size>1g</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/</mount> > <partition_id config:type="integer">131</partition_id> > <partition_type>primary</partition_type> > <size>1.5G</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/usr</mount> > <partition_id config:type="integer">131</partition_id> > <size>3G</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/opt</mount> > <partition_id config:type="integer">131</partition_id> > <size>1G</size> > </partition> > <partition> > <crypt>twofish256</crypt> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/var</mount> > <partition_id config:type="integer">131</partition_id> > <size>500M</size> > </partition> > </partitions> > <use>all</use> > </drive> > </partitioning> > > Main difference seems to be that there is no partition > number, but I don't > know too much about the syntax - could also be something > else, but at least > it works like this for me. > > Björn > > Am Dienstag, 21. Juni 2005 12:09 schrieb Götz Rieger: > > Hi, > > > > I would like AutoYaST to create three primary partitions > > and one extended partition with two logical partitions inside. > > > > The primary and extended partitions are created correctly, > > but the creation of the logical partitions fails because > > YaST tries to create them _behind_ the extended partition. > > > > If I specify the logical partition sizes with region_entry as > > sectors, everything works as expected. But this is not an > > option because I don´t want to be bound to specific disk > > geometries. So I can use <size> only... > > > > I have included the relevant part of my xml-file. > > > > Any tips? > > > > Regards, > > Goetz > > > > -------8><----------------------- > > <partitioning config:type="list"> > > <drive> > > <use>all</use> > > <device>/dev/sda</device> > > <partitions config:type="list"> > > <partition> > > <filesystem config:type="symbol" >ext3</filesystem> > > <mount>/</mount> > > <partition_id config:type="integer">131</partition_id> > > <partition_nr config:type="integer">1</partition_nr> > > <size>2048mb</size> > > </partition> > ... > > -- > Dr. Björn Lotz, Linux Curriculum Developer > Novell Worldwide Training Services > Novell GmbH, Frankfurter Ring 115a, 80807 München > Tel: 089/206002000 Fax: 089/206002100 > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

3 2

Problem Creating Logical Partitions
by Götz Rieger 21 Jun '05

21 Jun '05

Hi, I would like AutoYaST to create three primary partitions and one extended partition with two logical partitions inside. The primary and extended partitions are created correctly, but the creation of the logical partitions fails because YaST tries to create them _behind_ the extended partition. If I specify the logical partition sizes with region_entry as sectors, everything works as expected. But this is not an option because I don´t want to be bound to specific disk geometries. So I can use <size> only... I have included the relevant part of my xml-file. Any tips? Regards, Goetz -------8><----------------------- <partitioning config:type="list"> <drive> <use>all</use> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol" >ext3</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>2048mb</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>1024mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>1gb</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">4</partition_nr> <size>max</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var/log</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var/spool</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>2gb</size> </partition> </partitions> </drive> </partitioning> ----------------><8------------------------

2 1

Re: [suse-autoinstall] SLES9 autoinstall error
by Mike Marion 21 Jun '05

21 Jun '05

On 20 Jun, Uwe Gansert wrote: > just a guess. Can it be that your linuxrc command line has more than 255 > characters? Then the last characters would be cut off. Maybe that's it? that was going to be my guess.. we ran into this ages ago. I had to move a few of the options (like the install= option) to the info file in the initrd to save space. I really with autoyast was smart enough to do something like step through the path the autoyast= path has and see if the install tree is there instead of having to name both seperately... since we keep the autoyast bits underneath the install tree. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Talking about web page "design"] "I think my standards have lowered enough that now I think ``good design'' is when the page doesn't irritate the living fuck out of me." ==>jwz (http://www.jwz.org/gruntle/design.html)

2 1

Re: [suse-autoinstall] SLES9 autoinstall error
by Mike Marion 21 Jun '05

21 Jun '05

On 20 Jun, Ajay Mulwani wrote: > No, the entire command that I give at the PXE "boot:" prompt is: > boot: *SLES9 autoyast=nfs://abc/home/static.xml* > ** > Do I have to include all the characters which are there with the "append" > statement of "SLES9" label in the PXE "default" file? yes, all of that stuff gets cat'd together on the line.. and there will also be something added like: BOOT_IMAGE=linux (or whatever the kernel name is).. and it all adds up pretty fast. for a quick test.. just echo the whole line after append, and your added bits above and pipe to wc.. if it's anywhere near, or especially over 200.. then that's probably it. I'd recommend moving at least install to the info file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Talking about web page "design"] "I think my standards have lowered enough that now I think ``good design'' is when the page doesn't irritate the living fuck out of me." ==>jwz (http://www.jwz.org/gruntle/design.html)

2 1

Dynamic changes in autoYast control file (Not through rules)
by Alexander Dubinin 20 Jun '05

20 Jun '05

Hi all, Does anybody know, which variables I can use in AutoYast control file, reflecting system configuration? Or can I use any at all? Is it possible to use XML XInclude for AutoYast in SLES9? Idea is to generate swap partition size automatically, using script. Does I have possibility to start some script _before_ autoyast config file is processed? 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. Really, I prefer to do this in "pre" scripts - which have network configured and have set of basic tools, like wget (To download needed binaries from WEB, for example) -- Regards, Alexander Dubinin

1 0

SLES9 autoinstall error
by Ajay Mulwani 20 Jun '05

20 Jun '05

Hello, I am using the network installation method to install SLES9 and providing an nfs path to the autoinst.xml file. Now the two issues that I am facing with all/ any of my installations are: 1. The system displays the following error: "Your computer does not fulfill all requirements for a graphical installation.There is less than 96MB memory or the X server could not be started. As a fallback, the text found-end of YaST will guide you through the installation. This front-end offers the same functionality as the graphical one, but the screens differ from those in the manual." ... and the entire installation is in text mode. 2. After displaying the message in (1) above; when autoyast tries to read the control (autoinst.xml) file; it truncates the path to that file then asks for the same path again which was correctly defined at the PXE "boot:" prompt. Once the path to autoinst.xml is entered again the entire installation goes fine unattended in text mode and the system comes up with graphics/ video correctly configured. Any suggestions to resolve these issues will be highly appreciated. Thank you, Ajay

3 5

Re: [suse-autoinstall] initrd module load order not following info file
by Michael Steinmann 16 Jun '05

16 Jun '05

Jiri Srain wrote: > Hi Mike! > > Dne pondělí 30 květen 2005 10:26 jste napsal(a): > >>Jiri Srain wrote: >> >>>Dne pondělí 30 květen 2005 09:59 jste napsal(a): > > >>>>SLES10 seems a bit too far on the horizon. This is the first system >>>>we're trying to install using autoyast with SLES9. >>> >>>It is not issue of autoinstallatino only - plain installatino is affected >>>as well. >> >>but there at least you have the option of checking the initrd before you >>boot. I tried with adding "boot confirm true" (can't remember the exact >>syntax) in autoinst.xml but that option didn't seem to have any effect >>as the machine booted automatically right after installation finished. > > > Don't know, pass the question to the list. > > >>I would be happy if I had the chance to alter the MKINITRD and create a >>correct initrd _before_ the initial reboot, as we're not really looking >>for fully-automated setups. >>Any idea on why this might not work? > > > No, no idea. I didn't know about this option before. That's (or rather was) the option in autoinst.xml: <install> <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> </mode> According to autoyast documentation here http://www.suse.de/~nashif/autoinstall/9.1/autoyast.pdf it has been dropped for SuSE9.1/SLES9. >>>It is not possible to add all modules which are in info file to initrd - >>>because it would put there a lot of modules which are not needed. >>> >>> >>>>Where does the MKINITRD variable get set? Which file would I have to >>>>look into to tweak it myself? >>> >>>/usr/share/YaST2/modules/Initrd.ycp, after modifying it needs to be >>>recompiled by 'ycpc -c Initrd.ycp'. >> >>thanks for the pointer. I'll look into it tomorrow when I'm on site. > > > If you just want to update sysconfig and recreated initrd before the reboot, > the probably easiest would be to add to /usr/share/YaST2/clients/inst_finish > just after bootloader is installed eg. > > Popup::Message (_("Update the inirdd now")); > > This will show you message after bootloader is saved and you can switch to the > console to change anything you want to. > > Just remember that you have to change the file in the installation system > (which is stored on CD1 in /boot/root). It is cramfs image. that sounds like a good workaround, thanks.

3 2

gfxboot bootlogo
by Stefan K 13 Jun '05

13 Jun '05

Hello auto-installer, i want to change the bootlogo file on a SuSE 8.2 CD (the CD boot with isolinux) . Does anybody knows how i must convert my pcx file ..?? commands and examples are welcome ;o) thanks a lot ... Stefan __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

3 2

autoinst.xml placed on USB-Memorystick or USB-Floppy
by Link, Johannes 13 Jun '05

13 Jun '05

Hi, we used to place our autoinst.xml files on floppy disks to autoinstall our servers. Our installation media is a customized SLES8/SLES9 CD-set. But since newer hardware (like FSC Primergy TX600S2) does not ship with an integrated floppy drive anymore, we have a little problem. Is it possible to put the autoinst.xml file on a USB-Memorystick or a USB-Floppy? How does YaST deal with integrated SCSI devices? I guess we'll get a problem when we use a commandline option like "autoyast=device://sdb/autoinst.xml" since we usually don't know how many SCSI drives are already installed. Any help would be highly appreciated. Mit freundlichem Gruß / kind regards Johannes Link Siemens Business Services SBS ORS GD AHS CC 11 Würzburger Str. 121 90766 Fürth Deutschland Fon: +49 911 978-3728 Fax: +49 911 978-4080 eFax: +49 911 978-10 3728 Email: johannes.link(a)siemens.com

1 0

autoinst.xml for dual boot.
by Ajay Mulwani 13 Jun '05

13 Jun '05

Hello List, I have about 30 laptops to be installed as dual boot (Windows and SLES9). Currently the laptops are installed with Windows and other linux (most of them with redhat). Is it possible to create a single autoinst.xml file which should delete all the existing Linux partitions, if any and install SLES on that space? If yes, could you suggest the contents of that autoinst file. Thank you, Ajay

1 0

Problems trying to autoinstall NIC SLES 9 + SP 1
by Patrick O'Toole 11 Jun '05

11 Jun '05

Sorry to bother everyone but I am trying to autoinstall SLES 9 + SP1 via DOS and FTP. AM able to get the OS to install but after install the OS does not remember the NIC it used to get the files with in the first place. I put my autoinst.xml below, any ideas? Am a newbie so apologize for bothering you. THanks, Pat <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>local</domain> <hostname>linux</hostname> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>tg3</module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>10.10.1.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <tftp-server> <start_tftpd config:type="boolean">false</start_tftpd> </tftp-server> <x11> <color_depth config:type="integer">8</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">true</enable_3d> <monitor> <display> <frequency config:type="integer">72</frequency> <height config:type="integer">480</height> <width config:type="integer">640</width> </display> <monitor_device>640X480@72HZ</monitor_device> <monitor_vendor> VESA</monitor_vendor> </monitor> <resolution>640x480</resolution> <window_manager>kde</window_manager> </x11> </configure> <install> <bootloader> <activate config:type="boolean">false</activate> <loader_type>grub</loader_type> <repl_mbr config:type="boolean">true</repl_mbr> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>US/Central</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> </mode> <mouse> <id>22_exps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <software> <addons config:type="list"> <addon>Kde-Desktop</addon> <addon>Basis-Sound</addon> <addon>Basis-Devel</addon> <addon>File-Server</addon> <addon>Base-System</addon> <addon>Gnome</addon> <addon>HA</addon> <addon>dhcp_DNS-Server</addon> <addon>LSB</addon> <addon>SuSE-Documentation</addon> <addon>Linux-Tools</addon> <addon>analyze</addon> <addon>Mail_News-Server</addon> <addon>Various-Tools</addon> <addon>WBEM</addon> <addon>auth</addon> <addon>LAMP</addon> <addon>X11</addon> <addon>Print-Server</addon> <addon>YaST2</addon> </addons> <base>Full-Installation</base> </software> </install> </profile> __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

gfxboot bootlogo erstellen
by Stefan K 10 Jun '05

10 Jun '05

Hallo *nixer, ich möchte auf einer SuSE 8.2 Boot-CD das bootlogo ändern/austauschen. Da die CD ja mit isolinux bootet, frage ich mich nun wie bootlogo Datei erstellt wird. In dem installierten gfxboot und gfxboot-devel rpm gibt es unter /usr/share/gfxboot/SuSE ja die orginal pcx-Dateien von SuSE und die Datei bootlogo -- aber wie erstelle ich diese ?? Ich habe schon einiges gelesen, aber nichts hat funktioniert ... besten Dank für die Hilfe Stefan _________________________________________________________________________ Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179

1 0

Re: Ant: Re: [suse-autoinstall] SLES8 vs. UL1
by Michael Marion 10 Jun '05

10 Jun '05

On 10 Jun, FITZ MAILING wrote: > Sorry but your answer won't help me. How can I force, > that SLES8 is installed and not UL1 with one > repository, that contains both CD's (UL and SLES8)???? AFAIK.. you can't. I don't think that sles8 is a complete OS.. Just look at the sles8 specific tree, there's no kernel in there. Even under there are directories named UnitedLinux.. at least in my copy. SLES8 takes UL1, then puts suse/sles specific packages on top of that. About the best you could do is install just a very base system. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com "But these are not inherent flaws in the operating system - they don't happen by accident." - Mike Nash, "Director of Microsoft's Infrastructure Systems" explaining why NT has so many patches to fix crashes caused by malicious net users.

1 0

Re: [suse-autoinstall] autoinstall of OES novell components
by Chris Partridge 10 Jun '05

10 Jun '05

Here is a support document from Novell that should help you configure an autoyast control file to install OES components. http://support.novell.com/techcenter/articles/01_10033.html I stumbled onto it searching google for something else. Chris >>> Anas Nashif <nashif(a)suse.de> 4/24/2005 6:21 PM >>> Victor, AFAIK it is not possible currently to that via the UI. However it should be available for the next OES service pack. Anas Victor Billings wrote: > Sorry if this has been answered previously, I have done a rudimentary > search of the archive and found no answers. > > I have used autoinstall in the past and been quite pleased. But now I am > trying to do an autoinstall of the Novell components of OES. While I can > get the packages to install correctly, the YaST configuration is a > complete mystery. The Novell components all show up in my software > addons section ie; <addon>novell-base</addon> > <addon>novell-eDirectory</addon> correctly, but I do not have the > respective configuration of those components. I have been unable to find > a UI in Autoinstall for the configuration of the novell components. > > Is this currently possible via autoinstall? > > Thanks, > > Victor > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SLES8 vs. UL1
by FITZ MAILING 10 Jun '05

10 Jun '05

Hello guys, I am little bit confused about the differences between SLES8 and UL1. I created a http-repository with both UL1 CD1-CD3 and SLES 8 CD1-3 and SP3/SP4. (All files in one repository with script create_package_descr) If I boot with SLES8 CD1 or with SP4 CD everytime I will get a installed system with welcome screen "UnitedLinux1.0....". What I have to do, if I want to install SLES8 and not United Linux 1? Or is it only the banner that I have to change (/var/adm/YaST/ProdDB)? Its so important for me, because some commercial software is supported under SLES8 (e.g. vmware) and other under UL1 (e.g. trendmicro), so I have to make differences. thx and best regards ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

2 2

Question on script <location> tag and SLES 9.0
by James Mello 09 Jun '05

09 Jun '05

So I read in the SLES 9.1 documentation that you can use a <location> tag to specify a file via a URI. I'm currently running SLES 9.0 and have run the latest patches to update autoyast and other yast modules. Will this feature be available through the patches, or do I have to run SLES 9.1 to get it? When I look in /usr/share/autoinstall/dtd/scripts.dtd I see that the location tag is still commented out. Tips or pointers would be greatly appreciated!

3 3

SuSE 9.3 dhcp server config
by Volkmar Glauche 09 Jun '05

09 Jun '05

Hi, I want to install a DHCP server using autoyast over a network connection. The dhcp-server section of my control file looks like this: <?xml version="1.0"?> <dhcp-server xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns:xinclude="http://www.w3.org/2001/XInclude"> <allowed_interfaces config:type="list"> <allowed_interface>eth0</allowed_interface> </allowed_interfaces> <chroot>1</chroot> <start_service>1</start_service> <use_ldap>0</use_ldap> </dhcp-server> The dhcpd.conf comes from elsewhere, since it is a quite complicated setup on replicated machines (although YaST2 did quite a good job in translating the external source into an xml config). Now, when I install, everything is fine (control file ok, network up and running...), but the autoconfiguration module for the dhcp server fires up a message box stating "No network interface found..." and a message that YaST will stop now. When I hit OK, then autoinstallation continues and dhcp gets set up properly. Here is a snippet from y2log, which relates to this part of the autoinstallation: 2005-06-09 07:32:00 <1> linux(7718) [wfm] Y2WFMComponent.cc(import):637 Y2WFMComponent::import (Sequencer) 2005-06-09 07:32:00 <2> linux(7718) [Parser] clients/dhcp-server_auto.ycp:89 Warning: 'select ()' is deprecated 2005-06-09 07:32:00 <1> linux(7718) [wfm] Y2CCWFM.cc(createInLevel):153 Parsing finished 2005-06-09 07:32:00 <1> linux(7718) [Interpreter] Call.ycp:144 Calling YaST client dhcp-server_auto (arguments: ["Import", $["allowed_interfaces":["eth0"], "chroot":"1", "start_service":"1", "use_ldap":"0"]]) 2005-06-09 07:32:00 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:26 ---------------------------------------- 2005-06-09 07:32:00 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:27 DhcpServer auto started 2005-06-09 07:32:07 <3> linux(7718) [YCP] Report.ycp:420 Für ein einwandfreies Funktionieren benötigt dieser Server mindestens ein konfiguriertes Netzwerkgerät (neben loopback). Konfigurieren Sie eines. YaST wird nun beendet. 2005-06-09 07:32:07 <3> linux(7718) [YCP] TablePopup.ycp:65 Unknown attribute add_delete_butons 2005-06-09 07:32:07 <3> linux(7718) [YCP] TablePopup.ycp:65 Unknown attribute add_delete_butons 2005-06-09 07:32:07 <3> linux(7718) [YCP] TablePopup.ycp:65 Unknown attribute add_delete_butons 2005-06-09 07:32:07 <3> linux(7718) [YCP] TablePopup.ycp:65 Unknown attribute add_delete_butons 2005-06-09 07:32:07 <3> linux(7718) [YCP] TablePopup.ycp:65 Unknown attribute add_delete_butons 2005-06-09 07:32:07 <3> linux(7718) [YCP] TablePopup.ycp:65 Unknown attribute add_delete_butons 2005-06-09 07:32:07 <3> linux(7718) [YCP] TablePopup.ycp:65 Unknown attribute add_delete_butons 2005-06-09 07:32:07 <1> linux(7718) [wfm] Y2WFMComponent.cc(import):637 Y2WFMComponent::import (Mode) 2005-06-09 07:32:07 <1> linux(7718) [wfm] Y2WFMComponent.cc(import):637 Y2WFMComponent::import (ProductFeatures) 2005-06-09 07:32:07 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:143 DhcpServer auto finished 2005-06-09 07:32:07 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:144 ---------------------------------------- 2005-06-09 07:32:07 <1> linux(7718) [Interpreter] Call.ycp:144 Called YaST client returned: nil 2005-06-09 07:32:07 <2> linux(7718) [Parser] clients/dhcp-server_auto.ycp:89 Warning: 'select ()' is deprecated 2005-06-09 07:32:07 <1> linux(7718) [wfm] Y2CCWFM.cc(createInLevel):153 Parsing finished 2005-06-09 07:32:07 <1> linux(7718) [Interpreter] Call.ycp:144 Calling YaST client dhcp-server_auto (arguments: ["Packages"]) 2005-06-09 07:32:07 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:26 ---------------------------------------- 2005-06-09 07:32:07 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:27 DhcpServer auto started 2005-06-09 07:32:07 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:143 DhcpServer auto finished 2005-06-09 07:32:07 <1> linux(7718) [YCP] clients/dhcp-server_auto.ycp:144 ---------------------------------------- 2005-06-09 07:32:07 <1> linux(7718) [Interpreter] Call.ycp:144 Called YaST client returned: $["install":["dhcp-server"], "remote":[]] 2 A workaround would be to set the sysconfig variables directly and add the service start to a <runlevel> section. Any other ideas? Yours, -- Volkmar Glauche - Department of Neurology volkmar.glauche(a)uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5310 79106 Freiburg

2 2

Re: [suse-autoinstall] SLES 9 - AutoYaST partitioning
by Chris Partridge 08 Jun '05

08 Jun '05

Thanks for looking into it. My script seems to do what I need it to, so I'll keep it. In case anyone else is interested, here's what I'm using (it's not a complicated script at all). <scripts> <post-scripts config:type=list> <script> <interpreter>shell</interpreter> <filename>cleanup.sh</filename> <source><![CDATA[ #!/bin/sh (echo 0,0; echo 0,0; echo 0,0; echo 0,0;) | sfdisk /dev/sdb ]]> </source> </script> </post-scripts> </scripts> >>>Uwe Gansert <ug(a)suse.de> 06/08/05 6:19 am >>> On Tuesday 07 June 2005 17:33, Chris Partridge wrote: >Yep. As soon as I put a second drive section in, autoyast implements a >default partitioning scheme, so you just want to have an empty second drive, with no partition on it? Then I would suggest you to solve this by a script like you already did. Such a thing is not solved by the auto partitioning part of autoyast I guess (at least, I don't know how). Autoyast partitioning will always create at least one huge partition. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- 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] SLES 9 - AutoYaST partitioning
by Chris Partridge 08 Jun '05

08 Jun '05

Yep. As soon as I put a second drive section in, autoyast implements a default partitioning scheme, or sets up to put a swap and root partition on the second drive. I have my first drive partitioned with a /boot, swap, and / partitions. It seems to not matter if I use the <initialize> or not, and it seems to not matter how I order the <drive> sections. I've tried including a blank <partitions> section, and a few other things. So far I've been unsuccessful. The only thing I've been able to do so far is not include a second <drive> section, and wipe the drive manually. I also just made a post-script to wipe it, which works. I'd like to be able to do it in the partitioning section though. Thanks. >>>Uwe Gansert <ug(a)suse.de> 06/07/05 5:53 am >>> On Monday 06 June 2005 21:55, Chris Partridge wrote: >I have systems with more than one disk, and I'd like to configure AutoYaST >to partition the first disk, and wipe out the rest. I've tried everything >I can think of, without success. Is this possible? I would think this is possible, even though I never tried it on my own (if I understand you right at all). You tried a second <drive><device>...</drive> section? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Re: [suse-autoinstall] SLES 9 - AutoYaST partitioning
by Michael Marion 07 Jun '05

07 Jun '05

On 7 Jun, Chris Partridge wrote: > Yep. As soon as I put a second drive section in, autoyast implements a > default partitioning scheme, or sets up to put a swap and root partition on > the second drive. I have my first drive partitioned with a /boot, swap, > and / partitions. It seems to not matter if I use the <initialize> or not, > and it seems to not matter how I order the <drive> sections. I've tried > including a blank <partitions> section, and a few other things. So far I've > been unsuccessful. The only thing I've been able to do so far is not include > a second <drive> section, and wipe the drive manually. I also just made a > post-script to wipe it, which works. I'd like to be able to do it in the > partitioning section though. Your one solution sounds good.. it's still automated. My only suggestion would basically be similar, but opposite.. make one partition on it, with size max and some mountpoint you don't need. Then use the post.sh to comment out or remote the line from the mtab file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com AJ - "Ye GODS! NT crashed the microwave!" Pitr - " Hmmm. Am thinkink we should put Elder Sign seal on microwave now. Leave alone." -- User Friendly 2/28/1999.

1 0

SLES 9 - AutoYaST partitioning
by Chris Partridge 07 Jun '05

07 Jun '05

I have systems with more than one disk, and I'd like to configure AutoYaST to partition the first disk, and wipe out the rest. I've tried everything I can think of, without success. Is this possible? Christopher Partridge (cpartridge(a)novell.com) Novell, Inc., the leading provider of information solutions (801) 861-3867 http://www.novell.com

2 1

[Autoyast] Install to a directory
by emmanuel.nghunza.syalya＠eu.effem.com 07 Jun '05

07 Jun '05

Hello, I use SLES 9 - SP1 and I have found that with yast2 I could install suse in a directory (Yast -> Software -> Installation to a directory) and then make an image wich seems to be a gzip file. My questions: Is anybody know how this image can be usefull ( Can it help use to make a live CD for example) My aim is to make a live CD. Any advises and information will be welcome. I tried this tool (www.linux-live.org) without success. Thank you Best regards, Emmanuel --------------------------------------------------------------------------------- Global Processing - Unix Phone : +33 (0) 388-05-1639 Internal : SXB *170x1639 mailto : emmanuel.nghunza.syalya(a)eu.effem.com

2 1

Custom rules and instmode
by Pavlin Maslyankov 07 Jun '05

07 Jun '05

Hi guys, Do somebody knows whether there is a way to get the *instmode* type/linuxrc argument and use it in a custom rule? Regards, Pavlin Maslyankov "Tumbleweed E-mail Firewall <tumbleweed.com>" made the following annotations on 06/07/05 04:08:05 ------------------------------------------------------------------------------ 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. ==============================================================================

2 1

AutoYaST auto-installation options
by Darren Davis 03 Jun '05

03 Jun '05

Hello, I am working with a customer that is trying to use AutoYaST to do a Full Installation auto-install. They are having an issue in getting all the packages to be selected. Here is what they said; We are setting up autoyast install xml files and noticed when we select Full Installation that the install does not install all the RPMS, only about 976 of them. Currently the only way I have found to install all packages is to select each package group and do a install all. Is this the way that autoyast is setup to install all rpm files or is there another option to select everything. For Example on Redhat we can set an option Everything and that will allow installation of all rpm packages. Is there an option in Autoyast to do the same thing. Can this be done? Thanks, Darren Darren R. Davis Linux Developer Evangelist Novell Strategic Partner Engineering

1 0

remote access and autoyast
by Benjamin Indermühle 03 Jun '05

03 Jun '05

Hi there how can you enable "Remote Graphical Login" in autoyast.xml ? I have tried <displaymanager_remote_access>yes</displaymanager_remote_access> <fw_services_ext_tcp>http ssh 10000 5901</fw_services_ext_tcp> that doesn't seem to work though thanks a lot for your help greets ben -- *~*~* *~*~* We are connecting the world ! *~*~* *~*~* SolNet - Internet Solution Provider Bechburgstrasse 29, 4528 Zuchwil, Switzerland Phone: +41 32 686 82 82, Fax: +41 32 685 96 13 WWW: http://www.solnet.ch - E-Mail:ib@solnet.ch *~*~* *~*~* *~*~* *~*~* *~*~* *~*~* *~*~* *~*~* *~*~*~*

3 2

Problem with YaST and SCSI disk
by fraser_bailey＠agilent.com 03 Jun '05

03 Jun '05

Hi I have an Intel system with 4 SCSI adapters. The internal adapters are aic7902 adapaters driven by the aic79xx module. The external adapters are aic7899 adapters driven by the aic7xxx module My install is performed when only 2 disks are present on scsi 1. There are no disks on scsi 0 or scsi2 or scsi3. The install configures /etc/sysconfig/kernel as follows: INITRD_MODULES="aic79xx aic7xxx aic79xx reiserfs" and the first disk on scsi 1 is assigned sda1 nad has the root partition installed onto it. However, if I run YaST through any of the options which reconfigure initrd this variable is reset to: INITRD_MODULES="aic7xxx aic79xx reiserfs" This means that if I now attach an external disk array to scsi2 or scsi3 these disks will be located first because aic7xxx is loaded first. Disks in the disk array are assigned to sda1 and so on, rahther than the internal disk. The upshot is that the attempt to mount / on /dev/sda1 now fails and the system startup halts. Have I setup my install configuration wrongly? Or is this a bug in YaST mkinitrd scripts? Any help or advice would be much appreciated.

1 0

A questio about autoyast harddrive installation
by Pavlin Maslyankov 03 Jun '05

03 Jun '05

Hi guys, I am using SuSE LES 9.0 and I am trying to do an autoyast installation from a specific partition of the harddrive. When I tried to use the same harddrive partition for a location of autoinst.xml file in this way: autoyast=device://hdpart/autoinst.xml it saw that the mount failed because of the fact that the same device is already mounted. So I used the file:///mounts/extra/ for a value of autoyast argument. My question is : May I be sure that this will not be changed in the future or there is another way to use the same partition which is more clear. Regards, Pavlin "Tumbleweed E-mail Firewall <tumbleweed.com>" made the following annotations on 06/03/05 01:13:40 ------------------------------------------------------------------------------ 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

Confirmation of kernel-nogpl-package
by Achim Ziegler 01 Jun '05

01 Jun '05

Hi there, I created an unattended installation procedure for SuSE 9.2 using AutoYaST. But there are still a few problems, I couldn't fix. During the installation, YaST asks for confirmation for installing the kernel-nongpl package. Is there a possibility to disable or auto-confirm the installation? These parameters don't work: --- <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">false</reboot> </mode> --- Thanks for your help! Achim

1 0