August 2008 - openSUSE Autoinstall - openSUSE Mailing Lists

AW: [suse-autoinstall] auto install with service pack
by Martin.Linten＠rzf.fin-nrw.de 15 May '25

15 May '25

Hallo Anas, hallo list! I am trying to install sles8 with service pack 2 in an automated way. The kernel and the inird from the sp2-CD (chosen because of hardware support) are booted via pxe. When checking the software selection I always get a long list of dependency errors beginning with "aaa_skel not available..." and so on. Please help and tell me how I can do better! I suppose it has nothing to do with the /UnitedLinux-i386-1 directory, but maybe I am wrong... My nfs-exported directory for linuxrc looks like this: |--boot | `--loader |--content (file from sles8) |--media.1 (from sles8) |--sles8 | |--UnitedLinux | |--boot | |--docu | |--dosutils | |--media.1 | |--media.2 | |--media.3 | |--suse | `--yast |--sp2 | |--UnitedLinux | |--boot | |--docu | |--i386 | |--images | |--linux | `--media.1 `--yast |--ul |--instorder (file) `--order (file) I011-52:/autoinst/suse/sles8sp2/yast # cat order /sles8 /sles8 /sp2 /sp2 I011-52:/autoinst/suse/sles8sp2/yast # cat instorder # I want to prefer sp2 packages if possible /sp2 /sp2 /sles8 /sles8 Thanks a lot, Martin -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet am: Dienstag, 15. Juli 2003 09:39 An: Aaron McSorley Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] auto install with service pack Hi, It can be done in an automated way. For example, my nfs export for SLES8 i386 with SP2 looks like this: |-- SP2 | |-- UnitedLinux | |-- boot | |-- docu | |-- i386 | |-- images | |-- linux | `-- media.1 |-- SuSE-Linux-SLES-i386-8 | `-- CD1 | |-- boot | |-- docu | |-- media.1 | |-- suse | `-- yast |-- UnitedLinux-i386-1 | |-- CD1 | | |-- UnitedLinux | | |-- boot | | |-- docu | | |-- dosutils | | `-- media.1 | `-- CD2 | |-- UnitedLinux | |-- boot | `-- media.2 |-- boot | `-- loader |-- media.1 `-- yast `-- ul in the directory yast, there are 2 files: order and instorder This is the content which references the location of the root of every source. (where the media.1 directory is available) # cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 avicenna:/work/CDs/sles8-i386 # cat yast/order /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 (delimiter is tab) more details can be found at http://www.suse.de/~nashif/autoinstall/8.1/html/advanced.html#AEN1251 Hope that helps... Anas Aaron McSorley wrote: > Is there a method for incorporating a service pack into an > auto install of SLES8. > > I tried putting the service pack in its own directory in my auto install > repository > and giving it preference in the order and instorder directories. > The install starts ok but, after package install I get alot of package > install failures. > After hitting ok to the fail log it prompts me to insert the service > pack cdrom. > > I thought about just replacing the original packages with the new ones > from the service pack but, > I would like to keep the service pack separate from the original > repository so I can > install without it if I want. > > thanks > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] How can I fix network configuaration settins of multiple NIC cards using AutoYast on OpenSUSE 11.0
by Alan Keng 29 Oct '08

29 Oct '08

