March 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] 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] opensuse 11.4 pxe installation - no repository in 'iso:/?iso=openSUSE-11.4-DVD-i586.iso&url=nfs://...
by Pierre Girard 27 May '11

27 May '11

Hello, I'm trying to install opensuse 11.4 and so far the machine loads pxe, starts initrd and linux, and starts the installation process. At some point it looks to add repositories and I get an error message saying there was a problem adding a repository. Here's the message from y2log: 2011-03-14 10:56:08 <1> client.example.com(3182) [YCP] Progress.ycp:599 Subprogress initialization skipped 2011-03-14 10:56:08 <3> client.example.com(3182) [YCP] Packages.ycp:1484 No repository in 'iso:/?iso=openSUSE-11.4-DVD-i586.iso&url=nfs://nfsserver.example.com/suse/o…' 2011-03-14 10:56:08 <1> client.example.com(3182) [Pkg] Packages.ycp:1063 Pkg Builtin called: LastError I checked the path, and I was able to manually mount the directory from one of the terminals without problem. Here's part of the pxelinux.cfg/default label workstation11.4-32 kernel linux11.4-32 append initrd=initrd11.4-32 ramdisk_size=65536 insmod=e100 textmode=1 autoyast=nfs://nfsserver.example.com/suse/autoyast-workstation-11.4 install=nfs://nfsserver.example.com/suse/opensuse/distribution/11.4/iso/ope… label manual11.4-32 kernel linux11.4-32 append initrd=initrd11.4-32 ramdisk_size=65536 manual=1 install='nfs://nfsserver.example.com/suse/opensuse/distribution/11.4/iso/openSUSE-11…' For now I'm trying to make the manual installation work. I have the same lines for opensuse 11.3 and 11.2 and those installations work correctly. Any idea what could be the problem? Thank you. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

11 19

[opensuse-autoinstall] VMWare and cloning
by Tim Kirby 31 Mar '11

31 Mar '11

Has anyone written any thoughts on the interplay between VM cloning and autoyast ? I haven't seen anything that I can recall but then again I haven't been watching closely... but it appears to have appeared on my radar screen now, so I thought I'd ask. 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

4 3

[opensuse-autoinstall] LDAP login not possible
by Henrik Schmidt 28 Mar '11

28 Mar '11

Hi, I install with autoyast and LDAP activated since 10.3 without a problem. With 11.4 LDAP login does not work any longer though the autoyast config for LDAP is the same as in older working versions. I can see that the PAM files in /etc/pam.d do not have any ldap entries at all. I tried to add ldap with pm-config --add --ldap by hand but it failed too. I can use the yast2 LDAP Browser successfully so basically LDAP is ok. Any hint ? Here are my ldap settings with server IP hidden: <ldap> <base_config_dn>ou=ldapconfig,dc=ks,dc=informatik,dc=uni-kiel,dc=de</base_config_dn> <bind_dn>cn=admin,dc=ks,dc=informatik,dc=uni-kiel,dc=de</bind_dn> <create_ldap config:type="boolean">false</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>dc=ks,dc=informatik,dc=uni-kiel,dc=de</ldap_domain> <ldap_server>XXX.XXX.XXX.XXX</ldap_server> <ldap_tls config:type="boolean">true</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <login_enabled config:type="boolean">true</login_enabled> <member_attribute>member</member_attribute> <nss_base_group>ou=group,dc=ks,dc=informatik,dc=uni-kiel,dc=de</nss_base_group> <nss_base_passwd>ou=people,dc=ks,dc=informatik,dc=uni-kiel,dc=de</nss_base_passwd> <nss_base_shadow>ou=people,dc=ks,dc=informatik,dc=uni-kiel,dc=de</nss_base_shadow> <pam_password>crypt</pam_password> <start_autofs config:type="boolean">true</start_autofs> <start_ldap config:type="boolean">true</start_ldap> </ldap> -- 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] Re: Partition/sector boundary alignment [SOLVED]
by big beer 25 Mar '11

25 Mar '11

I should have asked for some more info while this was hot, but at the time the issues around alignment didn't matter to me. Fast forward to getting a netapp box and it becomes important..... >On Sat, Dec 04, 2010 at 05:25:43PM +0000, Paul wrote: >> >> 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. >> > >If anyone's interested, I discovered that it is possible to specify the >size of a partition using sectors instead of the GB size. The >properties partition_id and partition_type control such behaviour. To >specify the size in sectors, the list resource region is used. >-Paul. Anyone have some example xml on how to setup partitions to start/stop on specific sectors? I'm also curious about lvm pv's created by autoyast. The disks are getting a partition created on them as well, any chance of just using the whole disk? (like pvcreate /dev/sdd ) Thanks! --BigBeer -- 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] Updates are not installed although configured
by Joschi Brauchle 23 Mar '11

23 Mar '11

Hello everyone, I have a problem with an OpenSuSE 11.4 installation via AutoYaST: Although I configured a (locally mirrored) update repository as an add-on product in the XML file, the available updates are not installed after the installation has finished. My XML file includes: <add-on> <add_on_products config:type="list"> <listentry> <media_url>nfs://192.168.109.3/export/install/linux/opensuse/11.4/update/</media_url> <product>OpenSUSE11.4 Updates</product> <product_dir>/</product_dir> <name>AutoYaST_Updates</name> </listentry> ... </add_on_products> </add-on> And I additionally set the <software> <do_online_update config:type="boolean">true</do_online_update> </software> Tag. But still, after the system is done with the installation, a "zypper lu" shows some available updates... Any suggestions? Thanks, Joschi -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2