January 2014 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] State of Autoyast for OpenSUSE 13.1
by Joschi Brauchle 18 Dec '14

18 Dec '14

Hi everyone, sorry for asking such a general question, but what is the state of AutoYast for OpenSUSE 13.1? I converted a completely working XML from a 12.3 installation to 13.1. The autoinstallation finishes, but the installed system is - missing Sysconfig configuration from <sysconfig> section - has not run any of the <post-scripts> and <init-scripts> - does not accept the root password configured in the <users> section - is missing all files installed from the <files> section of the XML - misses LDAP and KRB config from <ldap> and <kerberos> - services are not configured as in <services> and many more problems. To me it looks like the complete second stage is missing, as all those things are done there. Is this a known problem? Or are there known problems for 13.1? Did anyone succeed with AutoYast and 13.1 with any of the above mentioned XML sections? The y2log file from second stage is very small and does not show any errors... Best regards, Joschi Brauchle

6 25

[opensuse-autoinstall] Network interface configuration and systemd's predictable network interface names
by David Huffman 28 Jan '14

28 Jan '14

Hi, thanks to systemd's predictable network interface names (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac…) I have no way to tell what my eth0 interface is actually going to be called ahead of time as it varies amongst different computers. Is there anyway to affect all available network interfaces with autoyast? <networking> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>How do I make it affect all devices? Or at least systemd's equivalent to eth0.</device> <startmode>onboot</startmode> </interface> </interfaces> </networking> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

5 4

[opensuse-autoinstall] Passing module parameters via pxelinux?
by Frank Steiner 15 Jan '14

15 Jan '14

Hi, SLES 11 SP3 has a problem in the hpsa module not supporting the P410i controller found e.g. on HP ProLion ML350 G6. Novell suggest passing the hpsa_allow_any module parameter: http://www.novell.com/support/kb/doc.php?id=7014067 I fail to do that in AY. We boot via PXE and I load the needed modules for the raid controllers e.g. with "insmod=hpsa" in te pxelinux.cfg file. But I didn't find a way to pass the hpsa_allow_any parameter here. Is it possible somehow? Putting hpsa_allow_any as normal kernel parameter (just "hpsa_allow_any") did not work, neither did "hpsa_allow_any=1" right after the insmod=hpsa. I tried putting <init> <info_file> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf insmod=hpsa hpsa_allow_any=1 # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> in my control file, but before linuxrc loads the cciss module before considering the XML file. Same with passing "info=nfs://myserver/mypath/info" and "insmod: hpsa hpsa_allow_any=1" in the info file. Seems to come in too late. Is there a way to a) either tell linuxrc it should blacklist the cciss module b) or pass the hpsa_allow_any parameter to linuxrc in the pxelinux.cfg file c) or let linuxrc consider the info or xml file before the automatic hardware scan? 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 To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 4