From Dick.Waite at softwareag.com Mon Nov 23 23:49:33 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Tue, 24 Nov 2015 06:49:33 +0000 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> Grand New Day, I have been keeping an eye on what "Backports". Not a lot in the SLES12 area but the good LEAP-42-1 has a lot of good stuff. Now we are coming down to the short strokes with SLES12-SP1 I'd very much like to do my own "product" testing with the DM I have used for years. How long will it take before we see KDE on the "backports" and be able to download and use. Be a bit dim to use SLE-Classic to do SAG Product testing and then a few days later KDE is there and we have to do the lot again. If your looking for Beta testers for this my hand is up. __R -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of KRONSEDER, Thomas, Dr. Sent: Montag, 16. November 2015 09:20 To: 'Frederic Crozat' Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] SLE-Classic et. al. Hi Frederik, thank you for this update. So there is going to be some "optional" package update announcement on the package notification mailing list, isn't it? Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: Frederic Crozat [mailto:fcrozat at suse.com] Gesendet: Montag, 16. November 2015 08:52 An: KRONSEDER, Thomas, Dr. Cc: sles-beta at lists.suse.com Betreff: Re: AW: [sles-beta] SLE-Classic et. al. Le lundi 16 novembre 2015 ? 07:39 +0000, KRONSEDER, Thomas, Dr. a ?crit : > Hello, > > regarding: > > > > We do have quite a number of modules now that you can add into the > > > mix, would it be very hard to have a KDE module so that one could > > > have a DM of ones own choice ? > > > I think some announcements at SUSECon this week might help with that > > (hint, hint ;) > > Do you have a pointer to the respective announcement(s) ? I don't have any pointer but this was about SUSE Package Hub (so far, there is very few documentation available at https://en.opensuse.org/Portal:Backports ;) KDE 5 will be available there soon, but unsupported. I'm expecting broader announcement on Package hub soon but I don't have any ETA. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. _______________________________________________ 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), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From thomas.kronseder at mtu.de Tue Nov 24 00:20:53 2015 From: thomas.kronseder at mtu.de (KRONSEDER, Thomas, Dr.) Date: Tue, 24 Nov 2015 07:20:53 +0000 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> Message-ID: <01559031EB071C47AA06542D982B9CD59AC64104@memc023.de.mtu.corp> Hi Dick, I'm also going to build an SLES12SP1/WE + kde image as soon as all components are available. Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: Waite, Dick (External) [mailto:Dick.Waite at softwareag.com] Gesendet: Dienstag, 24. November 2015 07:50 An: KRONSEDER, Thomas, Dr.; 'Frederic Crozat' Cc: sles-beta at lists.suse.com Betreff: RE: [sles-beta] SLE-Classic et. al. Grand New Day, I have been keeping an eye on what "Backports". Not a lot in the SLES12 area but the good LEAP-42-1 has a lot of good stuff. Now we are coming down to the short strokes with SLES12-SP1 I'd very much like to do my own "product" testing with the DM I have used for years. How long will it take before we see KDE on the "backports" and be able to download and use. Be a bit dim to use SLE-Classic to do SAG Product testing and then a few days later KDE is there and we have to do the lot again. If your looking for Beta testers for this my hand is up. __R -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of KRONSEDER, Thomas, Dr. Sent: Montag, 16. November 2015 09:20 To: 'Frederic Crozat' Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] SLE-Classic et. al. Hi Frederik, thank you for this update. So there is going to be some "optional" package update announcement on the package notification mailing list, isn't it? Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: Frederic Crozat [mailto:fcrozat at suse.com] Gesendet: Montag, 16. November 2015 08:52 An: KRONSEDER, Thomas, Dr. Cc: sles-beta at lists.suse.com Betreff: Re: AW: [sles-beta] SLE-Classic et. al. Le lundi 16 novembre 2015 ? 07:39 +0000, KRONSEDER, Thomas, Dr. a ?crit : > Hello, > > regarding: > > > > We do have quite a number of modules now that you can add into the > > > mix, would it be very hard to have a KDE module so that one could > > > have a DM of ones own choice ? > > > I think some announcements at SUSECon this week might help with that > > (hint, hint ;) > > Do you have a pointer to the respective announcement(s) ? I don't have any pointer but this was about SUSE Package Hub (so far, there is very few documentation available at https://en.opensuse.org/Portal:Backports ;) KDE 5 will be available there soon, but unsupported. I'm expecting broader announcement on Package hub soon but I don't have any ETA. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. _______________________________________________ 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), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From markus.hubler at isc-ejpd.admin.ch Tue Nov 24 02:54:16 2015 From: markus.hubler at isc-ejpd.admin.ch (markus.hubler at isc-ejpd.admin.ch) Date: Tue, 24 Nov 2015 09:54:16 +0000 Subject: [sles-beta] sha256sum apparmor-docs Message-ID: <59462F911036934D8BF6834B607DD7CEA4FE30AE@sb00106a.adb.intra.admin.ch> Hi folks It seems as if a package has a different sha256sum with Sles12 and Sles 12 SP1. It is the same version has been packaged at the same date. However the signature date is different. Beside from this everything in these two packages is identical. Signature : RSA/SHA256, Fri 04 Sep 2015 03:04:45 PM CEST, Key ID 70af9e8139db7c82 Signature : RSA/SHA256, Fri 04 Sep 2015 03:05:40 PM CEST, Key ID 70af9e8139db7c82 At the end I have two different checksums. This leads to an installation problem when doing a new installation with cobbler (from Suse Manager). The machine does not refer to the rpm from sp1 but to the rpm from the update section from sp0. The expected checksum of file .... is ... but the current checksum is ... This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system. Use it anyway? This message is shown for more than 10 packages... # sha256sum /var/spacewalk/instsrv/sles12_1/suse/noarch/apparmor-docs-2.8.2-36.1.noarch.rpm a727bebac6b8dd8fc18fd2df00782042b9612c5e31acbb3240d4b41373c44059 /var/spacewalk/instsrv/sles12_1/suse/noarch/apparmor-docs-2.8.2-36.1.noarch.rpm # sha256sum /var/spacewalk/packages/NULL/df3/apparmor-docs/2.8.2-36.1/noarch/df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a/apparmor-docs-2.8.2-36.1.noarch.rpm df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a /var/spacewalk/packages/NULL/df3/apparmor-docs/2.8.2-36.1/noarch/df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a/apparmor-docs-2.8.2-36.1.noarch.rpm Now my question: Is there a good way to work around this problem. Or are there any needs to fix this? Regards Markus From fcrozat at suse.com Tue Nov 24 03:00:36 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 24 Nov 2015 11:00:36 +0100 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> Message-ID: <1448359236.6197.3.camel@suse.com> Le mardi 24 novembre 2015 ? 06:49 +0000, Waite, Dick (External) a ?crit : > Grand New Day, > > I have been keeping an eye on what "Backports". Not a lot in the > SLES12 area but the good LEAP-42-1 has a lot of good stuff. Now we > are coming down to the short strokes with SLES12-SP1 I'd very much > like to do my own "product" testing with the DM I have used for > years. How long will it take before we see KDE on the "backports" and > be able to download and use. Sorry, I don't have information about that. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From sbahling at suse.com Tue Nov 24 03:22:08 2015 From: sbahling at suse.com (Scott Bahling) Date: Tue, 24 Nov 2015 11:22:08 +0100 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> Message-ID: <1448360528.24052.16.camel@suse.com> On Tue, 2015-11-24 at 06:49 +0000, Waite, Dick (External) wrote: > Grand New Day, > > I have been keeping an eye on what "Backports". Not a lot in the > SLES12 area but the good LEAP-42-1 has a lot of good stuff. Now we are > coming down to the short strokes with SLES12-SP1 I'd very much like to > do my own "product" testing with the DM I have used for years. How > long will it take before we see KDE on the "backports" and be able to > download and use. Not before SP1 is released. It has come to our attention that KDE requires updating some core libraries in SLE12 and the risk of doing that still needs to be assessed. Updating those libraries on the SP1 media at this point in time is not an option. We are looking into other options at the moment, but our priority is on getting SP1 released. -Scott -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: This is a digitally signed message part URL: From eblock at nde.ag Tue Nov 24 04:58:54 2015 From: eblock at nde.ag (Eugen Block) Date: Tue, 24 Nov 2015 12:58:54 +0100 Subject: [sles-beta] network settings for SLES12 installation In-Reply-To: <1448360528.24052.16.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <1448360528.24052.16.camel@suse.com> Message-ID: <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> Hi all, I have a question regarding the installation process of SLES12 since SP0. I use virt-manager on a Xen host running on SLES11-SP3, but my question also refers to installing xen-guests directly via config files. If I wanted to avoid network setup via dhcp on SLES11 VMs I used the "Additional Arguments" in virt-manager, in the xen-config file it is the "extra" line, where I used to provide information like "Netsetup=-dhcp,all Hostname= Domain= Hostip= Nameserver= Gateway=". If I use the same syntax with SLES12-SP0/SP1-RC2/SP1-RC3/SP1-GMC, I always get into the linuxrc confirmation screen where all my entries are preselected (see the attached screenshot), I just have to confirm them. So somehow linuxrc knows what it is, but why do I have to confirm it? My colleage helped me and found a syntax where linuxrc doesn't ask for this confirmation, but then the settings I have provided aren't stored anywhere. So it is just a temporary network configuration to enable PXE boot or to provide an autoyast file, is that correct? For auto-installations this can be a little annoying, so I wanted to ask you guys what's up with that. I'd appreciate any information. Thanks, Eugen -- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock at nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 -------------- next part -------------- A non-text attachment was scrubbed... Name: sles12 virt-manager.png Type: image/png Size: 24847 bytes Desc: not available URL: From eblock at nde.ag Tue Nov 24 05:57:30 2015 From: eblock at nde.ag (Eugen Block) Date: Tue, 24 Nov 2015 13:57:30 +0100 Subject: [sles-beta] network settings for SLES12 installation In-Reply-To: <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <1448360528.24052.16.camel@suse.com> <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> Message-ID: <20151124135730.Horde.zWaZhGxbkX1RHW7pcIOQbeq@www3.nde.ag> Sorry, for the sake of completeness I should have added which syntax is accepted without asking for confirmation. To provide the same information I used this string: ifcfg='eth0=/24,,,' Hostname= Regards, Eugen Zitat von Eugen Block : > Hi all, > > I have a question regarding the installation process of SLES12 since > SP0. I use virt-manager on a Xen host running on SLES11-SP3, but my > question also refers to installing xen-guests directly via config > files. > If I wanted to avoid network setup via dhcp on SLES11 VMs I used the > "Additional Arguments" in virt-manager, in the xen-config file it is > the "extra" line, where I used to provide information like > "Netsetup=-dhcp,all Hostname= Domain= Hostip= > Nameserver= Gateway=". > If I use the same syntax with SLES12-SP0/SP1-RC2/SP1-RC3/SP1-GMC, I > always get into the linuxrc confirmation screen where all my entries > are preselected (see the attached screenshot), I just have to > confirm them. So somehow linuxrc knows what it is, but why do I have > to confirm it? > My colleage helped me and found a syntax where linuxrc doesn't ask > for this confirmation, but then the settings I have provided aren't > stored anywhere. So it is just a temporary network configuration to > enable PXE boot or to provide an autoyast file, is that correct? For > auto-installations this can be a little annoying, so I wanted to ask > you guys what's up with that. I'd appreciate any information. > > Thanks, > Eugen > > -- > Eugen Block voice : +49-40-559 51 75 > NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 > Postfach 61 03 15 > D-22423 Hamburg e-mail : eblock at nde.ag > > Vorsitzende des Aufsichtsrates: Angelika Mozdzen > Sitz und Registergericht: Hamburg, HRB 90934 > Vorstand: Jens-U. Mozdzen > USt-IdNr. DE 814 013 983 -- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock at nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 From snwint at suse.de Tue Nov 24 07:21:59 2015 From: snwint at suse.de (Steffen Winterfeldt) Date: Tue, 24 Nov 2015 15:21:59 +0100 (CET) Subject: [sles-beta] network settings for SLES12 installation In-Reply-To: <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <1448360528.24052.16.camel@suse.com> <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> Message-ID: Hi Eugen, On Tuesday 2015-11-24 12:58, Eugen Block wrote: > I have a question regarding the installation process of SLES12 since SP0. I > use virt-manager on a Xen host running on SLES11-SP3, but my question also > refers to installing xen-guests directly via config files. > If I wanted to avoid network setup via dhcp on SLES11 VMs I used the > "Additional Arguments" in virt-manager, in the xen-config file it is the > "extra" line, where I used to provide information like "Netsetup=-dhcp,all > Hostname= Domain= Hostip= Nameserver= > Gateway=". > If I use the same syntax with SLES12-SP0/SP1-RC2/SP1-RC3/SP1-GMC, I always get > into the linuxrc confirmation screen where all my entries are preselected (see > the attached screenshot), I just have to confirm them. So somehow linuxrc > knows what it is, but why do I have to confirm it? The original plan is/was for netsetup to provide network setup dialogs. Like netsetup=hostip,gateway should show two popups asking for hostip and gateway. Likewise netsetup=-dhcp would just skip the question about dhcp usage. What it actually does in sle11 is to show popups only if it thinks some data is still needed. So netsetup=-dhcp hostip=10.10.0.1/16 will not ask for gateway or nameserver (as it should) as linuxrc is fine setting up a network based on just the ip and netmask. The 'all' was just a hack making netsetup=dhcp,all run dhcp on all interfaces. All in all the network config syntax was not in a good shape up to sle11. So there is now in sle12 the 'ifcfg' option which lets you specify exactly what you want to go into the ifcfg files without getting the linuxrc guesswork in the way. That said, I agree that 'netsetup' in sle12 is not perfect either. So if you go ahead and make a bugreport, I will look into this for sp2. > My colleage helped me and found a syntax where linuxrc doesn't ask for this > confirmation, but then the settings I have provided aren't stored anywhere. So The network config is always copied to the target system. Steffen From Dick.Waite at softwareag.com Wed Nov 25 02:31:03 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Wed, 25 Nov 2015 09:31:03 +0000 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <01559031EB071C47AA06542D982B9CD59AC64104@memc023.de.mtu.corp> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <01559031EB071C47AA06542D982B9CD59AC64104@memc023.de.mtu.corp> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0C60718@hqmbx6.eur.ad.sag> Grad New Day, Had to burn a couple of DVD's this morning, where is K2b ? ? ? gone with the wind or SLES12. It's been by my side for so many years. I do see the good LEAP-42-1 still has it running so I could burn, but that would be another grand application for the "Backports". Gee life without K3b .... I do find it a bit odd installing the GMC2... In days and nights gone by I would have: Added the new Server GMC2 iso into the known items using the Yast2 Software Repositories, put the old GMC server at 100 and disabled it. Used the refresh tab "refresh all enabled" Using Software manager selected "packages", hi-lite "all packages", selected "Update if newer version available". Q.E.D The system would be at GMC2.... But now... it get a very very bad hair day with all the stuff https://updates......... 'cos it seems they have gone with the wind. One has to do a full IPL "updated" so that all these https:// stuff can be removed.... So a full IPL Update just for a few updates to yast... seem heavy. I would like to be flooded with ways of doing GMC2 with having to IPL the system, and using Yast of course J __R -----Original Message----- From: KRONSEDER, Thomas, Dr. [mailto:thomas.kronseder at mtu.de] Sent: Dienstag, 24. November 2015 08:21 To: Waite, Dick (External); 'Frederic Crozat' Cc: sles-beta at lists.suse.com Subject: AW: [sles-beta] SLE-Classic et. al. Hi Dick, I'm also going to build an SLES12SP1/WE + kde image as soon as all components are available. Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: Waite, Dick (External) [mailto:Dick.Waite at softwareag.com] Gesendet: Dienstag, 24. November 2015 07:50 An: KRONSEDER, Thomas, Dr.; 'Frederic Crozat' Cc: sles-beta at lists.suse.com Betreff: RE: [sles-beta] SLE-Classic et. al. Grand New Day, I have been keeping an eye on what "Backports". Not a lot in the SLES12 area but the good LEAP-42-1 has a lot of good stuff. Now we are coming down to the short strokes with SLES12-SP1 I'd very much like to do my own "product" testing with the DM I have used for years. How long will it take before we see KDE on the "backports" and be able to download and use. Be a bit dim to use SLE-Classic to do SAG Product testing and then a few days later KDE is there and we have to do the lot again. If your looking for Beta testers for this my hand is up. __R -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of KRONSEDER, Thomas, Dr. Sent: Montag, 16. November 2015 09:20 To: 'Frederic Crozat' Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] SLE-Classic et. al. Hi Frederik, thank you for this update. So there is going to be some "optional" package update announcement on the package notification mailing list, isn't it? Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: Frederic Crozat [mailto:fcrozat at suse.com] Gesendet: Montag, 16. November 2015 08:52 An: KRONSEDER, Thomas, Dr. Cc: sles-beta at lists.suse.com Betreff: Re: AW: [sles-beta] SLE-Classic et. al. Le lundi 16 novembre 2015 ? 07:39 +0000, KRONSEDER, Thomas, Dr. a ?crit : > Hello, > > regarding: > > > > We do have quite a number of modules now that you can add into the > > > mix, would it be very hard to have a KDE module so that one could > > > have a DM of ones own choice ? > > > I think some announcements at SUSECon this week might help with that > > (hint, hint ;) > > Do you have a pointer to the respective announcement(s) ? I don't have any pointer but this was about SUSE Package Hub (so far, there is very few documentation available at https://en.opensuse.org/Portal:Backports ;) KDE 5 will be available there soon, but unsupported. I'm expecting broader announcement on Package hub soon but I don't have any ETA. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. _______________________________________________ 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), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From fcrozat at suse.com Wed Nov 25 02:36:49 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Wed, 25 Nov 2015 10:36:49 +0100 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0C60718@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <01559031EB071C47AA06542D982B9CD59AC64104@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C60718@hqmbx6.eur.ad.sag> Message-ID: <1448444209.6197.79.camel@suse.com> Le mercredi 25 novembre 2015 ? 09:31 +0000, Waite, Dick (External) a ?crit : > Grad New Day, > > Had to burn a couple of DVD's this morning, where is K2b ? ? ? gone > with the wind or SLES12. It's been by my side for so many years. I do > see the good LEAP-42-1 still has it running so I could burn, but that > would be another grand application for the "Backports". Gee life > without K3b .... For burning DVD, we are providing Brasero on SLES and SLED. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Dick.Waite at softwareag.com Wed Nov 25 02:51:38 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Wed, 25 Nov 2015 09:51:38 +0000 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <1448444209.6197.79.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <01559031EB071C47AA06542D982B9CD59AC64104@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C60718@hqmbx6.eur.ad.sag> <1448444209.6197.79.camel@suse.com> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0C6078F@hqmbx6.eur.ad.sag> Grand Day Frederic, And I'm sure it a very fine application, but it's not K3b and after all these years as the saying goes, " If it ain't broke, don't fix it ". I cut my teeth on SuSE linux in the 7's and 8's and for me if an application does what it says on the tin, then use it. I have my LEAP running KDE and work against the SLES12's happy as Larry... Just hoping for an early Christmas with KDE in the "backports", now that would be a very very good gift for your older users... Remember it's Adabas I'm running and testing against GMC2 and this old bird is over 40 now and still does what it says on the tin, plus of course a lot more than it did in the 70's.... Gee it even knows SOA and REST now, but as with z/OS JCL what worked in the 70's works in the 15's. Have a very good day Frederic. __R -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Frederic Crozat Sent: Mittwoch, 25. November 2015 10:37 To: sles-beta at lists.suse.com Subject: Re: [sles-beta] SLE-Classic et. al. Le mercredi 25 novembre 2015 ? 09:31 +0000, Waite, Dick (External) a ?crit : > Grad New Day, > > Had to burn a couple of DVD's this morning, where is K2b ? ? ? gone > with the wind or SLES12. It's been by my side for so many years. I do > see the good LEAP-42-1 still has it running so I could burn, but that > would be another grand application for the "Backports". Gee life > without K3b .... For burning DVD, we are providing Brasero on SLES and SLED. -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ 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), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From Joerg.Reisenweber at btc-it-services.com Wed Nov 25 04:17:25 2015 From: Joerg.Reisenweber at btc-it-services.com (Joerg.Reisenweber at btc-it-services.com) Date: Wed, 25 Nov 2015 12:17:25 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC 2 is available In-Reply-To: <20151124202328.GB15601@suse.de> References: <20151124202328.GB15601@suse.de> Message-ID: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0FBF2C87@OLCA9095.btcnet.btc-ag.com> Dear beta testers, are Suse Manager and/or local SMT ready to test with 12.1 GMC? Thanks J?rg -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Stefan Behlert Gesendet: Dienstag, 24. November 2015 21:23 An: sles-beta at lists.suse.com Betreff: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC 2 is available !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear all, Thanks for your feedback for the GMC images. Using this as well as the results of our internal testing, we decided to create a GMC 2 with some small changes compared to GMC. We limited them to the area of autoyast and yast2, as well as some metadata creation that got corrected. Please have a look at the attached changelog snippet to see details about what has changed. The ISO images are available from download.novell.com and the usual locations. 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. Please verify the sha256sum of the ISO using the SHA256SUMS file, which can be found in the same directory on the download servers. Thanks for all your testing, Your SUSE Linux Enterprise Team -- Stefan Behlert, SUSE LINUX Release Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From jsrain at suse.cz Wed Nov 25 04:32:51 2015 From: jsrain at suse.cz (Jiri Srain) Date: Wed, 25 Nov 2015 12:32:51 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC 2 is available In-Reply-To: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0FBF2C87@OLCA9095.btcnet.btc-ag.com> References: <20151124202328.GB15601@suse.de> <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0FBF2C87@OLCA9095.btcnet.btc-ag.com> Message-ID: <56559C63.4020302@suse.cz> Hello, for SMT: You can either use SMT included in SLES12-SP1 GMC snapshots (you don't need any additional media like in SLE11, just install the SMT pattern) or you can test your SLE12-SP1 hosts against SMT11-SP3. In the later case just make sure that SMT is configured against SCC (and not NCC); if you already register SLE12 hosts against SMT, it is configured properly and you just need to mirror the SP1 repositories. HTH, Jiri On 11/25/2015 12:17 PM, Joerg.Reisenweber at btc-it-services.com wrote: > Dear beta testers, > > are Suse Manager and/or local SMT ready to test with 12.1 GMC? > > Thanks > J?rg > > -----Urspr?ngliche Nachricht----- > Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Stefan Behlert > Gesendet: Dienstag, 24. November 2015 21:23 > An: sles-beta at lists.suse.com > Betreff: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC 2 is available > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > Dear all, > > Thanks for your feedback for the GMC images. Using this as well as the results of our internal testing, we decided to create a GMC 2 with some small changes compared to GMC. > > We limited them to the area of autoyast and yast2, as well as some metadata creation that got corrected. > > Please have a look at the attached changelog snippet to see details about what has changed. > > > The ISO images are available from download.novell.com and the usual locations. > > 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. > > Please verify the sha256sum of the ISO using the SHA256SUMS file, which can be found in the same directory on the download servers. > > > Thanks for all your testing, > > Your SUSE Linux Enterprise Team > > -- > Stefan Behlert, SUSE LINUX > Release Manager Enterprise Server > > Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -- 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 markus.hubler at isc-ejpd.admin.ch Wed Nov 25 05:39:54 2015 From: markus.hubler at isc-ejpd.admin.ch (markus.hubler at isc-ejpd.admin.ch) Date: Wed, 25 Nov 2015 12:39:54 +0000 Subject: [sles-beta] sha256sum apparmor-docs In-Reply-To: <59462F911036934D8BF6834B607DD7CEA4FE30AE@sb00106a.adb.intra.admin.ch> References: <59462F911036934D8BF6834B607DD7CEA4FE30AE@sb00106a.adb.intra.admin.ch> Message-ID: <59462F911036934D8BF6834B607DD7CEA4FE3248@sb00106a.adb.intra.admin.ch> Hi list The problem still occurs with GMC2. Regards Markus -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von markus.hubler at isc-ejpd.admin.ch Gesendet: Dienstag, 24. November 2015 10:54 An: sles-beta at lists.suse.com Betreff: [sles-beta] sha256sum apparmor-docs Hi folks It seems as if a package has a different sha256sum with Sles12 and Sles 12 SP1. It is the same version has been packaged at the same date. However the signature date is different. Beside from this everything in these two packages is identical. Signature : RSA/SHA256, Fri 04 Sep 2015 03:04:45 PM CEST, Key ID 70af9e8139db7c82 Signature : RSA/SHA256, Fri 04 Sep 2015 03:05:40 PM CEST, Key ID 70af9e8139db7c82 At the end I have two different checksums. This leads to an installation problem when doing a new installation with cobbler (from Suse Manager). The machine does not refer to the rpm from sp1 but to the rpm from the update section from sp0. The expected checksum of file .... is ... but the current checksum is ... This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system. Use it anyway? This message is shown for more than 10 packages... # sha256sum /var/spacewalk/instsrv/sles12_1/suse/noarch/apparmor-docs-2.8.2-36.1.noarch.rpm a727bebac6b8dd8fc18fd2df00782042b9612c5e31acbb3240d4b41373c44059 /var/spacewalk/instsrv/sles12_1/suse/noarch/apparmor-docs-2.8.2-36.1.noarch.rpm # sha256sum /var/spacewalk/packages/NULL/df3/apparmor-docs/2.8.2-36.1/noarch/df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a/apparmor-docs-2.8.2-36.1.noarch.rpm df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a /var/spacewalk/packages/NULL/df3/apparmor-docs/2.8.2-36.1/noarch/df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a/apparmor-docs-2.8.2-36.1.noarch.rpm Now my question: Is there a good way to work around this problem. Or are there any needs to fix this? Regards Markus _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From behlert at suse.com Wed Nov 25 06:59:46 2015 From: behlert at suse.com (Stefan Behlert) Date: Wed, 25 Nov 2015 14:59:46 +0100 Subject: [sles-beta] sha256sum apparmor-docs In-Reply-To: <59462F911036934D8BF6834B607DD7CEA4FE30AE@sb00106a.adb.intra.admin.ch> References: <59462F911036934D8BF6834B607DD7CEA4FE30AE@sb00106a.adb.intra.admin.ch> Message-ID: <20151125135946.GA8566@suse.de> Moin, On Nov 24, 15 09:54:16 +0000, markus.hubler at isc-ejpd.admin.ch wrote: > Hi folks > > It seems as if a package has a different sha256sum with Sles12 and Sles 12 SP1. It is the same version has been packaged at the same date. However the signature date is different. Beside from this everything in these two packages is identical. > > Signature : RSA/SHA256, Fri 04 Sep 2015 03:04:45 PM CEST, Key ID 70af9e8139db7c82 > Signature : RSA/SHA256, Fri 04 Sep 2015 03:05:40 PM CEST, Key ID 70af9e8139db7c82 It took me a while and several inquiries to understand this. First, both signatures are correct. The explanation is this: - For an update, the packages are build in a repository. - From this repository the packages are taken to be released as maintenance update for SLE 12 and to be included on the SLE 12 SP1 medium (if we have nothing newer for SP1). - Now, when the packages are taken for the update, the system resigns the packages it releases in the update channel, as the key (general speaking) could be different between the update channel and the build repository. - The ones in the build repository are _not_ resigned, but taken 'as is'. - For the SLE case, the key is identical for the build repository and the released packages. That's the reason why you see different signature times for some packages. We have changed this behavior at some point in time, to have the same signature (time), and not different ones. Unfortunately the package you mentioned was handled before that change, so you see different signature times there still. The other packages mentioned are most likely also affected by that. > At the end I have two different checksums. This leads to an installation > problem when doing a new installation with cobbler (from Suse Manager). > The machine does not refer to the rpm from sp1 but to the rpm from the > update section from sp0. > > The expected checksum of file .... is ... but the current checksum is ... > > This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system. > > Use it anyway? > > This message is shown for more than 10 packages... > > # sha256sum /var/spacewalk/instsrv/sles12_1/suse/noarch/apparmor-docs-2.8.2-36.1.noarch.rpm > a727bebac6b8dd8fc18fd2df00782042b9612c5e31acbb3240d4b41373c44059 /var/spacewalk/instsrv/sles12_1/suse/noarch/apparmor-docs-2.8.2-36.1.noarch.rpm > > # sha256sum /var/spacewalk/packages/NULL/df3/apparmor-docs/2.8.2-36.1/noarch/df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a/apparmor-docs-2.8.2-36.1.noarch.rpm > df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a /var/spacewalk/packages/NULL/df3/apparmor-docs/2.8.2-36.1/noarch/df366fb83e165d33866ae42a717658742069b5e3f5cba8629ddd52ddeabb434a/apparmor-docs-2.8.2-36.1.noarch.rpm > > > Now my question: Is there a good way to work around this problem. Or are there any needs to fix this? I'm not familiar enough with neither cobbler nor SUSE Manager to answer that, sorry. I've relayed this message to the responsible team, hoping they can help you. ciao, Stefan > > Regards > Markus > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Stefan Behlert, SUSE LINUX Release Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From eblock at nde.ag Wed Nov 25 08:31:11 2015 From: eblock at nde.ag (Eugen Block) Date: Wed, 25 Nov 2015 16:31:11 +0100 Subject: [sles-beta] network settings for SLES12 installation In-Reply-To: References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <1448360528.24052.16.camel@suse.com> <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> Message-ID: <20151125163111.Horde.-i_neQkRGy42IxQhd1jLZeq@www3.nde.ag> Hi Steffen, > I agree that 'netsetup' in sle12 is not perfect either. So if you > go ahead and make a bugreport, I will look into this for sp2. It was more a question of how it is designed to be used than a potential bug report. Thanks for clearing that up, it helps me a lot! > The network config is always copied to the target system. I ran another test with SLE12-GMC using the ifcfg syntax, you are absolutely right about the VMs configuration, I find all the values I provided. What I didn't find - and that must be the part which let me write that statement about not storing the network settings - is the complete network configuration in the autoinst.xml which is created automatically after the installation. I saw only the ip address and the netmask, the gateway, nameserver and domain were not included (I only used these parameters). I guess this refers to your statement "as linuxrc is fine setting up a network based on just the ip and netmask"? Then I ran another test with the GMC2, and in that autoinst.xml the gateway is included, but still no hostname or nameserver. Is there a reason for that? Regards, Eugen Zitat von Steffen Winterfeldt : > Hi Eugen, > > On Tuesday 2015-11-24 12:58, Eugen Block wrote: > >> I have a question regarding the installation process of SLES12 >> since SP0. I use virt-manager on a Xen host running on SLES11-SP3, >> but my question also refers to installing xen-guests directly via >> config files. >> If I wanted to avoid network setup via dhcp on SLES11 VMs I used >> the "Additional Arguments" in virt-manager, in the xen-config file >> it is the "extra" line, where I used to provide information like >> "Netsetup=-dhcp,all Hostname= Domain= Hostip= >> Nameserver= Gateway=". >> If I use the same syntax with SLES12-SP0/SP1-RC2/SP1-RC3/SP1-GMC, I >> always get into the linuxrc confirmation screen where all my >> entries are preselected (see the attached screenshot), I just have >> to confirm them. So somehow linuxrc knows what it is, but why do I >> have to confirm it? > > The original plan is/was for netsetup to provide network setup dialogs. Like > netsetup=hostip,gateway should show two popups asking for hostip and gateway. > Likewise netsetup=-dhcp would just skip the question about dhcp usage. > > What it actually does in sle11 is to show popups only if it thinks > some data is > still needed. So netsetup=-dhcp hostip=10.10.0.1/16 will not ask for > gateway or > nameserver (as it should) as linuxrc is fine setting up a network > based on just > the ip and netmask. > > The 'all' was just a hack making netsetup=dhcp,all run dhcp on all > interfaces. > > All in all the network config syntax was not in a good shape up to sle11. > > So there is now in sle12 the 'ifcfg' option which lets you specify exactly > what you want to go into the ifcfg files without getting the linuxrc > guesswork in the way. > > That said, I agree that 'netsetup' in sle12 is not perfect either. So if you > go ahead and make a bugreport, I will look into this for sp2. > >> My colleage helped me and found a syntax where linuxrc doesn't ask >> for this confirmation, but then the settings I have provided aren't >> stored anywhere. So > > The network config is always copied to the target system. > > > Steffen > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock at nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 From torsten.hallmann at suse.com Wed Nov 25 09:28:34 2015 From: torsten.hallmann at suse.com (Torsten Hallmann) Date: Wed, 25 Nov 2015 09:28:34 -0700 Subject: [sles-beta] Antw: Re: [ANNOUNCE] SLES 12 SP1 GMC 2 is available In-Reply-To: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0FBF2C87@OLCA9095.btcnet.btc-ag.com> References: <20151124202328.GB15601@suse.de> <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0FBF2C87@OLCA9095.btcnet.btc-ag.com> Message-ID: <5655EFC20200005A0012CECA@prv-mh.provo.novell.com> Hi J?rg, SUSE Manager is not enabled for SLES 12 SP1 channels so far. I just checked for available updates to sm-ncc-sync-data, but there is none so far. So /usr/share/susemanager/channels.xml does not reflect SP1 channels. Beside that there will be also updates for several other packages to make it work not only with SP1 channels but also clients (mgr-bootstrap etc.) :) I guess that this on the way, but I do not have a date available. I expect it closely around the final SP1 release date. Regards, Torsten -- Torsten Hallmann SUSE Teamlead Sales Engineering Office Center 1 Central Europe Flughafenstrasse 90 CH-8302 Kloten +41 43 456 23 81 torsten.hallmann at suse.com We adapt. You succeed. >>> schrieb am 11/25/2015 um 12:17 : > Dear beta testers, > > are Suse Manager and/or local SMT ready to test with 12.1 GMC? > > Thanks > J?rg > > -----Urspr?ngliche Nachricht----- > Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] > Im Auftrag von Stefan Behlert > Gesendet: Dienstag, 24. November 2015 21:23 > An: sles-beta at lists.suse.com > Betreff: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC 2 is available > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > Dear all, > > Thanks for your feedback for the GMC images. Using this as well as the > results of our internal testing, we decided to create a GMC 2 with some small > changes compared to GMC. > > We limited them to the area of autoyast and yast2, as well as some metadata > creation that got corrected. > > Please have a look at the attached changelog snippet to see details about > what has changed. > > > The ISO images are available from download.novell.com and the usual > locations. > > 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. > > Please verify the sha256sum of the ISO using the SHA256SUMS file, which can > be found in the same directory on the download servers. > > > Thanks for all your testing, > > Your SUSE Linux Enterprise Team > > -- > Stefan Behlert, SUSE LINUX > Release Manager Enterprise Server > > Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE Linux > GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG > N?rnberg) > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From vmoutoussamy at suse.com Thu Nov 26 02:57:40 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 26 Nov 2015 10:57:40 +0100 Subject: [sles-beta] reboot error on GMC/GMC2 References: Message-ID: Hi, Forwarding the email below, since I've received it as a bounce. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > > From: Hang Rao > > Date: 26 November 2015 at 02:51:11 GMT+1 > To: "sles-beta-bounces at lists.suse.com " > > Subject: [sles-beta] reboot error on GMC/GMC2 > > > Hi Sles team, > > In the GMC/GMC2 releases, we encountered the reboot error. > > Reproducing steps: > 1.install the SLES SP1 SP1 GMC in ESXi host (5.1, 5.5 or 6.0) > 2.Open a terminal > 3.Reboot the OS by command: > #reboot > or > #sudo reboot > 4. Call trace appears as the attached screen shot. > > On the previous RC releases there?s no such issue, does anyone encounter the same issue on GMC/GMC2? > > Best regards, > Hang Rao > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SLES_SP1_GMC_reboot.png Type: image/png Size: 293765 bytes Desc: not available URL: From vmoutoussamy at suse.com Thu Nov 26 04:07:03 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 26 Nov 2015 12:07:03 +0100 Subject: [sles-beta] reboot error on GMC/GMC2 In-Reply-To: References: Message-ID: <063334FD-82ED-4F50-876B-5070F84FE02C@suse.com> Hi, We can reproduce this issue internally, so as you imagine we will take an extra care to this issue! Of course we will keep you in touch. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 26 Nov 2015, at 10:57, Vincent Moutoussamy wrote: > > Hi, > > Forwarding the email below, since I've received it as a bounce. > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > > > >> >> From: Hang Rao > >> Date: 26 November 2015 at 02:51:11 GMT+1 >> To: "sles-beta-bounces at lists.suse.com " > >> Subject: [sles-beta] reboot error on GMC/GMC2 >> >> >> Hi Sles team, >> >> In the GMC/GMC2 releases, we encountered the reboot error. >> >> Reproducing steps: >> 1.install the SLES SP1 SP1 GMC in ESXi host (5.1, 5.5 or 6.0) >> 2.Open a terminal >> 3.Reboot the OS by command: >> #reboot >> or >> #sudo reboot >> 4. Call trace appears as the attached screen shot. >> >> On the previous RC releases there?s no such issue, does anyone encounter the same issue on GMC/GMC2? >> >> Best regards, >> Hang Rao >> >> > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joerg.Reisenweber at btc-it-services.com Thu Nov 26 04:21:59 2015 From: Joerg.Reisenweber at btc-it-services.com (Joerg.Reisenweber at btc-it-services.com) Date: Thu, 26 Nov 2015 12:21:59 +0100 Subject: [sles-beta] Antw: Re: [ANNOUNCE] SLES 12 SP1 GMC 2 is available In-Reply-To: <5655EFC20200005A0012CECA@prv-mh.provo.novell.com> References: <20151124202328.GB15601@suse.de> <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0FBF2C87@OLCA9095.btcnet.btc-ag.com> <5655EFC20200005A0012CECA@prv-mh.provo.novell.com> Message-ID: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0FBF2C89@OLCA9095.btcnet.btc-ag.com> Hi Torsten, thank you for the info. Let's hope that SuMa 12.1 support arrives quite soon as this is our main management platform. Regards J?rg -----Urspr?ngliche Nachricht----- Von: Torsten Hallmann [mailto:torsten.hallmann at suse.com] Gesendet: Mittwoch, 25. November 2015 17:29 An: Reisenweber, J?rg; sles-beta at lists.suse.com Betreff: Antw: Re: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC 2 is available Hi J?rg, SUSE Manager is not enabled for SLES 12 SP1 channels so far. I just checked for available updates to sm-ncc-sync-data, but there is none so far. So /usr/share/susemanager/channels.xml does not reflect SP1 channels. Beside that there will be also updates for several other packages to make it work not only with SP1 channels but also clients (mgr-bootstrap etc.) :) I guess that this on the way, but I do not have a date available. I expect it closely around the final SP1 release date. Regards, Torsten -- Torsten Hallmann SUSE Teamlead Sales Engineering Office Center 1 Central Europe Flughafenstrasse 90 CH-8302 Kloten +41 43 456 23 81 torsten.hallmann at suse.com We adapt. You succeed. >>> schrieb am 11/25/2015 um 12:17 : > Dear beta testers, > > are Suse Manager and/or local SMT ready to test with 12.1 GMC? > > Thanks > J?rg > > -----Urspr?ngliche Nachricht----- > Von: sles-beta-bounces at lists.suse.com > [mailto:sles-beta-bounces at lists.suse.com] > Im Auftrag von Stefan Behlert > Gesendet: Dienstag, 24. November 2015 21:23 > An: sles-beta at lists.suse.com > Betreff: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC 2 is available > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > Dear all, > > Thanks for your feedback for the GMC images. Using this as well as the > results of our internal testing, we decided to create a GMC 2 with > some small changes compared to GMC. > > We limited them to the area of autoyast and yast2, as well as some > metadata creation that got corrected. > > Please have a look at the attached changelog snippet to see details > about what has changed. > > > The ISO images are available from download.novell.com and the usual > locations. > > 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. > > Please verify the sha256sum of the ISO using the SHA256SUMS file, > which can be found in the same directory on the download servers. > > > Thanks for all your testing, > > Your SUSE Linux Enterprise Team > > -- > Stefan Behlert, SUSE LINUX > Release Manager Enterprise Server > > Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE > Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB > 21284 (AG > N?rnberg) > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From torsten.hallmann at suse.com Thu Nov 26 06:08:42 2015 From: torsten.hallmann at suse.com (Torsten Hallmann) Date: Thu, 26 Nov 2015 06:08:42 -0700 Subject: [sles-beta] Antw: Re: network settings for SLES12 installation In-Reply-To: <20151125163111.Horde.-i_neQkRGy42IxQhd1jLZeq@www3.nde.ag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <1448360528.24052.16.camel@suse.com> <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> <20151125163111.Horde.-i_neQkRGy42IxQhd1jLZeq@www3.nde.ag> Message-ID: <5657126A0200005A0012D090@prv-mh.provo.novell.com> Hi Eugen, is this an autoyast or manual install? If autoyast, did you use keep_install_network? Also what I did with regards to installing kvm hosts where it needs a bridge, but linuxrc does not know about, is to implement an ask dialog filled with pre-defaults from cmd output with auto accept timeout. See statements below for autoyast. By that I was able to kickoff an installation with netsetup=-dhcp,all and then transfer the net settings to br0 instead of eth0 :) initial 1 Network Settings Enter the network settings for this host. networking,dns,hostname Hostname string cat /proc/sys/kernel/hostname | awk -F'.' '{printf $1$2$3$4}' 30 initial 1 networking,interfaces,0,ipaddr IP Address br0 string ifconfig eth0 | grep Mask | cut -d ":" -f2 | awk '{printf $1}' 30 initial 1 networking,interfaces,0,netmask Netmask br0 string ifconfig eth0 | grep Mask | awk -F':' '{printf $4}' 30 initial 1 networking,dns,nameservers,0 Nameserver string grep nameserver /etc/resolv.conf | awk '{printf $2}' 30 initial 1 networking,dns,domain networking,dns,searchlist,0 Domain string grep search /etc/resolv.conf | awk '{printf $2}' 30 initial 1 networking,routing,route,0,gateway Default Gateway string route -n | grep ^0.0.0.0 | awk '{printf $2}' 30 Maybe you can tweak that a bit for your use case. >>> Eugen Block schrieb am 11/25/2015 um 4:31 : > Hi Steffen, > >> I agree that 'netsetup' in sle12 is not perfect either. So if you >> go ahead and make a bugreport, I will look into this for sp2. > > It was more a question of how it is designed to be used than a > potential bug report. Thanks for clearing that up, it helps me a lot! > >> The network config is always copied to the target system. > > I ran another test with SLE12-GMC using the ifcfg syntax, you are > absolutely right about the VMs configuration, I find all the values I > provided. What I didn't find - and that must be the part which let me > write that statement about not storing the network settings - is the > complete network configuration in the autoinst.xml which is created > automatically after the installation. I saw only the ip address and > the netmask, the gateway, nameserver and domain were not included (I > only used these parameters). I guess this refers to your statement "as > linuxrc is fine setting up a network based on just the ip and netmask"? > > Then I ran another test with the GMC2, and in that autoinst.xml the > gateway is included, but still no hostname or nameserver. Is there a > reason for that? > > Regards, > Eugen > > > Zitat von Steffen Winterfeldt : > >> Hi Eugen, >> >> On Tuesday 2015-11-24 12:58, Eugen Block wrote: >> >>> I have a question regarding the installation process of SLES12 >>> since SP0. I use virt-manager on a Xen host running on SLES11-SP3, >>> but my question also refers to installing xen-guests directly via >>> config files. >>> If I wanted to avoid network setup via dhcp on SLES11 VMs I used >>> the "Additional Arguments" in virt-manager, in the xen-config file >>> it is the "extra" line, where I used to provide information like >>> "Netsetup=-dhcp,all Hostname= Domain= Hostip= >>> Nameserver= Gateway=". >>> If I use the same syntax with SLES12-SP0/SP1-RC2/SP1-RC3/SP1-GMC, I >>> always get into the linuxrc confirmation screen where all my >>> entries are preselected (see the attached screenshot), I just have >>> to confirm them. So somehow linuxrc knows what it is, but why do I >>> have to confirm it? >> >> The original plan is/was for netsetup to provide network setup dialogs. Like >> netsetup=hostip,gateway should show two popups asking for hostip and > gateway. >> Likewise netsetup=-dhcp would just skip the question about dhcp usage. >> >> What it actually does in sle11 is to show popups only if it thinks >> some data is >> still needed. So netsetup=-dhcp hostip=10.10.0.1/16 will not ask for >> gateway or >> nameserver (as it should) as linuxrc is fine setting up a network >> based on just >> the ip and netmask. >> >> The 'all' was just a hack making netsetup=dhcp,all run dhcp on all >> interfaces. >> >> All in all the network config syntax was not in a good shape up to sle11. >> >> So there is now in sle12 the 'ifcfg' option which lets you specify exactly >> what you want to go into the ifcfg files without getting the linuxrc >> guesswork in the way. >> >> That said, I agree that 'netsetup' in sle12 is not perfect either. So if you >> go ahead and make a bugreport, I will look into this for sp2. >> >>> My colleage helped me and found a syntax where linuxrc doesn't ask >>> for this confirmation, but then the settings I have provided aren't >>> stored anywhere. So >> >> The network config is always copied to the target system. >> >> >> Steffen >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta > > > -- > Eugen Block voice : +49-40-559 51 75 > NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 > Postfach 61 03 15 > D-22423 Hamburg e-mail : eblock at nde.ag > > Vorsitzende des Aufsichtsrates: Angelika Mozdzen > Sitz und Registergericht: Hamburg, HRB 90934 > Vorstand: Jens-U. Mozdzen > USt-IdNr. DE 814 013 983 > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From eblock at nde.ag Thu Nov 26 06:44:39 2015 From: eblock at nde.ag (Eugen Block) Date: Thu, 26 Nov 2015 14:44:39 +0100 Subject: [sles-beta] Antw: Re: network settings for SLES12 installation In-Reply-To: <5657126A0200005A0012D090@prv-mh.provo.novell.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <1448360528.24052.16.camel@suse.com> <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> <20151125163111.Horde.-i_neQkRGy42IxQhd1jLZeq@www3.nde.ag> <5657126A0200005A0012D090@prv-mh.provo.novell.com> Message-ID: <20151126144439.Horde._YzniFgdp1y6L0JXkIBISXr@www3.nde.ag> Hi Torsten, thanks for your response. What I mean is, at the end of a manual install an autoinst.xml is created automatically, the file is written to /root/autoinst.xml. And in that file I expect the mentioned information. When I used SLE11-SP3 it was quite comfortable, I manually installed my admin node once, and with the automatically created autoinst.xml I could easily reinstall it many times without touching that xml file. Now I have to edit the autoinst (once) before using it for a fresh install. Please don't get me wrong, it's not that I don't know how to handle it, it's just that I'm kind of lazy and expected the autoinst to be as complete as it is in sle11. :-) I hope I could clear this up a little. Regards, Eugen Zitat von Torsten Hallmann : > Hi Eugen, > > is this an autoyast or manual install? If autoyast, did you use > keep_install_network? > > Also what I did with regards to installing kvm hosts where it needs > a bridge, but linuxrc does not know about, is to implement an ask > dialog filled with pre-defaults from cmd output with auto accept > timeout. See statements below for autoyast. By that I was able to > kickoff an installation with netsetup=-dhcp,all and then transfer > the net settings to br0 instead of eth0 :) > > > > initial > 1 > Network Settings > Enter the network settings for this host. > > networking,dns,hostname > > Hostname > string > > cat /proc/sys/kernel/hostname | awk -F'.' '{printf > $1$2$3$4}' > > 30 > > > initial > 1 > > networking,interfaces,0,ipaddr > > IP Address br0 > string > > ifconfig eth0 | grep Mask | cut -d ":" -f2 | awk > '{printf $1}' > > 30 > > > initial > 1 > > networking,interfaces,0,netmask > > Netmask br0 > string > > ifconfig eth0 | grep Mask | awk -F':' '{printf > $4}' > > 30 > > > initial > 1 > > networking,dns,nameservers,0 > > Nameserver > string > > grep nameserver /etc/resolv.conf | awk '{printf > $2}' > > 30 > > > initial > 1 > > networking,dns,domain > networking,dns,searchlist,0 > > Domain > string > > grep search /etc/resolv.conf | awk '{printf $2}' > > 30 > > > initial > 1 > > networking,routing,route,0,gateway > > Default Gateway > string > > route -n | grep ^0.0.0.0 | awk '{printf $2}' > > 30 > > > > Maybe you can tweak that a bit for your use case. > > >>>> Eugen Block schrieb am 11/25/2015 um 4:31 : >> Hi Steffen, >> >>> I agree that 'netsetup' in sle12 is not perfect either. So if you >>> go ahead and make a bugreport, I will look into this for sp2. >> >> It was more a question of how it is designed to be used than a >> potential bug report. Thanks for clearing that up, it helps me a lot! >> >>> The network config is always copied to the target system. >> >> I ran another test with SLE12-GMC using the ifcfg syntax, you are >> absolutely right about the VMs configuration, I find all the values I >> provided. What I didn't find - and that must be the part which let me >> write that statement about not storing the network settings - is the >> complete network configuration in the autoinst.xml which is created >> automatically after the installation. I saw only the ip address and >> the netmask, the gateway, nameserver and domain were not included (I >> only used these parameters). I guess this refers to your statement "as >> linuxrc is fine setting up a network based on just the ip and netmask"? >> >> Then I ran another test with the GMC2, and in that autoinst.xml the >> gateway is included, but still no hostname or nameserver. Is there a >> reason for that? >> >> Regards, >> Eugen >> >> >> Zitat von Steffen Winterfeldt : >> >>> Hi Eugen, >>> >>> On Tuesday 2015-11-24 12:58, Eugen Block wrote: >>> >>>> I have a question regarding the installation process of SLES12 >>>> since SP0. I use virt-manager on a Xen host running on SLES11-SP3, >>>> but my question also refers to installing xen-guests directly via >>>> config files. >>>> If I wanted to avoid network setup via dhcp on SLES11 VMs I used >>>> the "Additional Arguments" in virt-manager, in the xen-config file >>>> it is the "extra" line, where I used to provide information like >>>> "Netsetup=-dhcp,all Hostname= Domain= Hostip= >>>> Nameserver= Gateway=". >>>> If I use the same syntax with SLES12-SP0/SP1-RC2/SP1-RC3/SP1-GMC, I >>>> always get into the linuxrc confirmation screen where all my >>>> entries are preselected (see the attached screenshot), I just have >>>> to confirm them. So somehow linuxrc knows what it is, but why do I >>>> have to confirm it? >>> >>> The original plan is/was for netsetup to provide network setup >>> dialogs. Like >>> netsetup=hostip,gateway should show two popups asking for hostip and >> gateway. >>> Likewise netsetup=-dhcp would just skip the question about dhcp usage. >>> >>> What it actually does in sle11 is to show popups only if it thinks >>> some data is >>> still needed. So netsetup=-dhcp hostip=10.10.0.1/16 will not ask for >>> gateway or >>> nameserver (as it should) as linuxrc is fine setting up a network >>> based on just >>> the ip and netmask. >>> >>> The 'all' was just a hack making netsetup=dhcp,all run dhcp on all >>> interfaces. >>> >>> All in all the network config syntax was not in a good shape up to sle11. >>> >>> So there is now in sle12 the 'ifcfg' option which lets you specify exactly >>> what you want to go into the ifcfg files without getting the linuxrc >>> guesswork in the way. >>> >>> That said, I agree that 'netsetup' in sle12 is not perfect either. >>> So if you >>> go ahead and make a bugreport, I will look into this for sp2. >>> >>>> My colleage helped me and found a syntax where linuxrc doesn't ask >>>> for this confirmation, but then the settings I have provided aren't >>>> stored anywhere. So >>> >>> The network config is always copied to the target system. >>> >>> >>> Steffen >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sles-beta >> >> >> -- >> Eugen Block voice : +49-40-559 51 75 >> NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 >> Postfach 61 03 15 >> D-22423 Hamburg e-mail : eblock at nde.ag >> >> Vorsitzende des Aufsichtsrates: Angelika Mozdzen >> Sitz und Registergericht: Hamburg, HRB 90934 >> Vorstand: Jens-U. Mozdzen >> USt-IdNr. DE 814 013 983 >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta -- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock at nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 From vmoutoussamy at suse.com Thu Nov 26 10:04:36 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 26 Nov 2015 18:04:36 +0100 Subject: [sles-beta] Odd happenings in the register with RC2 to RC3 update In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0C56784@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C55DDD@hqmbx6.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76DF0C56098@hqmbx6.eur.ad.sag> <20151030102913.GA27855@suse.de> <46AC8C81C10B8C48820201DF2AE1D76DF0C56784@hqmbx6.eur.ad.sag> Message-ID: <5375D1F4-0182-4424-A54A-F2637F8AFB3B@suse.com> Hi, here is statement about the hostname of a machine registered in SCC: - Registration during installation: Like Thorsten said: > When the system at the moment of registration has a hostname set, this gets > send to SCC. Else we fall back to the ipv4 address. So if during a basic installation you do not set the hostname of your machine via the network configuration (cf. reg-netconf.png) -> Hostname/DNS (cf. hostname-net.png), and thus keep the default hostname ?linux?, then during the registration phase it will take the IP address of the server as the ?hostname on scc?. But if you replace the default hostname ?linux? and set, for instance "server1", "the hostname on scc? will be correctly set to "server1?. - Registration after installation: You can easily change ?the hostname on scc? of an already installed server with: 1) Setting/changing hostname: yast -> system -> network settings -> Hostname/DNS-> Hostname 2) Update the registration: # SUSEconnect -r regcode So you don?t really need to de-register and register again. I hope this help you to understand the setting of the hostname during the registration process. If by any chance this statement does not describe your case, please describe your case so that we could understand and reproduce it. Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hostname-net.png Type: image/png Size: 93126 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: reg-netconf.png Type: image/png Size: 100309 bytes Desc: not available URL: From snwint at suse.de Fri Nov 27 03:01:37 2015 From: snwint at suse.de (Steffen Winterfeldt) Date: Fri, 27 Nov 2015 11:01:37 +0100 (CET) Subject: [sles-beta] Antw: Re: network settings for SLES12 installation In-Reply-To: <20151126144439.Horde._YzniFgdp1y6L0JXkIBISXr@www3.nde.ag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> <46AC8C81C10B8C48820201DF2AE1D76DF0C6006D@hqmbx6.eur.ad.sag> <1448360528.24052.16.camel@suse.com> <20151124125854.Horde.93wd2F8ZOSDciUQg4PXUWfE@www3.nde.ag> <20151125163111.Horde.-i_neQkRGy42IxQhd1jLZeq@www3.nde.ag> <5657126A0200005A0012D090@prv-mh.provo.novell.com> <20151126144439.Horde._YzniFgdp1y6L0JXkIBISXr@www3.nde.ag> Message-ID: Hi Eugen, On Thursday 2015-11-26 14:44, Eugen Block wrote: > thanks for your response. What I mean is, at the end of a manual install an > autoinst.xml is created automatically, the file is written to > /root/autoinst.xml. And in that file I expect the mentioned information. When > I used SLE11-SP3 it was quite comfortable, I manually installed my admin node > once, and with the automatically created autoinst.xml I could easily reinstall > it many times without touching that xml file. Now I have to edit the autoinst > (once) before using it for a fresh install. Please don't get me wrong, it's > not that I don't know how to handle it, it's just that I'm kind of lazy and > expected the autoinst to be as complete as it is in sle11. :-) I hope I could > clear this up a little. it's not clear (at least to me) whether this requires adjustments in the yast network or autoyast code. I would at this point just create a bug report and see what happens. Steffen From Dick.Waite at softwareag.com Sun Nov 29 00:22:02 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sun, 29 Nov 2015 07:22:02 +0000 Subject: [sles-beta] Service Request: 10980794901 - Unable to Register a s390x System Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0C61F46@hqmbx6.eur.ad.sag> Grand Sunday Morning, Part of the --debug output. I do have a SLES12-SP0 system registered Okay. I have looked at scc.suse.com and it looks Okay. I did try --cleanup and when that didn't work I tried: rm -f /etc/SUSEConnect rm -f /etc/zypp/services.d/* rm -f /etc/zypp/credentials.d/* but I still get -3 ebug=true, language="POSIX"> Executing: 'uname -i' Quiet: false Output: 's390x' Executing: 'read_values -s' Quiet: false Output: 'Error: Unable to open configuration, return_code =-3' command 'read_values -s' failed SUSEConnect error: SUSE::Connect::SystemCallError: Error: Unable to open configuration, return_code =-3 /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/toolkit/system_calls.rb:27:in `execute' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/s390.rb:46:in `output' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/s390.rb:16:in `cpus' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/s390.rb:7:in `hwinfo' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/base.rb:13:in `info' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/system.rb:13:in `hwinfo' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/api.rb:40:in `announce_system' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/client.rb:48:in `announce_system' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/client.rb:142:in `announce_or_update' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/client.rb:26:in `register!' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/cli.rb:42:in `execute!' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/bin/SUSEConnect:11:in `' /usr/sbin/SUSEConnect:23:in `load' /usr/sbin/SUSEConnect:23:in `
' I have copied the SDK of GMC3 to the s390x and added it to the software repositories with Yast. zypper dup ran Okay, see output below.... ########################################################################## dali158:~ # zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following 14 packages are going to be upgraded: autoyast2 autoyast2-installation release-notes-sles rollback-helper sles-release-DVD yast2-dhcp-server yast2-dns-server yast2-http-server yast2-installation yast2-mail yast2-network yast2-nis-server yast2-schema yast2-services-manager 14 packages to upgrade. Overall download size: 2.4 MiB. Already cached: 0 B. After the operation, additional 29.5 KiB will be used. Continue? [y/n/? shows all options] (y): Retrieving package release-notes-sles-12.1.20151119-1.1.noarch (1/14), 443.4 KiB ( 1.0 MiB unpacked) Retrieving package rollback-helper-0.1-3.1.noarch (2/14), 7.9 KiB ( 1.5 KiB unpacked) Retrieving package yast2-dns-server-3.1.17-1.43.noarch (3/14), 200.1 KiB ( 2.3 MiB unpacked) Retrieving package yast2-mail-3.1.5-3.179.noarch (4/14), 141.3 KiB ( 1.2 MiB unpacked) Retrieving package yast2-services-manager-3.1.40-1.1.noarch (5/14), 34.6 KiB ( 81.7 KiB unpacked) Retrieving package sles-release-DVD-12.1-1.331.s390x (6/14), 3.4 KiB ( 66 B unpacked) Retrieving package yast2-network-3.1.134-4.1.s390x (7/14), 196.2 KiB (808.1 KiB unpacked) Retrieving package yast2-schema-3.1.5-1.79.s390x (8/14), 71.8 KiB (934.5 KiB unpacked) Retrieving package yast2-dhcp-server-3.1.5-3.241.noarch (9/14), 207.6 KiB ( 2.8 MiB unpacked) Retrieving package yast2-nis-server-3.1.3-3.211.noarch (10/14), 33.5 KiB (140.5 KiB unpacked) Retrieving package yast2-http-server-3.1.6-3.186.noarch (11/14), 167.8 KiB ( 1.8 MiB unpacked) Retrieving package autoyast2-installation-3.1.101.2-1.1.noarch (12/14), 151.2 KiB (681.3 KiB unpacked) Retrieving package autoyast2-3.1.101.2-1.1.noarch (13/14), 650.2 KiB ( 6.4 MiB unpacked) Retrieving package yast2-installation-3.1.162.1-1.1.noarch (14/14), 192.1 KiB (672.2 KiB unpacked) Checking for file conflicts: ................................................................................................................................[done] ( 1/14) Installing: release-notes-sles-12.1.20151119-1.1 ....................................................................................................[done] ( 2/14) Installing: rollback-helper-0.1-3.1 .................................................................................................................[done] ( 3/14) Installing: yast2-dns-server-3.1.17-1.43 ............................................................................................................[done] ( 4/14) Installing: yast2-mail-3.1.5-3.179 ..................................................................................................................[done] Additional rpm output: Updating /etc/sysconfig/mail... ( 5/14) Installing: yast2-services-manager-3.1.40-1.1 .......................................................................................................[done] ( 6/14) Installing: sles-release-DVD-12.1-1.331 .............................................................................................................[done] ( 7/14) Installing: yast2-network-3.1.134-4.1 ...............................................................................................................[done] ( 8/14) Installing: yast2-schema-3.1.5-1.79 .................................................................................................................[done] ( 9/14) Installing: yast2-dhcp-server-3.1.5-3.241 ...........................................................................................................[done] (10/14) Installing: yast2-nis-server-3.1.3-3.211 ............................................................................................................[done] (11/14) Installing: yast2-http-server-3.1.6-3.186 ...........................................................................................................[done] (12/14) Installing: autoyast2-installation-3.1.101.2-1.1 ....................................................................................................[done] (13/14) Installing: autoyast2-3.1.101.2-1.1 .................................................................................................................[done] Additional rpm output: Updating /etc/sysconfig/autoinstall... (14/14) Installing: yast2-installation-3.1.162.1-1.1 ........................................................................................................[done] Additional rpm output: Updating /etc/sysconfig/security... dali158:~ # __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), Eric Duffaut, 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: