, I don't see the log message. E.g. <domain type='kvm'> <name>sles12b8-kvm</name> <uuid>40855800-b30d-c171-d447-f84e30aaa6cf</uuid> <title>This is a test

From darrent at akurit.com.au Mon Jun 16 00:35:27 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 16 Jun 2014 16:35:27 +1000 Subject: [sles-beta] Cosmetic, incorrect package install progress at end of install Message-ID: Team This is a cosmetic glitch in the new installer (from a network install/autoyast build). The package installation reports packages still to be installed, however the installation process has clearly finished that part and is moving onto other processes, leaving incorrect details showing (see screenshot). Is this worth raising an SR about or is it already known? -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: incorrect-package-install-reported.png Type: image/png Size: 46264 bytes Desc: not available URL: From jreidinger at suse.com Mon Jun 16 00:41:55 2014 From: jreidinger at suse.com (Josef Reidinger) Date: Mon, 16 Jun 2014 08:41:55 +0200 Subject: [sles-beta] Help, getting an autoyast build for "multi-user" target In-Reply-To: References: Message-ID: <20140616084155.0db2b152@dhcp150.suse.cz> On Mon, 16 Jun 2014 13:08:34 +1000 "Darren Thompson" wrote: > Team > > Does anyone have an example autoyast file they can share which > reliably builds a server to the "multi-user" target (e.g. no > X/display server running). > > Simmilarly, what are the steps for go from a server built to the > "graphical" target and getting it to reliably boot to the "multi-user" > target. > > The "service-manager" Yast module seems to be able to adjust the > "target" level but I cannot seem to workout how to get it to accept > "multi-user" - Am I missing something or is that yast module "broken"? > > Any/all help appreciated. > > background: > I have traditionally built my SLES servers with the full graphical > install. I would then go into 'yast2 run-level' module and in 'expert > mode' change the default to "run level 3". > This would allow me to run the servers themselves without any > graphical display, but I could still SSH into them and run all the > graphical tools (via x-forwarding). > I'm hoping to be able to achve the same result with SLES12 > > Regards > Darren > Hi Darren, my quick check of services manager xml schema - https://github.com/yast/yast-services-manager/blob/master/src/autoyast_rnc/services-manager.rnc show that what you are looking for can be multi-user If this do not work, then it is probably bug and we need to check it together with logs what can go wrong. Josef From jreidinger at suse.cz Mon Jun 16 01:09:15 2014 From: jreidinger at suse.cz (Josef Reidinger) Date: Mon, 16 Jun 2014 09:09:15 +0200 Subject: [sles-beta] Cosmetic, In-Reply-To: References: Message-ID: <20140616090915.32e5833b@dhcp150.suse.cz> On Mon, 16 Jun 2014 16:35:27 +1000 "Darren Thompson" wrote: > Team > > This is a cosmetic glitch in the new installer (from a network > install/autoyast build). > > The package installation reports packages still to be installed, > however the installation process has clearly finished that part and > is moving onto other processes, leaving incorrect details showing > (see screenshot). > > Is this worth raising an SR about or is it already known? > > Hi Darren, This is already known. We are trying to figure out where exactly is problem with slideshow details part. Josef From darrent at akurit.com.au Mon Jun 16 01:09:20 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 16 Jun 2014 17:09:20 +1000 Subject: [sles-beta] Help, getting an autoyast build for "multi-user" target In-Reply-To: <20140616084155.0db2b152@dhcp150.suse.cz> References: <20140616084155.0db2b152@dhcp150.suse.cz> Message-ID: Josef I can say clearly that "something" is broken. I'm not sure "what" is broken at this stage. The "yast service-manager" module does not even list multi-user as an available target to choose on the pull-down list. If I try specifying: multi-user In my autoayst files then it gets really strange as you get dropped to an un-configured x-server login screen and then have to run "init 3" to get to the root console. Which of these odd/incorrect/non-intuitive behaviours do you wish me to log? Darren On 16 June 2014 16:41, Josef Reidinger wrote: > On Mon, 16 Jun 2014 13:08:34 +1000 > "Darren Thompson" wrote: > > > Team > > > > Does anyone have an example autoyast file they can share which > > reliably builds a server to the "multi-user" target (e.g. no > > X/display server running). > > > > Simmilarly, what are the steps for go from a server built to the > > "graphical" target and getting it to reliably boot to the "multi-user" > > target. > > > > The "service-manager" Yast module seems to be able to adjust the > > "target" level but I cannot seem to workout how to get it to accept > > "multi-user" - Am I missing something or is that yast module "broken"? > > > > Any/all help appreciated. > > > > background: > > I have traditionally built my SLES servers with the full graphical > > install. I would then go into 'yast2 run-level' module and in 'expert > > mode' change the default to "run level 3". > > This would allow me to run the servers themselves without any > > graphical display, but I could still SSH into them and run all the > > graphical tools (via x-forwarding). > > I'm hoping to be able to achve the same result with SLES12 > > > > Regards > > Darren > > > > Hi Darren, > my quick check of services manager xml schema - > > https://github.com/yast/yast-services-manager/blob/master/src/autoyast_rnc/services-manager.rnc > show that what you are looking for can be > > multi-user > > > If this do not work, then it is probably bug and we need to check it > together with logs what can go wrong. > > Josef > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From jreidinger at suse.cz Mon Jun 16 01:13:17 2014 From: jreidinger at suse.cz (Josef Reidinger) Date: Mon, 16 Jun 2014 09:13:17 +0200 Subject: [sles-beta] Help, getting an autoyast build for "multi-user" target In-Reply-To: References: <20140616084155.0db2b152@dhcp150.suse.cz> Message-ID: <20140616091317.4ecc5b67@dhcp150.suse.cz> On Mon, 16 Jun 2014 17:09:20 +1000 "Darren Thompson" wrote: > Josef > > I can say clearly that "something" is broken. > > I'm not sure "what" is broken at this stage. > > The "yast service-manager" module does not even list multi-user as an > available target to choose on the pull-down list. Hi Darren, this is known issue, so not needed to report it. > > If I try specifying: > > multi-user > > In my autoayst files then it gets really strange as you get dropped > to an un-configured x-server login screen and then have to run "init > 3" to get to the root console. > > Which of these odd/incorrect/non-intuitive behaviours do you wish me > to log? I am not aware of second one, so if you can report it it would help us and attach all logs, so we can see what exactly can be problem. Thanks Josef > > Darren > > > > > On 16 June 2014 16:41, Josef Reidinger wrote: > > > On Mon, 16 Jun 2014 13:08:34 +1000 > > "Darren Thompson" wrote: > > > > > Team > > > > > > Does anyone have an example autoyast file they can share which > > > reliably builds a server to the "multi-user" target (e.g. no > > > X/display server running). > > > > > > Simmilarly, what are the steps for go from a server built to the > > > "graphical" target and getting it to reliably boot to the > > > "multi-user" target. > > > > > > The "service-manager" Yast module seems to be able to adjust the > > > "target" level but I cannot seem to workout how to get it to > > > accept "multi-user" - Am I missing something or is that yast > > > module "broken"? > > > > > > Any/all help appreciated. > > > > > > background: > > > I have traditionally built my SLES servers with the full graphical > > > install. I would then go into 'yast2 run-level' module and in > > > 'expert mode' change the default to "run level 3". > > > This would allow me to run the servers themselves without any > > > graphical display, but I could still SSH into them and run all the > > > graphical tools (via x-forwarding). > > > I'm hoping to be able to achve the same result with SLES12 > > > > > > Regards > > > Darren > > > > > > > Hi Darren, > > my quick check of services manager xml schema - > > > > https://github.com/yast/yast-services-manager/blob/master/src/autoyast_rnc/services-manager.rnc > > show that what you are looking for can be > > > > multi-user > > > > > > If this do not work, then it is probably bug and we need to check it > > together with logs what can go wrong. > > > > Josef > > _______________________________________________ > > sles-beta mailing list > > sles-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sles-beta > > > > > From darrent at akurit.com.au Mon Jun 16 01:23:42 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 16 Jun 2014 17:23:42 +1000 Subject: [sles-beta] Help, getting an autoyast build for "multi-user" target In-Reply-To: <20140616091317.4ecc5b67@dhcp150.suse.cz> References: <20140616084155.0db2b152@dhcp150.suse.cz> <20140616091317.4ecc5b67@dhcp150.suse.cz> Message-ID: Josef This is the hardest part as I cannot seem to get a reliable build from autoyast so do not know if this lack of clean "multi-user" is the problem or just an incidental from my broken configuration attempts. (Hence the request for a "know good" example file). If I do a "default install" and then use the autoinst.xml as my starting point I get a long way through the build process but cannot get "graphics" target working and it ends with odd errors with networking. If I use some of my "earlier" working autoyast files, I get even more bizarre errors. (Is it just me or is there two complete duplicates of the "ser vice-manager" section in all the autoyast files that are created from "yast autoyast" module??? In any case, when I can get a "working" configuration I will be in a better situation to help run-down the "broken" test cases and raise SR's Darren On 16 June 2014 17:13, Josef Reidinger wrote: > On Mon, 16 Jun 2014 17:09:20 +1000 > "Darren Thompson" wrote: > > > Josef > > > > I can say clearly that "something" is broken. > > > > I'm not sure "what" is broken at this stage. > > > > The "yast service-manager" module does not even list multi-user as an > > available target to choose on the pull-down list. > > Hi Darren, > this is known issue, so not needed to report it. > > > > > If I try specifying: > > > > multi-user > > > > In my autoayst files then it gets really strange as you get dropped > > to an un-configured x-server login screen and then have to run "init > > 3" to get to the root console. > > > > Which of these odd/incorrect/non-intuitive behaviours do you wish me > > to log? > > I am not aware of second one, so if you can report it it would help us > and attach all logs, so we can see what exactly can be problem. > > Thanks > Josef > > > > > Darren > > > > > > > > > > On 16 June 2014 16:41, Josef Reidinger wrote: > > > > > On Mon, 16 Jun 2014 13:08:34 +1000 > > > "Darren Thompson" wrote: > > > > > > > Team > > > > > > > > Does anyone have an example autoyast file they can share which > > > > reliably builds a server to the "multi-user" target (e.g. no > > > > X/display server running). > > > > > > > > Simmilarly, what are the steps for go from a server built to the > > > > "graphical" target and getting it to reliably boot to the > > > > "multi-user" target. > > > > > > > > The "service-manager" Yast module seems to be able to adjust the > > > > "target" level but I cannot seem to workout how to get it to > > > > accept "multi-user" - Am I missing something or is that yast > > > > module "broken"? > > > > > > > > Any/all help appreciated. > > > > > > > > background: > > > > I have traditionally built my SLES servers with the full graphical > > > > install. I would then go into 'yast2 run-level' module and in > > > > 'expert mode' change the default to "run level 3". > > > > This would allow me to run the servers themselves without any > > > > graphical display, but I could still SSH into them and run all the > > > > graphical tools (via x-forwarding). > > > > I'm hoping to be able to achve the same result with SLES12 > > > > > > > > Regards > > > > Darren > > > > > > > > > > Hi Darren, > > > my quick check of services manager xml schema - > > > > > > > https://github.com/yast/yast-services-manager/blob/master/src/autoyast_rnc/services-manager.rnc > > > show that what you are looking for can be > > > > > > multi-user > > > > > > > > > If this do not work, then it is probably bug and we need to check it > > > together with logs what can go wrong. > > > > > > Josef > > > _______________________________________________ > > > sles-beta mailing list > > > sles-beta at lists.suse.com > > > http://lists.suse.com/mailman/listinfo/sles-beta > > > > > > > > > > > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From jreidinger at suse.cz Mon Jun 16 01:27:57 2014 From: jreidinger at suse.cz (Josef Reidinger) Date: Mon, 16 Jun 2014 09:27:57 +0200 Subject: [sles-beta] Help, In-Reply-To: References: <20140616084155.0db2b152@dhcp150.suse.cz> <20140616091317.4ecc5b67@dhcp150.suse.cz> Message-ID: <20140616092757.4c55eab0@dhcp150.suse.cz> On Mon, 16 Jun 2014 17:23:42 +1000 "Darren Thompson" wrote: > Josef > > This is the hardest part as I cannot seem to get a reliable build from > autoyast so do not know if this lack of clean "multi-user" is the > problem or just an incidental from my broken configuration attempts. > (Hence the request for a "know good" example file). I think some PMs can have something from QA that they use for testing. > > If I do a "default install" and then use the autoinst.xml as my > starting point I get a long way through the build process but cannot > get "graphics" target working and it ends with odd errors with > networking. It is worth reporting as it should happen. > > If I use some of my "earlier" working autoyast files, I get even more > bizarre errors. (Is it just me or is there two complete duplicates of > the "ser vice-manager" section in all the autoyast files that are > created from "yast autoyast" module??? This also looks like bug, please also report. I think it is relict from support of old runlevel scheme. Josef > > In any case, when I can get a "working" configuration I will be in a > better situation to help run-down the "broken" test cases and raise > SR's > > Darren > > > On 16 June 2014 17:13, Josef Reidinger wrote: > > > On Mon, 16 Jun 2014 17:09:20 +1000 > > "Darren Thompson" wrote: > > > > > Josef > > > > > > I can say clearly that "something" is broken. > > > > > > I'm not sure "what" is broken at this stage. > > > > > > The "yast service-manager" module does not even list multi-user > > > as an available target to choose on the pull-down list. > > > > Hi Darren, > > this is known issue, so not needed to report it. > > > > > > > > If I try specifying: > > > > > > multi-user > > > > > > In my autoayst files then it gets really strange as you get > > > dropped to an un-configured x-server login screen and then have > > > to run "init 3" to get to the root console. > > > > > > Which of these odd/incorrect/non-intuitive behaviours do you wish > > > me to log? > > > > I am not aware of second one, so if you can report it it would help > > us and attach all logs, so we can see what exactly can be problem. > > > > Thanks > > Josef > > > > > > > > Darren > > > > > > > > > > > > > > > On 16 June 2014 16:41, Josef Reidinger > > > wrote: > > > > > > > On Mon, 16 Jun 2014 13:08:34 +1000 > > > > "Darren Thompson" wrote: > > > > > > > > > Team > > > > > > > > > > Does anyone have an example autoyast file they can share which > > > > > reliably builds a server to the "multi-user" target (e.g. no > > > > > X/display server running). > > > > > > > > > > Simmilarly, what are the steps for go from a server built to > > > > > the "graphical" target and getting it to reliably boot to the > > > > > "multi-user" target. > > > > > > > > > > The "service-manager" Yast module seems to be able to adjust > > > > > the "target" level but I cannot seem to workout how to get it > > > > > to accept "multi-user" - Am I missing something or is that > > > > > yast module "broken"? > > > > > > > > > > Any/all help appreciated. > > > > > > > > > > background: > > > > > I have traditionally built my SLES servers with the full > > > > > graphical install. I would then go into 'yast2 run-level' > > > > > module and in 'expert mode' change the default to "run level > > > > > 3". This would allow me to run the servers themselves without > > > > > any graphical display, but I could still SSH into them and > > > > > run all the graphical tools (via x-forwarding). > > > > > I'm hoping to be able to achve the same result with SLES12 > > > > > > > > > > Regards > > > > > Darren > > > > > > > > > > > > > Hi Darren, > > > > my quick check of services manager xml schema - > > > > > > > > > > https://github.com/yast/yast-services-manager/blob/master/src/autoyast_rnc/services-manager.rnc > > > > show that what you are looking for can be > > > > > > > > multi-user > > > > > > > > > > > > If this do not work, then it is probably bug and we need to > > > > check it together with logs what can go wrong. > > > > > > > > Josef > > > > _______________________________________________ > > > > sles-beta mailing list > > > > sles-beta at lists.suse.com > > > > http://lists.suse.com/mailman/listinfo/sles-beta > > > > > > > > > > > > > > > > > > > From darrent at akurit.com.au Mon Jun 16 01:46:20 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 16 Jun 2014 17:46:20 +1000 Subject: [sles-beta] Help, In-Reply-To: <20140616092757.4c55eab0@dhcp150.suse.cz> References: <20140616084155.0db2b152@dhcp150.suse.cz> <20140616091317.4ecc5b67@dhcp150.suse.cz> <20140616092757.4c55eab0@dhcp150.suse.cz> Message-ID: I have created this SR for the autoinst.xml issue: " 10897186801 *Description: autoinst.xml created from "default install" does not work for autoyast"* On 16 June 2014 17:27, Josef Reidinger wrote: > On Mon, 16 Jun 2014 17:23:42 +1000 > "Darren Thompson" wrote: > > > Josef > > > > This is the hardest part as I cannot seem to get a reliable build from > > autoyast so do not know if this lack of clean "multi-user" is the > > problem or just an incidental from my broken configuration attempts. > > (Hence the request for a "know good" example file). > > I think some PMs can have something from QA that they use for testing. > > > > > If I do a "default install" and then use the autoinst.xml as my > > starting point I get a long way through the build process but cannot > > get "graphics" target working and it ends with odd errors with > > networking. > > It is worth reporting as it should happen. > > > > > If I use some of my "earlier" working autoyast files, I get even more > > bizarre errors. (Is it just me or is there two complete duplicates of > > the "ser vice-manager" section in all the autoyast files that are > > created from "yast autoyast" module??? > > This also looks like bug, please also report. I think it is relict from > support of old runlevel scheme. > > Josef > > > > > In any case, when I can get a "working" configuration I will be in a > > better situation to help run-down the "broken" test cases and raise > > SR's > > > > Darren > > > > > > On 16 June 2014 17:13, Josef Reidinger wrote: > > > > > On Mon, 16 Jun 2014 17:09:20 +1000 > > > "Darren Thompson" wrote: > > > > > > > Josef > > > > > > > > I can say clearly that "something" is broken. > > > > > > > > I'm not sure "what" is broken at this stage. > > > > > > > > The "yast service-manager" module does not even list multi-user > > > > as an available target to choose on the pull-down list. > > > > > > Hi Darren, > > > this is known issue, so not needed to report it. > > > > > > > > > > > If I try specifying: > > > > > > > > multi-user > > > > > > > > In my autoayst files then it gets really strange as you get > > > > dropped to an un-configured x-server login screen and then have > > > > to run "init 3" to get to the root console. > > > > > > > > Which of these odd/incorrect/non-intuitive behaviours do you wish > > > > me to log? > > > > > > I am not aware of second one, so if you can report it it would help > > > us and attach all logs, so we can see what exactly can be problem. > > > > > > Thanks > > > Josef > > > > > > > > > > > Darren > > > > > > > > > > > > > > > > > > > > On 16 June 2014 16:41, Josef Reidinger > > > > wrote: > > > > > > > > > On Mon, 16 Jun 2014 13:08:34 +1000 > > > > > "Darren Thompson" wrote: > > > > > > > > > > > Team > > > > > > > > > > > > Does anyone have an example autoyast file they can share which > > > > > > reliably builds a server to the "multi-user" target (e.g. no > > > > > > X/display server running). > > > > > > > > > > > > Simmilarly, what are the steps for go from a server built to > > > > > > the "graphical" target and getting it to reliably boot to the > > > > > > "multi-user" target. > > > > > > > > > > > > The "service-manager" Yast module seems to be able to adjust > > > > > > the "target" level but I cannot seem to workout how to get it > > > > > > to accept "multi-user" - Am I missing something or is that > > > > > > yast module "broken"? > > > > > > > > > > > > Any/all help appreciated. > > > > > > > > > > > > background: > > > > > > I have traditionally built my SLES servers with the full > > > > > > graphical install. I would then go into 'yast2 run-level' > > > > > > module and in 'expert mode' change the default to "run level > > > > > > 3". This would allow me to run the servers themselves without > > > > > > any graphical display, but I could still SSH into them and > > > > > > run all the graphical tools (via x-forwarding). > > > > > > I'm hoping to be able to achve the same result with SLES12 > > > > > > > > > > > > Regards > > > > > > Darren > > > > > > > > > > > > > > > > Hi Darren, > > > > > my quick check of services manager xml schema - > > > > > > > > > > > > > > https://github.com/yast/yast-services-manager/blob/master/src/autoyast_rnc/services-manager.rnc > > > > > show that what you are looking for can be > > > > > > > > > > multi-user > > > > > > > > > > > > > > > If this do not work, then it is probably bug and we need to > > > > > check it together with logs what can go wrong. > > > > > > > > > > Josef > > > > > _______________________________________________ > > > > > sles-beta mailing list > > > > > sles-beta at lists.suse.com > > > > > http://lists.suse.com/mailman/listinfo/sles-beta > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From schubi at suse.de Mon Jun 16 04:25:37 2014 From: schubi at suse.de (Stefan Schubert) Date: Mon, 16 Jun 2014 12:25:37 +0200 Subject: [sles-beta] autoyast, sshd and snapper In-Reply-To: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr> References: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr> Message-ID: <539EC621.1070602@suse.de> Hi, the snapper support should be available for beta9: https://bugzilla.novell.com/show_bug.cgi?id=878722 Please open a bug for the sshd problem. Greetings Stefan Am 16.06.2014 12:01, schrieb FOLTIER Julien: > > Hi, > > When I?m trying to install SLES12 beta 8 with an autoyast file, I > don?t have a snapper configuration after this installation and sshd is > not enable and not started. > > How can I implement those 2 parameters in the autoyast file ? > > Thanks > > Best regards, > > Julien FOLTIER > > > Post-scriptum La Poste > > Ce message est confidentiel. Sous reserve de tout accord conclu par > ecrit entre vous et La Poste, son contenu ne represente en aucun cas > un engagement de la part de La Poste. Toute publication, utilisation > ou diffusion, meme partielle, doit etre autorisee prealablement. Si > vous n'etes pas destinataire de ce message, merci d'en avertir > immediatement l'expediteur. > > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From S.M.Flood at ucs.cam.ac.uk Mon Jun 16 05:31:51 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Mon, 16 Jun 2014 12:31:51 +0100 Subject: [sles-beta] [ANNOUNCE] SLE Workstation Extension 12 Beta8 is available In-Reply-To: <1402084535.15734.2.camel@par-r81vxc7.par.novell.com> References: <1402084535.15734.2.camel@par-r81vxc7.par.novell.com> Message-ID: <539ED5A7.6070704@ucs.cam.ac.uk> On 06/06/2014 20:55, Frederic Crozat wrote: > we are happy to announce Beta 8 release of > > SUSE Linux Enterprise Workstation Extension 12 > > (this is the new name of the previously named SLED Extension) Maybe I missed a message and/or webinar but what is SLE Workstation Extension (pka SLED Extension)? Is this a SLES-only thing or does it also relate to SLED? It sounds like it either turns SLES into SLED or adds desktop capabilities(?) to SLES. If so, not something I want to do. Thanks, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner From jweber at suse.com Mon Jun 16 05:36:08 2014 From: jweber at suse.com (Jan Weber) Date: Mon, 16 Jun 2014 13:36:08 +0200 Subject: [sles-beta] [ANNOUNCE] SLE Workstation Extension 12 Beta8 is available In-Reply-To: <539ED5A7.6070704@ucs.cam.ac.uk> References: <1402084535.15734.2.camel@par-r81vxc7.par.novell.com> <539ED5A7.6070704@ucs.cam.ac.uk> Message-ID: <539ED6A8.2080205@suse.com> Hi Simon, On 06/16/2014 01:31 PM, Simon Flood wrote: > On 06/06/2014 20:55, Frederic Crozat wrote: > >> we are happy to announce Beta 8 release of >> >> SUSE Linux Enterprise Workstation Extension 12 >> >> (this is the new name of the previously named SLED Extension) > > Maybe I missed a message and/or webinar but what is SLE Workstation > Extension (pka SLED Extension)? > > Is this a SLES-only thing or does it also relate to SLED? > > It sounds like it either turns SLES into SLED or adds desktop > capabilities(?) to SLES. If so, not something I want to do. It is adding further desktop capabilities to SLES, for those that need both Server and Desktop technologies. We did get some requests for Desktop only packages to be available for SLES as well, for a larger variety of different packages, this is the best way we can offer this in a supportable way. Jan -- Jan Weber E jweber at suse.com SUSE Linux Products GmbH Product Manager M +49(179)4573255 HRB 16746 (AG N?rnberg) SUSE Linux Enterprise GF: Jeff Hawn, Jennifer Guild http://www.suse.com/ Felix Imend?rffer From S.M.Flood at ucs.cam.ac.uk Mon Jun 16 06:05:23 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Mon, 16 Jun 2014 13:05:23 +0100 Subject: [sles-beta] [ANNOUNCE] SLE Workstation Extension 12 Beta8 is available In-Reply-To: <539ED6A8.2080205@suse.com> References: <1402084535.15734.2.camel@par-r81vxc7.par.novell.com> <539ED5A7.6070704@ucs.cam.ac.uk> <539ED6A8.2080205@suse.com> Message-ID: <539EDD83.9050901@ucs.cam.ac.uk> On 16/06/2014 12:36, Jan Weber wrote: > It is adding further desktop capabilities to SLES, for those that need > both Server and Desktop technologies. We did get some requests for > Desktop only packages to be available for SLES as well, for a larger > variety of different packages, this is the best way we can offer this in > a supportable way. Thanks. Can I suggest that SLES Workstation Extension (note SLES not SLE) is a better name if it's specific to SLES although I realise there could be confusion with Server vs Workstation (though you had that with Server vs Desktop in the previous name). Since there's nothing for me to see here I'll now move along. Thanks, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner From MLaguilharre at novell.com Mon Jun 16 07:01:31 2014 From: MLaguilharre at novell.com (Marc Laguilharre) Date: Mon, 16 Jun 2014 14:01:31 +0100 Subject: [sles-beta] autoyast, sshd and snapper In-Reply-To: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr> References: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr> Message-ID: <539F06CB0200009300085124@mail.emea.novell.com> Hi Julien, For enabling sshd in autoyast can you try configuration from: https://github.com/yast/yast-services-manager Thanks Marc Marc Laguilharre Technical Support Engineer Tel :+33 (0) 950775295 Mob :+33 (0) 682827857 Email : mlaguilharre at novell.com >>> FOLTIER Julien 6/16/2014 12:01 PM >>> Hi, When I'm trying to install SLES12 beta 8 with an autoyast file, I don't have a snapper configuration after this installation and sshd is not enable and not started. How can I implement those 2 parameters in the autoyast file ? Thanks Best regards, Julien FOLTIER Post-scriptum La Poste Ce message est confidentiel. Sous reserve de tout accord conclu par ecrit entre vous et La Poste, son contenu ne represente en aucun cas un engagement de la part de La Poste. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur. From julien.foltier at laposte.fr Mon Jun 16 07:44:24 2014 From: julien.foltier at laposte.fr (FOLTIER Julien) Date: Mon, 16 Jun 2014 13:44:24 +0000 Subject: [sles-beta] autoyast, sshd and snapper In-Reply-To: <539F06CB0200009300085124@mail.emea.novell.com> References: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr> <539F06CB0200009300085124@mail.emea.novell.com> Message-ID: <02954CD80554BB4AA0977E7110B60C722782BB19@RPN00150.melposte.log.intra.laposte.fr> It works, thanks Julien FOLTIER -----Message d'origine----- De?: Marc Laguilharre [mailto:MLaguilharre at novell.com] Envoy??: lundi 16 juin 2014 15:02 ??: FOLTIER Julien; sles-beta at lists.suse.com Objet?: Re: [sles-beta] autoyast, sshd and snapper Hi Julien, For enabling sshd in autoyast can you try configuration from: https://github.com/yast/yast-services-manager Thanks Marc Marc Laguilharre Technical Support Engineer Tel :+33 (0) 950775295 Mob :+33 (0) 682827857 Email : mlaguilharre at novell.com >>> FOLTIER Julien 6/16/2014 12:01 PM >>> Hi, When I'm trying to install SLES12 beta 8 with an autoyast file, I don't have a snapper configuration after this installation and sshd is not enable and not started. How can I implement those 2 parameters in the autoyast file ? Thanks Best regards, Julien FOLTIER Post-scriptum La Poste Ce message est confidentiel. Sous reserve de tout accord conclu par ecrit entre vous et La Poste, son contenu ne represente en aucun cas un engagement de la part de La Poste. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur. Post-scriptum La Poste Ce message est confidentiel. Sous reserve de tout accord conclu par ecrit entre vous et La Poste, son contenu ne represente en aucun cas un engagement de la part de La Poste. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur. From radmanic at suse.com Mon Jun 16 08:33:00 2014 From: radmanic at suse.com (Milisav Radmanic) Date: Mon, 16 Jun 2014 16:33:00 +0200 Subject: [sles-beta] YaST authentication client In-Reply-To: References: Message-ID: <539F001C.3070306@suse.com> Am 08.06.2014 15:41, schrieb Sander van Vugt: > Hi, > > I?m trying to understand the authentication client module in YaST to set > up LDAP client authentication to my (confirmed working) LDAP server. I > think the setup of the module is confusing, it?s just a yast interface > to sssd.conf, but it doesn?t really add any meaning. Is this going to be > enhanced? Or: if I?m missing the clue, is there any documentation of > this module where I can read how to use it? The documentation will improve soon. Currently there is no plan to expand the configuration options offered by the according YaST-module. The authentication module is limited to the bare minimum that is required in order to create a successful setup. Users who want to do expert settings will need to edit the configuration file itself. Providing the "URI" and the "base dn" usually is enough to connect a client to a LDAP-service. If there are issues, please provide your configuration files. best regards Milisav -- Milisav Radmanic Sr. Engineering Manager SUSE Linux Enterprise Applications SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From gjn at gjn.priv.at Mon Jun 16 09:10:04 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Mon, 16 Jun 2014 17:10:04 +0200 Subject: [sles-beta] intel_rapl missing Message-ID: <1483424.3xXKQTWd5z@gjn.priv.at> Hello, what is this new message from the kernel, I never see it before ? Intel_rapl: no valid rapl domains found inpackage 0 Thank's for a answer, -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From jweber at suse.com Mon Jun 16 10:22:32 2014 From: jweber at suse.com (Jan Weber) Date: Mon, 16 Jun 2014 18:22:32 +0200 Subject: [sles-beta] [ANNOUNCE] SLE Workstation Extension 12 Beta8 is available In-Reply-To: <539EDD83.9050901@ucs.cam.ac.uk> References: <1402084535.15734.2.camel@par-r81vxc7.par.novell.com> <539ED5A7.6070704@ucs.cam.ac.uk> <539ED6A8.2080205@suse.com> <539EDD83.9050901@ucs.cam.ac.uk> Message-ID: <539F19C8.9060908@suse.com> On 06/16/2014 02:05 PM, Simon Flood wrote: > On 16/06/2014 12:36, Jan Weber wrote: > >> It is adding further desktop capabilities to SLES, for those that need >> both Server and Desktop technologies. We did get some requests for >> Desktop only packages to be available for SLES as well, for a larger >> variety of different packages, this is the best way we can offer this in >> a supportable way. > > Thanks. Can I suggest that SLES Workstation Extension (note SLES not > SLE) is a better name if it's specific to SLES although I realise there > could be confusion with Server vs Workstation (though you had that with > Server vs Desktop in the previous name). We are trying to avoid having product names in the names of other products, hence the renaming to SUSE Linux Enterprise Workstation Extension. Jan -- Jan Weber E jweber at suse.com SUSE Linux Products GmbH Product Manager M +49(179)4573255 HRB 16746 (AG N?rnberg) SUSE Linux Enterprise GF: Jeff Hawn, Jennifer Guild http://www.suse.com/ Felix Imend?rffer From darrent at akurit.com.au Mon Jun 16 14:25:18 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Tue, 17 Jun 2014 06:25:18 +1000 Subject: [sles-beta] YaST2 from SSH failing again with SLES12B8 In-Reply-To: References:

