- openSUSE Autoinstall

[opensuse-autoinstall] What should my module return?
by Erico Mendonça 02 Jun '10

02 Jun '10

I'm running a self-written YaST module at the start of the installation (via control.xml, inserted right before the prepareprogress module), and even though my modules finishes with success, I get a YaST error (red screen). Do I need to return/set any specific values? I already tried returning true/false/0/1/nil/GetInstArgs(0), etc, all with the same result. There doesn't seem to be any specific error messages in the log, it just informs that the YaST client module was finished. -- -- Erico -- 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] grub boots wrong kernel after stage 1
by Antje Bendrich 01 Jun '10

01 Jun '10

Good morning, we are using PXE to boot into autoyast and install the packages from local repositories via http and are having a problem since Suse released a new kernel package in April. Everything works fine up to the first reboot after finishing stage 1. Then grub has two kernels to choose from: 2.6.31.12-0.1-default, which is the kernel of the autoyast installation, and 2.6.31.12-0.2-desktop, which is the newest kernel freshly installed from our repositories. Grub boots the 2.6.31.12-0.1-default-kernel, complains (with good cause) 'unable to canonicalize path "/lib/modules/2.6.31.12-0.1-default/systemtap/preloadtrace.ko": No such file or directory' and continues booting, but fails to load the modules for the network card and the graphics card (and probably others). This leads to X not starting and -worse- autoyast failing to load some configuration files via ftp, configured like this: <file> <file_path>/etc/somefile</file_path> <file_owner>root:root</file_owner> <file_permissions>644</file_permissions> <file_location>ftp://somehost/files/etc/somefile</file_location> </file> Autoyast does not complain very visibly about this failure while it's running. The files not loaded do exist on the system afterwards, alas with a size of 0 bytes. The normal system logs do not contain that first boot, so it is kinda hard to figure out exactly why the final system does not work like it should. If I babysit the installation and manually choose the other kernel version (2.6.31.12-0.2-desktop) when grub comes up after stage 1, everything continues like it should, but I don't really want to wait to hit "down down return" at the exact right time... So: Why is the installation kernel still configured in grub when it is not fully functional anymore? How do I get rid of it at this early time? Or is our error something else entirely? Thanks in advance, Antje -- Antje Bendrich (Team IT-Services), Phone +49 40 808077-642 DFN-CERT Services GmbH, https://www.dfn-cert.de/, Phone +49 40 808077-555 Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.: DE 232129737 Sachsenstraße 5, 20097 Hamburg/Germany, CEO: Dr. Klaus-Peter Kossakowski

2 5

[opensuse-autoinstall] Cannot create raid with autoyast on 11.3 M7
by Peter Pointner 01 Jun '10

01 Jun '10

Hello, I try to create a raid-1 with autoyast on opensuse-11.3 Milestone 7 x86_64. It fails with "Error while configuring partitions. Try again." The same xml-file works with opensuse-11.2 x86_64. Did I miss relevant changes between 11.2 and 11.3? Should I provide more information here on the list or open a bug on bugzilla? Peter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] SLED-11-SP1 install failing claiming it can't find autoyast2-installation
by Lonni J Friedman 27 May '10

27 May '10

Greetings, I'm trying to get SLED-11-SP1 installing via autoyast, but the install (for both i686 & x86_64) fails as soon as it reaches the 'Create partition plans' step with a pop-up error stating: These packages could not be found in the software repositories: autoyast2-installation I'm rather puzzled by this, as I've got that very RPM on my installation server under $OS/suse/noarch Anyone have any suggestions? thanks -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand https://netllama.linux-sxs.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] correct way to set hostname to FQDN in SLES 11 and openSuSE 11.2
by Yiping Zhang 27 May '10

27 May '10

