December 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

Problem with AutoInstallRules.ycp and merge.xslt
by Luzian Scherrer 16 Mar '06

16 Mar '06

Hello, I think there is a typo in AutoInstallRules.ycp (version 1.34.4.9 that comes with SLES9 SP2): the xsltproc to merge classes is called with the following param there (line 733): --param dontmerge \"'package, addon'\" and I'm quite sure that it sould be: --param dontmerge \"'package'\" --param dontmerge2 \"'addon'\" The result of this typo is that neither <package> nor <addon> are correctly aggregated, which is the desired effect I believe and I also hope. Quick demonstration: idhpb02:/ # cat /tmp/a.xml <?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"> <install> <software> <addons config:type="list"> <addon>addon-A</addon> </addons> <packages config:type="list"> <package>package-A</package> </packages> </software> </install> </profile> idhpb02:/ # cat /tmp/b.xml <?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"> <install> <software> <addons config:type="list"> <addon>addon-B</addon> </addons> <packages config:type="list"> <package>package-B</package> </packages> </software> </install> </profile> Calling it the wrong way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package, addon'" --param with "'/tmp/b.xml'" /usr/share/ autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-B</ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Calling it the (as I think) right way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package'" --param dontmerge2 "'addon'" --param with "'/ tmp/b.xml'" /usr/share/autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-A</ns1:addon><ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-A</ns1:package><ns1:package>package-B</ ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Could this be fixed? Or is it already known and possibly a workaround in existance? Thanks in advance, -Luzian

4 6

Module cd creator
by Rodrigo_Albert_Fedosi 02 Jan '06

02 Jan '06

It is possible install the Yast module "cd creator" of the Suse enterprise server in the Suse professional. If it will go as I do? Att. Rodrigo Albert Fedosi Suporte TI Tel: (31) 3419-8854 Fax: (31) 3419-8803 rodrigo(a)bhz.jamef.com.br www.jamef.com.br

2 1

Updating drivers and dealing with patches in AutoYast
by aquajtk-suse＠yahoo.com 02 Jan '06

02 Jan '06

