October 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

passing boot ( interactively) options to grub combined with with using the menu.lst
by Hans-Joachim Ehlers 25 Nov '05

25 Nov '05

Hi folks, i am trying to move a Suse Installation CD to a USB-Stick so i can use the USB Stick for installation. The suse installation has the wonderfull option that you can add on a command line additional parameters to the kernel . Like: -> Select Installation -> On the command line add: hostname=myws At the moment i am able to boot from the USB-Stick with grub and can select 'Installation' from the grub menu. But how do i add additional parameter to grub without the need to modify the menu.lst ? Like the isolinux.cfg when booting from cd/dvd Extract from the menu.lst .. title Installation root (hd0,0) kernel /boot/loader/linux root=dev/sda1 vga=791 initrd /boot/loader/initrd tia Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int

2 1

Re: [suse-autoinstall] Best practices for adding external package sources?
by Michael T. Halligan 03 Nov '05

03 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael, Is there a good searchable site for the archives? Right now, the best I've found is http://lists.suse.com/archive/suse-autoinstall/ and not very useful... Perhaps a FAQ on this topic would be appropriate at this point, if anybody @ Novell is reading this.. Since it comes up so often. Mihcael On Oct 18, 2005, at 4:03 PM, Michael Marion wrote: > On 18 Oct, Michael T. Halligan wrote: > > >> I have two dilemmas with AutoYast I'm sure somebody here will be able >> to help me solve. They're >> really the same issue, and that is adding external rpms. >> > > Both of what you want to do can be easily solved using a custom > path with > custom RPMS. > > Look in the archives for the subject: > > Additional Package & Silent install > > One message of which also talks about 2 other threads with more in- > depth info. > > -- > Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com > Frasier: "...we know for whom the bell tolls." > [A bell dinging is heard, everyone looks around a little confused] > Martin: "Anybody else hear that?" > Daphne: "Oh! The biscuits!" --Fraiser > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDXx9AwjCqooJyNAMRArHOAJ94RnQFYkwOuurmFUGocMH0CrVKGACdHO2s pEdANrCvZt0Y8lj4Bq8z3OM= =7Az6 -----END PGP SIGNATURE-----

4 6

(Auto-)install multiple languages?
by Thomas Ribbrock 03 Nov '05

03 Nov '05

Hi all, after I just finished my first succesful autoinstall (yeah!) :-) I am left with a couple of questions as to how to improve it further. One thing I need to do is to automatically install more than one language - basically like you do under YaST2 in the "language" module with adding "Secondary Languages". I have seached through http://www.suse.de/~ug/autoyast_doc/ as well as through the archive of this list http://marc.theaimsgroup.com/?l=suse-autoinstall&r=1&w=2 but came up empty. Is there an easy way to accomplish this? If not, I can think of only two alternatives: - Manually add all language related packages for the languages I need to the package list (brrrrr...) - Try to do some script-wizardry in post-install or init? I have yet to figure out whether I can convince YaST2 to add the secondary languages from the commandline - if not, I'm down to the first option... Any hints (including docs I might have missed...) are welcome! Cheerio, Thomas

4 7

Strange behaviour of autoinstall
by Bernhard Duebi 02 Nov '05

02 Nov '05

Dear everybody, I have two problems: 1) CD Creator doesn't respect SP2 2) ncompress package is not installed I use a custom CD to install all our servers. I create the CD with SuSE Yast CD Creator. With SLES9 SP1 everything was fine. With SP2 I noticed that not all files on the CD are up to date. The driverupdate file comes from the SP1 CDs. The /boot comes even from the original SLES9 CDs. I fixed this by copying the SP2 files into the directory and regenerating the ISO image by hand, but I think this is the job of CD Creator. I need /usr/bin/uncompress to install one of our enterprise tools. In SP1 this was in the sharutils package. With SP2 it moved to the ncompress package. Though, I added the ncompress package to my XML file and recreated the ISO image. When I install a machine with this new CD, the GUI tells me that the ncompress package is being installed. The Yast logfiles, tell me that the installation of ncompress was successful. But if I do a rpm –q ncompress it tells me that ncompress is not installed and I can't find the /usr/bin/uncompress on disk. If I do rpm –ihv /media/cdrom/suse/*/ncompress*.rpm it installs cleanly. I also installed the machine with an install-server using the same XML files. The result is the same. The logfiles tell me that ncompress was successfully installed, but the files are not on disk. Any idea what's happening here ? Sincerely Bernhard Dübi

2 1

Re: [suse-autoinstall] Warum ist SLES9
by Petteri Hakkarainen 28 Oct '05

28 Oct '05

Kaikki RPM:t eivät aina asennu. Petteri -----Original Message----- From: Christian Goetze <cg(a)sensage.com> To: suse-autoinstall(a)suse.com Date: Fri, 28 Oct 2005 11:58:37 -0700 Subject: [suse-autoinstall] Warum ist SLES9 "Full-Installation" nicht full installation? Wieso werden nicht alle *-devel rpms installiert wenn ich "Full Installation" auswaehle? Im Moment muss ich eine Menge extra *-devel RPMs explizit angeben... -- cg -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Warum ist SLES9 "Full-Installation" nicht full installation?
by Christian Goetze 28 Oct '05

28 Oct '05

Wieso werden nicht alle *-devel rpms installiert wenn ich "Full Installation" auswaehle? Im Moment muss ich eine Menge extra *-devel RPMs explizit angeben... -- cg

1 0

SuSE 10.0: howto put an info file into initrd
by Gunreben, Peter (Peter) 28 Oct '05

28 Oct '05

Hi, if you want to put an "info" file into the SuSE 10.0 initrd, e.g. for creating an autoinstall-CD, you can do it in the following way: ============= 8< ============ mv initrd{,.gz} gunzip initrd.gz echo info | cpio -o -H newc -A -F initrd gzip -9 initrd mv initrd{.gz,} ============= 8< ============ It took me a while to notice the necessary "-H newc" option. Regards, Peter.

3 2

Rules compatibility between Novell OES1 and SLES 9 x64
by Dwayne McGarty 28 Oct '05

28 Oct '05

Greetings, I presently have an autoyast set up to deliver Novell OES1 (SLES9 i386 based). I wish to build some servers with just the SLES9 x64 distribution and was hoping to use the same rules.xml file to kick things off. Here is the rules.xml that is presently working for OES1: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <product> <match>*</match> <match_type>exact</match_type> </product> <result> <profile>profiles/templates/base.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <mac> <match>*</match> <match_type>exact</match_type> </mac> <result> <profile>profiles/mac/@mac@/eth0.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <script> <![CDATA[ #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin if [ -n "`grep build= /proc/cmdline`" ] then echo -n `cat /proc/cmdline | sed -e 's/.*build=$.*$/\1/' -e 's/^$.*$ BOOT.*/\1/'` else echo -n "hse9-32" fi ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>profiles/software/@custom1@.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> The SLES9 x64 autoyast attempts using the same rules.xml file but seems to not match any of the rules and prompts for the location of a proper rules file. On inspecting the /var/log/YaST2/y2log file, it appears that the bit of shell scripting being kicked off to compare the product/mac strings to the * character are failing and returning 1 instead of 0 as they do with the OES1 installation. ie the scripts are treating the wildcard (*) character literally. Does the SLES9 x64 autoyast support the use of wildcards in the match? If not, what can I use instead Thanks for any help...

