July 2008 - openSUSE Autoinstall - openSUSE Mailing Lists

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] 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

[opensuse-autoinstall] add_on products fails
by georg.wallner＠ead-systeme.de 15 Aug '08

15 Aug '08

Hallo, i get the following error again and again. I want add certain rpm Pakets to an add_on folder and the autoinstaller complains about Invalid URL. I could create the add_on part with the autoyast wizard. The error: Yast2 Fehler: Zusatzprodukt konnte nich hinzugefügt werden less /var/log/Yast2/y2log [..]Source_Create.cc(SourceCreateEx):593 Invalid URL: Das URL-Schema ist eine erforderliche Komponente [...] /etc/exports: /installation/repository *(rw,no_root_squash,sync,no_subtree_check) /installation/autoinstall *(ro,no_root_squash,sync,no_subtree_check) /installation/repository/OpenSuSE110/CD1 *(rw,no_root_squash,sync,no_subtree_check) /installation/repository/OpenSuSE110/CD1/updates *(rw,no_root_squash,sync,no_subtree_check) /installation/repository/OpenSuSE110/distribution/11.0/repo/non-oss *(rw,no_root_squash,sync,no_subtree_check) /installation/repository/OpenSuSE110/distribution/11.0/repo/oss *(rw,no_root_squash,sync,no_subtree_check) /installation/repository/OpenSuSE110/update/11.0 *(rw,no_root_squash,sync,no_subtree_check) The Folder /installation/repository/OpenSuSE110/CD1/updates was created like on the homepage http://www.suse.com/~ug/ create_update_source.sh /installation/repository/OpenSuSE110/CD1 cd /installation/repository/OpenSuSE110/CD1 cp -a /installation/packages/vmware-server-1.06/VMware-server-1.0.6-91891.i386.rpm updates/suse/i386 cd updates/suse create_package_descr -x setup/descr/EXTRA_PROV cd setup/descr ls > directory.yast # the following two steps are required since openSUSE 11.0 cd ../../.. create_sha1sums -x -n ./ The /installation/repository/OpenSuSE110/CD1/updates/content file looks like this: PRODUCT openSUSE Updates VERSION 11.0 DISTPRODUCT SuSE-Linux-Updates TYPE base VENDOR SUSE LINUX Products GmbH, Nuernberg, Germany RELNOTESURL http://www.suse.com/relnotes/i386/openSUSE/11.0/release-notes-openSUSE.rpm ARCH.x86_64 x86_64 i686 i586 i486 i386 noarch ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i586 REQUIRES openSUSE-release = 11.0 pattern:basesystem PROVIDES product:openSUSE = 11.0 OBSOLETES product:SUSE_LINUX product:openSUSE < 11.0 package:openSUSE < 11.0 LINGUAS cs da de en en_GB en_US es fi fr hu it ja nb nl pl pt pt_BR ru sv zh zh_CN zh_TW SHORTLABEL oS 11.0 LABEL openSUSE 11.0 LABEL.de openSUSE 11.0 DESCRDIR suse/setup/descr DATADIR suse FLAGS update LANGUAGE en_US Following the autoyast.xml part <add-on> <add_on_products config:type="list" > <signature-handling > <accept_file_without_checksum config:type="boolean" >true</accept_file_without_checksum> <accept_non_trusted_gpg_key config:type="boolean" >true</accept_non_trusted_gpg_key> <accept_unknown_gpg_key config:type="boolean" >true</accept_unknown_gpg_key> <accept_unsigned_file config:type="boolean" >true</accept_unsigned_file> <accept_verification_failed config:type="boolean" >true</accept_verification_failed> <import_gpg_key config:type="boolean" >true</import_gpg_key> </signature-handling> <listentry > <media_url>nfs://192.168.0.2/installation/repository/OpenSuSE110/CD1/updates</media_url> <product>SuSE-Linux-Updates</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> <software > <packages config:type="list" > <package >autoyast2-installation</package> <package >autoyast2</package> <package >VMware-server</package> </packages> <patterns config:type="list" > <pattern >base</pattern> <pattern >enhanced_base</pattern> <pattern >enhanced_base_opt</pattern> <pattern >fonts</pattern> <pattern >fonts_opt</pattern> <pattern >sw_management</pattern> <pattern >x11</pattern> <pattern >x11_opt</pattern> <pattern >x11_yast</pattern> <pattern >xfce</pattern> <pattern >yast2_basis</pattern> <pattern >yast2_install_wf</pattern> </patterns> </software> -- 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] autoyast complete configuration files?
by pierre.girard＠gerad.ca 14 Aug '08