Hello, I'm having 3 questions : 1. I've tried to install SLES9 SP2 on an IBM x306 however i was having problems with the installation cuz it did not recognize the raid controller and it showed both physical drives instead of the logical drive. I had to manually install this server using a driver update disk. Needless to say, but i also want to automatically deploy SLES9 SP2 on this server. I've checkout this document : http://mirror.mcs.anl.gov/suse-people/hvogel/Update-Media-HOWTO/Update-Medi… It states that i will need to put a file 'driverupdate' in the root of my repository. (I assume that's the driver update disk image i can download from IBM's support site). How can i use several update disks if they all should be named 'driverupdate'? 2. Say I have an http repository which contains the installation sources for SLES9 SP2. One day Novell releases a critical security patch and I'd like to integrate this patch in my repository so i don't need to install these patches after installing a server. Is there a way to do this (besides doing this with post-install scripts that just run rpm-commands)? Replacing the package in the repository won't work i think, cuz (if i'm not wrong) there is a list of packages on the install sources. 3. Currently i'm using a file in pxelinux.cfg which contains references to the kernel- and initrdimage and also the linuxrc command line parameters. AutoYasts documentation mentiones an info file that contains these parameters. Where do i place such an info file? Can i combine the info file and the command line parameters? eg i could put all parameters that are not unique for a given server in the info file and then put the server specific option in the file in pxelinux.cfg. Thanks a lot! Johan

2 1

Possible bug with LVM and <size>max</size>
by Luzian Scherrer 02 Jan '06

02 Jan '06

Hello, The size-part of this controlfile-section doesn't work with SuSE 10.0 AutoYaST: <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <size>max</size> </partition> However, when I change 'max' to an absolute size (like '4096MB') it works. Defining the size as 'max' did work with SLES 9 SP2 AutoYaST. Is this a feature? ;) PS: Is this mailing-list the correct place to submit AutoYaST bugs or is there a bug-tracking system? Thanks, -Luzian

2 1

How can I use a320raid instead of aic79xx after autoyast-installation
by ? 27 Dec '05

27 Dec '05

I'm trying to install SLES9 SP2 x86_64 on an IBM x346 machine(HostRAID is enabled, in this mode, system should use a320raid) via autoyast, but every time system uses aic79xx instead of a320raid after installation. I've added following section into autoyast config file: <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>INITRD_MODULES</sysconfig_key> <sysconfig_path>kernel</sysconfig_path> <sysconfig_value>reiserfs a320raid</sysconfig_value> </sysconfig_entry> </sysconfig> and <initrd_modules config:type="list"> <module>a320raid</module> </initrd_modules> The entry "INITRD_MODULES" in /etc/sysconfig/kernel have been created correctly by above sections after installation: ... # INITRD_MODULES="reiserfs a320raid" ... But system still used aic79xx: c79l1ms01:/etc/sysconfig # lsmod Module Size Used by floppy 73296 0 ipv6 317432 12 freq_table 13952 0 af_packet 33676 0 joydev 19584 0 sg 51128 0 st 51236 0 sr_mod 26788 0 tg3 96004 0 hw_random 14504 0 ehci_hcd 39300 0 uhci_hcd 41376 0 evdev 19072 0 usbcore 132984 4 ehci_hcd,uhci_hcd subfs 17664 2 dm_mod 69344 0 reiserfs 264688 1 aic79xx 267032 2 sd_mod 30208 3 scsi_mod 144000 5 sg,st,sr_mod,aic79xx,sd_mod I added a chroot script to create an initrd: ... sed -i 's/INITRD_MODULES.*/INITRD_MODULES=\"a320raid reiserfs\"/' /etc/sysconfig/kernel mkinitrd ... But after installation, system still used aic79xx, though a320raid has been loaded in: c79l1ms01:/etc/sysconfig # lsmod ... a320raid 377656 0 reiserfs 264688 1 aic79xx 267032 2 sd_mod 30208 3 scsi_mod 144000 6 sg,st,sr_mod,a320raid,aic79xx,sd_mod Actually, I think the initrd in /boot was created as I wished, but it seems system did not use this ramdisk at the first time system booted. And after I rebooted machine again, a320raid was loaded correctly: c79l1ms01:/etc/sysconfig # lsmod ... a320raid 377656 2 reiserfs 264688 1 sd_mod 30208 3 scsi_mod 144000 6 sg,st,sr_mod,a320raid,sd_mod Does anyone know which initrd system uses at the first time system boots? And how can I let system use a320raid at the first boot? _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

1 0

RE: [suse-autoinstall] merging autoyast and yast2
by Schumacher, Gordon 22 Dec '05

22 Dec '05

# From: Jordi Massaguer Pla [mailto:jordi.massaguer@opentrends.net] # Sent: Thursday, December 22, 2005 4:46 AM # To: suse-autoinstall(a)suse.com # Subject: [suse-autoinstall] merging autoyast and yast2 # # Hi! # I would like to install a system with some defaults, like the user # management, but let the user select some other stuff, like the software. # # How could this be achieved? There is a "confirm" option which lets the user confirm that everything is the way they want it before the installation proceeds. The XML looks like this: <mode> <confirm config:type="boolean">true</confirm> </mode> I forget where that is in the autoyast module though. If this is set to true, the user can change things. Be it noted that bad things will happen if the user changes the partitioning without also changing the GRUB config to match, and such things.

1 0

merging autoyast and yast2
by Jordi Massaguer Pla 22 Dec '05

22 Dec '05

Hi! I would like to install a system with some defaults, like the user management, but let the user select some other stuff, like the software. How could this be achieved? I tried writing the users section of the autoinst.xml into the control.xml in a custom CD, but seemed not to work at all. Any idea will be very welcome, thanks, jordi

1 0

Adding a custom package to auto-install / IP/DNS info
by Sean.Gilley＠huntington.com 14 Dec '05

14 Dec '05

I'm having trouble finding the answers I need. After doing a lot of searching I still can't quite figure out what needs to be done. Here's my situation. I have a box installed as an SLES 9 load server. I let yast copy the CDs, and yast places each CD into a different directory under the main directory. My goal is to be able to insert a CD in a machine, give it an IP address and gateway information, then walk away and have everything installed automatically. I've got it partially working. I've created a load file which works just fine to load the exact packages from the SLES distribution; now I need to be able to load one or more additional, customized packages that I've created. Can anyone point me a document that leads me, step by step, through the process to do this? The only things I've been able to find are difficult to follow and not always applicable because they aren't for SLES distributions. The other issue is that though it installs using the IP and GW I typed in, it doesn't keep the IP/GW and use them for the installed machine's IP and GW. Can anyone tell me what I need to do to pass the IP/GW info on through the install process? Oh, and finally, as a bit of extra icing on my cake, I'd like to change some of the function key text and functions and haven't been able to find that anywhere on the disk. Can someone point me to where that is or how it can be changed? Thanks, Sean. -- Sean L. Gilley IS Technical Specialist Huntington National Bank 614-331-9468, 614-374-7573 (mobile) sean.gilley(a)huntington.com

2 1

pre-script + /tmp/profile/modified.xml modification
by jaiber john 13 Dec '05

13 Dec '05

>From a recent thread I found that I can modify autoyast.xml in /tmp/profile through pre-script and save it as /tmp/profile/modified.xml so that autoyast re-reads the modified information (dynamically generated partition info). Will this technique work for SLES9 autoinstall? I found a reference to this only in the SLES10 autoinstall manual. Thanks!

3 6

[suse-autoinstall] configuring grub
by Thomas Holzapfel 12 Dec '05

12 Dec '05

Hi, I'm using autoyast to install SuSE 10.0 on a set of systems. I want to configure grub, which works fine using SuSE 9.3. I want to - set the boot loader location to the boot sector of my boot partition - activate the boot loader partition - set the boot menu timeout - set the vga mode - set the kernel parameters like resume and splash=verbose The corresponding part of my config file is <bootloader> <loader_type>grub</loader_type> <location>custom</location> <loader_device>/dev/sda1</loader_device> <activate config:type="boolean">true</activate> <repl_mbr config:type="boolean">false</repl_mbr> <global config:type="list"> <global_entry> <key>timeout</key> <value config:type="integer">5</value> </global_entry> </global> <sections config:type="list"> <section> <append>selinux=0 resume=/dev/sda8 splash=verbose showopts</append> <initial>1</initial> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>0</lines_cache_id> <name>SuSE Linux 10.0</name> <original_name>linux</original_name> <root>/dev/sda6</root> <type>image</type> <vga>794</vga> </section> ... </sections> </bootloader> I'm using the following directive to check the result of my config file <mode> <confirm config:type="boolean">true</confirm> </mode> Autoyast ignores the directives <location> and <loader_device>, instead MBR is selected as the boot loader location. The timeout setting in the global section is also ignored. I think all global settings are ignored. At last, in the section settings the directive <vga>794</vga> is set to blank and the splash=verbose option is replaced by splash=silent! Only activating the boot loader partition is set right. Any ideas, what's going wrong? Thanks, -- Thomas Holzapfel Lehrstuhl und Institut fuer Wasserbau und Wasserwirtschaft RWTH Aachen

2 1

Failure to auto-install 9.3/10.0 using same XML file....
by UNIX-admin 12 Dec '05

12 Dec '05

Hi everyone, I've been having one of those days, and I would like to know if anyone else has seen the same problems I have been experiencing... I have a Linux server running 9.2, serving installation sources via http for SuSE 9.2, 9.3, and 10. Using a 9.2 DVD, I can quite happily install a new system over the network using the following (IPs changed to protect the not-so-innocent, 10.20.30.59 is serving the sources via Apache): initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.2 autoyast=http://10.20.30.59:/conf/infra.xml However, if I use *EXACTLY* the same xml configuration file but this time using a 9.3 DVD... initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.3 autoyast=http://10.20.30.59:/conf/infra.xml it fails (as far as I can make out) with an "out of swap space" error. I of course then tried increasing swap, but received the same error, albeit I think a bit further along than before. Its hard to say for sure because it still fails installing the kernel source rpm, just not at the exact same point. Swap is now twice the size of core memory. I then tried (again using *EXACTLY* the same xml file) to install 10: initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/10.0 autoyast=http://10.20.30.59:/conf/infra.xml It got further, but the system appeared to completely hang about 25 seconds from completing the package install. I was unable to get any response at all. The hardware is a brand-new DL380-G4 with 2Gb RAM. The 9.2 installation source server has not been patched to the absolute latest (but why would this matter - I'm only using it to share the installation media, right?). I should also point out I suffer from the old problem with the network timeout due to spanning tree on the switches (don't think it has any bearing on the issue though). The DVDs are straight out of the box, and are the professional versions. The xml config file is nothing fancy - just sets up the partitioning, defines package selection, and runs a post-install script. I searched the net, and trawled through the archives (oh for a search facility ;-) ), but I couldn't find anything. Could someone please point me in the right direction? Thanks! Colin.

4 5

[suse-autoinstall] keeping partitions
by Thomas Holzapfel 12 Dec '05

12 Dec '05

Hi, I'm using autoyast to install SuSE 10.0 on a set of systems. Keeping partitions seems to be a problem. The partitiontable looks like Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 4 32098+ 83 Linux /dev/sda2 5 1279 10241437+ 7 HPFS/NTFS /dev/sda3 1280 2554 10241437+ 7 HPFS/NTFS /dev/sda4 2555 14593 96703267+ f W95 Ext'd (LBA) /dev/sda5 2555 2558 32098+ 83 Linux /dev/sda6 2559 3323 6144831 83 Linux /dev/sda7 3324 4088 6144831 83 Linux /dev/sda8 4089 4216 1028128+ 82 Linux swap /dev/sda9 4217 8041 30724281 83 Linux /dev/sda10 8042 13141 40965718+ 7 HPFS/NTFS /dev/sda11 13142 14593 11663158+ c W95 FAT32 (LBA) What I want to do is to keep all the partitions, just to format the boot- and root- partition of the new system (/dev/sda1 , /dev/sda6) and to set some mount points. In a first attempt the relevant part of my config file was <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext2</filesystem> <partition_nr config:type="integer">1</partition_nr> <mount>/boot</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">ext2</filesystem> <partition_nr config:type="integer">5</partition_nr> <mount>/export/suse/9.3/boot</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <partition_nr config:type="integer">6</partition_nr> <mount>/</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">reiser</filesystem> <partition_nr config:type="integer">7</partition_nr> <mount>/export/suse/9.3/root</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">reiser</filesystem> <partition_nr config:type="integer">9</partition_nr> <mount>/local</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">fat</filesystem> <partition_nr config:type="integer">11</partition_nr> <mount>/transfer</mount> </partition> </partitions> </drive> </partitioning> In the "Create partition plans" stage I got the error message "Error while configuring partitions. Try again." After a series of try and error, nearly all works fine with the following modifications in the config file: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext2</filesystem> <partition_nr config:type="integer">1</partition_nr> <mount>/boot</mount> </partition> ...  ... </partitions> </drive> <use>1</use> </partitioning> Using the directive above to set the mount point of partition nr 5 results in the same error message "Error while configuring partitions. Try again." Any ideas to fix that problem rather than setting the mount point manually? Is it possible to prevent autoyast from setting the mount points to ntfs-partitions? -- thanks, Thomas Holzapfel Institut fuer Wasserbau und Wasserwirtschaft RWTH Aachen

3 5

32-bit binaries on 64-bit machines
by Thorbjörn Jemander 09 Dec '05

09 Dec '05

Hello, some time ago I found a message on this list that explained how to disable the 64-bit check in the early start-up process. However, no matter how I look now, I can't find it. So, how do I force the 32-bit binares to be installed, despite that I install on a 64-bit machine? (automacically) Thanks in advance, ________________________________________________ Dr. Thorbjörn Jemander, Senior RT/Systems Expert Enea Epact AB, Teknikringen 8, Linköping, Sweden thje(a)enea.se +46 13 465 58 67 www.enea.com

1 1

where to store the config?
by fisch 07 Dec '05

07 Dec '05

Hi, I have a problem, I have to make an autoyast install (SuSE 10.0) for clients that do not have floppy, cd and network. I only have an external USB-DVD and an USB-stick. I tried to store the autoyast.xml on the USB-stick but Yast can not access it. I am confused because of the situation: /dev/sda -> SATA harddisk /dev/sdb -> USB-Stick I give the bootoption: autoyast=/dev/sdb1/autoyast.xml Yast shows the error: Can't find /dev/sdb1/autoyast.xml when I change into tty I am able to mount /dev/sdb1 and can access the autoyast.xml what's going wrong? Is it possible to "remaster" the install-dvd and store the autoyast.xml there? bye fisch

2 1

RE: [suse-autoinstall] Failure to auto-install 9.3/10.0 usingsame XML file....
by Yan Fitterer 07 Dec '05

07 Dec '05

> Or are you saying what I need to do is generate xml config files for > each distribution and then use rules to select the appropriate ones > (implying that the config files generated are different in some way > between each distribution)? Yes. You can avoid duplication of identical elements by using classes (if you feel fancy). Yan

1 0

Re: [suse-autoinstall] Failure to auto-install 9.3/10.0 using same XML file....
by Yan Fitterer 07 Dec '05

07 Dec '05

Using rules, it is possible to have a single "install system" (i.e. a set of xml config files) that works for different versions with different configs. As a starting point, you should look at: http://www.suse.de/~ug/autoyast_doc/rulesandclass.html Hint: create a rule that detects the OS version being installed (see installed_product and/or installed_product_version attributes), and select a profile based on that.

1 0

Re: [suse-autoinstall] Failure to auto-install 9.3/10.0 using same XML file....
by Hans-Joachim Ehlers 07 Dec '05

07 Dec '05

Hi, i had a similar problem with Suse 9.3 and installation via http. For a minimum installation via http i needed 2 GB of swap space so depending on your software selection it might be much more. For testing i would do one of the following - increase swap to 8GB - use an NFS installation I think in the docu is also something mentioned about copy the software first to the disk before installing it. hth Hajo >>> UNIX-admin <UNIX-admin(a)m151.uklinux.net> 06/12/05 22:13 >>> Hi everyone, I've been having one of those days, and I would like to know if anyone else has seen the same problems I have been experiencing... I have a Linux server running 9.2, serving installation sources via http for SuSE 9.2, 9.3, and 10. Using a 9.2 DVD, I can quite happily install a new system over the network using the following (IPs changed to protect the not-so-innocent, 10.20.30.59 is serving the sources via Apache): initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.2 autoyast=http://10.20.30.59:/conf/infra.xml However, if I use *EXACTLY* the same xml configuration file but this time using a 9.3 DVD... initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/9.3 autoyast=http://10.20.30.59:/conf/infra.xml it fails (as far as I can make out) with an "out of swap space" error. I of course then tried increasing swap, but received the same error, albeit I think a bit further along than before. Its hard to say for sure because it still fails installing the kernel source rpm, just not at the exact same point. Swap is now twice the size of core memory. I then tried (again using *EXACTLY* the same xml file) to install 10: initrd netdevice=eth0 hostip=10.20.30.40 netmask=255.255.255.0 gateway=10.20.30.1 install=http://10.20.30.59:/10.0 autoyast=http://10.20.30.59:/conf/infra.xml It got further, but the system appeared to completely hang about 25 seconds from completing the package install. I was unable to get any response at all. The hardware is a brand-new DL380-G4 with 2Gb RAM. The 9.2 installation source server has not been patched to the absolute latest (but why would this matter - I'm only using it to share the installation media, right?). I should also point out I suffer from the old problem with the network timeout due to spanning tree on the switches (don't think it has any bearing on the issue though). The DVDs are straight out of the box, and are the professional versions. The xml config file is nothing fancy - just sets up the partitioning, defines package selection, and runs a post-install script. I searched the net, and trawled through the archives (oh for a search facility ;-) ), but I couldn't find anything. Could someone please point me in the right direction? Thanks! Colin. -- 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] documentation of XML control file anywher e?
by Gunreben, Peter (Peter) 06 Dec '05