2 1

adding new istall source in yast2
by Edward Dunagin 26 Oct '05

26 Oct '05

when i get the menu, there is a spot for the server name, which i put in as: download.opensuse.org/ choosing http and : disribution/-OSS-stable/inst-source-java/ as the directory on server, then i get an error, (which by the way, is unintelligble(?) : InstSrc:E_no_instsrc_on_media anyone know what i'm doing wrong and interpet the error message? thenks ...............ed Edward M Dunagin 4646 Glenwood Drive Bozeman, MT 59718 Mobile 406.570-0992 Skype-phone +1 406 322 2566 Digital 406.556.7282 __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

Re: [suse-autoinstall] AutoYaST generated partitioning plan with SL-10.0
by Friedrich Delgado Friedrichs 26 Oct '05

26 Oct '05

Hey! That did it. My mistake, of course... I used the old xml snippets for ip-address and hostname configuration which were generated from a template of the old autoyast (from SuSE 9.1). Uwe Gansert schrieb: > On Wednesday 26 October 2005 15:33, you wrote: > > you have <configure> tags in your profile. > Please remove the <configure> and the </configure> tag. Thanks a lot! FDF -- Friedrich Delgado Friedrichs (IT-Services), DFN-CERT Services GmbH https://www.dfn-cert.de/, +49 40 808077-555 (Hotline)

1 0

AutoYaST generated partitioning plan with SL-10.0
by Friedrich Delgado Friedrichs 26 Oct '05

26 Oct '05

Hi! I've ported an old installation profile from SuSE 9.1 to SL-10.0 with "yast2 autoyast". Unfortunatly in the "Create partition plans" stage I get the error message "Error while configuring partitions. Try again.". The installation is started over pxe. The relevant of my config file is: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fs_options> <opt_blocksize> <option_str>-b</option_str> <option_value>auto</option_value> </opt_blocksize> <opt_bytes_per_inode> <option_str>-I</option_str> <option_value>default</option_value> </opt_bytes_per_inode> <opt_inode_density> <option_str>-i</option_str> <option_value>auto</option_value> </opt_inode_density> <opt_raid> <option_str>-Rstride=</option_str> <option_value>none</option_value> </opt_raid> <opt_reserved_blocks> <option_str>-m</option_str> <option_value>auto</option_value> </opt_reserved_blocks> </fs_options> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>256M</size> </partition> <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>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fs_options> <opt_blocksize> <option_str>-b</option_str> <option_value>auto</option_value> </opt_blocksize> <opt_bytes_per_inode> <option_str>-I</option_str> <option_value>default</option_value> </opt_bytes_per_inode> <opt_inode_density> <option_str>-i</option_str> <option_value>auto</option_value> </opt_inode_density> <opt_raid> <option_str>-Rstride=</option_str> <option_value>none</option_value> </opt_raid> <opt_reserved_blocks> <option_str>-m</option_str> <option_value>auto</option_value> </opt_reserved_blocks> </fs_options> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>2G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fs_options> <opt_blocksize> <option_str>-b</option_str> <option_value>auto</option_value> </opt_blocksize> <opt_bytes_per_inode> <option_str>-I</option_str> <option_value>default</option_value> </opt_bytes_per_inode> <opt_inode_density> <option_str>-i</option_str> <option_value>auto</option_value> </opt_inode_density> <opt_raid> <option_str>-Rstride=</option_str> <option_value>none</option_value> </opt_raid> <opt_reserved_blocks> <option_str>-m</option_str> <opt_reserved_blocks> <option_str>-m</option_str> <option_value>auto</option_value> </opt_reserved_blocks> </fs_options> <loop_fs config:type="boolean">false</loop_fs> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <size>11G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</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>2G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</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>4G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <size>1G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,noacl</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/var/cache/afs</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>4G</size> </partition> <partition> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/scratch</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> I regenerated the partition plan from scratch with autoyast, however other parts of the config were imported to autoyast and then modified. The configuration worked for the SuSE 9.1 installations. I also saved the y2log file which is 182k large. Please tell me, what I can do to identify the problem! Kind regards FDF -- Friedrich Delgado Friedrichs (IT-Services), DFN-CERT Services GmbH https://www.dfn-cert.de/, +49 40 808077-555 (Hotline)

2 3

control.xml / software tag
by mm＠gnulinux.de 25 Oct '05

25 Oct '05

Hi, I am trying to modify a control.xml from a default installation CD. I have changed the software tag to something like: <selection_type config:type=”symbol”>fixed</selection_type> <base>Minimal</base> But it seems to be ignored. The installer just shows: ? (161.3 MB total) I have also tried to preselect another base category, which also is ignored. Any Ideas? Marcus PS: Perhaps I have to mention that I have removed the desktop_new module from the control file.

2 2

Control file not found - must be an easy mistake
by Stefan Pfeiffer 25 Oct '05

25 Oct '05

Hi! I tried an autoinstall with an autoinst.xml on a floppy and the Suse 10.0 (retail version) installation DVD, like outlined in the 7.3.2. section of the autoyast documentation "Auto-installing a Single System". When booting, the floppy gets accessed, but the logging console says "You must supply a control file", or something similar (I do not have the machine right here now where i can write mails). Yast also says that it cannot find a control file. I tried no special kernel paramater, but also "autoyast=default" und "autoyast=floppy" without success. The xml control file is named autoinst.xml and is placed in the root of the floppy. I must have overlooked a silly little detail... Thanks for any help... Regards, Stefan Pfeiffer -- # Dipl.-Phys. Stefan Pfeiffer # Abteilung Modellierung und Simulation # Fraunhofer Institut f. Lasertechnik # Steinbachstr. 15, D-52074 Aachen, Germany. # Tel: + 49 (241) 8906 153 , Fax: +49 (241) 8906 121 # EMail: pfeiffer(a)ilt.fhg.de, WWW: http://www.ilt.fhg.de/nld/

2 2

boot partition for openpower systems
by Reynold L Demarco 20 Oct '05

20 Oct '05

I am trying to autoyast an IBM OpenPower 520 system. When I autoyast the system without creating a PReP boot partition, the autoyast won't complete without error. I get the following error when it tries to install the boot loader.... ERROR: boot = /dev/null is not a valid block device When I create a PRep boot partition using the following in my autoyast file.... <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">65</partition_id> <partition_type>primary</partition_type> <size>24M</size> </partition> The autoyast completes fine and I get a bootable system. However, when I do an fdisk on the booted system, the PReP Boot partition starts and ends on cylinder 1 and I get a message stating that "Partition 1 does not end on cylinder boundary". So I have a couple of questions... -Do I need to create this PReP Boot partition? If so, what is the correct configuration so to not get the cylinder boundary error? -If I must have it, how do I mount it after the fact so I can modify bootloader settings? -Can this partition be a FAT16 partition, and if so how do I create this, I tried using partiton_id 5 and 6 and my autoyast fails. Any help appreciated.

1 0

Yast Autoinstall
by Marvin H Green 20 Oct '05

20 Oct '05

Hello, I already created my control file for the Auto install but I'm not sure where to go next. I would like to get things setup so that the control file would be read during installation and avoid use intervention. Any ideas of what/how to do this? Thank you, Marvin H Green Coop/Intern, z/VM System Test IBM - Endicott, NY 13760 Email: mhgreen(a)us.ibm.com Tel: (607) 429-5964 or T/L 620-5964

3 3

Re: [suse-autoinstall] autoyast beginner question
by Yan Fitterer 20 Oct '05

20 Oct '05

All you need is to autoinstall=nfs://x.x.x.x/installsource/autoinst.xml on your install kernel command line. autoyast=default will not pick up a file called autoinst.xml Best, Yan >>> Rainer Krienke <krienke(a)uni-koblenz.de> >>> Hello, I am using opensuse10.0 at the moment. i do installations of hosts usually via NFS which woks fine. What I wanted to achive is that when an installation starts a certain set of packages is used for this installation without the need to go into the yast menues an select the packages I would like to install. So i created my own package selection and integrated it in mediaroot/suse/setup/descr/ . Manually I can activate this package selection in yast. Now I would like to automatically select this package selection when yast starts up in an installation process. So I thought I create a autinstall.xml file containing code to select my package selection and then go on installing like usual. The autoinst.xml file is very simple (created by yast autoinstall): <?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"> <software> <addons config:type="list"> <addon>Min</addon> <addon>uniko-4.2</addon> </addons> <base>Minimal</base> </software> </profile> I put this file in the root directory that I specify for NFS installation. When I now start an installation and say autoyast=default on the kernel commandline autoyast comes up and at the point of "Steuerdatei abrufen und einlesen" it asks me in a dialog Box for "Pfad für Systemprofil" (Path to system profile). And now I actually do not know what autoyast needs? I thought my autoinst.xml file is the system profile needed? But it seems there is something more? Can anyone help Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke(a)uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------

5 5

autoyast beginner question
by Rainer Krienke 20 Oct '05

20 Oct '05

Hello, I am using opensuse10.0 at the moment. i do installations of hosts usually via NFS which woks fine. What I wanted to achive is that when an installation starts a certain set of packages is used for this installation without the need to go into the yast menues an select the packages I would like to install. So i created my own package selection and integrated it in mediaroot/suse/setup/descr/ . Manually I can activate this package selection in yast. Now I would like to automatically select this package selection when yast starts up in an installation process. So I thought I create a autinstall.xml file containing code to select my package selection and then go on installing like usual. The autoinst.xml file is very simple (created by yast autoinstall): <?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"> <software> <addons config:type="list"> <addon>Min</addon> <addon>uniko-4.2</addon> </addons> <base>Minimal</base> </software> </profile> I put this file in the root directory that I specify for NFS installation. When I now start an installation and say autoyast=default on the kernel commandline autoyast comes up and at the point of "Steuerdatei abrufen und einlesen" it asks me in a dialog Box for "Pfad für Systemprofil" (Path to system profile). And now I actually do not know what autoyast needs? I thought my autoinst.xml file is the system profile needed? But it seems there is something more? Can anyone help Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke(a)uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------

1 0

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Ajay Mulwani 19 Oct '05

19 Oct '05

Hi Hans, 1. The class.xml file was missing that header and footer info which I added and restarted the install. It seems the swap is still not there !! 2. rules.xml : is exactly the same as you had mailed earlier. $ cat rules.xml <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ #!/bin/sh mem=$( cat /proc/meminfo | grep -i memtotal | awk '{ print $2 } ' } # Output is in kbytes echo -n $mem ]]> </script> <match>499999</match> <match_type>greater</match_type> </custom1> <result> <profile>classes/largeswap.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>500000</match> <match_type>lower</match_type> </custom1> <profile>classes/smallswap.xml</profile> <continue config:type="boolean">true</continue> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/autoinst.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> $ 3. /var/adm/autoinstall/cache/InstalledSystem.xml is certainly missing the swap partition info. 4. The latest documentation link seems to not working currently. Regards, Ajay

2 1

RE: [suse-autoinstall] Output of post scripts
by Stephens, Bill {PBSG} 19 Oct '05

19 Oct '05

Try ctrl+alt+f3 or f4 -----Original Message----- From: Dennis Peere [mailto:sycrontw@hotmail.com] Sent: Wednesday, October 19, 2005 10:15 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Output of post scripts Hi all, Can anyone tell me if there is any way to show some output of a post installation script to the console screen ? I'd like to show what scripts it is performing and show some results. Regards, Dennis _________________________________________________________________ Bescherm je Inbox: Phishing - hoe te herkennen, rapporteren en voorkomen http://www.msn.be/security/phishing/ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Output of post scripts
by Dennis Peere 19 Oct '05

19 Oct '05

Hi all, Can anyone tell me if there is any way to show some output of a post installation script to the console screen ? I'd like to show what scripts it is performing and show some results. Regards, Dennis _________________________________________________________________ Bescherm je Inbox: Phishing - hoe te herkennen, rapporteren en voorkomen http://www.msn.be/security/phishing/

1 0

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Hans-Joachim Ehlers 19 Oct '05

19 Oct '05

Hi Ajay, 1) verify with ' xmllint ' any of your xml files. 2) Keep in mind that the rules.xml was an UNTESTed example. 3) Verfiy your directory structure and file security setting . No softlinks and what so ever. 4) I mentioned also the /var/log/Yast2 directory. You will find there the y2log* files . Search them for rules.xml. You will see what happens during parsing the rules.xml. 5) I hope that your 'global' xml does not contain any Swap info. Maybe it is a good idea to REMOVE any partition info from your 'global' xml file and put all partition information into your class files for the sake of simplity To make the point: a) verify that your rules.xml works as expected ( search in the log files ) If it works as aspected: b) Verify the the merging process / the merged xml file And maybe Uwe got an idea ? hth Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int >>> Ajay Mulwani <ajaymulwani(a)gmail.com> 19/10/05 15:25 >>> Hi Hans, 1. The class.xml file was missing that header and footer info which I added and restarted the install. It seems the swap is still not there !! 2. rules.xml : is exactly the same as you had mailed earlier. $ cat rules.xml <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ #!/bin/sh mem=$( cat /proc/meminfo | grep -i memtotal | awk '{ print $2 } ' } # Output is in kbytes echo -n $mem ]]> </script> <match>499999</match> <match_type>greater</match_type> </custom1> <result> <profile>classes/largeswap.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>500000</match> <match_type>lower</match_type> </custom1> <profile>classes/smallswap.xml</profile> <continue config:type="boolean">true</continue> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/autoinst.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> $ 3. /var/adm/autoinstall/cache/InstalledSystem.xml is certainly missing the swap partition info. 4. The latest documentation link seems to not working currently. Regards, Ajay

