July 2011 - 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] autoyast with multiple LVM Volume Groups
by big beer 07 Sep '12

07 Sep '12

Hello, I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups. . . . <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>firstvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>secondvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> . . . The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist. Am I trying this wrong or am I hitting some sort of bug? thanks -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 7

[opensuse-autoinstall] Repository Priority
by Tim Kirby 28 Sep '11

28 Sep '11

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- 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] Setting environment variable for installation
by Jochen Schaefer 25 Aug '11

25 Aug '11

Hi, I need to set an environment variable which should be present within the installation environment. Is there any cmd line option which can fulfill that? Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7

[opensuse-autoinstall] Identification of NICs by MAC address
by Sebastian Wenner 24 Aug '11

24 Aug '11

Hi, is there a way of identifying NICs by MAC address rather than by interface name? We have several multi-nic machines where we run into trouble with "normal" interface names. They have e.g. 4 onboard nics, powered by the bnx2 driver and an additional quad-port card powered by the e1000 driver. If the e1000 gets loaded before the bnx2, the first onboard (which is our usual link into the install network) comes up as eth4 instead of eth0. Identifying the adapter by its mac address would do a great job to avoid this confusion... Is there a way of specifying this in the autoyast file and at the boot prompt? Best regards Sebastian -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 20

[opensuse-autoinstall] Partition/sector boundary alignment
by Paul 12 Aug '11

12 Aug '11

Hi, Can anyone suggest how to ensure AutoYAST creates partitions that are aligned to 4K boundaries? As far as I can tell, AY doesn't allow for specifying start sectors -- only by size. I understand that without such alignment the disk I/O subsystem will be worked harder than it needs to be in order to satisfy requests. My build will be SLES11sp1 on both physical and VMware. Thanks, -Paul -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

[opensuse-autoinstall] yast2-transfer and DIGEST Auth
by Jochen Schaefer 28 Jul '11

28 Jul '11

Hi, I tried to setup an automated installation via autoyast and digest authentication. I faced the same problem as with client-certificates. apache2 error.log: Digest: client used wrong authentication scheme `Basic': /lh/xml/0 ... yast2-transfer is using libcurl and is using basic auth per default. No possibility to change that. @Uwe - another point which should be considered with libcurl. Applications like wget decide on type of challenge which encoding scheme to use. May be it could be implemented that way. Best Regards, Jochen -- 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] Installation via HTTPS client certificate
by Jochen Schaefer 27 Jul '11

27 Jul '11

Hi list, I'm trying an auto installation (SLES11-SP1) via HTTPS and authentication with client certificates. To achieve this I copied CA certificate and client certificate into initrd, executed c_rehash and edited /root/.curlrc within initrd to know about the certificates: --capath = /etc/ssl/certs/ --cert = /etc/ssl/client/xyz profile is specified like https://10.1.1.1/xml/ Unfortunately yast is still not able to fetch the profile. When I do an ssh based installation ending up in the dialog where yast failes I'm able to get the profile from a second ssh console via curl without specifying any cert parameters: curl https://10.1.1.1/xml/default shows the content of default file. A check from outside the installation environment without specifying a certificate fails with SSL Handshake error and proves that the virtual host configuration seems ok. The opposite check where I provided certificate parameters to curl from outside worked as well. /var/log/YaST/y2log within installation environment shows: CurlConfig.cc(parseConfig):44 Going to parse /root/.curlrc 2011-07-26 06:17:00 <1> 10.0.4.96(3544) [zypp++] CurlConfig.cc(parseConfig):106 GOT: capath 2011-07-26 06:17:00 <1> 10.0.4.96(3544) [zypp++] CurlConfig.cc(setParameter):178 Ignoring option capath 2011-07-26 06:17:00 <1> 10.0.4.96(3544) [zypp++] CurlConfig.cc(parseConfig):106 GOT: cert 2011-07-26 06:17:00 <1> 10.0.4.96(3544) [zypp++] CurlConfig.cc(setParameter):178 Ignoring option cert which leads to the assumption that yast is not considering options from /root/.curlrc? Does anybody know how to configure yast/curl to accept parameters from .curlrc? Another attempt could be to use aria2c within initrd since following line is displayed in y2log: aria2c not found. Falling back to curl But will yast consider any certificate parameters for aria2c or will I end with the same problem finally? Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

RE: [opensuse-autoinstall] Specifying a local (i.e. on DVD) Add-On Repository in add_on_products.xml for SLES 11 SP1
by Jason Babicka 27 Jul '11

27 Jul '11

> on Monday, July 25, 2011 Uwe Gansert wrote: > > You can also try to specify the add-on in the autoyast XML file instead of the > add_on_products.xml file Just add: > > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>cd:///updates</media_url> > <product>SuSE-Linux-Updates</product> > <product_dir>/</product_dir> > <name>MyUpdates</name> > </listentry> > </add_on_products> > </add-on> > > and remove the add_on_products.xml > There is a bug in SP1 that relurl will not work in the autoyast XML file. It only > works with the add_on_products.xml So you don't have to try relurl with the > XML above. Uwe, I tried this suggestion. In my testing I think that specifying the add-on product location in the autoinstall.xml file instead of in the add_on_products.xml file should allow me to get the results that I want. Thank you for this suggestion. -Jason This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] Prevent manual installation after interruption of autoyast
by Jochen Schaefer 26 Jul '11

26 Jul '11

Hi Steffen, I now managed the desired behaviour via the setupcmd parameter. It calls a wrapper script which executes the setcsid `console` ... command and checks /etc/yast.inf in a while loop for the "Aborted" entry. If the entry exists a reboot -f ensures that no manual interaction can be done at console anymore. Thanks again for this nice hint. Now the only problem left is to induce yast/curl/aira2c to use client certificate based authentication. But this is another topic. Jochen >>> Steffen Winterfeldt 07/25/11 3:30 PM >>> Hi Jochen, On Mon, 25 Jul 2011, Jochen Schaefer wrote: > Hi Steffen, > > do you know where to find some documentation about yast.inf? Old linuxrc versions used to have some bits about it: http://www.gitorious.org/opensuse/linuxrc/blobs/sl_10.1/README.linuxrc Newer yast variants write 'abort: 1' to differentiate between crash & user abort. One more things: yast exit code is 0 (install ok) vs. !=0 (crash, abort). Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0