Hi, I configured 2 NICs on my system with 2 static IP in 2 different subnets. Then I used Autoinstallation to save the XML control file. <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>172.24.255.11</ipaddr> <name>CK804 Ethernet Controller</name> <netmask>255.255.0.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <ipaddr>172.19.1.1</ipaddr> <name>82541PI Gigabit Ethernet Controller</name> <netmask>255.255.0.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> After many installations with AutoYast, most of the time the system would detect CK804 NIC (MAC address) as eth0 and 82541PI (MAC address) as eth1. However, it is not true all the time. So there would be the case that the eth0 with name of CK804 is set to the MAC address of 82541PI NIC and eth1 with name of 82541PI is set to the MAC address of CK804. (CK804 is an integrated NIC and 82541PI is a PCI NIC card). Is there a way to make sure the network settings would be the same after every installation using AutoYast?? (I would like to have one NIC with specific IP setting and the other one has another specific IP setting all the time)? If I use the XML control file to autoinstall on another system with different 2 NICs (not CK804 and 8254 PI anymore), what will happen? By the way, the Linuxrc would always see the CK804 NIC as eth1 and 82541PI as eth0 (at least so far). Is it possible you could kindly point me to some directions so that I could solve those problems. I am not sure how the NICs are detected as eth0, eth1, etc. Why the Linuxrc always detects CK804 as eth1 but most of the time the AutoYast would detect CK804 as eth0? Thank you so much for your time and I look forward to hearing from you. Sincerely, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 14

[opensuse-autoinstall] chroot scripts does not run
by Magnus Boman 21 Aug '08

21 Aug '08

Hello, I'm trying to use AutoYaST to install SLES10SP1. I need to make use of chroot scripts, but found an issue with it; This is a snippet from my AutoYaST script; <scripts> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">false</chrooted> <location>file:///mounts/extra/chroot-1.sh</location> </script> <script> <chrooted config:type="boolean">true</chrooted> <location>file:///mounts/extra/chroot-2.sh</location> </script> </chroot-scripts> </scripts> In the example above, the chrooted=false script runs just fine, but the chrooted=true does not. It looks like it is still trying to run it from /mnt/var/... instead of /var/... /mnt/var/... does not exist since we've done a chroot into / at this stage. This is a snippet from y2log for the chroot-2.sh script; 2008-08-19 06:13:31 <1> linux(3086) [Interpreter] clients/autoinst_scripts2_finish.ycp:57 Calling YaST client autoinst_scripts2_finish (arguments: ["Write"]) 2008-08-19 06:13:31 <1> linux(3086) [YCP] clients/autoinst_scripts2_finish.ycp:33 starting autoinst_scripts2_finish 2008-08-19 06:13:31 <1> linux(3086) [YCP] AutoinstScripts.ycp:484 Writing chroot script into /mnt/var/adm/autoinstall/scripts/chroot-scripts 2008-08-19 06:13:31 <1> linux(3086) [agent-system] SystemAgent.cc(Execute):1098 mkdir /tmp/YaST2-03086-eyCR4s/tmp_mount 2008-08-19 06:13:31 <1> linux(3086) [YCP] autoinstall/io.ycp:119 Copy profile: cp /mounts/extra/config/etc/config-builder/chroot-2.sh /mnt/var/adm/autoinstall/scripts/chroot-scripts 2008-08-19 06:14:12 <1> linux(3086) [YCP] AutoinstScripts.ycp:548 Script Execution command: /bin/sh -x /mnt/var/adm/autoinstall/scripts/chroot-scripts 2&> /mnt/var/adm/autoinstall/logs/chroot-scripts.log 2008-08-19 06:14:12 <1> linux(3086) [YCP] clients/autoinst_scripts2_finish.ycp:57 autoinst_scripts2_finish finished 2008-08-19 06:14:12 <1> linux(3086) [Interpreter] clients/autoinst_scripts2_finish.ycp:57 Called YaST client returned: nil Any ideas on what's happening here? Thanks, Magnus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] xincludes
by Georg Wallner 21 Aug '08

21 Aug '08

Hi, I get errors, when including xml files in autoyast profile. xmllint --xinclude opensuse110-4-xincludes.xml > ausgabe.xml doesn't complain. Autoyast doesn' t find the xml file, because it isn't in the mounted tmp directory. I tried several includes like: <xi:include href="nfs://x.x.x.x/installation/classes/include/include.xml"/> <xi:include href="http://x.x.x.x/installation/classes/include/include.xml"/> and just file <xi:include href="classes/include/include.xml"/> Nothing works. Any hints ? Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] classes
by georg.wallner＠ead-systeme.de 19 Aug '08