1 0

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Hans-Joachim Ehlers 19 Oct '05

19 Oct '05

Hi Ajay 1) Even an class.xml file must contain the header and footer for an autoinstall XML File Example: ( I do not know if its valid or not ) <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> ... ... </autoinstall> So your example is missing them. The best is to take the lines from your autoinst.xml file 2) Have you checked your rules.xml Be carefull with the <continue config:type="boolean">false</continue> because my example is pretty simple ( It does not use AND or OR logic for rules ) and after that no rules are processed any further. so you might post also your rules.xml 3) Check the Yast-Log files ( I think you will find the log after installation at /var/log/Yast2 ) and also look at /var/adm/autoinstall/cache/InstalledSystem.xml because it should be your merged final control/autoinstall file. 4) Latest Documenation for autoyast http://www.suse.de/~ug/autoyast_doc/rulesandclass.htm hth Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int >>> Ajay Mulwani <ajaymulwani(a)gmail.com> 19/10/05 13:38 >>> Hello Hans, Thanks for the excellent info. I was testing this and configured my setup exactly the same way as mentioned in your example. The host on which I tried the installation is having more then 500MB RAM. Therefore I assumed largeswap.xml and autoinst.xml files should have been be merged to create the final control file. The contents of largeswap.xml file in my case are: $ cat largeswap.xml <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>2000mb</size> </partition> $ ..... and rest everything is defined in autoinst.xml. However after installation was over I saw all the partitions except swap. Please let me know if I did anything wrong or misunderstood somewhere. Regards, Ajay