06 Dec '05

Paul, > From: Paul Beltrani > On 12/5/05, Gunreben, Peter (Peter) <pgunreben(a)lucent.com> wrote: > > [...] > > > Is there some place where I can find the exact details of all > > > the tags and attributes used by the autoyast xml control file? > > > > http://www.suse.de/~ug/ > ... > > Perhaps I've missed something. Where at that site is a list of the > resources/properties that may be specified in the control file? There's not really a list, but you can find the resources in the chapters 4-6 in: http://www.suse.de/~ug/autoyast_doc/index.html However, a complete list of xml tags would be a good idea. Uwe? Peter.

2 1

Partitioning problems doing RAID + LVM on SL 10.0
by Gavin Carr 06 Dec '05

06 Dec '05

Hi, I'm having all kinds of problems trying to get a RAID1 + LVM partitioning scheme working on SL10.0. I'm wanting this: /dev/sda: swap auto raid1a 100MB raid2a 100MB raid3a 100MB raid4a max /dev/sdb: swap auto raid1b 100MB raid2b 100MB raid3b 100MB raid4b max RAID: md0: raid1a + raid1b, /boot md1: raid2a + raid2b, /boot2 md2: raid3a + raid3b, /boot3 md3: raid4a + raid4b, LVM physical volume LVM: volume group /dev/system: /dev/md3 logical volumes: / ext3 5GB /data ext3 200GB i.e. an LVM physical volume on a RAID1 partition. The partitioning fragment of my autoyast config looks like this: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">0</partition_nr> <mount>/boot</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <mount>/boot2</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <mount>/boot3</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>system</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root1</lv_name> <mount>/</mount> <size>5gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>data</lv_name> <mount>/data</mount> <size>200gb</size> </partition> </partitions> <pesize>32M</pesize> <use>all</use> </drive> </partitioning> This validates against the DTDs with xmllint, and it _almost_ works under autoyast. Here's the Partitioning confirmation output: Create extended partition /dev/sda1 (232.8 GB) Create swap partition /dev/sda5 (1.0 GB) Create partition /dev/sda6 (101.9 MB) with id=8E Create partition /dev/sda7 (101.9 MB) with id=8E Create partition /dev/sda8 (101.9 MB) with id=8E Create partition /dev/sda9 (231.5 GB) with id=8E Create extended partition /dev/sdb1 (232.8 GB) Create swap partition /dev/sdb5 (1.0 GB) Create partition /dev/sdb6 (101.9 MB) with id=FD Create partition /dev/sdb7 (101.9 MB) with id=FD Create partition /dev/sdb8 (101.9 MB) with id=FD Create partition /dev/sdb9 (231.5 GB) with id=FD Create software RAID /dev/md0 (101.9 MB) for /boot with ext3 Create software RAID /dev/md1 (101.9 MB) for /boot2 with ext3 Create software RAID /dev/md2 (101.9 MB) for /boot3 with ext3 Create software RAID /dev/md3 (231.5 GB) Create volume group system Create logical volume /dev/system/data (200.0 GB) for /data with ext3 Create logical volume /dev/system/root1 (5.0 GB) for / with ext3 The problem is that somehow it comes up with the wrong partition type /dev/sda[6-9] partitions, making them LVM partitions (8E) instead of RAID partitions (FD), it's added all the /dev/sda partitions to the /dev/system volume group, and the raid partitions only contain the /dev/sdb members, and so raid volume creation fails. Does this look like an error in my config somewhere, or a bug? If I correct these problems by hand, everything works. In addition, if I try and initialise the drives I get even more bizarre problems - the /dev/sda partitions disappear altogther. I've been deleting the partition tables by hand to get it this far. This is x86_64 on sata drives, in case that matters. Thanks a lot for any clues/ideas. Been banging my head against this for a day and a half now ... Cheers, Gavin