Hi, I am using autoyast to install both SLES11 and openSUSE 11.2 hosts. I want all host to use FQDN for hostname, but for unknown reasons, some of them do, and some others only have a short name without domain part. The autoyast.xml file is auto generated for each node, and only FQDN are referenced in there. I have following sections in autoyast.xml (real host name replaced, to protect innocent): <host> <hosts config:type="list"> <hosts_entry> <host_address>127.0.0.1</host_address> <names config:type="list"> <name>localhost </name> </names> </hosts_entry> <hosts_entry> <host_address>10.1.68.86</host_address> <names config:type="list"> <name>myhostname,example.com</name> </names> </hosts_entry> </hosts> </host> and <dns> <domain>example.com</domain> <hostname>myhostname.example.com</hostname> <nameservers config:type="list"> ... </nameservers> <searchlist config:type="list"> ... </searchlist> </dns> I also have following line in /etc/sysctl.conf: kernel.hostname = myhostname.example.com Even after reboot, above sysctl.conf entry doesn't seem to do anything, or some scripts has changed hostname after /etc/init.d/boot.d/S13boot.sysctl script. So my question is how should I set hostname during initial set up ? Thanks, -- 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] CheckMedia
by Erico Mendonça 26 May '10

26 May '10

I'm trying to use the CheckMedia functions from within my customized YaST module. It appears to be working fine, as I can detect drives/start/stop/fetch progress. However, the customized media I created fails verification. The read test finishes ok, but I get an "md5sum not computed" error. My question is, where is the media descriptor/MD5 stored on the media? How do I generate it? It seems to ignore the "content" files with SHA1 checksums. -- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] 2 questions auf configuration
by prengel 10 May '10

10 May '10

Hallo, I using autoyast only once per year. My problems: 1) I made a xml-file basing on a working system. Now the network-card-detection doesn t work. In my cloned system 2 cards are detected. The old one and the new one without any configuration. 2) The kde-configuration: What ist the option to configure a german keyboard-layout. Thanks Ralf Prengel Manager Customer Care Comline AG Hauert 8 D-44227 Dortmund/Germany Fon +49 231 97575 904 Fax +49 231 97575 257 Mobil +49 151 10831 157 EMail Ralf.Prengel(a)comline.de www.comline.de Vorstand Stephan Schilling, Erwin Leonhardi Aufsichtsrat Dr. Franz Schoser (Vorsitzender) HR Dortmund B 14570 USt.-ID-Nr. DE 124727422 Für die Erstellung unserer Dokumente benutzen wir die Produkte aus dem Microsoft Office 2007 Paket. Sollte sich ein Anhang in der Mail befinden, der mit einer älteren Office Version nicht geöffnet werden kann, installieren Sie bitte das Compatibility Pack für Office 2007. http://www.microsoft.com/downloads/details.aspx?FamilyID=941b3470-3ae9-4aee… -- 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] Media check with autoyast
by Erico Mendonça 07 May '10

07 May '10

Is there a way to use call/use the installation media check feature from within an autoyast profile? I would like to check the media before the unattended installation. If the media is bad, it shouldn't even try to install. -- -- Erico -- 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] CRYPT=md5 to CRYPT=DES
by Dirk.Lohmann＠Bertelsmann.de 20 Apr '10

20 Apr '10

Hello In SLES11 I want to change in /etc/default/passwd The Entry CRYPT=md5 to CRYPT=DES In got this in my xml file but this is not working <security> <group_encryption>des</group_encryption> <passwd_encryption>des</passwd_encryption> </security> Dirk Lohmann -- 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] SLES11 SAP xml
by Dirk.Lohmann＠Bertelsmann.de 14 Apr '10

14 Apr '10

Hello I have to setup xml file for Sap server installation. Is there a way to set this value automatily in xml file ? Do not set Write Hostname to /etc/hosts Otherwise There is an entry in /etc/hosts 127.0.0.2 <hostname>.<domain> <hostname> Setzen Sie während der Netzwerkkonfiguration nicht die Option "Write Hostname to /etc/hosts". (Diese Option wird in Service Pack 1 in "Assign Hostname to Loopback IP" umbenannt.) Andernfalls wird ein zusätzlicher Eintrag in /etc/hosts angelegt: 127.0.0.2 <hostname>.<domain> <hostname> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1