2 1

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Ajay Mulwani 19 Oct '05

19 Oct '05

Hello Hans, Thanks for the excellent info. I was testing this and configured my setup exactly the same way as mentioned in your example. The host on which I tried the installation is having more then 500MB RAM. Therefore I assumed largeswap.xml and autoinst.xml files should have been be merged to create the final control file. The contents of largeswap.xml file in my case are: $ cat largeswap.xml <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>2000mb</size> </partition> $ ..... and rest everything is defined in autoinst.xml. However after installation was over I saw all the partitions except swap. Please let me know if I did anything wrong or misunderstood somewhere. Regards, Ajay

1 0

RE: [suse-autoinstall] Supplementary installation-sources and version numbers
by Marlier, Ian 18 Oct '05

18 Oct '05

I'd grab the .src RPM, and change the name of the package. Leave the deps and everything alone, but if it's got a different package name then it shouldn't be overwritten. (ie, call is drdb-lars-0.7.13-0) -----Original Message----- From: Lars Neyjahr [mailto:lars.neyjahr@bcc.de] Sent: Tue 9/27/2005 9:17 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Supplementary installation-sources and version numbers Hi there, I have a few questions about installation of different versions of RPM-packages during auto-install. I use an additional installation-source which was added by "installation_sources -ea ftp://..." and I'd like to install an older (by version-number) package from this source rather than from my local SuSE-mirror. Here is an example: drbd-0.8.0-3 <= original SuSE-package which I don't want drbd-0.7.13-0.ln.0 <= my own package which I want to install How can I install a specific version - 0.7.13-0.ln.0 in this case - if the original version number is higher and how do i prevent any following online-update from installing the newer version? Thanks in advance. Bye... ...Lars -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Ethernet aliases?
by Michael T. Halligan 18 Oct '05

18 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What's the best way to do an ethernet alias in a control file? Like creating an eth0:1 or eth0:2 device? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDVVj1wjCqooJyNAMRAtuvAKCv52ETl58JXg6Ijsu6crkbajukIACgtVwd U1B5HPiYjxugQqHAFjQPuNM= =PrBT -----END PGP SIGNATURE-----

1 0

Re: [suse-autoinstall] Network installation - kernel command line limitation
by Alexander Dubinin 18 Oct '05

18 Oct '05

