August 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] SLES11SP2 - repomd.xml.asc is required?
by Douglas_Parrish＠Dell.com 19 Sep '11

19 Sep '11

For my team, I manage several Linux auto-installations for RedHat & SLES. I have fairly stock autoyast.xml's that have been working quite well for a while. With SLES11SP2, I'm running into a new problem. As our add-on repository is for internal access only, we've never seen any value in signing our packages. I use the signature-handling flags to bypass the signing checks: <signature-handling> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> <accept_non_trusted_gpg_key config:type="boolean">true</accept_non_trusted_gpg_key> <import_gpg_key config:type="boolean">true</import_gpg_key> </signature-handling> </general> With SLES11SP2 (beta3) autoyast attempts to retrieve the repomd.xml.asc and repomd.xml.key files anyway. This throws up a blocking error dialog. Am I doing something wrong or has this behavior changed? -- Douglas Parrish Programmer Dell | PG Customer Operations -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

[opensuse-autoinstall] Running several post-install scripts
by Robert Klein 13 Sep '11

13 Sep '11

Hi, I'm trying to run two post-install scripts from file, however it seems, autoyast can't do this. If I include one script in <script> <source>...</source> </script> and one in <script> <location>ftp://.....</location> </script> both scripts run. However, when I try to use two scripts with <location>,,,,</location> only the first one gets done, regardless of an additional script with <source>,,,</source> or not. Is it simply not possible to do so? I tried openSuSE 11.2 and SLES11 SP1 I used the following in the autoyast.xml file: a) <script> <location>ftp://xyzzy/autoyast/mail-settings-112.sh</location> </script> <script> <location>ftp://xyzzy/autoyast/backup-deployment.sh</location> </script> and b) <script> <location>ftp://xyzzy/autoyast/mail-settings-112.sh</location> <filename>mail-settings-112.sh</filename> </script> <script> <location>ftp://xyzzy/autoyast/backup-deployment.sh</location> <filename>backup-deployment.sh</filename> </script> at b) I get log files for both, not only one postinstall-scripts.log, with the second lob, "mail-settings-112.sh.log" being empty. Any help is appreciated. Thank you very much Robert Klein -- 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] 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] Using autoyast non interactively in a call like: yast autoyast file filename config.xml
by Rainer Krienke 19 Aug '11

19 Aug '11

Hello, I have a bunch of openSuSE desktops that are running in a network environment with central user management. User authentication for login is done up to now via a central NIS password database. Now I would like to change this and instead athenticate users against a central ldap server. This works when I configure it manually using yast on a already installed system but my problem is how can I automatically reconfigure existing desktops to use ldap instead of NIS. My idea was to use autoyast. So I configured one system, cloned it to get an autoyast config.xml file. Then on another system I wanted to reconfigure I started yast in the following manner: yast autoyast file filename config.xml This basically worked fine, but the problem is, that this was not completely noninteractively, I manually had to select the yast menu to apply the new autoyast configuration to the system. Is there a way to do this without user interaction? Does anyone have another idea how to automatically reconfigure a system from NIS to ldap athentication? Thanks you very much Rainer -- Rainer Krienke, Uni Koblenz, Rechenzentrum, A22, Universitaetsstrasse 1 56070 Koblenz, http://userpages.uni-koblenz.de/~krienke, Tel: +49261287 1312 PGP: http://userpages.uni-koblenz.de/~krienke/mypgp.html,Fax: +49261287 1001312

2 4

[opensuse-autoinstall] ext4 for SLES 11 SP1
by Frank Steiner 17 Aug '11

17 Aug '11

Hi, ext4 is not part of the SLES 11 SP1 kernel, one needs the ext4dev-kmp-default rpm to add support for ext4 file systems. Thus I wonder if there is any way to format file systems (not the root partition) with ext4 during the hard disk setup of autoyast. I haven't found a documentation about this. Can I load the ext4 module into the AY installer somehow? Maybe with a driverupdate or sth.? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 10

[opensuse-autoinstall] Copying installation DVD to installed system
by Andreas Taschner 17 Aug '11

17 Aug '11

Hi In an isolated server scenario (defense solution), servers are installed from DVD with AutoYaST profile and info file on a USB stick and an additional DVD with a patch-set as an add-on product. On a regular basis, a DVD containing a new patch-set is distributed. This all works fine until we (Novell) release a patch that will install packages from the installation repository, which obviously does not exist on these servers. To prevent that problem from ever occurring, I am trying to find a way to copy the whole content of the SLES DVD to a directory on the target system in e.g. a chroot script and then add it as a repository with zypper. I have tried to find the path to the installation medium with "find -t d" in various scripts, also chroot with chrooted=false, but no luck. Does anybody know how to access those files ? Thank you Best regards Andreas -- 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] Forcing a specific package version
by Erico Mendonça 16 Aug '11