14 Aug '08

Hello, i was trying to setup some printers and i have some PPD files for them that aren't included in opensuse so i went in autoyast and created a new "complete configuration file" and loaded the PPD file into it. In the "File path" i typed the complete file name and i filled the owner and permissions (root:root and 644). After the installation is complete when i go to the directory where the file should be it isn't there. Is there a way to debug this without reinstalling each time? Thanks for your help. -- 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 have ZMD running at the time I have a post script being called
by Alan Mosca 05 Aug '08

05 Aug '08

Hi, I have an install with a post script that needs to run some commands using 'rug' (mainly to add repositories and do some logging of the status of the machine and what's available on it). The problem is that I keep getting "ERROR: ZMD does not appear to be running." in the log. I have attached the xml for the script (it's quite a long script and I don't want to bother you with it - if I run it alone it works). Does anyone have any suggestions on how to get zmd up before this is run? -------- <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">false</debug> <feedback config:type="boolean">false</feedback> <filename>setupcluster.pl</filename> <interpreter>perl</interpreter> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[#!/usr/bin/perl #(script removed) ]]></source> </script> </post-scripts> </scripts> ---------- Thank you all! Alan Mosca -- 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 bypass AutoYaST license WITHOUT removing the license from the media?
by Richard Hefner 04 Aug '08

04 Aug '08

Hi all - We have an environment where we loop mount (read-only, of course) our SuSE media and do not have the option of removing the license.zip (or the entries in the directory.yast file) to bypass the license agreements upon an auto installation with AutoYaST. Is there any other possible way to do this? I don't really care if it's just a hack to get it working.. We just need something. =20 One method I've been trying is using a pre-install script: for each system, I customize an initrd for it and throw a modified control.xml (control.xml.bak) file into it, along with an info file and an autoyast.xml file. I was thinking that it could be possible to run a pre-install script that copies the modified control.xml.bak file (the one with the license module(s) commented out) to the "real" control.xml file. The only problem with this approach that I've seen is that yast needs to re-read the modified control.xml file, as if the pre-install script does this, I have errors with my partitioning plan. Is there any way to invoke a re-read of this file without killing yast and restarting? If not, what's the best way to accomplish a reload of yast without exiting the installation? The only answers I've seen on this list is to remove the license files from the media. Or, one method that I've seen that works is to leave the license files on the media but comment out (or remove) the section for the license modules in the control.xml file. Hopefully there's a way to do this? Thank you for your time! -Richard Hefner -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 10

[opensuse-autoinstall] Content file and REQUIRES
by Patrick Keys 31 Jul '08

31 Jul '08

Hi We've been using a single add on product for the additional RPMs that we deliver to our systems - SLES10 SP1 and openSUSE 10.2. This has been working fine, but I've recently tried to upgrade to openSUSE 11.0 and am now experiencing problems with the REQUIRES line in the content file. In our current implementation, the REQUIRES line reads as follows: REQUIRES sles-release AutoYast on both SLES and openSUSE used to work correctly allowing RPMs from the add-on product to be installed. In openSUSE 11.0 the add on product fails because AutoYast cannot resolve sles-release. Is there a way to use the same content file for both - i.e. can a logical 'or' be specified on the REQUIRES line? Or is there a way to revert to the old behaviour and essentially ignore the REQUIRES line? Many thanks for your help Patrick This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender (as shown above). Kindly do not reproduce, print or forward any material received in error, please delete it immediately. Pharos Communications Limited (Company No. 3458137) is incorporated in England and Wales and has its registered office at 83 London Street, Reading, Berkshire, UK, RG1 4QA -- 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] How to have zmd running whilst a "post" script is being called
by Alan Mosca 31 Jul '08

31 Jul '08

I have a setup in SLES10 SP2 with a "post" script that needs to use 'rug' to get info back. Obviously rug needs to talk to ZMD, so I added a `rczmd start` at the beginning of the script, but that didn't work either. Is there any other way I can get zmd up at that time? Thanks -- Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0