Hi Hans-Joachim, all, No, there is :) Please, look at documentation for autoyast - PDF file, section 7.3.3, named "Combining linuxrc info file with YaST2 control file": - Cut - 3.3. Combining linuxrc info file with YaST2 control file If you choose to pass information to linuxrc using the info file, it is possible to integrate the keywords in the XML control file. In the case the file has to be accessible to linuxrc and has to be named info. Linuxrc will look for a string (start_linuxrc_conf in the control file which represents the beginning of the file. If it is found, it will parse the content starting from that string and will finish when the string end_linuxrc_conf is found. The options are stored in the control file in the following way: Example 7.2. Linxurc options in the control file .... <install> .... <init> <info_file> <![CDATA[ ## Don't remove the following line: # start_linuxrc_conf # install: nfs://192.168.1.1/CDs/full-i386 textmode: 1 autoyast: file:///info # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> ...... </install> .... Note that the autoyast keyword must point to the same file, i.e. if it is on a floppy, then the protocol floppy has to be used. In other cases where the info file is stored in the initial ram-disk, the file option has to be used. - Cut - Recreation of initrd is not suitable - as I need to install SLES9 in many different locations (As I understand it's "Enterprize" Linux, isn't it? ;) and from different NFS servers. Even in one office, there are few LABs, located behind firewall, where addresses of NFS server are different. So, target is to have generated autoyast control file for different offices (Using CGI script and database with server names, NFS paths, partition layouts, etc.) and install SLES9 transparently for customers. And of course, there is no reason to recreate initrd image, used for PXE boot for each of hundred locations - it's crazy. 2005/10/18, Hans-Joachim Ehlers <HansJoachim.Ehlers(a)eumetsat.int>: > > >>> Alexander Dubinin <adubinin(a)gmail.com> 17/10/05 22:22 >>> > >Does anybody have other ideas? Or maybe somebody know, how to make > >"info" section in control file working? > > There is no INFO section in the control file. > Add the file ' info ' into the initrc file what just means: > Unpack the file ( Its a cpio archiv conating a minimal linux bootkernel and modules afaik ) > Add the info file to it. > repack the the initrc and be happy. > > Sorry for the sort answer but its pretty late in germany. > > hth > Hajo No problems :) Anyway - thanks for try to help! -- Regards, Alexander Dubinin

1 0

Re: [suse-autoinstall] Network installation - kernel command line limitation
by Hans-Joachim Ehlers 17 Oct '05

17 Oct '05

>>> Alexander Dubinin <adubinin(a)gmail.com> 17/10/05 22:22 >>> >Does anybody have other ideas? Or maybe somebody know, how to make >"info" section in control file working? There is no INFO section in the control file. Add the file ' info ' into the initrc file what just means: Unpack the file ( Its a cpio archiv conating a minimal linux bootkernel and modules afaik ) Add the info file to it. repack the the initrc and be happy. Sorry for the sort answer but its pretty late in germany. hth Hajo

1 0

Network installation - kernel command line limitation
by Alexander Dubinin 17 Oct '05

17 Oct '05

Hi all, Recently I've found that pxelinux, supplied with SLES9 still have limitation with 255 characters in kernel command line. So, if you want to append "aytoyast=<URL> install=<NFS_PATH> <some_kernel_options>" - it's very easy fall out to some strange mode during installation... For example, I had "showopts" argument cut at first letter - as result "s" was added to kernel options... You can imagine result ;) As I understand, it's problem of pxelinux - it uses old boot protocol, instead of new one - 2.02 - which have no such limitation. Is there any workaround? I've tried to use "Combining linuxrc info file with YaST2 control file" - but not understand, how it supposed to work. When I've placed required section to control file, retrieved from CGI script, and removed "install=" option from kernel command line, it just not working. Seems like linuxrc don't know how to get it from HTTP... So, looks like there are 2 options left - rewrite pxelinux to support longer kernel command line, or make "info" section of control file working... Does anybody have other ideas? Or maybe somebody know, how to make "info" section in control file working? Any help will be _very_ appreciated! -- Regards, Alexander Dubinin

1 0

Loadlin 1.6C problem when installing Novell Linux Desktop 9
by Dennis Peere 14 Oct '05

14 Oct '05

Hi, I'm trying to perform an automated harddisk installation of NLD 9 but seem to have problems loading initrd with loadlin 1.6C. The original initrd deliverd on CD1 of NLD is 5706806 bytes and I think that's too big for loadlin 1.6C. When I boot in FREEDOS and start loadlin I use the following command LOADLIN LINUX initrd=INITRD ramdisk_size=65536 root=/dev/ram0 init=/linuxrc It ends with the following error message : RAMDISk: Compressed image found at block 0 Invalid compressed format (err=2) VFS: Mounted root (minix filesystem) readonly Freeing unused kernel memory: 212K freed I've tried the following commands, without success, to start loadlin : LOADLIN LINUX INITRD=INITRD ramdisk_size=65536 LOADLIN linux initrd=initrd init=/linuxrc LOADLIN linux initrd=initrd init=/linuxrc root=/dev/ram0 I've used the same loadlin version to install RedHat 8.0 and RHES 4 without any problems. Although I must say that the initrd.img's were smaller on RH (2711963 bytes for RH8 and 3092868 bytes for RHES4) If I boot from CD1 and start the installation, the following modules are loaded during installation : Module Size Used by reiserfs 241488 1 edd 9368 0 dm_snapshot 16796 0 dm_mod 50300 1 dm_snapshot multipath 7688 0 raid6 98576 0 raid5 20736 0 xor 15240 2 raid6,raid5 raid1 14848 0 raid0 8192 0 parport_pc 35520 0 parport 37832 1 parport_pc usb_storage 60096 0 uhci_hcd 29200 0 hid 40896 0 ehci_hcd 27908 0 usbcore 103644 6 usb_storage,uhci_hcd,hid,ehci_hcd ide_cd 36740 0 sg 35616 0 sr_mod 16292 0 sd_mod 20224 0 scsi_mod 108876 4 usb_storage,sg,sr_mod,sd_mod cdrom 36892 2 ide_cd,sr_mod cramfs 42868 1 vfat 14208 2 fat 43584 1 vfat af_packet 20872 0 nvram 8456 0 I've tried to mount the initrd (from the NLD cd's) and removed all modules that weren't loaded during the cd installation. The result was an initrd of 2056532 bytes When I started loadlin with that initrd I got the following error mesages with every module the kernel want to load : on VT3 insmod: error inserting '/modules/reiserfs.ko': -1 Invalid module format insmod: error inserting '/modules/eepro100.ko': -1 Invalid module format on VT4 ehci_hcd: disagrees about version of symbol struct_module uhci_hcd: disagrees about version of symbol struct_module After giving up on trying to find out what modules I needed to put in the initrd I started looking for an alternative program for loadlin that can mount the original initrd and found Tiny.exe => http://sourceforge.net/projects/gujin/ Used that with the following command : tiny.exe linux initrd root=/dev/ram0 ramdisk_size=65536 init=/linuxrc Error message : Kernel panic: No init found. Try passing init= option to kernel. linld.com => http://195.66.192.168/linux/linld/ Used that with the followinc command : linld.com image=linux initrd=initrd cl=nld.par nld.par includes : ramdisk_size=65536 install=hd://suse/nld/cd1 autoyast=file:///mounts/extra/autoinst.xml Error message : -1 Invalid module format for every module it wants to load. Hope someone can help me out :-( Regards, Dennis Peere _________________________________________________________________ Gratis bloggen op MSN Spaces http://spaces.msn.com/?mkt=nl-be

3 3

xinclude:include on AutoYaST SLES9
by Yan Fitterer 14 Oct '05

14 Oct '05

I'm having trouble using the xinclude:include syntax on SLES9 SP2. See file extracts below. A few questions: 1) Is the xinclude syntax is known to work on SLES9 SP2? 2) Is it possible to reference a local file in the href: ? (like href:=/tmp/osmf.xml) 3) From the error in y2log, it seems that autoyast can't get the http file, however if I do: wget http://10.26.248.155/SLES9CONTROL/sles9sp2/content.xml I get the file all right. Any clues please? Thanks Yan LOGS & FILES: I have in the 'container' file: <profile 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"> and down further: </partition> <xinclude:include href="http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml" /> <partition> The osmf.xml file: <?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" xmlns:xinclude="http://www.w3.org/2001/XInclude"> <install> <partitioning config:type="list"> <drive> <device>/dev/vg01</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>osmflv</lv_name> <mount>/osmf</mount> <size>200MB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </install> </profile> And in y2log 2005-10-13 21:21:16 <1> linux(3737) [agent-curl] CurlAgent.cc(Execute):210 Output: /tmp/YaST2-03737-IAsUEr/rules/container.xml 2005-10-13 21:21:21 <1> linux(3737) [YCP] AutoInstallRules.ycp:722 Working on file: container.xml 2005-10-13 21:21:21 <1> linux(3737) [YCP] XML.ycp:113 Reading /tmp/YaST2-03737-IAsUEr/rules/container.xml 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:2: 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 I/O 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 warning : 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 failed to load HTTP resource 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:21: 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 parser 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 error : 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 Opening and ending tag mismatch: partitioning line 5 and install 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 </install> 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:22: 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 parser 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 error : 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 Opening and ending tag mismatch: install line 4 and profile 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 </profile> 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:23: 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 parser 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 error : 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 Premature end of data in tag profile line 3 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 could not load http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml, and no fallback was found 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/content.xml:2: 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 I/O 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 warning : 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 failed to load HTTP resource 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> 2005-10-13 21:21:21 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:21 <3> linux(3737) [Interpreter] XML.ycp:114 Failed while processing XIncludes 2005-10-13 21:21:21 <3> linux(3737) [Interpreter] XML.ycp:114 SCR::Read() failed 2005-10-13 21:21:21 <3> linux(3737) [Interpreter] XML.ycp:81 Argument (contents) to Execute(...) is nil 2005-10-13 21:21:21 <3> linux(3737) [YCP] AutoInstallRules.ycp:727 Error reading XML file 2005-10-13 21:21:21 <3> linux(3737) [bash] ShellCommand.cc(shellcommand):73 cp: cannot stat `/tmp/YaST2-03737-IAsUEr/base_profile.xml': No such file or directory 2005-10-13 21:21:21 <1> linux(3737) [YCP] AutoInstallRules.ycp:756 Ok=true 2005-10-13 21:21:21 <2> linux(3737) [YCP] XML.ycp:120 XML file /tmp/YaST2-03737-IAsUEr/rules/prefinal_autoinst.xml (-1) not found 2005-10-13 21:21:21 <1> linux(3737) [YCP] Profile.ycp:98 importing profile 2005-10-13 21:21:21 <1> linux(3737) [YCP] Profile.ycp:80 Can't detect Profile Version 2005-10-13 21:21:21 <1> linux(3737) [YCP] AutoInstallRules.ycp:788 Checking classes... 2005-10-13 21:21:21 <3> linux(3737) [bash] ShellCommand.cc(shellcommand):73 cp: cannot stat `/tmp/YaST2-03737-IAsUEr/rules/prefinal_autoinst.xml': No such file or directory 2005-10-13 21:21:21 <1> linux(3737) [YCP] AutoInstallRules.ycp:823 returns=true 2005-10-13 21:21:21 <1> linux(3737) [YCP] ProfileLocation.ycp:143 rulesret=true 2005-10-13 21:21:22 <1> linux(3737) [YCP] XML.ycp:113 Reading /tmp/YaST2-03737-IAsUEr/autoinst.xml 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:2: 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 I/O 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 warning : 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 failed to load HTTP resource 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:21: 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 parser 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 error : 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 Opening and ending tag mismatch: partitioning line 5 and install 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 </install> 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:22: 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 parser 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 error : 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 Opening and ending tag mismatch: install line 4 and profile 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 </profile> 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml:23: 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 parser 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 error : 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 Premature end of data in tag profile line 3 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 could not load http://10.26.248.155/SLES9CONTROL/sles9sp2/osmf.xml, and no fallback was found 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 http://10.26.248.155/SLES9CONTROL/sles9sp2/content.xml:2: 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 I/O 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 warning : 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 failed to load HTTP resource 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> 2005-10-13 21:21:22 <3> linux(3737) [agent-xml] XmlAgent.cc(xmlagentError):678 ^ 2005-10-13 21:21:22 <3> linux(3737) [Interpreter] XML.ycp:114 Failed while processing XIncludes 2005-10-13 21:21:22 <3> linux(3737) [Interpreter] XML.ycp:114 SCR::Read() failed

2 1

Question on AutoYast and multiple nic cards on SLES9
by Jeff Christensen 13 Oct '05

13 Oct '05

Hi, I have a DL-380 that has four nic cards in it. I want to be able to setup AutoYast so that it assigns one ip to eth1 and one to eth2, skipping eth0. When I try to set this up I am assigning the mac address of the card as follows: <bootproto>dhcp</bootproto> <device>eth‑ id‑ 00:10:18:0c:5e:db</device> However, it still assigns a ip to eth0, and then one to eth1. I am using pxe for installs and want to reserver the eth0 interface for the pxe network boot. This DL-380 has 2 nics built-in and then 2 nics that I have added to it, Thank you for your suggestions and please let me know if you need more, Jeff Christensen

1 0

Is it possible to start an AutoYast installation from a diskless booted system?
by Joe Landman 11 Oct '05

11 Oct '05

Hi folks: For a number of reasons, I need to look into whether or not we can set up a system to boot into diskless mode, and while operating there, start the autoyast installation onto the hardware. Is this possible? Or does autoyast only work when you specify the autoyast=/path/to/xml/file on the boot command line? Thanks. Joe -- Joe Landman email: landman(a)scalableinformatics.com web : http://www.scalableinformatics.com

2 1

Bei Installation nach Partitionen fragen
by Boris "BXS" Schulz 10 Oct '05

10 Oct '05

Hi, wie schaffe ich es, daß mich Autoyast (suse9.2) bei der Installation nach meiner gewünschten Aufteilung der Festplatten und Partitionen fragt? Ich habe bisher nur herausbekommen, wie man die Partitionen fest in das autoinst.xml eintragen kann, was mir nicht weiterhilft. Leider scheint es die Hilfeseite von Nashif nicht mehr zu geben, daher würde ich mich umso mehr über eine Antwort freuen. mfg, B.S.

2 1

Novell stole my documentation! (or, "how do I use the 'custom' rule type?")
by Marlier, Ian 10 Oct '05

10 Oct '05

Okay, so I went to go read up on rules documentation, and discovered that http://yast.suse.com/ now redirects to http://forge.novell.com/modules/xfmod/project/?yast. And that I need to sign up for an account to actually read any of the docs there. And they seem to be SLES-specific, and I'm autoyast'ing SuSE Pro 9.3 machines. Sigh. In any case: I've got about 8 different distinct types of machines. Different disk configs, different uses and thus different package selections, and so on. I'd like to set up a custom rule that matches based on the DHCP-assigned hostname and/or the last octet of the IP address (ie, database machines are in the .12X range of the subnet, and have hostnames like "database-4". I want the rules file to give them a particular config by matching either the ".12" or the "database-"). Looking at the most recent docs that I have available (boo!), Rev. 1.1.6.4 from June 11, 2004, it looks like I'm going to have to resort to a custom rule. But there's no hint of how to put together a custom rule in the aforementioned doc. So, yeah -- my question (there had to be one here somewhere....): Does anyone have either of - A location for more recent docs that explain how to set up a custom rule; or - an example of using a custom rule that I might be able to look over? Thanks! - Ian

2 1

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Hans-Joachim Ehlers 10 Oct '05

10 Oct '05

>>> Ajay Mulwani <ajaymulwani(a)gmail.com> 10/10/05 09:00 >>> > Now I am also looking for detailed info on rules and classes. Could you >please point me to the latest document for autoinstall. Google resulted this >this link www.suse.de/~nashif/autoinstall/<http://www.suse.de/~nashif/autoinstall/>. >However > it looks the link is missing the required doc. Any alternate location !! >From there you should be able to go to: http://forgeftp.novell.com/yast/doc/SLES9/autoinstall/9.1/html/index.html I do not know any further online docu. But about rules and classes: The point is: 1) a so called class file is just a simple extract from a full installation ( control.xml, autoinstall.xml ) file. 2) the rules.xml will decide which files will be merged. Only the matched files will be merged, meaning NO default installation.xml file will be used by default. If you look at my example you see that the last rule will match everytime. So a ' standard ' XML file will be used/merged for every host. 3) All matched files will be merged to a large control.xml file which will be used for installation. The rest is just a place where the stuff will be. ./rules # Place/directory where the rules.xml file must be. ./classes # Just a directory where you place all your XML files. Keep in mind that if you use rules you must not supply a filename to autoyast ! Only the starting directory is allowed ( So the autoyast call must end with a slash ) Example: autoyast=nfs://server/suse9.3/ And below suse9.3 you have: ./rules/rules.xml ./classes/ ./largemem.xml ./lowmem.xml ./standard.xml hth Hajo

1 0

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Ajay Mulwani 10 Oct '05

10 Oct '05

Thanks Hans. I am yet to try this but it seems this is certainly useful for me. Now I am also looking for detailed info on rules and classes. Could you please point me to the latest document for autoinstall. Google resulted this this link www.suse.de/~nashif/autoinstall/<http://www.suse.de/~nashif/autoinstall/>. However it looks the link is missing the required doc. Any alternate location !! Thanks again. Ajay

1 0

Autoyast 'xmlns' and 'xmlns:config' values
by Mitko Haralanov 10 Oct '05

10 Oct '05

Hi, I have been having problem with autoyast very early in the installation process without any error messages showing up and I was trying to check the XML file. While the XML file looks correct, the values for the 'xmlns' and 'xmlns:config' attributes of the <profile> tag don't seem right. If I try to go to http://www.suse.com/1.0/ or http://www.suse.com/1.0/yast2ns with my browser I get 'Error 404: Object Not Found' errors. Has the URL for those files changed? What should be the values for the two attributes? -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== Let the machine do the dirty work. -- "Elements of Programming Style", Kernighan and Ritchie

2 5

TFTP / PXE simple, but I can not get it to work
by HG 08 Oct '05

08 Oct '05

Hello! I've just downloaded the ISO for 10.0. Now I tried to set it up to a laptop with PXE. The server is SuSE 9.3. I did this on the server: 1) mount the iso with: mount SUSE-10.0-EvalDVD-i386-GM.iso -o loop -t iso9660 /tftpboot 2) Open YaST2 + Network Services + TFTP server 3) There select enable (Firewall is disabled) and set boot image directory to /tftpboot/ 4) Select Finish Then I go to the laptop. Select PXE boot. Then it scans for the DHCP for a while, but then doesn't find any boot image (and continues to boot with the old OS). I have previously booted the server with Knoppix and selected the PXE server systems from Knoppix (I do not remember what it was called). That worked and the laptop booted into knoppix. Why can't I do the same with SuSE 9.3? What am I doing wrong? -- HG.

1 0

upgrade with autoyast
by detlef oertel 08 Oct '05

08 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, sorry if I missed something, but I found no documentation about automatic client upgrade with autoyast (e.g. 9.3 -> 10.0). Is this possible ? Is there any HowTo or documentation ? thanks a lot detlef -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDR48PiHgljbcBEOYRAnxmAJ41FY4+s5K5pyMO3aaz+M7gJ40fAACgno87 VuwO7uICRCFnDYKuq7+qWC8= =0ekj -----END PGP SIGNATURE-----

1 0

Re: [suse-autoinstall] Disk partitioning with pre script !!
by Hans-Joachim Ehlers 07 Oct '05

07 Oct '05

Use a rules.xml and remove Partitioning from the autoinst.xml and create classes hth Hajo NOT TESTEST $ cat rules.xml <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ #!/bin/sh mem=$( cat /proc/meminfo | grep -i memtotal | awk '{ print $2 } ' } # Output is in kbytes echo -n $mem ]]> </script> <match>499999</match> <match_type>greater</match_type> </custom1> <result> <profile>classes/largeswap.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>500000</match> <match_type>lower</match_type> </custom1> <profile>classes/smallswap.xml</profile> <continue config:type="boolean">true</continue> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/autoinst.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall>

1 0

Disk partitioning with pre script !!
by Ajay Mulwani 07 Oct '05

07 Oct '05

Hello List, Could someone please suggets any process to partition the disk probably using pre scripts or any other method in SLES9. I have a requirement to create swap which should be either equal or twice the RAM. Thanks, Ajay

3 3

Re: [suse-autoinstall] Using an USB-HDD as bootable install-media
by Stefan Pfeiffer 05 Oct '05

05 Oct '05

Hi! Hans-Joachim Ehlers wrote: >>easily be used during the install, as the NForce-4-Onboard-LAN is not >>recognized bei SUSE 10.0 RC1 and must be installed manually after an > > You might use the insmod option in the ' info' file to use the correct network driver during installation I would need to brew that network driver (that has to be compiled for that specific kernel) into the driver floppy disk (or the PXE boot image), a task i would like to avoid. I do not really need network install, and i think it adds difficulties for no benefit. I would really prefer to have my own tailored bootable media that i plugin when i need to reinstall the machine, if possible. That must be possible, i guess. > hth > Hajo Regards, Stefan -- # Dipl.-Phys. Stefan Pfeiffer # Abteilung Modellierung und Simulation # Fraunhofer Institut f. Lasertechnik # Steinbachstr. 15, D-52074 Aachen, Germany. # Tel: + 49 (241) 8906 153 , Fax: +49 (241) 8906 121 # EMail: pfeiffer(a)ilt.fhg.de, WWW: http://www.ilt.fhg.de/nld/

1 0

Including files
by Darío Mariani 05 Oct '05

05 Oct '05

Hello: I have an autoyast profile that looks like this: <?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> <firewall> <start_firewall config:type="boolean">false</start_firewall> </firewall> ... This profile woks perfect. Now I try the following (as sugested by http://www.suse.de/~nashif/autoinstallation/faq.html#id2460912): <?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> <xinclude:include href="http://path/to/firewall.xml" /> ... and firewall.xml looks like this: <firewall> <start_firewall config:type="boolean">false</start_firewall> </firewall> and this does not work. Any idea on what could be wrong?, I already verified that the included file is accesible. Thanks for any help, Darío PD: Is there any (nearly) complete documentation on autoyast? As the documentation found in the Novell site is quite incomplete.

2 1

Re: [suse-autoinstall] Using an USB-HDD as bootable install-media
by Hans-Joachim Ehlers 04 Oct '05

04 Oct '05

>easily be used during the install, as the NForce-4-Onboard-LAN is not >recognized bei SUSE 10.0 RC1 and must be installed manually after an You might use the insmod option in the ' info' file to use the correct network driver during installation hth Hajo

1 0

Using an USB-HDD as bootable install-media
by Stefan Pfeiffer 04 Oct '05

04 Oct '05

Hi! I need to autoinstall SUSE (10.0 as soon as it becomes available) using an USB-HDD instead of a DVD or CD-ROMs. How can i use that HDD instead of a boot CD as installation medium? The easy part will be to copy the CD-ROMs to that drive, and put installation scripts (xml and post-install-scripts) on that drive, too. How do i make that HDD bootable like a CD-ROM? Any hints on how to proceed are very welcome. I would like to have the machine automatically (without user interaction) installed when the USB HDD drive is plugged in. The machines have no CD-ROM-drive, and the ethernet connection cannot easily be used during the install, as the NForce-4-Onboard-LAN is not recognized bei SUSE 10.0 RC1 and must be installed manually after an installation from CD-ROM. Regards, Stefan -- # Dipl.-Phys. Stefan Pfeiffer # Abteilung Modellierung und Simulation # Fraunhofer Institut f. Lasertechnik # Steinbachstr. 15, D-52074 Aachen, Germany. # Tel: + 49 (241) 8906 153 , Fax: +49 (241) 8906 121 # EMail: pfeiffer(a)ilt.fhg.de, WWW: http://www.ilt.fhg.de/nld/

1 0

workaround for a problem loading SuSE 9.3 pro on a Sun v20z
by Joe Landman 03 Oct '05

03 Oct '05

Hi folks: We worked around an immediate hard kernel panic attempting to load SuSE 9.3 Pro on a small v20z unit using autoyast by the following method (note: this is not likely to be supported by SuSE, and they may actively discourage it) 1) download OpenSuSE-10 RC-1 2) copy the binary linux and initrd to your servers /tftpboot directory (where ever you serve your pxe from) 3) change your pxelinux.cfg/default (or similar file) to use this kernel and initrd rather than the ones you might be using now. I also set textmode=1 4) restart xinetd if you run tftpd through it (or simply restart your tftpd daemon) 5) boot and install I am not sure why SuSE 9.3 Pro immediately kernel panics on a v20z boot. Not sure if it is worth fixing if this method works. Joe -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics LLC, email: landman(a)scalableinformatics.com web : http://www.scalableinformatics.com phone: +1 734 786 8423 fax : +1 734 786 8452 cell : +1 734 612 4615

1 0