19 Aug '08

Hello, i wan't use classes in my profile.xml, for installing additional software and some scripts, depending on departments. But the autoyast doesn't fetch the additional software and scripts. Where is my fault? I have the following structur: myStart.xml <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <classes config:type="list"> <class> <class_name>additionalsoftware</class_name> <configuration>software.xml</configuration> </class> </classes> <software> <packages config:type="list"> <package>all packages</package> <patterns config:type="list"> <pattern>all patterns</pattern> </software> <scripts> <init-scripts config:type="list" > <script> <interpreter>shell</interpreter> <location>nfs://192.168.0.2/installation/autoinstall/w-scripts/init_install_db2.sh</location> <filename>init_install_db2.sh</filename> </script> </init-scripts> </scripts> </profile> In the folder classes/additonalsotware i have the software.xml <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <software> <post-packages config:type="list"> <package>psw_basis</package> <package>psw_ab1000</package> <package>psw_fb1000</package> <package>psw_winbasis</package> <package>psw_winab1000</package> <package>psw_winfb1000</package> </post-packages> </software> <scripts> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <interpreter>shell</interpreter> <filename>init-parity.sh</filename> <source> <![CDATA[ !#/bin/sh mkdir /home/abfb ln -sf /home/abfb /usr/parity ]]> </source> </script> </chroot-scripts> </scripts> </profile> Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] How to choose default screensaver?
by pierre.girard＠gerad.ca 18 Aug '08

18 Aug '08

Is there a way to select the default screensaver with autoyast? By default we'd like it to be set to blank instead of random. Thanks for your input. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Has anyone been able to install 10.3 or 11 on HP ProLiant DL160/165 servers?
by Mike Diehn 15 Aug '08

15 Aug '08

DQoNCldlIGhhdmUgOCBuZXcgREwxNjAgbWFjaGluZXMgKHR3byBkdWFsLWNvcmUgSW50ZWwgY3B1cykgYW5kIGFsbCB0aGUgaW5zdGFsbGF0aW9ucyBoYW5nIGF0ICJDYWxjdWxhdGluZyBrZXJuZWwgbW9kdWxlIGRlcGVuZGVuY2llcy4uLiIgIEl0IGhhcHBlbnMgb24gb3N1czEwLjMgYW5kIG9zdXNlMTEuDQoNClNMRVMgMTAuMiBnb2VzIG9uIGp1c3QgZmluZS4gIEFuZCBvZiBjb3Vyc2UsIEhQIHNheXMgdGhleSdsbCBvbmx5IGhlbHAgd2l0aCBTTEVTIG9yIGFub3RoZXIgc3VwcG9ydGVkIE9TLCBsaWtlIFJlZEhhdC4NCg0KQW55b25lIGVsc2Ugc2VlbiB0aGlzPw0KDQpNaWtlDQoNCk1pa2UgRGllaG4NClNyLiBTeXNBZG1pbg0KbWlrZS5kaWVobkBhbnN5cy5jb20NCisxLTYwMy03MjctNTQ5Mg0K-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.orgFor additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] post-packages broken in openSUSE 11.0
by Georg Wallner 15 Aug '08

15 Aug '08

Hello, i did following in file /installation/repository/OpenSuSE110/distribution/11.0/repo/oss/control.xml Around line 1059 there is a line like this: <name>rpmcopy_secondstage</name> change that line to <name>rpmcopy</name> no i get the error sorry, repository failed checksum test. What have i to do ? Greetings Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] List of valid patterns/packages?
by Lamarre, Michael 15 Aug '08

15 Aug '08

Kind of a silly question, but is there documentation anywhere that lists all of the valid values I can specify in <pattern> and <package> elements in the <software> section of the AutoYaST profile? Thanks, Michael -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 3