Message-ID: Gregory Thanks for the link, certainly a very interesting application and may help when I find PuTTY's terminal emulation options too limiting. As an aside, you do realise that Macintosh OS has "native" x-server and ssh clients (functionally identical to Linux)? Darren On 17 June 2014 04:59, Gregory D. Rosenberg wrote: > Darren, > > OK, thanks! I was just double checking. FYI - I use a mix of OSes. I > really like ZOC6 for MAC OS or Windows environments. Although it is not > free like Putty. It is a very powerful package and well worth the ~$80 I > spent on it. The license allow you to install it on as many machines as you > like (http://www.emtec.com/zoc/). I have no affiliation with Emtec. > > > On Jun 13, 2014, at 19:24 CDT, Darren Thompson > wrote: > > Greg > > Normally I use:" > > ssh -X root@{hostname or ip address} > > Once I'm logged in I "normally" can run any x-enabled application and the > screen is forwarded to the x-server running on my desktop (linux) > > I can achieve the same on Windows with PuTTY by checking the x-forwarding > option and running a "x-server" (I use x-ming). > > I did some more testing and when I'm getting this error (oddly not every > time I connect) I cannot run xterm either so i suspect the issue is in the > underlying xterm that YaST2 is trying to invoke. > > Darren > > > On 14 June 2014 09:24, Gregory D. Rosenberg wrote: > >> Darren, >> >> Do you have to enable any type of forwarding to make this work? >> >> On Jun 10, 2014, at 23:27 CDT, Darren Thompson >> wrote: >> >> Team >> >> I cannot get YaST2 to run any of it's modules when run through SSH (with >> X-forwarding enabled)... Again... >> >> YaST2 itself starts without error, but when a module is selected I get a >> "bouncing thing" which stops after a few minutes and no further activity. >> >> The "ssh shell" gets this echoed when this issue is occurring: >> "linux-7z01:~ # >> ** (y2controlcenter-gnome:5138): WARNING **: Couldn't connect to >> accessibility bus: Failed to connect to socket /tmp/dbus-21DTG0iwLz: >> Connection refused >> /usr/bin/xdg-su: line 503: 5163 Segmentation fault xterm -geom 60x5 >> -T "xdg-su: $cmd" -e su -c "$cmd" >> " >> >> This is the second time I have seen this behaviour (it also happened in >> B6, seemed to be resolved in B7 and is now back in B8) >> >> -- >> >> Darren Thompson >> >> Professional Services Engineer / Consultant >> >> ** >> >> Level 3, 60 City Road >> >> Southgate, VIC 3006 >> >> Mb: 0400 640 414 >> >> Mail: darrent at akurit.com.au >> Web: www.akurit.com.au >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> >> http://cp.mcafee.com/d/FZsS92gQ91NJ5yWr3BTxPxKVJ6Wrz2bPMVUSztdNx4QsEIcCQrI6zBcQsL6zBwQsCQrFKfCzBdxBYShzV4y2EOJaDbCUOJaDbCO5Jg76zBB_HYYehopWZOWrbwXAm7XK9YJteOaaJT6ul3PWApmU6CQjq9J7HFkr8kJ6h3Pq9I06vaAWthKDYLwCHIcfBisEeROx_QbAfDFKx_QbAfDFsxlK5LE2zVkDjGdQ_BPqatSm3pFrEvZ2V3VWqnjh01Z60iCq87oRld40Mc1sQgeX8-k29EwQzIE6y0NapcQg30l6xx5cpudLI6VUQ5Gf3FWizw >> >> >> >> >> P.S. Text the word BLIND to 85944 to donate $10 to the NFB Imagination >> Fund via your phone bill. >> >> The National Federation of the Blind knows that blindness is not the >> characteristic that defines you or your future. Every day we raise the >> expectations of blind people, because low expectations create obstacles >> between blind people and our dreams. You can have the life you want; >> blindness is not what holds you back. >> >> -- >> 73' & 75' >> Gregory D. Rosenberg AB9MZ >> gregg at ricis.com >> >> RICIS, Inc. >> 7849 Bristol Park Drive >> Tinley Park, IL 60477-4594 >> http://www.ricis.com >> >> 708-267-6664 Cell >> 708-444-2690 Office >> 708-444-1115 Fax >> (Please call before sending a fax) >> >> >> >> > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > ** > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > > > > > > P.S. Text the word BLIND to 85944 to donate $10 to the NFB Imagination > Fund via your phone bill. > > The National Federation of the Blind knows that blindness is not the > characteristic that defines you or your future. Every day we raise the > expectations of blind people, because low expectations create obstacles > between blind people and our dreams. You can have the life you want; > blindness is not what holds you back. > > -- > 73' & 75' > Gregory D. Rosenberg AB9MZ > gregg at ricis.com > > RICIS, Inc. > 7849 Bristol Park Drive > Tinley Park, IL 60477-4594 > http://www.ricis.com > > 708-267-6664 Cell > 708-444-2690 Office > 708-444-1115 Fax > (Please call before sending a fax) > > > > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From darrent at akurit.com.au Mon Jun 16 15:18:13 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Tue, 17 Jun 2014 07:18:13 +1000 Subject: [sles-beta] YaST2 from SSH failing again with SLES12B8 In-Reply-To: <370F73C9-1E98-455C-A067-89AD0A0546F8@ricis.com> References:

