From Vincent.Taluskie@emc.com Thu Jan 17 18:46:51 2013 From: "Taluskie, Vincent" To: autoinstall@lists.opensuse.org Subject: [opensuse-autoinstall] implement minimum hardware checking Date: Thu, 17 Jan 2013 13:45:43 -0500 Message-ID: <84F5D2A8-FF14-450B-B4B9-2EA92075F4D1@emc.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1738634172138692026==" --===============1738634172138692026== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, I would like to implement minimum hardware checking for SUSE 11 (SP1) using a= utoyast installation. It looks like using AutoYast rules.xml file would b= e a good way to handle this: Ideally, if the hardware meets the requirement= s, then select the installation profile (passes_requirements.xml) and proceed= as normal. One concept I am having a hard time finding docs around is how to flag failur= e during install. If there's not enough memory or disk to successfully supp= ort the application I am installing, I would like to return the fails_require= ments.xml profile and show the user an abort message rather than doing the in= stall. Does someone have a pointer to this kind of scenario? I have been searching = but not finding much discussion around handling failure during the auto insta= ll. =20 Thanks in Advance, vince --=20 To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org --===============1738634172138692026==-- From HansJoachim.Ehlers@eumetsat.int Thu Jan 17 18:59:51 2013 From: Hans-Joachim Ehlers To: autoinstall@lists.opensuse.org Subject: [opensuse-autoinstall] RE: implement minimum hardware checking Date: Thu, 17 Jan 2013 19:58:59 +0100 Message-ID: In-Reply-To: <84F5D2A8-FF14-450B-B4B9-2EA92075F4D1@emc.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1868301923576074345==" --===============1868301923576074345== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Section 6.1.2. Custom Rules at http://doc.opensuse.org/projects/autoyast/ru= lesandclass.html gives what you are looking for ( Or use a pre script )=20 Extract and translation: ... * exact @custom1(a)_requirements.xml true .............................................................................= ................................ -----Original Message----- From: Taluskie, Vincent [mailto:Vincent.Taluskie(a)emc.com]=20 Sent: Thursday, January 17, 2013 7:46 PM To: opensuse-autoinstall(a)opensuse.org Subject: [opensuse-autoinstall] implement minimum hardware checking Hi, I would like to implement minimum hardware checking for SUSE 11 (SP1) using a= utoyast installation. It looks like using AutoYast rules.xml file would b= e a good way to handle this: Ideally, if the hardware meets the requirement= s, then select the installation profile (passes_requirements.xml) and proceed= as normal. One concept I am having a hard time finding docs around is how to flag failur= e during install. If there's not enough memory or disk to successfully supp= ort the application I am installing, I would like to return the fails_require= ments.xml profile and show the user an abort message rather than doing the in= stall. Does someone have a pointer to this kind of scenario? I have been searching = but not finding much discussion around handling failure during the auto insta= ll. =20 Thanks in Advance, vince --=20 To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org --=20 To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org --===============1868301923576074345==-- From HansJoachim.Ehlers@eumetsat.int Thu Jan 17 19:38:15 2013 From: Hans-Joachim Ehlers To: autoinstall@lists.opensuse.org Subject: RE: [opensuse-autoinstall] RE: implement minimum hardware checking Date: Thu, 17 Jan 2013 20:37:27 +0100 Message-ID: In-Reply-To: <094C9E56-9CBB-4746-AF0D-E6323E1CB5C1@emc.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4125205071540225407==" --===============4125205071540225407== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sorry not but i think you are able to use the ask function of autoyast. http://doc.opensuse.org/projects/autoyast/configuration.html#CreateProfile.Ask See basically create a minimum install profile menationed in=20 http://users.suse.com/~ug/AutoYaST_FAQ.html=20 section: 1.4 What is smallest autoyast profile that makes sense? and combine that with the ask profile. Now you should have your minimum profi= le with a box that tells the user that the install faild because of ... and h= e can do nothing or reboot .... BTW: Why not using the rules.xml and a script within to tell the user that th= e installation failed ? =20 hth Hajo -----Original Message----- From: Taluskie, Vincent [mailto:Vincent.Taluskie(a)emc.com]=20 Sent: Thursday, January 17, 2013 8:16 PM To: Hans-Joachim Ehlers Subject: Re: [opensuse-autoinstall] RE: implement minimum hardware checking Thanks for your response, I will continue with the rules approach. The mai= n profile I have now focuses on a successful install of my application. I n= eed the simplest profile for failure that doesn't try to install any software= - just abort with an error message. Is there an example of a simple failure profile you've seen? =20 Vince On Jan 17, 2013, at 11:58 AM, Hans-Joachim Ehlers wrote: >=20 --=20 To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org --===============4125205071540225407==-- From Vincent.Taluskie@emc.com Thu Jan 17 19:44:45 2013 From: "Taluskie, Vincent" To: autoinstall@lists.opensuse.org Subject: Re: [opensuse-autoinstall] implement minimum hardware checking Date: Thu, 17 Jan 2013 14:43:54 -0500 Message-ID: In-Reply-To: <84F5D2A8-FF14-450B-B4B9-2EA92075F4D1@emc.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1211132758521501963==" --===============1211132758521501963== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I got a confirmation from another user about rules being a good way to do thi= s checking. Thank you! What I am looking for now is a simple failure.xml profile - put up a message = to the user that says "Unfortunately this hardware does not meet requirements= to support the application" and halt with no further installation. Anyone have something like that handy? All the profiles I've seen are geare= d around successful installation not handling a case where the hardware doesn= 't meet necessary requirements and handling the error case. Thanks, vince On Jan 17, 2013, at 11:45 AM, Taluskie, Vincent wrote: > Hi, >=20 > I would like to implement minimum hardware checking for SUSE 11 (SP1) using= autoyast installation. It looks like using AutoYast rules.xml file would= be a good way to handle this: Ideally, if the hardware meets the requireme= nts, then select the installation profile (passes_requirements.xml) and proce= ed as normal. >=20 > One concept I am having a hard time finding docs around is how to flag fail= ure during install. If there's not enough memory or disk to successfully su= pport the application I am installing, I would like to return the fails_requi= rements.xml profile and show the user an abort message rather than doing the = install. >=20 > Does someone have a pointer to this kind of scenario? I have been searchin= g but not finding much discussion around handling failure during the auto ins= tall. =20 >=20 > Thanks in Advance, >=20 > vince >=20 >=20 > --=20 > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org >=20 >=20 --=20 To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org --===============1211132758521501963==-- From erico.mendonca@gmail.com Thu Jan 17 19:51:52 2013 From: Erico =?utf-8?q?Mendon=C3=A7a?= To: autoinstall@lists.opensuse.org Subject: [opensuse-autoinstall] keeping installed packages Date: Thu, 17 Jan 2013 17:50:49 -0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3214570875616842773==" --===============3214570875616842773== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Is there a variable in AutoYaST to make it keep the package cache on disk, like zypper does with "--download-only"? My idea was finding a way to make all packages used during installation available as a local repo in the hard disk as a makeshift "recovery" partition. So far I couldn't find a way other than copying the repos directly from the DVD... -- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org --===============3214570875616842773==-- From krienke@uni-koblenz.de Tue Jan 22 14:12:54 2013 From: Rainer Krienke To: autoinstall@lists.opensuse.org Subject: [opensuse-autoinstall] Problem running systemd service script after autoyast installation Date: Tue, 22 Jan 2013 15:12:05 +0100 Message-ID: <50FE9E35.5020809@uni-koblenz.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7516936770362812140==" --===============7516936770362812140== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hello, since opensuse 12.2 I use systemd instead of sysv-init. Most of the systems I install this way need a full integration in our local university network, which means the need of autofs as well as NIS and LDAP and more modifications to the system. Installation of such linux systems is based on an autoyast file I wrote. Part of this autoinstallation is a autoyast-post script that creates a systemd lfinalinstall.service file, that should start later on to do the network integration and all the rest. Before opensuse 12.2 this was done via a /etc/init.d/lfinalinstall init script that did just the same like the systemd lfinalinstall.service file does now. My problem is that I would like the service script to execute right after the autoyast installation of linux has finished (without a further reboot). So the autoyast installtion is done and the system comes up to the default runlevel starting kdm and now the service script should start. This used to work fine for the /etc/init.d script in earlier suse versions but does no longer work for 12.2 using systemd. The service file is activated but won't start. Only If I reboot the system after the complete autoyast installation one more time the script runs just fine, but not after the autoyast driven installation when it boots up to the default runlevel the first time, without one more reboot. The lfinalinstall.service file that is created by the autoyast post script (also tried chroot script) looks like below. After the .service file has been written I call /bin/systemctl enable lfinalinstall.service as well as a /bin/systemctl daemon-reload command. [Unit] Description=install script After=apparmor.service local-fs.target network.service Before= ConditionPathExists=/var/lib/lfinal/_run_install_ [Service] Type=oneshot Environment=SYSTEMD_NO_WRAP=1 TERM=linux ExecStart=/var/lib/lfinal/lfinalinstall # do network integration RemainAfterExit=yes TimeoutSec=0 ExecStartPost=/bin/rm -f /var/lib/lfinal/_run_install_ StandardInput=tty [Install] WantedBy=default.target The dependency file /var/lib/lfinal/_run_install_ is also in place. And of course the real script to do the job /var/lib/lfinal/lfinalinstall is also available and executable. After autoyast istallation has completed a "systemctl status lfinalinstall.service" shows this: $ systemctl status lfinalinstall.service lfinalinstall.service - lfinalinstall install script Loaded: loaded (/lib/systemd/system/lfinalinstall.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/lfinalinstall.servic Now I wonder why this script won't start after the installation has finished and the system boots up to the default runlevel? Does anyone have an idea or perhaps an idea how to debug this problem? The autoyast postinstall.log file shows that the lfinalinstall.service file has been created and enabled and that "systemctl daemon-reload" has been executed. Thanks 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 --===============7516936770362812140== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIuMC4xOSAoR05V L0xpbnV4KQpDb21tZW50OiBVc2luZyBHbnVQRyB3aXRoIFRodW5kZXJiaXJkIC0gaHR0cDovL3d3 dy5lbmlnbWFpbC5uZXQvCgppRVlFQVJFQ0FBWUZBbEQrbmpvQUNna1FhbGR0amMvS0RFcDloUUNn akRrK0Jna082TnYwbVEvMzhWNTREQnlnCldlVUFvS3FUS292K3dUVHVrcGdqSHN0V1JWVEM0TTZs Cj00andZCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============7516936770362812140==-- From joschi.brauchle@tum.de Wed Jan 23 08:59:47 2013 From: Joschi Brauchle To: autoinstall@lists.opensuse.org Subject: Re: [opensuse-autoinstall] Problem running systemd service script after autoyast installation Date: Wed, 23 Jan 2013 09:58:56 +0100 Message-ID: <50FFA650.6010004@tum.de> In-Reply-To: <50FE9E35.5020809@uni-koblenz.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3962311810224932631==" --===============3962311810224932631== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I think this might be related to https://bugzilla.novell.com/show_bug.cgi?id=769924 AutoYast only enables the required services during installation. Then, it used to do an "init $runlevel" to start them all up. The systemd equivalent does not seem to work correctly at this point. Basically, i have come to the conclusion that for >12.2, you currently HAVE TO reboot to get a working system with all services running. All workarounds I have tried have failed so far... On 01/22/2013 03:12 PM, Rainer Krienke wrote: > Hello, > > since opensuse 12.2 I use systemd instead of sysv-init. Most of the > systems I install this way need a full integration in our local > university network, which means the need of autofs as well as NIS and > LDAP and more modifications to the system. > > Installation of such linux systems is based on an autoyast file I > wrote. Part of this autoinstallation is a autoyast-post script that > creates a systemd lfinalinstall.service file, that should start later on > to do the network integration and all the rest. Before opensuse 12.2 > this was done via a /etc/init.d/lfinalinstall init script that did just > the same like the systemd lfinalinstall.service file does now. > > My problem is that I would like the service script to execute right > after the autoyast installation of linux has finished (without a further > reboot). So the autoyast installtion is done and the system comes up to > the default runlevel starting kdm and now the service script should start. > > This used to work fine for the /etc/init.d script in earlier suse > versions but does no longer work for 12.2 using systemd. The service > file is activated but won't start. Only If I reboot the system after the > complete autoyast installation one more time the script runs just fine, > but not after the autoyast driven installation when it boots up to the > default runlevel the first time, without one more reboot. > > The lfinalinstall.service file that is created by the autoyast post > script (also tried chroot script) looks like below. After the .service > file has been written I call /bin/systemctl enable lfinalinstall.service > as well as a /bin/systemctl daemon-reload command. > > > [Unit] > Description=install script > After=apparmor.service local-fs.target network.service > Before= > ConditionPathExists=/var/lib/lfinal/_run_install_ > > [Service] > Type=oneshot > Environment=SYSTEMD_NO_WRAP=1 TERM=linux > ExecStart=/var/lib/lfinal/lfinalinstall # do network integration > RemainAfterExit=yes > TimeoutSec=0 > ExecStartPost=/bin/rm -f /var/lib/lfinal/_run_install_ > StandardInput=tty > > [Install] > WantedBy=default.target > > The dependency file /var/lib/lfinal/_run_install_ is also in place. And > of course the real script to do the job /var/lib/lfinal/lfinalinstall is > also available and executable. > After autoyast istallation has completed a "systemctl status > lfinalinstall.service" shows this: > > $ systemctl status lfinalinstall.service > lfinalinstall.service - lfinalinstall install script > Loaded: loaded (/lib/systemd/system/lfinalinstall.service; > enabled) > Active: inactive (dead) > CGroup: name=systemd:/system/lfinalinstall.servic > > Now I wonder why this script won't start after the installation has > finished and the system boots up to the default runlevel? Does anyone > have an idea or perhaps an idea how to debug this problem? The autoyast > postinstall.log file shows that the lfinalinstall.service file has been > created and enabled and that "systemctl daemon-reload" has been executed. > > Thanks > Rainer > -- Dipl.-Ing. Joschi Brauchle, M.S. 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/ --===============3962311810224932631== Content-Type: application/pkcs7-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIME-Version: 1.0 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIObzCCBCEw ggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0 c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQD ExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5 MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJ MSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUA A4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKm FNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItq aACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMq ljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYD VR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9E b3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYD VR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqz K50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IB AQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvh ERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0J a6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoL BzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIEzDCCA7SgAwIBAgIECfEKYzANBgkqhkiG 9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4GA1UECxMHREZO LVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4XDTA3MDIxMzEwMDMw MVoXDTE5MDIxMjAwMDAwMFowYDELMAkGA1UEBhMCREUxKTAnBgNVBAoTIFRlY2huaXNjaGUgVW5p dmVyc2l0YWV0IE11ZW5jaGVuMSYwJAYDVQQDEx1aZXJ0aWZpemllcnVuZ3NzdGVsbGUgZGVyIFRV TTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKjv6NPYBFzJ+ZELc6JfE/5aga/7K7LW MVBHZvohdJZGd31pN9QEfzQeph0kiqsm1X5kHraPtTc9jMH8SLASBI45JppNSSYRfw6j6RjKA7PU StRfV0dq5cBPBl5FpxAY23lAzMzY+6EQEq3/hS8Ia3zG5Q5saJsc+9B2So8+gvaVwZhrWhe7Nhyv VqYMiBpTE9fbViah3Ur5VdDpcGbsb/BqRDxRrOCjQdNQ6TCQHfIUEDTQMW/czj1wbgLxrp8sB5Xl wMPX7c2Do+yByWbcrkitdGEeagcWqC1gc8pD/f8PJIoVeW4cy60PjHRIfYC0NBVvg9P0viuwFEyW M17brI8CAwEAAaOCAZIwggGOMA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0PBAQDAgEGMB0GA1UdDgQW BBSdnyPwGRt+xyNdJyrMpTY6pmnliTAfBgNVHSMEGDAWgBRJt8bP6D0ff+pEexMp9/EKcD7eZDCB iAYDVR0fBIGAMH4wPaA7oDmGN2h0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2Ev cHViL2NybC9jYWNybC5jcmwwPaA7oDmGN2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJv b3QtY2EvcHViL2NybC9jYWNybC5jcmwwgaIGCCsGAQUFBwEBBIGVMIGSMEcGCCsGAQUFBzAChjto dHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNy dDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv Y2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAINoNtnDCyUwcPDc68e/u5O/ffcs +r4x4OeRxKtYXd3dRCyuCoxJAhhepSk2oQc89QhWFOOBxeT7KosoCsn+htLtgnZLj4R/yNX8Memz YP170OZ/m4X9vmRhty+gh90kCSZlaQgT9MfV+7g1C6QgelUDV8N68Nd4Pl1IMBWkAkZZLcT9/Hgo l59FGhFDF1uFx7Su+vYBlO3g+tHnI18XJBDOs2abHRXI5PmYcvtGirsVMfWcs0ooZOonYw5pvWI+ N8dat9DNIvgRdoChTOKdvPURjtkY3kJkvdAfPKsf/ZCj3HhdEn0b6VZQqDj7VJRCvFOL0tqSc2wU rHLRw/9Mu2gwggV2MIIEXqADAgECAgQQ26t7MA0GCSqGSIb3DQEBBQUAMGAxCzAJBgNVBAYTAkRF MSkwJwYDVQQKEyBUZWNobmlzY2hlIFVuaXZlcnNpdGFldCBNdWVuY2hlbjEmMCQGA1UEAxMdWmVy dGlmaXppZXJ1bmdzc3RlbGxlIGRlciBUVU0wHhcNMTAxMDE4MTEyMjIwWhcNMTMxMDE3MTEyMjIw WjCB3TELMAkGA1UEBhMCREUxDzANBgNVBAgTBkJheWVybjERMA8GA1UEBxMITXVlbmNoZW4xKTAn BgNVBAoTIFRlY2huaXNjaGUgVW5pdmVyc2l0YWV0IE11ZW5jaGVuMT4wPAYDVQQLEzVGYWt1bHRh ZXQgZnVlciBFbGVrdHJvdGVjaG5payB1bmQgSW5mb3JtYXRpb25zdGVjaG5pazEYMBYGA1UEAxMP Sm9zY2hpIEJyYXVjaGxlMSUwIwYJKoZIhvcNAQkBFhZqb3NjaGkuYnJhdWNobGVAdHVtLmRlMIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2cF6tIlKUNmY12XEz8gAtWLnifpPKQ06VhsH NH3FRa3qqpScW96ypYRLz3HTot2GdY7JSmEKSx7p5ehlOKbEcKsr57nbVzOkVW/0SmmWjroxzXe1 e4KTw9QmpxXXQI5FuUXRQoXZhgkPJWXa31uEzixbWIO4DHzM2TuEidFk3y2zcyA4j6g8flb8zMMS QjqAafTDA8CfA+j7cJZOCk30UZYNRuGLJi6tJi1nmaDy1ZMDAQA5P8nQJ3BpJGCxWwm5A0ppEBlK PFWjproJn8NErCRHRhWWcKkHwzwI48zB0bnrsKqMQVpkgSquGD94dbyDAIbht5M8HSE8eqmWj7Ug 6QIDAQABo4IBuDCCAbQwCQYDVR0TBAIwADALBgNVHQ8EBAMCBeAwKQYDVR0lBCIwIAYIKwYBBQUH AwIGCCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBSqoAQm9/5Acan0m0kcMmLzRDUuFDAf BgNVHSMEGDAWgBSdnyPwGRt+xyNdJyrMpTY6pmnliTAhBgNVHREEGjAYgRZqb3NjaGkuYnJhdWNo bGVAdHVtLmRlMHcGA1UdHwRwMG4wNaAzoDGGL2h0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvdHVtLWNh L3B1Yi9jcmwvY2FjcmwuY3JsMDWgM6Axhi9odHRwOi8vY2RwMi5wY2EuZGZuLmRlL3R1bS1jYS9w dWIvY3JsL2NhY3JsLmNybDCBkgYIKwYBBQUHAQEEgYUwgYIwPwYIKwYBBQUHMAKGM2h0dHA6Ly9j ZHAxLnBjYS5kZm4uZGUvdHVtLWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDA/BggrBgEFBQcwAoYz aHR0cDovL2NkcDIucGNhLmRmbi5kZS90dW0tY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqG SIb3DQEBBQUAA4IBAQCnQxDlwDKK5DSFIj5NaYxqCc3WxO2X/VXL+MSw+3cgsp9W9pYsnWSUoYY3 2lHoOj45LNGJWZ4ikueDiG20j23n/ao+G8lwVh3D+UPikmFPp2PWg3GlbRwQ33cbAxVIJ+XsOJup bQDfKh3U4AV91bdd/Eug3OAGOMbtB84HgD9Gsy1xEUDHuq4Ol24JUuZdimNPHUyMvk4bth+CECNc DjiUZ6kJ24m0AKE1GqkRbk7hyfqwhSCUOP2riJ6JBQZf0U9sK91TjdNF0+he8SZpDJtJdMFZ75TO 5Rwr7KLh6v6IefYYPo4f/IfdtMOXLIVBpOWj/snSrDeGoO9X62zPufqGMYIDUjCCA04CAQEwaDBg MQswCQYDVQQGEwJERTEpMCcGA1UEChMgVGVjaG5pc2NoZSBVbml2ZXJzaXRhZXQgTXVlbmNoZW4x JjAkBgNVBAMTHVplcnRpZml6aWVydW5nc3N0ZWxsZSBkZXIgVFVNAgQQ26t7MAkGBSsOAwIaBQCg ggG/MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDEyMzA4NTg1 NlowIwYJKoZIhvcNAQkEMRYEFPtTVT0mp7SbJ/iUREvoW7ZEc0O+MGwGCSqGSIb3DQEJDzFfMF0w CwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwdwYJKwYBBAGCNxAEMWowaDBgMQsw CQYDVQQGEwJERTEpMCcGA1UEChMgVGVjaG5pc2NoZSBVbml2ZXJzaXRhZXQgTXVlbmNoZW4xJjAk BgNVBAMTHVplcnRpZml6aWVydW5nc3N0ZWxsZSBkZXIgVFVNAgQQ26t7MHkGCyqGSIb3DQEJEAIL MWqgaDBgMQswCQYDVQQGEwJERTEpMCcGA1UEChMgVGVjaG5pc2NoZSBVbml2ZXJzaXRhZXQgTXVl bmNoZW4xJjAkBgNVBAMTHVplcnRpZml6aWVydW5nc3N0ZWxsZSBkZXIgVFVNAgQQ26t7MA0GCSqG SIb3DQEBAQUABIIBAD0qkUNklBnIksNacJ3p5Go51HK/OkTlqSkoEoQsxCWeaHWrIR2m5DQ5veTr wD63Aclyg4J0NqsU1GlawFiC832rwjhqC7NQjrZ7v9F5QZVJ76EW3hTiGJcSmNfvs44pc0D9NcDI bK49IpRFIgFxtYWeTEYJ4dfuWyFSMY7e+L7n9gZcmnuEjSJTWDH7reHu/9FT8gAuK6LCH3zDYO+u hNA4xJLrmJQTn9+aXPcAiOijmKLe1B2QJUxbJjmxZrEOZOGqaQSJ1sIYk74wX/zBlyx+JcXj3U4A qmhG5O94x3IZznJl1Xm6T2XDySHrZRv8q/hWwMRWT7akR8K5xbyb5LAAAAAAAAA= --===============3962311810224932631==-- From krienke@uni-koblenz.de Thu Jan 24 07:45:08 2013 From: Rainer Krienke To: autoinstall@lists.opensuse.org Subject: Re: [opensuse-autoinstall] Problem running systemd service script after autoyast installation Date: Thu, 24 Jan 2013 08:44:25 +0100 Message-ID: <5100E659.5000304@uni-koblenz.de> In-Reply-To: <50FFA650.6010004@tum.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8714198048766308383==" --===============8714198048766308383== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 23.01.2013 09:58, schrieb Joschi Brauchle: > I think this might be related to > https://bugzilla.novell.com/show_bug.cgi?id=769924 > > AutoYast only enables the required services during installation. Then, > it used to do an "init $runlevel" to start them all up. The systemd > equivalent does not seem to work correctly at this point. > > Basically, i have come to the conclusion that for >12.2, you currently > HAVE TO reboot to get a working system with all services running. All > workarounds I have tried have failed so far... > Thanks for the link. Yes I guess that the bug report from above describes the very same bug that I see. So for the moment I will simply live with this problem and reboot... Thanks 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 --===============8714198048766308383== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIuMC4xOSAoR05V L0xpbnV4KQpDb21tZW50OiBVc2luZyBHbnVQRyB3aXRoIFRodW5kZXJiaXJkIC0gaHR0cDovL3d3 dy5lbmlnbWFpbC5uZXQvCgppRVlFQVJFQ0FBWUZBbEVBNWxrQUNna1FhbGR0amMvS0RFcnNoUUNl Sm5nRE9xSElVS2dJZWlPRjVFaFVVVXpCCnVwd0FvSUR5RkpwVXZnNGJTY1BZbUd4SFpiMmhMd0Nq Cj1IblY3Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============8714198048766308383==--