3 3

RE: [suse-autoinstall] documentation of XML control file anywher e?
by Gunreben, Peter (Peter) 05 Dec '05

05 Dec '05

Christian > From: Christian Goetze > Sent: Freitag, 2. Dezember 2005 19:52 [...] > Is there some place where I can find the exact details of all > the tags and attributes used by the autoyast xml control file? http://www.suse.de/~ug/ Gruss, Peter.

2 1

Error -> Could not set base selection: default
by Shannon L. McMackin 05 Dec '05

05 Dec '05

I've been working on this all day and it's driving me crazy. I'm trying to run a PXE install and it gets to the point of parsing the xml file and then throws this error up when it gets to software configuration. I used yast2 instserver and yast2 autoyast to generate the install source and have been modifying the info file that I've placed in the initrd for different attempts. Here is my autoinst.xml > big-daddy:/tftpboot # more /var/lib/autoinstall/repository/autoinst.xml > <?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.c > om/1.0/configns"> > <configure> > <networking> > <dns> > <dhcp_hostname config:type="boolean">false</dhcp_hostname> > <dhcp_resolv config:type="boolean">false</dhcp_resolv> > </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>bcm5700</module> > <options></options> > </module_entry> > </modules> > <routing> > <ip_forward config:type="boolean">false</ip_forward> > </routing> > </networking> > <online_update> > <autoget config:type="boolean">false</autoget> > <enable_autoupdate config:type="boolean">false</enable_autoupdate> > <update_time> > <hour config:type="integer">-1</hour> > <minute config:type="integer">-1</minute> > </update_time> > </online_update> > <runlevel> > <default>3</default> > </runlevel> > </configure> > <install> > <bootloader> > <activate config:type="boolean">false</activate> > <global config:type="list"/> > <loader_device></loader_device> > <loader_type>grub</loader_type> > <location>mbr</location> > <repl_mbr config:type="boolean">false</repl_mbr> > <sections config:type="list"/> > </bootloader> > <general> > <clock> > <hwclock>localtime</hwclock> > <timezone>US/Eastern</timezone> > </clock> > <keyboard> > <keymap>english-us</keymap> > </keyboard> > <language>en_US</language> > <mode> > <confirm config:type="boolean">true</confirm> > <forceboot config:type="boolean">false</forceboot> > </mode> > <mouse> > <id>ignore</id> > </mouse> > </general> > <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> > <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>auto</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> > <loop_fs config:type="boolean">false</loop_fs> > <mount>/</mount> > <partition_id config:type="integer">131</partition_id> > <partition_type>primary</partition_type> > <size>max</size> > </partition> > </partitions> > <use>all</use> > </drive> > </partitioning> > <software> > <addons config:type="list"> > <addon>Base-System</addon> > <addon>Basis-Sound</addon> > <addon>Kde-Desktop</addon> > <addon>Linux-Tools</addon> > <addon>Print-Server</addon> > <addon>SuSE-Documentation</addon> > <addon>X11</addon> > <addon>YaST2</addon> > <addon>auth</addon> > </addons> > <base>default</base> > </software> > </install> > </profile> info file: > big-daddy:/tftpboot # more > /root/tempinitrd/info > Netdevice: eth0 > Server: 192.168.0.104 > Serverdir: nfs://192.168.0.104/home/SLES9/x86 > AutoYaST: file:///autoinst.xml > Install: nfs://192.168.0.104/home/SLES9/x86 > Textmode: 1 linuxrc.config: > big-daddy:/tftpboot # more /root/tempinitrd/linuxrc.config > KernelPCMCIA: 1 > UseUSBSCSI: 1 > Product: SUSE LINUX Enterprise Server 9 > UpdateDir: /linux/suse/i386-sles9 > MemLoadImage: 163840 > MinMemory: 256 > MemYaST: 64000 > MemYaSTText: 64000 If anyone has any ideas, please let me know... Shannon