16 Aug '11

Does anyone know how I could force a specific package version in AutoYaST? I have two packages, one original for SLES11SP1, and another (newer) with the same name and newer version, from a third-party. Both are available in repos during installation. -- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 9

[opensuse-autoinstall] disabling backup of config files at reinstall
by Magyari, Miklos 16 Aug '11

16 Aug '11

hi all, as I understand, autoyast has a feature for backing up some selected config files before doing partitioning/formatting. Is there an xml tag to disable this feature? I keep reinstalling my clients and I do not want to preserve any files from previous installations. thanks, Miki -- 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] 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] changing the default kernel
by Magyari, Miklos 12 Aug '11

12 Aug '11

hi, probably this is easy and has been answered several times, but I cannot find it. Is there a way in autoyast to change the default boot kernel? I have a 8 GB laptop but after autoinstalling, it boots the default kernel, while I would prefer the pae one (it is sled11 sp1, and default, pae and xen are all installed). I know I can change /boot/grub/menu.lst with a single sed command but maybe there is a more sophisticated solution for this. thanks, Miki -- 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] Samba-client and Kerberos documentation sought
by Geoff.Buckingham＠thomsonreuters.com 10 Aug '11

10 Aug '11

Is there any documentation on this? I am finding it hard to understand how this information get parsed. For example only some of the following global configuration make it into smb.conf: <samba-client> <active_directory> <kdc>lsci-dceadc01.dce.lsc.reuint.com</kdc> </active_directory> <global> <cached_login>yes</cached_login> <cups_options>raw</cups_options> <idmap_gid>10000-20000</idmap_gid> <idmap_uid>10000-20000</idmap_uid> <include config:type="list"/> <krb5_auth>yes</krb5_auth> <krb5_ccache_type>FILE</krb5_ccache_type> <logon_drive>P:</logon_drive> <logon_home>\\%L\%U\.9xprofile</logon_home> <logon_path>\\%L\profiles\.msprofile</logon_path> <map_to_guest>Bad User</map_to_guest> <passdb_backend>tdbsam</passdb_backend> <printcap_cache_time>750</printcap_cache_time> <printcap_name>cups</printcap_name> <printing>cups</printing> <realm>DCE.LSC.REUINT.COM</realm> <security>ADS</security> <template_homedir>/tmp/%D/%U</template_homedir> <template_shell>/bin/tcsh</template_shell> <usershare_allow_guests>No</usershare_allow_guests> <winbind_offline_logon>yes</winbind_offline_logon> <winbind_refresh_tickets>yes</winbind_refresh_tickets> <workgroup>LSCI-DCE</workgroup> </global> 8<snip8< Results in the following in smb.conf post install: At least realm, usershare_allow_guests, template_shell, template_homedir seem not to have made it into smb.conf (This was with SLES 11SP1) [global] workgroup = LSCI-DCE passdb backend = tdbsam printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = Yes idmap gid = 10000-20000 idmap uid = 10000-20000 realm = security = ADS template homedir = /home/%D/%U template shell = /bin/bash winbind offline logon = yes winbind refresh tickets = yes [homes] Geoff Buckingham Infrastructure Solutions Architect Thomson Reuters This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Fwd: [opensuse-autoinstall] YaST crashes when adding "partition" to "dont_merge" section in rules.xml
by Joschi Brauchle 08 Aug '11

08 Aug '11