<370F73C9-1E98-455C-A067-89AD0A0546F8@ricis.com> Message-ID: Gregory This is (sad) news for me and would stop me even considering buying an apple product in future "Apple no longer ships X on its installation media". It's a terrible shame as Apple makes "good value" hardware (personal opinion, taking into account battery life etc). How hard is it to get the sources/binaries for XQuartz? Darren On 17 June 2014 06:36, Gregory D. Rosenberg wrote: > > On Jun 16, 2014, at 15:25 CDT, Darren Thompson > wrote: > > Gregory > > Thanks for the link, certainly a very interesting application and may help > when I find PuTTY's terminal emulation options too limiting. > > As an aside, you do realise that Macintosh OS has "native" x-server and > ssh clients (functionally identical to Linux)? > > > Apple no longer ships X on its installation media, nor do they support it. > I do have Apple?s recommended package XQuartz installed. It is decent, but > rather limiting. It is not much better than the older Humingbird product. > > I am blind, so I tend to look for tools that allow me to operate more > efficiently. ZOC is not accessible, but on the days when I have better than > light perception it greatly improves my productivity. I live on the command > line pretty much. Apple Voice Over does a great job for me most of the time. > > I am only now starting to explore what accessibility I can get out of > SLES. We have been on the SLES bandwagon since the late 90?s. I hate Red > Hat. Although I still have to support it from time-to-time. > > > Darren > > > On 17 June 2014 04:59, Gregory D. Rosenberg wrote: > >> Darren, >> >> OK, thanks! I was just double checking. FYI - I use a mix of OSes. I >> really like ZOC6 for MAC OS or Windows environments. Although it is not >> free like Putty. It is a very powerful package and well worth the ~$80 I >> spent on it. The license allow you to install it on as many machines as you >> like (http://www.emtec.com/zoc/ >> ). >> I have no affiliation with Emtec. >> >> >> On Jun 13, 2014, at 19:24 CDT, Darren Thompson >> wrote: >> >> Greg >> >> Normally I use:" >> >> ssh -X root@{hostname or ip address} >> >> Once I'm logged in I "normally" can run any x-enabled application and the >> screen is forwarded to the x-server running on my desktop (linux) >> >> I can achieve the same on Windows with PuTTY by checking the x-forwarding >> option and running a "x-server" (I use x-ming). >> >> I did some more testing and when I'm getting this error (oddly not every >> time I connect) I cannot run xterm either so i suspect the issue is in the >> underlying xterm that YaST2 is trying to invoke. >> >> Darren >> >> >> On 14 June 2014 09:24, Gregory D. Rosenberg wrote: >> >>> Darren, >>> >>> Do you have to enable any type of forwarding to make this work? >>> >>> On Jun 10, 2014, at 23:27 CDT, Darren Thompson >>> wrote: >>> >>> Team >>> >>> I cannot get YaST2 to run any of it's modules when run through SSH (with >>> X-forwarding enabled)... Again... >>> >>> YaST2 itself starts without error, but when a module is selected I get a >>> "bouncing thing" which stops after a few minutes and no further activity. >>> >>> The "ssh shell" gets this echoed when this issue is occurring: >>> "linux-7z01:~ # >>> ** (y2controlcenter-gnome:5138): WARNING **: Couldn't connect to >>> accessibility bus: Failed to connect to socket /tmp/dbus-21DTG0iwLz: >>> Connection refused >>> /usr/bin/xdg-su: line 503: 5163 Segmentation fault xterm -geom >>> 60x5 -T "xdg-su: $cmd" -e su -c "$cmd" >>> " >>> >>> This is the second time I have seen this behaviour (it also happened in >>> B6, seemed to be resolved in B7 and is now back in B8) >>> >>> -- >>> >>> Darren Thompson >>> >>> Professional Services Engineer / Consultant >>> >>> ** >>> >>> Level 3, 60 City Road >>> >>> Southgate, VIC 3006 >>> >>> Mb: 0400 640 414 >>> >>> Mail: darrent at akurit.com.au >>> Web: www.akurit.com.au >>> >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> >>> http://cp.mcafee.com/d/FZsS92gQ91NJ5yWr3BTxPxKVJ6Wrz2bPMVUSztdNx4QsEIcCQrI6zBcQsL6zBwQsCQrFKfCzBdxBYShzV4y2EOJaDbCUOJaDbCO5Jg76zBB_HYYehopWZOWrbwXAm7XK9YJteOaaJT6ul3PWApmU6CQjq9J7HFkr8kJ6h3Pq9I06vaAWthKDYLwCHIcfBisEeROx_QbAfDFKx_QbAfDFsxlK5LE2zVkDjGdQ_BPqatSm3pFrEvZ2V3VWqnjh01Z60iCq87oRld40Mc1sQgeX8-k29EwQzIE6y0NapcQg30l6xx5cpudLI6VUQ5Gf3FWizw >>> >>> >>> >>> >>> P.S. Text the word BLIND to 85944 to donate $10 to the NFB Imagination >>> Fund via your phone bill. >>> >>> The National Federation of the Blind knows that blindness is not the >>> characteristic that defines you or your future. Every day we raise the >>> expectations of blind people, because low expectations create obstacles >>> between blind people and our dreams. You can have the life you want; >>> blindness is not what holds you back. >>> >>> -- >>> 73' & 75' >>> Gregory D. Rosenberg AB9MZ >>> gregg at ricis.com >>> >>> RICIS, Inc. >>> 7849 Bristol Park Drive >>> Tinley Park, IL 60477-4594 >>> http://www.ricis.com >>> >>> 708-267-6664 Cell >>> 708-444-2690 Office >>> 708-444-1115 Fax >>> (Please call before sending a fax) >>> >>> >>> >>> >> >> >> -- >> >> Darren Thompson >> >> Professional Services Engineer / Consultant >> >> ** >> >> Level 3, 60 City Road >> >> Southgate, VIC 3006 >> >> Mb: 0400 640 414 >> >> Mail: darrent at akurit.com.au >> Web: www.akurit.com.au >> >> >> >> >> >> P.S. Text the word BLIND to 85944 to donate $10 to the NFB Imagination >> Fund via your phone bill. >> >> The National Federation of the Blind knows that blindness is not the >> characteristic that defines you or your future. Every day we raise the >> expectations of blind people, because low expectations create obstacles >> between blind people and our dreams. You can have the life you want; >> blindness is not what holds you back. >> >> -- >> 73' & 75' >> Gregory D. Rosenberg AB9MZ >> gregg at ricis.com >> >> RICIS, Inc. >> 7849 Bristol Park Drive >> Tinley Park, IL 60477-4594 >> http://www.ricis.com >> >> 708-267-6664 Cell >> 708-444-2690 Office >> 708-444-1115 Fax >> (Please call before sending a fax) >> >> >> >> > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > ** > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > > > > > > P.S. Text the word BLIND to 85944 to donate $10 to the NFB Imagination > Fund via your phone bill. > > The National Federation of the Blind knows that blindness is not the > characteristic that defines you or your future. Every day we raise the > expectations of blind people, because low expectations create obstacles > between blind people and our dreams. You can have the life you want; > blindness is not what holds you back. > > -- > 73' & 75' > Gregory D. Rosenberg AB9MZ > gregg at ricis.com > > RICIS, Inc. > 7849 Bristol Park Drive > Tinley Park, IL 60477-4594 > http://www.ricis.com > > 708-267-6664 Cell > 708-444-2690 Office > 708-444-1115 Fax > (Please call before sending a fax) > > > > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From gjn at gjn.priv.at Tue Jun 17 05:06:40 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Tue, 17 Jun 2014 13:06:40 +0200 Subject: [sles-beta] libvirtd: metadata not found Message-ID: <155892374.PXeRjlWx84@gjn.priv.at> Hello, Is this a problem with libvirtd by a KVM installation? I found a patch on redhat this implements this metadata. #SR ? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From darrent at akurit.com.au Tue Jun 17 18:50:46 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Wed, 18 Jun 2014 10:50:46 +1000 Subject: [sles-beta] Help, getting an autoyast build for "multi-user" target In-Reply-To: References: Message-ID: Team I have been doing some testing on getting a "default graphical build" SLES12B8 server to become a "multi-user" server. It's harder than you would think, mainly due to the way display-server.service seems to be erroneously activated, even on multi-user target boots. I have found this process works: 1. Login to graphical console as root user. 2. run a "terminal" session (the yast service manager process is currently broken, it would be Bets/easier to just run that). 3. cd /etc/systemd/system 4. rm default.target 5. ln -s /usr/lib/systemd/system/multi-user.target default.target 6. cd /usr/lib/systemd/user 7. rm default.target 8. ln -s /usr/lib/systemd/system/multi-user.target default.target 9. cd /usr/lib/systemd/system 10. rm default.target 11. ln -s /usr/lib/systemd/system/multi-user.target default.target **** I have no idea why default.target is in these three locations, I would expect 2 of them are redundant but am not familiar enough with systemd to guess which **** This will "tell" systemd that you want to run in "multi-user" mode (e.g. the old init 3 level, without a X-server/GUI). The problem is that the display-server.service still seems to be run on boot (it mast be hard coded in somewhere) and I have not found a "working" way of stopping it ('systemstl disable display-server' does not help). What I have had to do is the following, which permanently stops the display-server from starting. 12. systemctl mask display-server *** reboot *** 13. shutdown -r now (you can achieve the same result by typing: 'init 3') if you prefer not to reboot. I hope this is found to be helpful. Darren On 16 June 2014 13:08, Darren Thompson wrote: > Team > > Does anyone have an example autoyast file they can share which reliably > builds a server to the "multi-user" target (e.g. no X/display server > running). > > Simmilarly, what are the steps for go from a server built to the > "graphical" target and getting it to reliably boot to the "multi-user" > target. > > The "service-manager" Yast module seems to be able to adjust the "target" > level but I cannot seem to workout how to get it to accept "multi-user" - > Am I missing something or is that yast module "broken"? > > Any/all help appreciated. > > background: > I have traditionally built my SLES servers with the full graphical install. > I would then go into 'yast2 run-level' module and in 'expert mode' change > the default to "run level 3". > This would allow me to run the servers themselves without any graphical > display, but I could still SSH into them and run all the graphical tools > (via x-forwarding). > I'm hoping to be able to achve the same result with SLES12 > > Regards > Darren > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From darrent at akurit.com.au Tue Jun 17 19:13:26 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Wed, 18 Jun 2014 11:13:26 +1000 Subject: [sles-beta] Service-manager configuration under autoyast is a mess Message-ID: Ok team Time for a rant about 'service-management' in SLES12B8 (and all previous betas). First off, it's oddly duplicated in the 'yast autoyast' module (see attached screenshot) which is confusing and could be a reason why it's not working properly. Secondly, all created autoyast file and even the automatically created 'autoinst.xml" file have both a "run-level" and and a "service-manager" section, which contain exactly the same information e.g. graphical graphical Lastly, the syntax/schema used does not even match that listed from the "yast system manager" entry on the public git-hub site ( https://github.com/yast/yast-services-manager ) which is a real pity as it's the only example I have found of how to disable a service (e.g. the pesky "display-server.service" ) when you want to install all the "graphical" files but only want to run "multi-user". This whole mess is going to have to recieve a lot more work before this is ready to be seen/used by the public. Regards Darren -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: service_manager_seeing_double.png Type: image/png Size: 38897 bytes Desc: not available URL: From darrent at akurit.com.au Tue Jun 17 21:02:24 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Wed, 18 Jun 2014 13:02:24 +1000 Subject: [sles-beta] Discussion point, is it worth delaying SLES12 to gain this functionality? Message-ID: Team I have just been reading Lennart Poettering's systemd blog and it got me thinking. Factory Reset, Stateless Systems, Reproducible Systems & Verifiable Systems http://0pointer.de/blog Is it worth delaying the release of SLES12 and incorporating this functionality as it would be a compelling reason to update or switch to SLES12. What are your thoughts? -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From mge at suse.com Wed Jun 18 00:30:45 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 18 Jun 2014 08:30:45 +0200 Subject: [sles-beta] Discussion point, is it worth delaying SLES12 to gain this functionality? In-Reply-To: References: Message-ID: <20140618063045.GB4757@suse.com> Hello Darren, On 2014-06-18 T 13:02 +1000 Darren Thompson wrote: > Team > > I have just been reading Lennart Poettering's systemd > blog and it got me thinking. > > Factory Reset, Stateless Systems, Reproducible Systems > & Verifiable Systems http://0pointer.de/blog Is it > worth delaying the release of SLES12 and incorporating > this functionality as it would be a compelling reason > to update or switch to SLES12. > > What are your thoughts? independent of the topic (I had no time to read the blog yet), SUSE Linux Enterprise has project- and test-plans which go beyond SUSE and not only involve this beta community, but also technology partners for example. Adding more time for betas and release candidates (as we announced some weeks ago) is possible or "in scope", adding a completly new init-stack would not, as it would invalidate a lot of testing. Hope this explains. so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From darrent at akurit.com.au Wed Jun 18 00:53:14 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Wed, 18 Jun 2014 16:53:14 +1000 Subject: [sles-beta] Discussion point, is it worth delaying SLES12 to gain this functionality? In-Reply-To: <20140618063045.GB4757@suse.com> References: <20140618063045.GB4757@suse.com> Message-ID: Matthias All perfectly reasonable, perhaps this could be a "stretch target" for SP1??? Darren On 18 June 2014 16:30, Matthias G. Eckermann wrote: > Hello Darren, > > On 2014-06-18 T 13:02 +1000 Darren Thompson wrote: > > > Team > > > > I have just been reading Lennart Poettering's systemd > > blog and it got me thinking. > > > > Factory Reset, Stateless Systems, Reproducible Systems > > & Verifiable Systems http://0pointer.de/blog Is it > > worth delaying the release of SLES12 and incorporating > > this functionality as it would be a compelling reason > > to update or switch to SLES12. > > > > What are your thoughts? > > independent of the topic (I had no time to read the blog > yet), SUSE Linux Enterprise has project- and test-plans > which go beyond SUSE and not only involve this beta > community, but also technology partners for example. > > Adding more time for betas and release candidates (as we > announced some weeks ago) is possible or "in scope", > adding a completly new init-stack would not, as it would > invalidate a lot of testing. > > Hope this explains. > > so long - > MgE > > -- > Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise > Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com > SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From darrent at akurit.com.au Wed Jun 18 01:01:56 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Wed, 18 Jun 2014 17:01:56 +1000 Subject: [sles-beta] Discussion point, In-Reply-To: <6CDFE0CA-92F4-49CB-8BFF-0CDAED98D7B1@suse.de> References: <6CDFE0CA-92F4-49CB-8BFF-0CDAED98D7B1@suse.de> Message-ID: Olaf A very simple use case is using this in conjunction with containers such that a "stateless" template is used to provision other containers which actually provide applications. e.g. a "factory reset" container is initially run-up and then "statefull" changes are made to the container after that. e.g. rather than running apache on the server OS itself, a container is provisioned, which runs apache/web sites etc. In that way a "cleaner" host OS is maintained and greater isolation between the "required" OS and the "provided" application is possible. As said, this is just a thought bubble for discussion at this time... Darren On 18 June 2014 16:57, Olaf Kirch wrote: > Hi Darren, > > Reading quickly through this, these ideas seem to be primarily geared > towards client type systems. These could inherently be stateless in the > sense that for many things, automated configuration and useful defaults go > a long way. Anything that provides a service is inherently stateful. > Anything that needs to trust an authentication service (such as a > directory) needs to be stateful. > > The other thing that sticks out a little is this: automated provisioning > is a continuing research topic in the communities. Puppet, chef, autoyast, > younameit. None of this stuff is trivial. This makes me wonder what > scenarios Lennart plans to support, specifically. Compared to the > contenders in the provisioning area, his is either a very restricted use > case, or he's underestimating the complexity a little. > > Either way, it sounds like this is really way off in the future. Maybe > material for SLE13, but definitely not for SLE12 :-) > > Regards > Olaf > > Am 18.06.2014 um 05:02 schrieb "Darren Thompson" : > > Team > > I have just been reading Lennart Poettering's systemd blog and it got me > thinking. > > Factory Reset, Stateless Systems, Reproducible Systems & Verifiable Systems > http://0pointer.de/blog > Is it worth delaying the release of SLES12 and incorporating this > functionality as it would be a compelling reason to update or switch to > SLES12. > > What are your thoughts? > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > ** > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From darrent at akurit.com.au Wed Jun 18 01:07:14 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Wed, 18 Jun 2014 17:07:14 +1000 Subject: [sles-beta] Discussion point, In-Reply-To: <6CDFE0CA-92F4-49CB-8BFF-0CDAED98D7B1@suse.de> References: <6CDFE0CA-92F4-49CB-8BFF-0CDAED98D7B1@suse.de> Message-ID: Olaf On another thought "reproducible and verifiable" systems also have merit in that it would be good to know exactly how every host varies from a know state, as it makes intrusion detection etc. much easier to achieve then the current "trip wire" type scenarios we are having to deploy now. Darren On 18 June 2014 16:57, Olaf Kirch wrote: > Hi Darren, > > Reading quickly through this, these ideas seem to be primarily geared > towards client type systems. These could inherently be stateless in the > sense that for many things, automated configuration and useful defaults go > a long way. Anything that provides a service is inherently stateful. > Anything that needs to trust an authentication service (such as a > directory) needs to be stateful. > > The other thing that sticks out a little is this: automated provisioning > is a continuing research topic in the communities. Puppet, chef, autoyast, > younameit. None of this stuff is trivial. This makes me wonder what > scenarios Lennart plans to support, specifically. Compared to the > contenders in the provisioning area, his is either a very restricted use > case, or he's underestimating the complexity a little. > > Either way, it sounds like this is really way off in the future. Maybe > material for SLE13, but definitely not for SLE12 :-) > > Regards > Olaf > > Am 18.06.2014 um 05:02 schrieb "Darren Thompson" : > > Team > > I have just been reading Lennart Poettering's systemd blog and it got me > thinking. > > Factory Reset, Stateless Systems, Reproducible Systems & Verifiable Systems > http://0pointer.de/blog > Is it worth delaying the release of SLES12 and incorporating this > functionality as it would be a compelling reason to update or switch to > SLES12. > > What are your thoughts? > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > ** > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From mge at suse.com Wed Jun 18 01:09:42 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 18 Jun 2014 09:09:42 +0200 Subject: [sles-beta] Discussion point, In-Reply-To: References: <6CDFE0CA-92F4-49CB-8BFF-0CDAED98D7B1@suse.de> Message-ID: <20140618070942.GB7858@suse.com> Hello Darren and all, On 2014-06-18 T 17:01 +1000 Darren Thompson wrote: > A very simple use case is using this in conjunction > with containers such that a "stateless" template is > used to provision other containers which actually > provide applications. e.g. a "factory reset" > container is initially run-up and then "statefull" > changes are made to the container after that. > > e.g. rather than running apache on the server OS > itself, a container is provisioned, which runs > apache/web sites etc. In that way a "cleaner" host OS > is maintained and greater isolation between the > "required" OS and the "provided" application is > possible. isn't this a use case you can implement already today on SUSE Linux Enterprise 11 (SP2+) with LXC containers (probably using btrfs + snapshots)? In the next SUSE Linux Enterprise 12 beta you'll also see that we add Docker as a TechPreview - even more working into the direction you are thinking. => No need to wait for systemd to implement this:-) so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From mge at suse.com Wed Jun 18 01:12:51 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 18 Jun 2014 09:12:51 +0200 Subject: [sles-beta] Discussion point, In-Reply-To: References: <6CDFE0CA-92F4-49CB-8BFF-0CDAED98D7B1@suse.de> Message-ID: <20140618071251.GD7858@suse.com> Hello Darren, On 2014-06-18 T 17:07 +1000 Darren Thompson wrote: > On another thought "reproducible and verifiable" > systems also have merit in that it would be good to > know exactly how every host varies from a know state, > as it makes intrusion detection etc. much easier to > achieve then the current "trip wire" type scenarios > we are having to deploy now. I suggest you review the "Advanced Systems Management" presentation given to the beta group by my colleague Andreas Jaeger some weeks ago. Th "machinery" framework approaches the topic of reproducible installations much broader than what Lennart seems to have in mind (I scanned over the blog meanwhile). so long - MgE > On 18 June 2014 16:57, Olaf Kirch wrote: > > > Hi Darren, > > > > Reading quickly through this, these ideas seem to be primarily geared > > towards client type systems. These could inherently be stateless in the > > sense that for many things, automated configuration and useful defaults go > > a long way. Anything that provides a service is inherently stateful. > > Anything that needs to trust an authentication service (such as a > > directory) needs to be stateful. > > > > The other thing that sticks out a little is this: automated provisioning > > is a continuing research topic in the communities. Puppet, chef, autoyast, > > younameit. None of this stuff is trivial. This makes me wonder what > > scenarios Lennart plans to support, specifically. Compared to the > > contenders in the provisioning area, his is either a very restricted use > > case, or he's underestimating the complexity a little. > > > > Either way, it sounds like this is really way off in the future. Maybe > > material for SLE13, but definitely not for SLE12 :-) > > > > Regards > > Olaf > > > > Am 18.06.2014 um 05:02 schrieb "Darren Thompson" : > > > > Team > > > > I have just been reading Lennart Poettering's systemd blog and it got me > > thinking. > > > > Factory Reset, Stateless Systems, Reproducible Systems & Verifiable Systems > > http://0pointer.de/blog > > Is it worth delaying the release of SLES12 and incorporating this > > functionality as it would be a compelling reason to update or switch to > > SLES12. > > > > What are your thoughts? > > > > > > -- > > > > Darren Thompson > > > > Professional Services Engineer / Consultant > > > > ** > > > > Level 3, 60 City Road > > > > Southgate, VIC 3006 > > > > Mb: 0400 640 414 > > > > Mail: darrent at akurit.com.au > > Web: www.akurit.com.au > > > > _______________________________________________ > > sles-beta mailing list > > sles-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sles-beta > > > > > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From lmb at suse.com Wed Jun 18 01:25:33 2014 From: lmb at suse.com (Lars Marowsky-Bree) Date: Wed, 18 Jun 2014 09:25:33 +0200 Subject: [sles-beta] Discussion point, In-Reply-To: References: <6CDFE0CA-92F4-49CB-8BFF-0CDAED98D7B1@suse.de> Message-ID: <20140618072533.GP2358@suse.de> On 2014-06-18T17:07:14, Darren Thompson wrote: > Olaf > > On another thought "reproducible and verifiable" systems also have merit > in that it would be good to know exactly how every host varies from a know > state, as it makes intrusion detection etc. much easier to achieve then the > current "trip wire" type scenarios we are having to deploy now. This is also something that can be addressed in the cloud/HVM stack. You can clone a "golden" image, and thus also reset everything back to that state at the press of a button (delete & clone again). That works with a variety of containers or hypervisors. (I'm heavily using this for my own SLE 12 and Factory testing based on KVM, hosted on a SLE HA 11 system with OCFS2 for the thin provisioning / cloning.) Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde From fcrozat at suse.com Wed Jun 18 01:52:16 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Wed, 18 Jun 2014 09:52:16 +0200 Subject: [sles-beta] Help, getting an autoyast build for "multi-user" target In-Reply-To: References: Message-ID: <1403077936.4212.154.camel@par-r81vxc7.par.novell.com> Le mercredi 18 juin 2014 ? 10:50 +1000, Darren Thompson a ?crit : > Team > > > I have been doing some testing on getting a "default graphical build" > SLES12B8 server to become a "multi-user" server. > > > It's harder than you would think, mainly due to the way > display-server.service seems to be erroneously activated, even on > multi-user target boots. > > > I have found this process works: > 1. Login to graphical console as root user. > 2. run a "terminal" session (the yast service manager process is > currently broken, it would be Bets/easier to just run that). > 3. cd /etc/systemd/system > 4. rm default.target > 5. ln -s /usr/lib/systemd/system/multi-user.target default.target > 6. cd /usr/lib/systemd/user > 7. rm default.target > 8. ln -s /usr/lib/systemd/system/multi-user.target default.target > 9. cd /usr/lib/systemd/system > 10. rm default.target > 11. ln -s /usr/lib/systemd/system/multi-user.target default.target > **** I have no idea why default.target is in these three locations, I > would expect 2 of them are redundant but am not familiar enough with > systemd to guess which **** Sorry but you are doing this the wrong way. NEVER ever change stuff in /usr/lib/systemd/system. /etc/systemd/system has ALWAYS precedence over /usr/lib/systemd/system, which means file with the same name in /etc/systemd/system will "hide" the one in /usr/lib/systemd/system. The proper way to do it is : run as root: systemctl set-default --force multi-user.target (or if you want to do it manually: ln -s -f /usr/lib/systemd/system/multi-user.target /etc/systemd/system/default.target) That's it. -- Frederic Crozat Project Manager Enterprise Desktop SUSE From darrent at akurit.com.au Wed Jun 18 02:13:24 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Wed, 18 Jun 2014 18:13:24 +1000 Subject: [sles-beta] Help, getting an autoyast build for "multi-user" target In-Reply-To: <1403077936.4212.154.camel@par-r81vxc7.par.novell.com> References: <1403077936.4212.154.camel@par-r81vxc7.par.novell.com> Message-ID: Frederic Good Point... Team, do it the way he says... ;-) e.g. 1. Login to graphical console as root user. 2. run a "terminal" session (the yast service manager process is currently broken, it would be Best/easier to just run that). 3. systemctl set-default --force multi-user.target - This will "tell" systemd that you want to run in "multi-user" mode (e.g. the old init 3 level, without a X-server/GUI). *** reboot *** 4 shutdown -r now (you can achieve the same result by typing: 'init 3' if you prefer not to reboot). If you want to reverse this and run the full "graphical" (X) console again 1. Login to test console as root user. 2. systemctl set-default --force graphical.target - This will "tell" systemd that you want to run in "Graphical" mode (e.g. the old init 5 level, with a X-server/GUI). *** reboot *** 4 shutdown -r now (you can achieve the same result by typing: 'init 5' if you prefer not to reboot). I hope this is found to be helpful. Darren On 18 June 2014 17:52, Frederic Crozat wrote: > Le mercredi 18 juin 2014 ? 10:50 +1000, Darren Thompson a ?crit : > > Team > > > > > > I have been doing some testing on getting a "default graphical build" > > SLES12B8 server to become a "multi-user" server. > > > > > > It's harder than you would think, mainly due to the way > > display-server.service seems to be erroneously activated, even on > > multi-user target boots. > > > > > > I have found this process works: > > 1. Login to graphical console as root user. > > 2. run a "terminal" session (the yast service manager process is > > currently broken, it would be Bets/easier to just run that). > > 3. cd /etc/systemd/system > > 4. rm default.target > > 5. ln -s /usr/lib/systemd/system/multi-user.target default.target > > 6. cd /usr/lib/systemd/user > > 7. rm default.target > > 8. ln -s /usr/lib/systemd/system/multi-user.target default.target > > 9. cd /usr/lib/systemd/system > > 10. rm default.target > > 11. ln -s /usr/lib/systemd/system/multi-user.target default.target > > **** I have no idea why default.target is in these three locations, I > > would expect 2 of them are redundant but am not familiar enough with > > systemd to guess which **** > > Sorry but you are doing this the wrong way. > > NEVER ever change stuff in /usr/lib/systemd/system. /etc/systemd/system > has ALWAYS precedence over /usr/lib/systemd/system, which means file > with the same name in /etc/systemd/system will "hide" the one > in /usr/lib/systemd/system. > > The proper way to do it is : > run as root: systemctl set-default --force multi-user.target > > (or if you want to do it manually: ln -s > -f /usr/lib/systemd/system/multi-user.target > /etc/systemd/system/default.target) > > That's it. > > -- > Frederic Crozat > Project Manager Enterprise Desktop > SUSE > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From rbrown at suse.de Wed Jun 18 03:25:42 2014 From: rbrown at suse.de (Richard Brown) Date: Wed, 18 Jun 2014 11:25:42 +0200 Subject: [sles-beta] Network configuration error during installation with autoyast In-Reply-To: References: Message-ID: <1403083542.13349.18.camel@ibrokeit.suse.de> On Wed, 2014-06-18 at 09:04 +0000, Datacenter/DFS wrote: > Hi, > > i tried SLES 12 Beta 8 with autoyast, but got this error "Internal error. Please report a bug report with logs. Details: Cannot detect used network service ..." (see screenshot). > After installation my eth0 interface is unconfigured, no wicked is running. > > Does anyone know why or observed the same error? Hello, I observed the error in testing, reported it, and I believe it should be resolved in Beta 9 Kind Regards, -- ------------------------------------------------------------------- Richard Brown, QA Engineer Phone +4991174053-361, Fax +4991174053-483 SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) ------------------------------------------------------------------- From KH.Schuh at Fraport.de Wed Jun 18 06:58:52 2014 From: KH.Schuh at Fraport.de (Schuh, Karl-Heinz) Date: Wed, 18 Jun 2014 12:58:52 +0000 Subject: [sles-beta] Network configuration error during installation with autoyast In-Reply-To: <1403083542.13349.18.camel@ibrokeit.suse.de> References: <1403083542.13349.18.camel@ibrokeit.suse.de> Message-ID: <7630C336720B0F4783EB9AE2823C5EB54FA873FC@FRASV010481.fra.fraport.de> HI, we have the same issue with beta8 - still after the autoyast install the network cannot be configured via Yast. Kind regards Karl -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Richard Brown Gesendet: Mittwoch, 18. Juni 2014 11:26 An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] Network configuration error during installation with autoyast On Wed, 2014-06-18 at 09:04 +0000, Datacenter/DFS wrote: > Hi, > > i tried SLES 12 Beta 8 with autoyast, but got this error "Internal error. Please report a bug report with logs. Details: Cannot detect used network service ..." (see screenshot). > After installation my eth0 interface is unconfigured, no wicked is running. > > Does anyone know why or observed the same error? Hello, I observed the error in testing, reported it, and I believe it should be resolved in Beta 9 Kind Regards, -- ------------------------------------------------------------------- Richard Brown, QA Engineer Phone +4991174053-361, Fax +4991174053-483 SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) ------------------------------------------------------------------- _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta Fraport AG Frankfurt Airport Services Worldwide, 60547 Frankfurt am Main, Sitz der Gesellschaft: Frankfurt am Main, Amtsgericht Frankfurt am Main: HRB 7042, Umsatzsteuer-Identifikationsnummer: DE 114150623, Vorsitzender des Aufsichtsrates: Karlheinz Weimar - Hessischer Finanzminister a.D.; Vorstand: Dr. Stefan Schulte (Vorsitzender), Anke Giesen, Michael Mueller, Peter Schmitz, Dr. Matthias Zieschang From Dick.Waite at softwareag.com Wed Jun 18 22:40:03 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Thu, 19 Jun 2014 04:40:03 +0000 Subject: [sles-beta] Thursday June 19th - Beta9 Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D5384CD93@hqmbx6.eur.ad.sag> Grand Sunny Morning in Darmstadt, I thought when I looked on the Beta download I'd see Beta9 ready to play it's part? Did I miss a cancel email? Planned releases: 2014-02-21 SLE 12 Beta 1 2014-03-07 SLE 12 Beta 2 2014-03-21 SLE 12 Beta 3 2014-04-04 SLE 12 Beta 4 2014-04-18 SLE 12 Beta 5 2014-05-09 SLE 12 Beta 6 2014-05-23 SLE 12 Beta 7 2014-06-06 Beta8 2014-06-18 Beta9 2014-07-11 RC1 2014-08-01 RC2 2014-08-22 RC3 2014-09-12 RC4 2014-October GMC __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdouglas at suse.com Wed Jun 18 23:46:50 2014 From: jdouglas at suse.com (Jason Douglas) Date: Thu, 19 Jun 2014 13:46:50 +0800 Subject: [sles-beta] libvirtd: metadata not found In-Reply-To: <155892374.PXeRjlWx84@gjn.priv.at> References: <155892374.PXeRjlWx84@gjn.priv.at> Message-ID: <53A2794A.8050703@suse.com> Hi Gunther, On 06/17/2014 07:06 PM, G?nther J. Niederwimmer wrote: > Hello, > > Is this a problem with libvirtd by a KVM installation? > > I found a patch on redhat this implements this metadata. > > #SR ? > Could you please provide some additional details? It isn't clear what you're referring to, especially since we don't see the string "metadata" in any libvirtd log files. Thanks. Jason From gjn at gjn.priv.at Thu Jun 19 00:17:57 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 19 Jun 2014 08:17:57 +0200 Subject: [sles-beta] libvirtd: metadata not found In-Reply-To: <53A2794A.8050703@suse.com> References: <155892374.PXeRjlWx84@gjn.priv.at> <53A2794A.8050703@suse.com> Message-ID: <2745376.LokCJaJUmJ@gjn.priv.at> Hello Jason, Am Donnerstag, 19. Juni 2014, 13:46:50 schrieb Jason Douglas: > Hi Gunther, > > On 06/17/2014 07:06 PM, G?nther J. Niederwimmer wrote: > > Hello, > > > > Is this a problem with libvirtd by a KVM installation? > > > > I found a patch on redhat this implements this metadata. > > > > #SR ? > > Could you please provide some additional details? It isn't clear what > you're referring to, especially since we don't see the string "metadata" > in any libvirtd log files. Thanks. This is a KVM Installation Beta8 with clients B8 I found in different Logs libvirtd[..]: metadata not found: Requested metadata element is not present I hope this helps? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From mge at suse.com Thu Jun 19 01:06:28 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Thu, 19 Jun 2014 09:06:28 +0200 Subject: [sles-beta] Thursday June 19th - Beta9 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D5384CD93@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D5384CD93@hqmbx6.eur.ad.sag> Message-ID: <20140619070628.GC5903@suse.com> Hello Dick, On 2014-06-19 T 04:40 +0000 Waite, Dick wrote: > 2014-06-18 Beta9 today is a public holiday in (parts of) Germany, and thus we had planned to ship beta9 the day before (=yesterday). However, the builds were in QA until late yesterday night, thus please expect availability tomorrow. Hope this explains. so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From fcrozat at suse.com Thu Jun 19 01:12:06 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Thu, 19 Jun 2014 09:12:06 +0200 Subject: [sles-beta] Thursday June 19th - Beta9 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D5384CD93@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D5384CD93@hqmbx6.eur.ad.sag> Message-ID: <1403161926.7555.3.camel@par-r81vxc7.par.novell.com> Le jeudi 19 juin 2014 ? 04:40 +0000, Waite, Dick a ?crit : > Grand Sunny Morning in Darmstadt, > > I thought when I looked on the Beta download I'd see Beta9 ready to > play it's part? Did I miss a cancel email? Don't worry, we are still targeting this week for Beta9. We should release Beta9 on Friday (as a reminder, today is a holiday in some part of Germany) hopefully (CDN is always slow to propagate ISO). -- Frederic Crozat Project Manager Enterprise Desktop SUSE From jdouglas at suse.com Thu Jun 19 02:10:13 2014 From: jdouglas at suse.com (Jason Douglas) Date: Thu, 19 Jun 2014 02:10:13 -0600 Subject: [sles-beta] libvirtd: metadata not found In-Reply-To: <2745376.LokCJaJUmJ@gjn.priv.at> References: <155892374.PXeRjlWx84@gjn.priv.at> <53A2794A.8050703@suse.com> <2745376.LokCJaJUmJ@gjn.priv.at> Message-ID: <53A29AE5.9000608@suse.com> Hi Gunther, On 06/19/2014 12:17 AM, G?nther J. Niederwimmer wrote: > Hello Jason, > > Am Donnerstag, 19. Juni 2014, 13:46:50 schrieb Jason Douglas: >> Hi Gunther, >> >> On 06/17/2014 07:06 PM, G?nther J. Niederwimmer wrote: >>> Hello, >>> >>> Is this a problem with libvirtd by a KVM installation? >>> >>> I found a patch on redhat this implements this metadata. >>> >>> #SR ? >> Could you please provide some additional details? It isn't clear what >> you're referring to, especially since we don't see the string "metadata" >> in any libvirtd log files. Thanks. > This is a KVM Installation Beta8 with clients B8 > > I found in different Logs > > libvirtd[..]: metadata not found: Requested metadata element is not present > > I hope this helps? We don't see anything like that in our logs. What tool are you using for VM management? Is it just the standard stuff that ships with SLES 12 (virt-manager, for example)? Is there a specific operation you're performing on your VM when you see that error? Does it correlate to changing the VM configuration, or to migrating the VM, for example? We'd like to help you get to the bottom of this, so thank you for your patience. jason From msvec at suse.com Thu Jun 19 02:24:14 2014 From: msvec at suse.com (Michal Svec) Date: Thu, 19 Jun 2014 10:24:14 +0200 (CEST) Subject: [sles-beta] [ANNOUNCE] Docker in SLES 12 Message-ID: Dear Beta participants, we are happy to announce that SUSE will include Docker as a part of SLES 12. For those not familiar with Docker yet, it is an open-source project that automates the deployment of applications inside software containers. It builds on top of Linux Containers, which we have had in SLES since quite some time (SLES 11 SP2) already and adds another layer allowing for easy image deployment and management. Starting with SLES 12 Beta8 Docker is now included on the SLES installation media, for now as a Technology Preview, feel free to give it a try and let us know how it works! Thanks in advance for all your testing Your SUSE Linux Enterprise Team Regards Michal -- Michal Svec Senior Product Manager SUSE Linux Enterprise, Virtualization SUSE, www.suse.com From darrent at akurit.com.au Thu Jun 19 02:26:40 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Thu, 19 Jun 2014 18:26:40 +1000 Subject: [sles-beta] [ANNOUNCE] Docker in SLES 12 In-Reply-To: References: Message-ID: Team Excellent work, is there any documentation or install/configure etc available yet? Is there a Cluster HA OCF template for Docker (Or am I just getting too far ahead of myself)? Regards Darren On 19 June 2014 18:24, Michal Svec wrote: > > Dear Beta participants, > > we are happy to announce that SUSE will include Docker as a part of SLES > 12. For those not familiar with Docker yet, it is an open-source project > that automates the deployment of applications inside software containers. > It builds on top of Linux Containers, which we have had in SLES since quite > some time (SLES 11 SP2) already and adds another layer allowing for easy > image deployment and management. > > Starting with SLES 12 Beta8 Docker is now included on the SLES > installation media, for now as a Technology Preview, feel free to give it a > try and let us know how it works! > > Thanks in advance for all your testing > > Your SUSE Linux Enterprise Team > > Regards > Michal > > -- > Michal Svec > Senior Product Manager > SUSE Linux Enterprise, Virtualization > SUSE, www.suse.com > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From lmb at suse.com Thu Jun 19 02:34:24 2014 From: lmb at suse.com (Lars Marowsky-Bree) Date: Thu, 19 Jun 2014 10:34:24 +0200 Subject: [sles-beta] [ANNOUNCE] Docker in SLES 12 In-Reply-To: References: Message-ID: <20140619083424.GL2358@suse.de> On 2014-06-19T18:26:40, Darren Thompson wrote: > Team > > Excellent work, is there any documentation or install/configure etc > available yet? > > Is there a Cluster HA OCF template for Docker (Or am I just getting too far > ahead of myself)? There isn't a resource agent for Docker yet in our product. If you want to play around with a current development version, you can grab one from https://github.com/davidvossel/resource-agents/commit/59ec814f6006bfe73d4caf5783cbe0778933fa32 though. Use at your own risk ;-) Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde From msvec at suse.com Thu Jun 19 02:44:38 2014 From: msvec at suse.com (Michal Svec) Date: Thu, 19 Jun 2014 10:44:38 +0200 (CEST) Subject: [sles-beta] [ANNOUNCE] Docker in SLES 12 In-Reply-To: References: Message-ID: Hello There's no documentation available yet, for now I recommend to follow the upstream official docu. I will see if we could provide something soon. Thanks Michal On Thu, 19 Jun 2014, Darren Thompson wrote: > Team > > Excellent work, is there any documentation or install/configure etc > available yet? > > Is there a Cluster HA OCF template for Docker (Or am I just getting too far > ahead of myself)? > > Regards > Darren > > > On 19 June 2014 18:24, Michal Svec wrote: > >> >> Dear Beta participants, >> >> we are happy to announce that SUSE will include Docker as a part of SLES >> 12. For those not familiar with Docker yet, it is an open-source project >> that automates the deployment of applications inside software containers. >> It builds on top of Linux Containers, which we have had in SLES since quite >> some time (SLES 11 SP2) already and adds another layer allowing for easy >> image deployment and management. >> >> Starting with SLES 12 Beta8 Docker is now included on the SLES >> installation media, for now as a Technology Preview, feel free to give it a >> try and let us know how it works! >> >> Thanks in advance for all your testing >> >> Your SUSE Linux Enterprise Team >> >> Regards >> Michal >> >> -- >> Michal Svec >> Senior Product Manager >> SUSE Linux Enterprise, Virtualization >> SUSE, www.suse.com >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta >> > > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > From gjn at gjn.priv.at Thu Jun 19 05:12:33 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 19 Jun 2014 13:12:33 +0200 Subject: [sles-beta] libvirtd: metadata not found In-Reply-To: <53A29AE5.9000608@suse.com> References: <155892374.PXeRjlWx84@gjn.priv.at> <2745376.LokCJaJUmJ@gjn.priv.at> <53A29AE5.9000608@suse.com> Message-ID: <9058454.4c5namfg66@gjn.priv.at> Hello Jason, Am Donnerstag, 19. Juni 2014, 02:10:13 schrieb Jason Douglas: > Hi Gunther, > > On 06/19/2014 12:17 AM, G?nther J. Niederwimmer wrote: > > Hello Jason, > > > > Am Donnerstag, 19. Juni 2014, 13:46:50 schrieb Jason Douglas: > >> Hi Gunther, > >> > >> On 06/17/2014 07:06 PM, G?nther J. Niederwimmer wrote: > >>> Hello, > >>> > >>> Is this a problem with libvirtd by a KVM installation? > >>> > >>> I found a patch on redhat this implements this metadata. > >>> > >>> #SR ? > >> > >> Could you please provide some additional details? It isn't clear what > >> you're referring to, especially since we don't see the string "metadata" > >> in any libvirtd log files. Thanks. > > > > This is a KVM Installation Beta8 with clients B8 > > > > I found in different Logs > > > > libvirtd[..]: metadata not found: Requested metadata element is not > > present > > > > I hope this helps? > > We don't see anything like that in our logs. What tool are you using for > VM management? Is it just the standard stuff that ships with SLES 12 > (virt-manager, for example)? :(. Yes, I install with original virt-manager. > Is there a specific operation you're performing on your VM when you see > that error? Does it correlate to changing the VM configuration, or to > migrating the VM, for example? I found it now ;) I am with "ssh -X root at server" on the server and when I start remote virt- manager, I found on a second remote Session with tail - f /var/log/messages this Log by starting virt-manager. Is this virt-manager oder ssh? > We'd like to help you get to the bottom of this, so thank you for your > patience. Thank's -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From darrent at akurit.com.au Fri Jun 20 02:19:37 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Fri, 20 Jun 2014 18:19:37 +1000 Subject: [sles-beta] SLSE12 - Activation codes and mirror account details Message-ID: Team I have to admit that I have been just skipping past the registration screen so far. With the imminent SLSE12B9 I want to start testing registration, updates and SMT. I seem to have missed the information on how to get a valid "evaluation" code for SLES12 and SLES12HA? Also how do I get the equivalent of "mirror credentials" for SCC to feed into SMT? -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From mge at suse.com Fri Jun 20 02:39:32 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Fri, 20 Jun 2014 10:39:32 +0200 Subject: [sles-beta] SLSE12 - Activation codes and mirror account details In-Reply-To: References: Message-ID: <20140620083932.GA25113@suse.com> Hello Darren and all, On 2014-06-20 T 18:19 +1000 Darren Thompson wrote: > I have to admit that I have been just skipping past > the registration screen so far. > > With the imminent SLSE12B9 I want to start testing > registration, updates and SMT. > > I seem to have missed the information on how to get a > valid "evaluation" code for SLES12 and SLES12HA? just use a valid SLE 11 code, either a real one or an evaluation code, as you get it from the download site. My understanding is that during the beta phase the use of a valid SLE 11 code will not be "accounted" for. > Also how do I get the equivalent of "mirror > credentials" for SCC to feed into SMT? The SLE 11 "mirror credentials" do work for me: I am are using the SMT Beta code as announced by Jiri. Please consult the README provided in the SMT Beta download directory for advice, how to migrate an existing, NCC based, SMT to SCC. Make sure to have a backup of your SMT configuration and data, just in case you have a need to go back. Btw.: this would be a good question for the SMT Beta mailinglist! Hint, hint, ... so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From darrent at akurit.com.au Fri Jun 20 02:45:00 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Fri, 20 Jun 2014 18:45:00 +1000 Subject: [sles-beta] SLSE12 - Activation codes and mirror account details In-Reply-To: <20140620083932.GA25113@suse.com> References: <20140620083932.GA25113@suse.com> Message-ID: Matthais Thank you for the responses. It would have been nicer/tidier if we could have had "clean" SLES12 codes to use so that out SLES11 subscriptions don't get crudded up with test systems etc. There is a SMT beta mailing list!!!! What is the mailing list address please? Darren On 20 June 2014 18:39, Matthias G. Eckermann wrote: > Hello Darren and all, > > On 2014-06-20 T 18:19 +1000 Darren Thompson wrote: > > > I have to admit that I have been just skipping past > > the registration screen so far. > > > > With the imminent SLSE12B9 I want to start testing > > registration, updates and SMT. > > > > I seem to have missed the information on how to get a > > valid "evaluation" code for SLES12 and SLES12HA? > > just use a valid SLE 11 code, either a real one or an > evaluation code, as you get it from the download site. > > My understanding is that during the beta phase the use > of a valid SLE 11 code will not be "accounted" for. > > > Also how do I get the equivalent of "mirror > > credentials" for SCC to feed into SMT? > > The SLE 11 "mirror credentials" do work for me: I am > are using the SMT Beta code as announced by Jiri. > Please consult the README provided in the SMT Beta > download directory for advice, how to migrate an > existing, NCC based, SMT to SCC. Make sure to have a > backup of your SMT configuration and data, just in case > you have a need to go back. > > Btw.: this would be a good question for the SMT Beta > mailinglist! Hint, hint, ... > > so long - > MgE > > -- > Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise > Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com > SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From jdouglas at suse.com Fri Jun 20 02:48:26 2014 From: jdouglas at suse.com (Jason Douglas) Date: Fri, 20 Jun 2014 02:48:26 -0600 Subject: [sles-beta] libvirtd: metadata not found In-Reply-To: <9058454.4c5namfg66@gjn.priv.at> References: <155892374.PXeRjlWx84@gjn.priv.at> <2745376.LokCJaJUmJ@gjn.priv.at> <53A29AE5.9000608@suse.com> <9058454.4c5namfg66@gjn.priv.at> Message-ID: <53A3F55A.3020702@suse.com> Hi Gunther, Thanks for your help. With your hint, we were able to duplicate the error in-house. Here's what my lead libvirt engineer has to say about it: ------- As it turns out, not really an error. If the domain config contains , I don't see the log message. E.g. <domain type='kvm'> <name>sles12b8-kvm</name> <uuid>40855800-b30d-c171-d447-f84e30aaa6cf</uuid> <title>This is a test ... virt-manager now asks for a domain's via virDomainGetMetadata. If the title exists, it is displayed next to the domain's little icon. virt-manager swallows the error if no <title> exists. virDomainGetMetadata is correctly returning an error (it cannot retrieve the requested metadata afterall), with the side-affect of the log entry. I'm not sure what we can do here, beyond patching out this little virt-manager feature. Jim ------- We haven't decided how to handle this in house, but now that we know the problem exists, we can deal with it. Do you have any questions or preferences on how we "fix" this issue? Thanks again for your diligent testing. Jason On 06/19/2014 05:12 AM, G?nther J. Niederwimmer wrote: > Hello Jason, > > Am Donnerstag, 19. Juni 2014, 02:10:13 schrieb Jason Douglas: >> Hi Gunther, >> >> On 06/19/2014 12:17 AM, G?nther J. Niederwimmer wrote: >>> Hello Jason, >>> >>> Am Donnerstag, 19. Juni 2014, 13:46:50 schrieb Jason Douglas: >>>> Hi Gunther, >>>> >>>> On 06/17/2014 07:06 PM, G?nther J. Niederwimmer wrote: >>>>> Hello, >>>>> >>>>> Is this a problem with libvirtd by a KVM installation? >>>>> >>>>> I found a patch on redhat this implements this metadata. >>>>> >>>>> #SR ? >>>> Could you please provide some additional details? It isn't clear what >>>> you're referring to, especially since we don't see the string "metadata" >>>> in any libvirtd log files. Thanks. >>> This is a KVM Installation Beta8 with clients B8 >>> >>> I found in different Logs >>> >>> libvirtd[..]: metadata not found: Requested metadata element is not >>> present >>> >>> I hope this helps? >> We don't see anything like that in our logs. What tool are you using for >> VM management? Is it just the standard stuff that ships with SLES 12 >> (virt-manager, for example)? > :(. > > Yes, I install with original virt-manager. > >> Is there a specific operation you're performing on your VM when you see >> that error? Does it correlate to changing the VM configuration, or to >> migrating the VM, for example? > I found it now ;) > > I am with "ssh -X root at server" on the server and when I start remote virt- > manager, I found on a second remote Session with tail - f /var/log/messages > this Log by starting virt-manager. > > Is this virt-manager oder ssh? > >> We'd like to help you get to the bottom of this, so thank you for your >> patience. > Thank's > From darrent at akurit.com.au Fri Jun 20 03:00:40 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Fri, 20 Jun 2014 19:00:40 +1000 Subject: [sles-beta] SLSE12 - Activation codes and mirror account details In-Reply-To: <CAEUhfEcviLqcgQT9US8Qy3Ryy9QQsN=RzLVtSM2O4akzKTnyKQ@mail.gmail.com> References: <CAEUhfEecM9n-iG46ES7uajv9Bz90-cTr+qrTcK71BUXtaWEyvA@mail.gmail.com> <20140620083932.GA25113@suse.com> <CAEUhfEcviLqcgQT9US8Qy3Ryy9QQsN=RzLVtSM2O4akzKTnyKQ@mail.gmail.com> Message-ID: <CAEUhfEch3TbA4-mCeY4QfpgLpTxiO=Upyy5FcMs-EZeM9=P5-g@mail.gmail.com> Matthias I'm not sure if I'm subscribed to the SMT Beta mail list and don;t know it's address to post to it so please ecuse my posting to these inappropriate lists until that is sorted out. How do I find out what the "mirror credentials" are in SCC? I can't seem to find an entry for that anywhere (it's all new so I could easily be missing the obvious). Do I need to go back to the NCC and dig out the SMT mirror credentials from there? Thanks Darren On 20 June 2014 18:45, Darren Thompson <darrent at akurit.com.au> wrote: > Matthais > > Thank you for the responses. It would have been nicer/tidier if we could > have had "clean" SLES12 codes to use so that out SLES11 subscriptions don't > get crudded up with test systems etc. > > There is a SMT beta mailing list!!!! > > What is the mailing list address please? > > Darren > > > On 20 June 2014 18:39, Matthias G. Eckermann <mge at suse.com> wrote: > >> Hello Darren and all, >> >> On 2014-06-20 T 18:19 +1000 Darren Thompson wrote: >> >> > I have to admit that I have been just skipping past >> > the registration screen so far. >> > >> > With the imminent SLSE12B9 I want to start testing >> > registration, updates and SMT. >> > >> > I seem to have missed the information on how to get a >> > valid "evaluation" code for SLES12 and SLES12HA? >> >> just use a valid SLE 11 code, either a real one or an >> evaluation code, as you get it from the download site. >> >> My understanding is that during the beta phase the use >> of a valid SLE 11 code will not be "accounted" for. >> >> > Also how do I get the equivalent of "mirror >> > credentials" for SCC to feed into SMT? >> >> The SLE 11 "mirror credentials" do work for me: I am >> are using the SMT Beta code as announced by Jiri. >> Please consult the README provided in the SMT Beta >> download directory for advice, how to migrate an >> existing, NCC based, SMT to SCC. Make sure to have a >> backup of your SMT configuration and data, just in case >> you have a need to go back. >> >> Btw.: this would be a good question for the SMT Beta >> mailinglist! Hint, hint, ... >> >> so long - >> MgE >> >> -- >> Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise >> Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com >> SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany >> GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) >> > > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au <steve at akurit.com.au> > Web: www.akurit.com.au > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au <steve at akurit.com.au> Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140620/e17469f6/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140620/e17469f6/attachment.jpg> From jsrain at suse.cz Fri Jun 20 03:19:33 2014 From: jsrain at suse.cz (Jiri Srain) Date: Fri, 20 Jun 2014 11:19:33 +0200 Subject: [sles-beta] SLSE12 - Activation codes and mirror account details In-Reply-To: <CAEUhfEcviLqcgQT9US8Qy3Ryy9QQsN=RzLVtSM2O4akzKTnyKQ@mail.gmail.com> References: <CAEUhfEecM9n-iG46ES7uajv9Bz90-cTr+qrTcK71BUXtaWEyvA@mail.gmail.com> <20140620083932.GA25113@suse.com> <CAEUhfEcviLqcgQT9US8Qy3Ryy9QQsN=RzLVtSM2O4akzKTnyKQ@mail.gmail.com> Message-ID: <53A3FCA5.8000904@suse.cz> On 06/20/2014 10:45 AM, Darren Thompson wrote: > Matthais > > Thank you for the responses. It would have been nicer/tidier if we could > have had "clean" SLES12 codes to use so that out SLES11 subscriptions > don't get crudded up with test systems etc. > > There is a SMT beta mailing list!!!! > > What is the mailing list address please? The announcement went out on sles-beta, see http://lists.suse.com/mailman/private/sles-beta/Week-of-Mon-20140609/001032.html It includes the information how to get and install it, as well as pointers to the mailing list. > > On 20 June 2014 18:39, Matthias G. Eckermann <mge at suse.com > <mailto:mge at suse.com>> wrote: > > Hello Darren and all, > > On 2014-06-20 T 18:19 +1000 Darren Thompson wrote: > > > I have to admit that I have been just skipping past > > the registration screen so far. > > > > With the imminent SLSE12B9 I want to start testing > > registration, updates and SMT. Please, be aware that SMT was tested with Beta8. AFAIK Beta9 switches to newer version of the SCC API, which is not supported by the released SMT. I intend to release an update of SMT as soon as possible, after some testing with Beta9, however, I cannot give any ETA at the moment. For now, please, use Beta8 for testing against SMT. Jiri > > I seem to have missed the information on how to get a > > valid "evaluation" code for SLES12 and SLES12HA? > > just use a valid SLE 11 code, either a real one or an > evaluation code, as you get it from the download site. > > My understanding is that during the beta phase the use > of a valid SLE 11 code will not be "accounted" for. > > > Also how do I get the equivalent of "mirror > > credentials" for SCC to feed into SMT? > > The SLE 11 "mirror credentials" do work for me: I am > are using the SMT Beta code as announced by Jiri. > Please consult the README provided in the SMT Beta > download directory for advice, how to migrate an > existing, NCC based, SMT to SCC. Make sure to have a > backup of your SMT configuration and data, just in case > you have a need to go back. > > Btw.: this would be a good question for the SMT Beta > mailinglist! Hint, hint, ... > > so long - > MgE > > -- > Matthias G. Eckermann Senior Product Manager SUSE? Linux > Enterprise > Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: > mge at suse.com <mailto:mge at suse.com> > SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg > Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG > N?rnberg) > > > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *cid:image001.jpg at 01CB7C0C.6C6A2AE0* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au <mailto:steve at akurit.com.au> > Web: www.akurit.com.au <http://www.akurit.com.au/> > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com From HamidulR at hcl.com Fri Jun 20 06:02:30 2014 From: HamidulR at hcl.com (Hamidul Rahman) Date: Fri, 20 Jun 2014 12:02:30 +0000 Subject: [sles-beta] Problems installing SLES12 under VMware Player In-Reply-To: <53A421B4.50405@ucs.cam.ac.uk> References: <53A421B4.50405@ucs.cam.ac.uk> Message-ID: <62D27842303B754FA23E7D980200CF672D42AE3D@NDA-HCLC-MBS03.hclc.corp.hcl.in> I Am using VMware workstation 10 and I am also getting the error during installation of SLES12 Beta 8. I am unable to install Beta 8 on VMware workstation. Regards Hamidul Rahman -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Simon Flood Sent: Friday, June 20, 2014 5:28 PM To: sles-beta at lists.suse.com Subject: [sles-beta] Problems installing SLES12 under VMware Player Is anyone else using VMware Player 6 (or perhaps VMware Workstation 10) to test SLES12? For the past couple of betas, beta 7 and 8, I'm getting a kernel panic after the system boots once install completed. See attached screenshot. I'm using the SLES11 64-bit guest OS profile and have tried switching from SCSI to SATA disks plus upping virtual RAM from 768MB to 1GB but that doesn't seem to have made any difference. These are basic text-only installs of SLES12 with nothing fancy. I'm booting from mini ISO then pointing at network-mounted DVD ISO. Both ISOs match their checksums. I saw it with a beta 6 but that seemed to be a one off as after restarting VM it then booted. Now it seems to be repeatable. Thanks, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------------------------------------------------------------------------------------- From Dick.Waite at softwareag.com Fri Jun 20 06:35:57 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Fri, 20 Jun 2014 12:35:57 +0000 Subject: [sles-beta] Problems installing SLES12 under VMware Player In-Reply-To: <62D27842303B754FA23E7D980200CF672D42AE3D@NDA-HCLC-MBS03.hclc.corp.hcl.in> References: <53A421B4.50405@ucs.cam.ac.uk> <62D27842303B754FA23E7D980200CF672D42AE3D@NDA-HCLC-MBS03.hclc.corp.hcl.in> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D5384E428@hqmbx6.eur.ad.sag> Grand Friday Afternoon, I test with VMware Workstation 10.0.2 on x86_64 machines. I have tested since Beta1 of SLE v12. I have not seen any issues with a New Install, I do get issues, as I have often nagged on this list with an Update/Upgrade from SLE 11-SP3. For the new install I use defaults as much as posable. I boot from the DVD1 iso's using both server and DSK. I have not tried to use a mini iso. When, when Beta9 arrives I'll try a New Install as the first test and let you know how it goes. Are you Workstation 10.0.2-b1744117 ? __R ___________________________________________ Dick Waite Senior R&D Consultant Phone: +49 6151 92-1505 Mobile: +49 171 8393 769 Software AG Uhlandstr. 12 | 64297 Darmstadt | Germany www.softwareag.com ___________________________________________ -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Hamidul Rahman Sent: Friday, June 20, 2014 2:03 PM To: Simon Flood; sles-beta at lists.suse.com Subject: Re: [sles-beta] Problems installing SLES12 under VMware Player I Am using VMware workstation 10 and I am also getting the error during installation of SLES12 Beta 8. I am unable to install Beta 8 on VMware workstation. Regards Hamidul Rahman -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Simon Flood Sent: Friday, June 20, 2014 5:28 PM To: sles-beta at lists.suse.com Subject: [sles-beta] Problems installing SLES12 under VMware Player Is anyone else using VMware Player 6 (or perhaps VMware Workstation 10) to test SLES12? For the past couple of betas, beta 7 and 8, I'm getting a kernel panic after the system boots once install completed. See attached screenshot. I'm using the SLES11 64-bit guest OS profile and have tried switching from SCSI to SATA disks plus upping virtual RAM from 768MB to 1GB but that doesn't seem to have made any difference. These are basic text-only installs of SLES12 with nothing fancy. I'm booting from mini ISO then pointing at network-mounted DVD ISO. Both ISOs match their checksums. I saw it with a beta 6 but that seemed to be a one off as after restarting VM it then booted. Now it seems to be repeatable. Thanks, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------------------------------------------------------------------------------------- _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From S.M.Flood at ucs.cam.ac.uk Fri Jun 20 07:17:38 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Fri, 20 Jun 2014 14:17:38 +0100 Subject: [sles-beta] Problems installing SLES12 under VMware Player In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D5384E428@hqmbx6.eur.ad.sag> References: <53A421B4.50405@ucs.cam.ac.uk> <62D27842303B754FA23E7D980200CF672D42AE3D@NDA-HCLC-MBS03.hclc.corp.hcl.in> <46AC8C81C10B8C48820201DF2AE1D76D5384E428@hqmbx6.eur.ad.sag> Message-ID: <53A43472.9010800@ucs.cam.ac.uk> On 20/06/2014 13:35, Waite, Dick wrote: > I test with VMware Workstation 10.0.2 on x86_64 machines. I have tested since Beta1 of SLE v12. I have not seen any issues with a New Install, I do get issues, as I have often nagged on this list with an Update/Upgrade from SLE 11-SP3. For the new install I use defaults as much as posable. I boot from the DVD1 iso's using both server and DSK. I have not tried to use a mini iso. When, when Beta9 arrives I'll try a New Install as the first test and let you know how it goes. Are you Workstation 10.0.2-b1744117 ? Thanks for the clue as installing from DVD ISO did the trick (whereas it seems repeatable when installing from network via mini ISO). A grand Friday afternoon indeed! I'll now do a network install via DVD to try and narrow it down to network and/or mini ISO. Note I'm not registering (thus not updating) during these particular installs. Thanks, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner From S.M.Flood at ucs.cam.ac.uk Fri Jun 20 07:21:22 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Fri, 20 Jun 2014 14:21:22 +0100 Subject: [sles-beta] Problems installing SLES12 under VMware Player In-Reply-To: <53A43472.9010800@ucs.cam.ac.uk> References: <53A421B4.50405@ucs.cam.ac.uk> <62D27842303B754FA23E7D980200CF672D42AE3D@NDA-HCLC-MBS03.hclc.corp.hcl.in> <46AC8C81C10B8C48820201DF2AE1D76D5384E428@hqmbx6.eur.ad.sag> <53A43472.9010800@ucs.cam.ac.uk> Message-ID: <53A43552.4050108@ucs.cam.ac.uk> On 20/06/2014 14:17, Simon Flood wrote: > Thanks for the clue as installing from DVD ISO did the trick (whereas it > seems repeatable when installing from network via mini ISO). A grand > Friday afternoon indeed! Grr I typed too soon - since the VM is NATted I disabled IPv6 in YaST (and changed hostname) then rebooted via "init 6". Result = kernel panic. So it's not a mini vs DVD ISO thing. Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner From allen at ua.edu Fri Jun 20 07:20:36 2014 From: allen at ua.edu (Beddingfield, Allen) Date: Fri, 20 Jun 2014 13:20:36 +0000 Subject: [sles-beta] Installation under Citrix XenServer 6.2.x Message-ID: <AAD7066EC17A5541BF5145CD44BEFA72010045BDED@EX10MBN02.ua-net.ua.edu> This may have been addressed before, but I can't recall seeing any messages about it... Has anyone had any success getting Beta 8 to install under Citrix XenServer 6.2? It goes through the motions of installing, and then it powers the VM down at this point in startup: Xen virtual console successfully installed as ttys0 i8042: PNP: No PS/2 controller found. Probing ports directly Those are the last two lines displayed before it powers down. Thanks. Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama From S.M.Flood at ucs.cam.ac.uk Fri Jun 20 07:54:29 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Fri, 20 Jun 2014 14:54:29 +0100 Subject: [sles-beta] Problems installing SLES12 under VMware Player In-Reply-To: <53A43552.4050108@ucs.cam.ac.uk> References: <53A421B4.50405@ucs.cam.ac.uk> <62D27842303B754FA23E7D980200CF672D42AE3D@NDA-HCLC-MBS03.hclc.corp.hcl.in> <46AC8C81C10B8C48820201DF2AE1D76D5384E428@hqmbx6.eur.ad.sag> <53A43472.9010800@ucs.cam.ac.uk> <53A43552.4050108@ucs.cam.ac.uk> Message-ID: <53A43D15.1040706@ucs.cam.ac.uk> On 20/06/2014 14:21, Simon Flood wrote: > Grr I typed too soon - since the VM is NATted I disabled IPv6 in YaST > (and changed hostname) then rebooted via "init 6". Result = kernel panic. Now seemingly fixed by booting into Rescue mode and running mkinitrd. Odd. Very odd. Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner From allen at ua.edu Fri Jun 20 08:07:19 2014 From: allen at ua.edu (Beddingfield, Allen) Date: Fri, 20 Jun 2014 14:07:19 +0000 Subject: [sles-beta] Installation under Citrix XenServer 6.2.x In-Reply-To: <53A40784020000750004B3CF@inet.eastcobbgroup.com> References: <AAD7066EC17A5541BF5145CD44BEFA72010045BDED@EX10MBN02.ua-net.ua.edu>, <53A40784020000750004B3CF@inet.eastcobbgroup.com> Message-ID: <AAD7066EC17A5541BF5145CD44BEFA72010045C04A@EX10MBN02.ua-net.ua.edu> I'll give that a try. I was using the SLES 11 selection... -- Allen Beddingfield Systems Engineer The University of Alabama ________________________________________ From: James Taylor [James.Taylor at eastcobbgroup.com] Sent: Friday, June 20, 2014 9:05 AM To: Beddingfield, Allen Subject: Re: [sles-beta] Installation under Citrix XenServer 6.2.x I was able to install beta5 into a Xenserver 6.2 environment using the "other" OS selection. I haven't tried beta8, yet. -jt James Taylor 678-697-9420 james.taylor at eastcobbgroup.com >>> "Beddingfield, Allen" <allen at ua.edu> 6/20/2014 9:20 AM >>> This may have been addressed before, but I can't recall seeing any messages about it... Has anyone had any success getting Beta 8 to install under Citrix XenServer 6.2? It goes through the motions of installing, and then it powers the VM down at this point in startup: Xen virtual console successfully installed as ttys0 i8042: PNP: No PS/2 controller found. Probing ports directly Those are the last two lines displayed before it powers down. Thanks. Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta If this is an unsolicited spam message, please click this link to report it: http://control.eastcobbgroup.com:49285/contents/spamreport.shtml?rptid=51847&srvid=16vl15t From fcrozat at suse.com Fri Jun 20 09:37:01 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 20 Jun 2014 17:37:01 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 12 Beta9 is available Message-ID: <1403278621.2047.66.camel@par-r81vxc7.par.novell.com> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta participants, we are happy to announce the ninth Beta of SUSE Linux Enterprise Server 12. ISO images should be available soon for download (replication is ongoing on our CDN provider). Please go to http://www.novell.com/beta and select "View my beta page". Here you should see all Beta's you are part of. Note that the directory contains the images for the SDK as well as for the SLE-WE Extension. We offer 3 DVD ISOs: DVD1 contains the binaries, the second DVD the sources and the third DVD the debuginfo packages. The final product will not contain the debuginfo packages on the media. For installation purposes you just need Media 1 for your architecture. Please verify the md5sum of the ISO using the MD5SUMS file, which can be found in the same directory on the download servers. Known issues (selection): (several) - not all texts are translated yet, but most are 881676 - runlevel 5 => 3 doesn't switch to VT1 but sticks on VT7 (general) - Firefox 30 beta8 is part of Beta8 (Firefox 31 ESR is target for SLE12) 883500 (ppc64le only): Bad page map in process modprobe Installation on s390x: Please disable the blacklisting of devices during the installation (cio_ignore). This code still has a bug and other devices beside the IPL device and the console are not enabled (bnc#882685) With this Beta9 snapshot we have reached several milestones: o Continue update, performance and regression tests. o Continue intense stress and certification tests. Be aware that we have provided snapshots of 'modules' at the download page with this Beta 9: Module "Legacy": The Legacy Module supports your migration from SUSE Linux Enterprise 10 and 11 and other systems to SUSE Linux Enterprise 12, by providing packages which are discontinued on SUSE Linux Enterprise Server, but which you may rely on, such as: CyrusIMAP, BSD like ftp client, sendmail, IBM Java6. Access to the Legacy Module is included in your SUSE Linux Enterprise Server subscription. The module has a different lifecycle than SUSE Linux Enterprise Server itself; please check the Release Notes for further details. Module "Web & Scripting": The SUSE Linux Enterprise Web and Scripting Module delivers a comprehensive suite of scripting languages, frameworks, and related tools helping developers and systems administrators accelerate the creation of stable, modern web applications. Access to the Web and Scripting Module is included in your SUSE Linux Enterprise Server subscription. The module has a different lifecycle than SUSE Linux Enterprise Server itself; please check the Release Notes for further details. Module "Advanced System Management": This Module gives you a sneak-peak into our upcoming systems management toolbox which allows you to inspect systems remotely, store their system description and create new systems to deploy them in datacenters and clouds. The toolbox is still in active development and will get regular updates. Note that both are provided "as is" and not all packages that will go into them are already contained in them. We recommend to use them through the repositories available online after registration. Thanks in advance for all your testing Your SUSE Linux Enterprise Team -- Frederic Crozat Project Manager Enterprise Desktop SUSE -- Frederic Crozat Project Manager Enterprise Desktop SUSE From fcrozat at suse.com Fri Jun 20 09:37:12 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 20 Jun 2014 17:37:12 +0200 Subject: [sles-beta] [ANNOUNCE] Changelog for SLES 12 Beta9 Message-ID: <1403278632.2047.67.camel@par-r81vxc7.par.novell.com> As mentionned in the announcement email, CDN is propagating ISO around the globe. If you don't see Beta9 there or get an 404 error when trying to download, wait some hours and try again. Find attached the Changelog differences between Beta 8 and Beta 9. The complete changelog can be found on DVD 1. thanks, Your SUSE Linux Enterprise Team -- Frederic Crozat Project Manager Enterprise Desktop SUSE -------------- next part -------------- A non-text attachment was scrubbed... Name: ChangeLog-Beta8-Beta9-SLES.txt.gz Type: application/gzip Size: 50239 bytes Desc: not available URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140620/c816edab/attachment.bin> From fcrozat at suse.com Fri Jun 20 09:37:17 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 20 Jun 2014 17:37:17 +0200 Subject: [sles-beta] [ANNOUNCE] SLE Workstation Extension 12 Beta9 is available Message-ID: <1403278637.2047.68.camel@par-r81vxc7.par.novell.com> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta participants, we are happy to announce Beta 9 release of SUSE Linux Enterprise Workstation Extension 12 (this is the new name of the previously named SLED Extension) SLE Workstation Extension is providing additional packages for SLES, which were only available on SLED before. ISO images will be available for download in a few hours (CDN is syncing). Please go to http://www.novell.com/beta and select "View my beta page". Here you should see all Beta's you are part of. We offer 2 DVD ISOs: DVD1 contains the binaries, the second DVD the sources and debuginfo packages. The final product will not contain the debuginfo packages on the media. To use this extension (together with SLES 12 Beta9), you can either: - select the extension during installation, after registration through SCC or - choose "use add-ons from media" during installation to select the Add-on ISO image. Highlights: - Many bug fixes in the entire distribution Known problems: bnc#861543 - ICAClient not installable Happy testing! Your SUSE Linux Enterprise Team -- Frederic Crozat Project Manager Enterprise Desktop SUSE From allen at ua.edu Fri Jun 20 09:47:16 2014 From: allen at ua.edu (Beddingfield, Allen) Date: Fri, 20 Jun 2014 15:47:16 +0000 Subject: [sles-beta] Installation under Citrix XenServer 6.2.x In-Reply-To: <AAD7066EC17A5541BF5145CD44BEFA72010045BDED@EX10MBN02.ua-net.ua.edu> References: <AAD7066EC17A5541BF5145CD44BEFA72010045BDED@EX10MBN02.ua-net.ua.edu> Message-ID: <AAD7066EC17A5541BF5145CD44BEFA72010045C140@EX10MBN02.ua-net.ua.edu> So, just an update on this. Following James's suggestion of using the "Other" template, I was able to get Beta 8 to install as a guest on XenServer 6.2. HOWEVER, it did not detect that it was running under Xen, so it did not load the Xen kernel, and it does not drop out to the TUI installer, as it normally would when installing under Xen. So, to sum it up. Beta 8 hangs on boot if I select the SLES 11 template in XenServer, but it will install if I select the "Other" template. When selecting this one, it does not detect the hypervisor correctly, and uses the "hda, hdb" naming convention for block devices, does not load the Xen kernel, and DOES work with the graphical installation. The above is just a general "reporting my findings" paragraph, but now that I have gone through this exercise, it makes me wonder why the installer defaults to not loading the GUI installer under XenServer, even though the XenCenter client is capable of displaying the graphical content... Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama ________________________________________ From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Beddingfield, Allen [allen at ua.edu] Sent: Friday, June 20, 2014 8:20 AM To: 'sles-beta at lists.suse.com' Subject: [sles-beta] Installation under Citrix XenServer 6.2.x This may have been addressed before, but I can't recall seeing any messages about it... Has anyone had any success getting Beta 8 to install under Citrix XenServer 6.2? It goes through the motions of installing, and then it powers the VM down at this point in startup: Xen virtual console successfully installed as ttys0 i8042: PNP: No PS/2 controller found. Probing ports directly Those are the last two lines displayed before it powers down. Thanks. Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From gjn at gjn.priv.at Fri Jun 20 15:20:35 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Fri, 20 Jun 2014 23:20:35 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 12 Beta9 is available In-Reply-To: <1403278621.2047.66.camel@par-r81vxc7.par.novell.com> References: <1403278621.2047.66.camel@par-r81vxc7.par.novell.com> Message-ID: <2286456.CVRbCipqlm@gjn.priv.at> Hello, Am Freitag, 20. Juni 2014, 17:37:01 schrieb Frederic Crozat: > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > > Dear Beta participants, > > we are happy to announce the ninth Beta of > > SUSE Linux Enterprise Server 12. > > ISO images should be available soon for download (replication is ongoing on > our CDN provider). Please go to > http://www.novell.com/beta and select "View my beta page". > Here you should see all Beta's you are part of. > > Note that the directory contains the images for the SDK as well as for the > SLE-WE Extension. > > We offer 3 DVD ISOs: DVD1 contains the binaries, the second > DVD the sources and the third DVD the debuginfo packages. > The final product will not contain the debuginfo packages on the media. > > For installation purposes you just need Media 1 for your architecture. I have always a 404 for the download, all other is working -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From S.M.Flood at ucs.cam.ac.uk Fri Jun 20 16:31:00 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Fri, 20 Jun 2014 23:31:00 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 12 Beta9 is available In-Reply-To: <2286456.CVRbCipqlm@gjn.priv.at> References: <1403278621.2047.66.camel@par-r81vxc7.par.novell.com> <2286456.CVRbCipqlm@gjn.priv.at> Message-ID: <e8d353f8-033f-4e27-b274-c82318edc278@email.android.com> On 20 June 2014 22:20:35 BST, "G?nther J. Niederwimmer" wrote: >I have always a 404 for the download, all other is working Apart from the SDK ISO I'm getting a 404 for all other x86_64 DVD1 ISOs. Simon Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner From tparker at cbnco.com Fri Jun 20 21:42:03 2014 From: tparker at cbnco.com (Tom Parker) Date: Fri, 20 Jun 2014 23:42:03 -0400 Subject: [sles-beta] iSCSI Booting has been removed from the release notes Message-ID: <53A4FF0B.2030200@cbnco.com> Hello I see in the changelog and in the release notes that there is no longer a mention of iscsi booting. Has this feature been removed? Tom From tparker at cbnco.com Fri Jun 20 21:44:38 2014 From: tparker at cbnco.com (Tom Parker) Date: Fri, 20 Jun 2014 23:44:38 -0400 Subject: [sles-beta] cciss driver for HP hardware Message-ID: <53A4FFA6.9060407@cbnco.com> Hello I see that the cciss driver for older HP hardware is no longer supported. Does this mean it has been removed from the kernel and is no longer available or just that SLES will not support systems using this driver? We still have many HP BL460 G5 servers running in QA and Development that have many more years of useful life in them and all of them use the Hewlett-Packard Company Smart Array E200i Controller which is listed as not supported Thanks Tom From gjn at gjn.priv.at Sat Jun 21 03:53:23 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 21 Jun 2014 11:53:23 +0200 Subject: [sles-beta] Failed to start Create Volatile Files and Directories Beta 9 Message-ID: <8614377.re42WXzq2O@gjn.priv.at> Hello, Is this only on my system? I have a Message See 'systemctl status systemd-tmpfiles-setup.service' for detail This is a missing user / group problem. Unknown user 'ddclient' Thanks, -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From mge at suse.com Sat Jun 21 04:22:00 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Sat, 21 Jun 2014 12:22:00 +0200 Subject: [sles-beta] cciss driver for HP hardware In-Reply-To: <53A4FFA6.9060407@cbnco.com> References: <53A4FFA6.9060407@cbnco.com> Message-ID: <20140621102200.GA18878@suse.com> Hello Tom and all, On 2014-06-20 T 23:44 -0400 Tom Parker wrote: > I see that the cciss driver for older HP hardware is > no longer supported. Does this mean it has been > removed from the kernel and is no longer available or > just that SLES will not support systems using this > driver? please see the Release Notes, chapter 4.2.2: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage Compared to other recent distributions, SLES 12 has special code in the hpsa driver to support more of the older controllers, i.e. more than the upstream driver. > We still have many HP BL460 G5 servers running in QA > and Development that have many more years of useful > life in them and all of them use the Hewlett-Packard > Company Smart Array E200i Controller which is listed > as not supported However, unfortunately, the E200i is not among those, where we can implement this. I am afraid, this is out of SUSE's control and should be brought up with the hardware vendor, who also maintains the upstream driver(s). so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From tparker at cbnco.com Sat Jun 21 07:59:52 2014 From: tparker at cbnco.com (Tom Parker) Date: Sat, 21 Jun 2014 09:59:52 -0400 Subject: [sles-beta] cciss driver for HP hardware In-Reply-To: <20140621102200.GA18878@suse.com> References: <53A4FFA6.9060407@cbnco.com> <20140621102200.GA18878@suse.com> Message-ID: <53A58FD8.3070802@cbnco.com> Has the old cciss driver been removed from the kernel? On my SP3 systems I see from lspci that both the hspa and cciss drivers are available for this PCIID 0b:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i (SAS Controller) Subsystem: Hewlett-Packard Company Smart Array E200i Kernel driver in use: cciss Kernel modules: hpsa, cciss I will have to test beta 9 on an old server on Monday Thanks Tom On 21/06/14 06:22 AM, Matthias G. Eckermann wrote: > Hello Tom and all, > > On 2014-06-20 T 23:44 -0400 Tom Parker wrote: > >> I see that the cciss driver for older HP hardware is >> no longer supported. Does this mean it has been >> removed from the kernel and is no longer available or >> just that SLES will not support systems using this >> driver? > please see the Release Notes, chapter 4.2.2: > https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage > > Compared to other recent distributions, SLES 12 has > special code in the hpsa driver to support more of the > older controllers, i.e. more than the upstream driver. > >> We still have many HP BL460 G5 servers running in QA >> and Development that have many more years of useful >> life in them and all of them use the Hewlett-Packard >> Company Smart Array E200i Controller which is listed >> as not supported > However, unfortunately, the E200i is not among those, > where we can implement this. > > I am afraid, this is out of SUSE's control and should be > brought up with the hardware vendor, who also maintains > the upstream driver(s). > > so long - > MgE > From kukuk at suse.de Sat Jun 21 08:11:08 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Sat, 21 Jun 2014 16:11:08 +0200 Subject: [sles-beta] Failed to start Create Volatile Files and Directories Beta 9 In-Reply-To: <8614377.re42WXzq2O@gjn.priv.at> References: <8614377.re42WXzq2O@gjn.priv.at> Message-ID: <20140621141108.GA15199@suse.de> On Sat, Jun 21, G?nther J. Niederwimmer wrote: > Hello, > > Is this only on my system? > > I have a Message > > See 'systemctl status systemd-tmpfiles-setup.service' for detail > > This is a missing user / group problem. > > Unknown user 'ddclient' Very old problem already fixed. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From gjn at gjn.priv.at Sat Jun 21 08:20:34 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 21 Jun 2014 16:20:34 +0200 Subject: [sles-beta] Failed to start Create Volatile Files and Directories Beta 9 In-Reply-To: <8614377.re42WXzq2O@gjn.priv.at> References: <8614377.re42WXzq2O@gjn.priv.at> Message-ID: <100244934.eUFe0hr0UP@gjn.priv.at> Hello, Am Samstag, 21. Juni 2014, 11:53:23 schrieb G?nther J. Niederwimmer: > Hello, > > Is this only on my system? > > I have a Message > > See 'systemctl status systemd-tmpfiles-setup.service' for detail > > This is a missing user / group problem. > > Unknown user 'ddclient' > > Thanks, ;) OK, with a new installation it is fixed (no zypper dup) ;)) -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From darrent at akurit.com.au Sun Jun 22 17:29:32 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 23 Jun 2014 09:29:32 +1000 Subject: [sles-beta] Suggestion to speed up installs/Upgrades/patching for "future" SLE Message-ID: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com> Team Whilst watching an upgrade/install of SLE-12 I made the following observation: 1. dracut takes a long time to build it's images and install. 2. dracut is called LOTS of times during the installation process (every time a process touches a startup device etc, e.g. Kernel, multipath, portland etc. 3. Logically only the 'last" time it's run is it doing anything useful. My suggestion: Analyse the installation process for modules that touch a startup device. Set a "dracut needed" flag instead of actually running dracut Get yast/zypper to check for the "dracut needed" flag and run it as the last action during an install if set. I know that probably requires touching some low level install processes but I think the speed-up produced would make that worth investigation. Regards -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au <steve at akurit.com.au> Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/1f36b701/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/1f36b701/attachment.jpg> From mge at suse.com Sun Jun 22 18:36:36 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Mon, 23 Jun 2014 02:36:36 +0200 Subject: [sles-beta] Suggestion to speed up installs/Upgrades/patching for "future" SLE In-Reply-To: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com> References: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com> Message-ID: <20140623003636.GD9332@suse.com> Hello Darren, don't you think that we already did consider this? The problem with this approach is that it leaves the system in an undefinied / inconsistent state for a few minutes, and if it crashes then, you have a really bad experience. Thus we have decided to follow the save way which indeed needs a bit more time, but we hope that people appreciate consistency and stability over 2-3 minutes of time. so long - MgE On 2014-06-23 T 09:29 +1000 Darren Thompson wrote: > Team > > Whilst watching an upgrade/install of SLE-12 I made the following > observation: > 1. dracut takes a long time to build it's images and install. > 2. dracut is called LOTS of times during the installation process (every > time a process touches a startup device etc, e.g. Kernel, multipath, > portland etc. > 3. Logically only the 'last" time it's run is it doing anything useful. > > My suggestion: > Analyse the installation process for modules that touch a startup device. > Set a "dracut needed" flag instead of actually running dracut > Get yast/zypper to check for the "dracut needed" flag and run it as the > last action during an install if set. > > I know that probably requires touching some low level install processes but > I think the speed-up produced would make that worth investigation. > > Regards > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au <steve at akurit.com.au> > Web: www.akurit.com.au > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From darrent at akurit.com.au Sun Jun 22 20:46:04 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 23 Jun 2014 12:46:04 +1000 Subject: [sles-beta] SLES12B9 - hostname being reset to "linux" on zypper dup Message-ID: <CAEUhfEd-nvrgrd1P-hpHuoZpnu9s=18KqfcC3xHUkqBNwn9FdQ@mail.gmail.com> Team I know inplace updates are not supported... However for those of us that do do it, be aware that the hostname is being reset to "linux" instead of being retained, if you do a "zypper dup" All other network setting seem to be reatined and are correct, it's just the hostname that is being messed up.p Caused a little fun and games with my SLES12 cluster before I realised that everything was named "linux" ;-) Regards Darren -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au <steve at akurit.com.au> Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/1f125709/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/1f125709/attachment.jpg> From darrent at akurit.com.au Sun Jun 22 22:44:18 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 23 Jun 2014 14:44:18 +1000 Subject: [sles-beta] Suggestion to speed up installs/Upgrades/patching for "future" SLE In-Reply-To: <20140623003636.GD9332@suse.com> References: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com> <20140623003636.GD9332@suse.com> Message-ID: <CAEUhfEfHrYphUSRFc5DyX2LD6JTsb2KN0xzO1VU9+f7KVNpGHg@mail.gmail.com> Matthias All good points and certainly for upgrades I agree with you, it's one of the best features of SLES that the updates can (mostly) be recovered if there are errors. I would still say that the "New Install" workflow would benefit enormously (much mpre than the "2-3 minutes of time" you suggest) from removing this repeated, time consuming step. I have not put a "stop watch" to it but I would say that between 20% and 30% of the installation time is taken with repeated dracut builds - at-least in my test ring case. I concede that "super fast" hardware would not be so impacted. In any case, as a beta tester I understood my role was to "make observations" and I still feel that this was a reasonable suggestion. Darren On 23 June 2014 10:36, Matthias G. Eckermann <mge at suse.com> wrote: > Hello Darren, > > don't you think that we already did consider this? > > The problem with this approach is that it leaves the > system in an undefinied / inconsistent state for a few > minutes, and if it crashes then, you have a really bad > experience. > > Thus we have decided to follow the save way which indeed > needs a bit more time, but we hope that people appreciate > consistency and stability over 2-3 minutes of time. > > so long - > MgE > > On 2014-06-23 T 09:29 +1000 Darren Thompson wrote: > > Team > > > > Whilst watching an upgrade/install of SLE-12 I made the following > > observation: > > 1. dracut takes a long time to build it's images and install. > > 2. dracut is called LOTS of times during the installation process (every > > time a process touches a startup device etc, e.g. Kernel, multipath, > > portland etc. > > 3. Logically only the 'last" time it's run is it doing anything useful. > > > > My suggestion: > > Analyse the installation process for modules that touch a startup device. > > Set a "dracut needed" flag instead of actually running dracut > > Get yast/zypper to check for the "dracut needed" flag and run it as the > > last action during an install if set. > > > > I know that probably requires touching some low level install processes > but > > I think the speed-up produced would make that worth investigation. > > > > Regards > > > > -- > > > > Darren Thompson > > > > Professional Services Engineer / Consultant > > > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > > > Level 3, 60 City Road > > > > Southgate, VIC 3006 > > > > Mb: 0400 640 414 > > > > Mail: darrent at akurit.com.au <steve at akurit.com.au> > > Web: www.akurit.com.au > > > > > _______________________________________________ > > sles-beta mailing list > > sles-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sles-beta > > > -- > Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise > Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com > SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au <steve at akurit.com.au> Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/1983cc81/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/1983cc81/attachment.jpg>