2 2

RE: [suse-autoinstall] documentation of XML control file anywher e?
by Gunreben, Peter (Peter) 05 Dec '05

05 Dec '05

Hi, > From: fraser_bailey(a)agilent.com [...] >> In particular, I want to know why the X session manager comes up even >> though I have: >> >> <runlevel> >> <default>3</default> >> </runlevel> [...] > It's runlevels, not runlevel. The documentation is wrong. I've just asked Uwe Gransert from SuSE and he told me that <runlevel> is the correct tag. BTW, the autoyast also writes the <runlevel> tag into the xml-file. Regards, Peter.

1 0

RE: [suse-autoinstall] documentation of XML control file anywhere?
by fraser_bailey＠agilent.com 04 Dec '05

04 Dec '05

It's runlevels, not runlevel. The documentation is wrong. -----Original Message----- From: Christian Goetze [mailto:cg@sensage.com] Sent: Friday, December 02, 2005 6:52 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] documentation of XML control file anywhere? Is there some place where I can find the exact details of all the tags and attributes used by the autoyast xml control file? In particular, I want to know why the X session manager comes up even though I have: <runlevel> <default>3</default> </runlevel> Is "default" not strong enough? -- cg -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

documentation of XML control file anywhere?
by Christian Goetze 02 Dec '05

02 Dec '05

Is there some place where I can find the exact details of all the tags and attributes used by the autoyast xml control file? In particular, I want to know why the X session manager comes up even though I have: <runlevel> <default>3</default> </runlevel> Is "default" not strong enough? -- cg

1 0