- openSUSE Autoinstall

[opensuse-autoinstall] Fwd: network configuration in post scripts?
by Razvan Cosma 10 Feb '12

10 Feb '12

Hello, Moving the conversation here, as it's probably more appropriate than in general help. ---------- Forwarded message ---------- From: Razvan Cosma <rg(a)cosma.name> Date: Wed, Feb 8, 2012 at 11:12 AM Subject: network configuration in post scripts? To: opensuse(a)opensuse.org Hello everyone, In version 11 (both opensuse and sles) I was configuring various system parameters in the <chroot-scripts> section, which had the filesystem mounted and network (dhcp) up. In 12 though, my changes (ifcfg, hostname, routes, udev) are overwritten by the last autoyast step after reboot. I've also tried post-scripts and init-scripts, same problem. A working setup in 11 is: <networking><interfaces config:type="list"><interface><bootproto>dhcp4</bootproto><device>eth0</device><startmode>auto</startmode></interface></interfaces></networking> this ensures network is up on the first interface, the post script is supposed to configure the others <packages config:type="list"><package>dialog</package><package>wget</package> <chroot-scripts config:type="list"><script><chrooted config:type="boolean">true</chrooted><source><![CDATA[ sysid=$(dialog --no-cancel --stdout --backtitle "Post-install configuration" --inputbox "Enter system id:" 8 30 localhost) read iname mac ip gw hname <<<$(IFS=" "; wget -q -O - "http://server?$sysid") echo $hname > /etc/HOSTNAME sed -i -e "s/$$mac.*NAME=\"$.*/\1$iname\"/" /etc/udev/rules.d/70-persistent-net.rules echo -e "BOOTPROTO='static'\nSTARTMODE='onboot'\nIPADDR='$ip'\n" > /etc/sysconfig/network/ifcfg-$iname #other various system settings ]]></source></script></chroot-scripts> This ensured that udev always assigns a specific IP to the correct interface, data is in some SQL. The files are zeroed in 12, though, any hints on what has changed? Thank you, Razvan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 3

[opensuse-autoinstall] opensuse 12.1 welcome screen
by Pierre Girard 08 Dec '11

08 Dec '11

Hello, I'm making an autoyast configuration for 12.1 and when the install is complete I get a grey login screen with a clock on it which is not what I get when I do a manual install. I started yast on a machine and looked into the sysconfig editor and put the same options I saw in the « display manager » and « window manager » sections. The only thing what got written out is this part (I assume because the other options are default). <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>kdm</sysconfig_value> </sysconfig_entry> </sysconfig> There must be something I' missing somewhere, but I can't find it. Any clues? Thanks. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 2

[opensuse-autoinstall] autoyast-Profile causes yast-Segfault
by Daniel Spannbauer 01 Dec '11

01 Dec '11

Hello, strange problem: I have a autoyast-xml-File (made from a set of xml-sniplets) which causes a Segfault of yast2 when I load that profile in yast2-Auto-Installation-Module. YaST got signal 11 at YCP file Profile.ycp:88 /sbin/yast2: line 423: 31763 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS System is openSuSE 11.4, autoyast2-installation-2.20.9-1.2.1, autoyast2-2.20.9-1.2.1, Can I check the validity of the profile without Yast? Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 2

[opensuse-autoinstall] How to remove entry from XML file with merging?
by Joschi Brauchle 30 Nov '11

30 Nov '11

Hello everyone, I have the following problem: We have an autoyast base-profile.xml for all our Linux machines, which includes --------- <software> <remove-packages config:type="list"> <package>NetworkManager</package> </remove-packages> </software> --------- because all those machines use the traditional ifup method. Now, I want to integrate a mobile workstation, which should use NetworkManager to manage LAN/WLAN/VPN connections. Thus, I would somehow have to remove the above entry by merging with another XML. Otherwise I cannot install NetworkManager as a regular <package>. I guess that is not possible? I can only add/change entries by merging with another XMl, but not remove thing... correct? (Of course I could remove that line from the base-profile.xml, but so far I'm looking for a better solution) Is it possible to work on the final installation XML file (after merging is done) with a pre-script? How would I get the path to that file? So far, it looks like it is burried somewhere in /tmp/Yast-XXXXXX-YYYYY/ during installation... Thanks for your help! Regards, Joschi Brauchle

2 3

[opensuse-autoinstall] opensuse 11.4 and Post-Packages
by Daniel Spannbauer 25 Nov '11

25 Nov '11

Hello, yes, I know, it is a known bug. But I have to install some packages as postpackes. I searched and found a solution, but I think I do anythuing wrong at it. I tried to fix it like described here: https://bugzilla.novell.com/show_bug.cgi?id=679435#c45 So, my xml looks as follows.... --------------------- [...] <service> <service_name>smbfs</service_name> <service_start>disable</service_start> </service> <service> <service_name>splash</service_name> <service_start>disable</service_start> </service> </services> </runlevel> <x11> <color_depth config:type="integer">16</color_depth> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <monitor_device>1280X1024@60HZ</monitor_device> <monitor_vendor>--> VESA</monitor_vendor> </monitor> <resolution>1280x1024 (SXGA)</resolution> <window_manager>kde</window_manager> </x11> <chroot-scripts config:type="list"> <script>  <chrooted config:type="boolean">true</chrooted> <filename>fix_postinstall_bug.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/bash ( while [ ! -f /var/lib/YaST2/installation_disabled_steps ]; do sleep 1 done cp /var/lib/YaST2/installation_disabled_steps /var/lib/YaST2 /installation_disabled_steps.bkp cat /var/lib/YaST2/installation_disabled_steps.bkp | grep -v "rpmcopy_secondstage" > /var/lib/YaST2/installation_disabled_steps) &]]> </source> </script> </chroot-scripts> </profile> ---------------------------- But this didn't work. So, I think I have an error at the syntax. Or do I have to put the chroot-scripts elsewhere in the xml? Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] change / bug with init scripts in opensuse 12.1 ?
by winfried_mb2＠xmsnet.nl 22 Nov '11

22 Nov '11

I tried to upgrade my autoyast configuration to opensuse 12.1. In my autoinst.xml I have the section below. The init script worked fine in openSuse 11.4, but isn't executed with 12.1 after autoyast finishes. The script is still in /var/adm/autoinstall/init.d When I reboot the machine myself, the script *is* executed. Could this be a change or bug related to the new systemd init tool? thanks in advance W. Dobbe <scripts> <chroot-scripts config:type="list"> (deleted) </chroot-scripts> <init-scripts config:type="list"> <script> <chrooted config:type="boolean">false</chrooted> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/sh chvt 1 exec < /dev/tty1 > /dev/tty1 cd /opt/vidigo_li/scripts/postinstall /opt/vidigo_li/scripts/postinstall/run_postinstall.sh ]]></source> </script> </init-scripts> </scripts> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 4

[opensuse-autoinstall] Mount points
by Michael Welle 22 Nov '11

22 Nov '11

Hello, I have a somewhat odd question which arose from merging the autoyast process with some third party tools. During the installation the target filesystem is mounted on /mnt in the ram disk. Can I configure this mount point? The third party tools use this mount point also. Trying to mount or umount something on /mnt while the installer is running leads to some funny effects ;). Regards hmw -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html Flood - Your friendly network packet generator http://www.c0t0d0s0.de/flood/flood.html -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 6

[opensuse-autoinstall] Set starting block of first partition
by Alexander Holte-Davidsen 22 Nov '11

22 Nov '11

Hello fellow autoyast'ers, I have a questions that I can't seem to find the answer for in the autoyast documentation. The question is quite simple: I want the first partition on each disk to start on block 64 or preferably block 16384. Is there anyway to accomplish this using autoyast? >From what I can see, the partition starts on block 63 on systems installed with autoyast. I can't see any options for this in the partition-section of autoyast... Disk /dev/sda: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x0008dbe5 Device Boot Start End Blocks Id System /dev/sda1 * 63 273104 136521 83 Linux Thanks, Alexander Holte-Davidsen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 2

[opensuse-autoinstall] NFS options for network install
by Geoff.Buckingham＠thomsonreuters.com 16 Nov '11

16 Nov '11

When giving the following kernel argument in menu.lst for PXE grub they get applied to the nfs mount to fetch the squashfs images, however the later mount for yast to install rpms from NFS server ignores these and takes default options. Is there another way to control this? Some other way to provide nfs options to the install? nfsopts=tcp,vers=3,rsize=32768,wsize=32768 Default behaviour seems to use very large [r|w]size and udp leading to poor performance and occasional timeout. (Observed in SLES 11SP1) Geoff Buckingham 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 To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] Adding own RPMs to 11.4-Installation-DVD
by Daniel Spannbauer 14 Nov '11

14 Nov '11

Hello, until now, we created our own Installation-Media with 10.2. We only added the RPMs to the DVD, that are going to be installed. So we kept the DVD-Image small for downloading by our Customers (only 1.2 GB instead of 4 GB). Now, we have to do the same thing with 11.4, but I have problems with the signature. We create a yast-Installation-Source, put the boot-Environment (initrd, kernel etc.) in the right places, add the License-files, add the SuSE-RPMs and our own RPMs to i586, i686, create the xml-File for Autoyast etc. (like we did it with 10.2) MD4SUMS etc. are created automatically. The gpg-Key ist added to the initrd (as described here: http://users.suse.com/~ug/AutoYaST_FAQ.html#bB) the new sha1sum of the initrd is put in the content-file and this file is signed with the key that was put into the initrd. So, everything should be fine (I think). But everytime we start the installation, yast complains about an invalid signature of the content-file. When I switch to a console is see, that the key is directly in / of the running system. The installkey.gpg of opensuse is also in that place. Can anybody tell me what I'm doing wrong here? Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 5