The actual error message reads ---- ... YaST got signal 11 at YCP file Profile.ycp:88 ... ---- Note that it does not matter if there is a partitioning section in the XMl file that gets merged with this rule. The crash is solely triggered by adding the "partition" element to the "dont_merge" part of the rules.xml. -------- Original Message -------- Subject: [opensuse-autoinstall] YaST crashes when adding "partition" to "dont_merge" section in rules.xml Date: Mon, 8 Aug 2011 13:01:52 +0200 From: Joschi Brauchle <joschi.brauchle(a)tum.de> To: opensuse-autoinstall(a)opensuse.org <opensuse-autoinstall(a)opensuse.org> Hi everyone, I wanted to customize the partitioning for a specific node type of my auto installation, thus I added ---- <rule>  <custom1> <script>  </script> <match></match> <match_type>regex</match_type> </custom1> <result> <profile></profile> <continue config:type="boolean">true</continue> <dont_merge config:type="list"> <element></element> <element></element> <element></element> <element>partition</element> </dont_merge> </result> </rule> ---- to my rules/rules.xml. YaST crashes at the beginning of the installation when reading/merging the profiles as soon as I added the "partition" element to the "dont_merge" section. If I remove it, the installation runs fine. The error message is something like (I took video and noted this down): ---- error: cannot open Packages index using db3 - No such file or directory (2) YaST got signal 11 at YCP file Profile.ycp:86 /usr/lib/YaST2/startup/YaST.call: line 284: 3549 Segmentation fault (core dumped) $OPT_FBITERM y2base "$Y2_MODULE_NAME" "Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS ---- Is there any known problem/workaround? Best regards, Dipl.-Ing. Joschi Brauchle, M.Sc. Institute for Communications Engineering (LNT) Technische Universitaet Muenchen (TUM) 80290 Munich, Germany Tel (work): +49 89 289-23474 Fax (work): +49 89 289-23490 E-mail: joschi.brauchle(a)tum.de Web: http://www.lnt.ei.tum.de/

2 1

[opensuse-autoinstall] YaST crashes when adding "partition" to "dont_merge" section in rules.xml
by Joschi Brauchle 08 Aug '11

08 Aug '11

Hi everyone, I wanted to customize the partitioning for a specific node type of my auto installation, thus I added ---- <rule>  <custom1> <script>  </script> <match></match> <match_type>regex</match_type> </custom1> <result> <profile></profile> <continue config:type="boolean">true</continue> <dont_merge config:type="list"> <element></element> <element></element> <element></element> <element>partition</element> </dont_merge> </result> </rule> ---- to my rules/rules.xml. YaST crashes at the beginning of the installation when reading/merging the profiles as soon as I added the "partition" element to the "dont_merge" section. If I remove it, the installation runs fine. The error message is something like (I took video and noted this down): ---- error: cannot open Packages index using db3 - No such file or directory (2) YaST got signal 11 at YCP file Profile.ycp:86 /usr/lib/YaST2/startup/YaST.call: line 284: 3549 Segmentation fault (core dumped) $OPT_FBITERM y2base "$Y2_MODULE_NAME" "Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS ---- Is there any known problem/workaround? Best regards, Dipl.-Ing. Joschi Brauchle, M.Sc. Institute for Communications Engineering (LNT) Technische Universitaet Muenchen (TUM) 80290 Munich, Germany Tel (work): +49 89 289-23474 Fax (work): +49 89 289-23490 E-mail: joschi.brauchle(a)tum.de Web: http://www.lnt.ei.tum.de/

1 0

[opensuse-autoinstall] AutoYast device type to determine partition layout. Feature request or existing functionality?
by Nefi Munoz 03 Aug '11

03 Aug '11

Hi, Novell customer asked the following: "Currently, we can set the XML AY profiles to install to /dev/cciss/c0d0 or /dev/sda for example. In the case of servers with Boot-from-SAN or Solid State Drivers, this can cause some device naming confusion. Wouldn*t it be cool if AutoYaST could take the device type (i.e. *IBM 2145*), size of disk or LUN ID as a parameter to determine the partition layout to apply?" Is this currently possible? Thanks in Advance, Nefi M. Nefi Munoz DSE - Cardinal Health nmunoz(a)novell.com Mobile: 614-935-2411 Novell Making IT Work as One www.novell.com

2 2

[opensuse-autoinstall] NFS mount fails on NFSv3-only server
by Joschi Brauchle 02 Aug '11

02 Aug '11

Hello everyone, I am trying to serve an NFS repository from an NFSv3-only server, i.e. on the server I set VERSION_LIST="-2 +3 -4" and pass "--no-nfs-version 2 --no-nfs-version 4" to the nfs daemon. Now I have specified the boot option install=nfs://<server-ip>/<path-to-repo> and this fails on the client with a message "unknown error". When I use wireshark to debug the problem, I see that the server responds to the client's mount request with: "Accept State: remote can't support version # (2)" Is there any possibility to pass the NFS version along with the install parameter? Best regards, J Brauchle

1 0

[opensuse-autoinstall] signing a driverupdate file
by Jochen Schaefer 02 Aug '11

02 Aug '11

Hi list, is there any description how to sign a driverupdate file to get rid of the "file not signed" message? I'm aware of the insecure=1 parameter but would rather sign the repository or driverupdate file. Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0