From jrd at netlab1.net Mon Apr 7 03:04:32 2014 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 07 Apr 2014 10:04:32 +0100 Subject: [sles-beta] Beta 4 installation detail Message-ID: <53426A20.8080109@netlab1.net> I am installing beta 4 and this is a good time to mention an annoyance. When in the compendium screen choosing amongst software, booting, system and such, we can select the default run level (console vs gui). I choose console mode. The screen then comes back in red letters saying that it knows far better than me and I should be a GUI only consumer. Well, really! Please remove such helpful advice. The installing person makes the decisions. Further on this. The menu choice text reads "Default systemd target" which is about as obscure as one can make this. You can see my choice of terms above, console or GUI. Thanks, Joe D. From jrd at netlab1.net Mon Apr 7 03:12:56 2014 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 07 Apr 2014 10:12:56 +0100 Subject: [sles-beta] Beta 4 installation, network Message-ID: <53426C18.9000505@netlab1.net> Another beta 4 installation problem. The network configuration is not requested during the basic installation steps. The system comes up on the network using DHCP. It may very well be that we do not want the server coming up that way. The installation steps should include a proper network setup section before it goes onto the wires. Thanks, Joe D. From fbernasek at aol.com Mon Apr 7 06:16:08 2014 From: fbernasek at aol.com (Franz Bernasek) Date: Mon, 07 Apr 2014 14:16:08 +0200 Subject: [sles-beta] Kernel not found in boot Message-ID: <53429708.7010403@aol.com> Hi all if have install SLE 12 Beta 4 with default setup and hdd layout, after reboot when sucessful install message no Kernel 3.12.X found in /boot ? /boot is ext4 file system , maybe this the problem ? Thanks for Feedback Best Regards Franz From gjn at gjn.priv.at Mon Apr 7 08:08:50 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Mon, 07 Apr 2014 16:08:50 +0200 Subject: [sles-beta] Kernel not found in boot In-Reply-To: <53429708.7010403@aol.com> References: <53429708.7010403@aol.com> Message-ID: <2927245.T72pa9cZJX@gjn.priv.at> Am Montag, 7. April 2014, 14:16:08 schrieb Franz Bernasek: > Hi all > > if have install SLE 12 Beta 4 with default setup and hdd layout, after > reboot when sucessful install message no Kernel 3.12.X found in /boot ? > > /boot is ext4 file system , maybe this the problem ? ? Default install is btrfs and /home XFS But the better way read the filsystem.pdf from download directory ;) > Thanks for Feedback > Best Regards > > Franz > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gjn at gjn.priv.at Mon Apr 7 09:26:15 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Mon, 07 Apr 2014 17:26:15 +0200 Subject: [sles-beta] SLES12 Beta4 manual installation Yast network issue hostname does not get written into /etc/hosts In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0EFAB775@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0EFAB775@HXMB12.pnet.ch> Message-ID: <2517284.9qa4c7RcUj@gjn.priv.at> Hi Urs, Am Montag, 7. April 2014, 14:58:40 schrieb urs.frey at post.ch: > Hi > > When installing SLES12 x86_64 manually I can see the network configuration > menu with the tabs as known in Yast2 under Network Devices On witch place you can found the network configuration menu ? I would install with a static configuration, but I never found a network configuration menu :( ;) My install configuration is always DHCP and I have to change it afterward. > When editing the device under Overview everything OK > When editing Hostname/DNS, only /etc/resolv.conf gets filled out. NOK > /etc/hosts has only 127.0.0.1 localhost entry When editing Routing > tab, the routing entry gets written OK > > After installation, when going into yast I can see, that under Hostname/DNS > there stands still hostname=Linux and Domain Name=site > > So during the installation, somehow the input was not taken. Yes, the YaST network module have many, many bugs -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From mge at suse.com Mon Apr 7 10:16:07 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Mon, 7 Apr 2014 18:16:07 +0200 Subject: [sles-beta] SLES12 Beta4 Btrfs and autoyast ? In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0EFAB7AD@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0EFAB7AD@HXMB12.pnet.ch> Message-ID: <20140407161607.GB31036@suse.com> On 2014-04-07 T 16:03 +0000 urs.frey at post.ch wrote: > So I really like to go into things and use Btrfs. > But Btrfs must be installable using autoyast. Yes, indeed, looks like a bug. Please open a service request. TIA - 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 Mon Apr 7 10:19:00 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Mon, 7 Apr 2014 18:19:00 +0200 Subject: [sles-beta] SLES12 Beta4 manual installation Yast network issue hostname does not get written into /etc/hosts In-Reply-To: <2517284.9qa4c7RcUj@gjn.priv.at> References: <40637DBB36AF3941B243A286A432CA0B0EFAB775@HXMB12.pnet.ch> <2517284.9qa4c7RcUj@gjn.priv.at> Message-ID: <20140407161900.GC31036@suse.com> On 2014-04-07 T 17:26 +0200 G?nther J. Niederwimmer wrote: > On witch place you can found the network configuration > menu ? > > I would install with a static configuration, but I > never found a network configuration menu :( ;) > My install configuration is always DHCP and I have to > change it afterward. In Beta4 the Network Config dialog will only come up, if DHCP is _not_ successful. We currently working to make this dialog always (optionally) available, even if DHCP succeeds. No need for a Service Request in this case: it's already work in progress. 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 urs.frey at post.ch Mon Apr 7 10:22:32 2014 From: urs.frey at post.ch (urs.frey at post.ch) Date: Mon, 7 Apr 2014 16:22:32 +0000 Subject: [sles-beta] SLES12 Beta4 Btrfs and autoyast ? In-Reply-To: <20140407161607.GB31036@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0EFAB7AD@HXMB12.pnet.ch> <20140407161607.GB31036@suse.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0EFAB7E9@HXMB12.pnet.ch> Hi Mathias >Yes, indeed, looks like a bug. Please open a service request. Another challenge! I will have to get the YaST Logs and supportconfig from a remote SLES12 server installation which I can not boot anymore ;-D Hen & egg problem ... This way I can also test the SLES12 rescue system Best regards Urs Frey????????????????????????????????????????????? Post CH AG Informationstechnologie IT Betrieb Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: Matthias G. Eckermann [mailto:mge at suse.com] Gesendet: Monday, April 07, 2014 6:16 PM An: Frey Urs, IT222; sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLES12 Beta4 Btrfs and autoyast ? On 2014-04-07 T 16:03 +0000 urs.frey at post.ch wrote: > So I really like to go into things and use Btrfs. > But Btrfs must be installable using autoyast. Yes, indeed, looks like a bug. Please open a service request. TIA - 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 Mon Apr 7 11:16:01 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Mon, 7 Apr 2014 19:16:01 +0200 Subject: [sles-beta] Beta 4 installation, network In-Reply-To: <53426C18.9000505@netlab1.net> References: <53426C18.9000505@netlab1.net> Message-ID: <20140407171601.GC31478@suse.com> Hello Joe and all, On 2014-04-07 T 10:12 +0100 Joe Doupnik wrote: > Another beta 4 installation problem. The network > configuration is not requested during the basic > installation steps. The system comes up on the network > using DHCP. It may very well be that we do not want > the server coming up that way. The installation steps > should include a proper network setup section before > it goes onto the wires. as said in my other mail: yes, this is work in progress. We are aware that not everybody has DHCP or wants to use the result of DHCP for a Server installation, ... 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 jrd at netlab1.net Mon Apr 7 11:43:15 2014 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 07 Apr 2014 18:43:15 +0100 Subject: [sles-beta] Beta 4 installation, network In-Reply-To: <20140407171601.GC31478@suse.com> References: <53426C18.9000505@netlab1.net> <20140407171601.GC31478@suse.com> Message-ID: <5342E3B3.4050508@netlab1.net> On 07/04/2014 18:16, Matthias G. Eckermann wrote: > Hello Joe and all, > > On 2014-04-07 T 10:12 +0100 Joe Doupnik wrote: > >> Another beta 4 installation problem. The network >> configuration is not requested during the basic >> installation steps. The system comes up on the network >> using DHCP. It may very well be that we do not want >> the server coming up that way. The installation steps >> should include a proper network setup section before >> it goes onto the wires. > as said in my other mail: yes, this is work in progress. > We are aware that not everybody has DHCP or wants to use > the result of DHCP for a Server installation, ... > > so long - > MgE > ----------- Understood. I shall wait for that section to be completed. Hopefully it will permit setting the interface name at the same time (our ethN vs ensN discussion). Thanks, Joe D. From allan.graves at oracle.com Mon Apr 7 14:12:56 2014 From: allan.graves at oracle.com (Allan Graves) Date: Mon, 07 Apr 2014 16:12:56 -0400 Subject: [sles-beta] xattr.h? Message-ID: <534306C8.8070501@oracle.com> In sles11 this was in the libattr-devel package. Is this package still available for sles12, or has the file moved to another rpm? I don't see any libattr-devel in DVD1, although libattr is there. Thanks, Allan From mpost at suse.com Mon Apr 7 17:14:18 2014 From: mpost at suse.com (Mark Post) Date: Mon, 07 Apr 2014 17:14:18 -0600 Subject: [sles-beta] xattr.h? In-Reply-To: <534306C8.8070501@oracle.com> References: <534306C8.8070501@oracle.com> Message-ID: <5342F90A0200006D0015BB30@prv-mh.provo.novell.com> >>> On 4/7/2014 at 04:12 PM, Allan Graves wrote: > In sles11 this was in the libattr-devel package. > > Is this package still available for sles12, or has the file moved to > another rpm? > > I don't see any libattr-devel in DVD1, although libattr is there. The libattr-devel package has been moved to the SDK. When I looked, it did contain /usr/include/attr/xattr.h Mark Post From allan.graves at oracle.com Mon Apr 7 17:19:23 2014 From: allan.graves at oracle.com (Allan Graves) Date: Mon, 07 Apr 2014 19:19:23 -0400 Subject: [sles-beta] xattr.h? In-Reply-To: <5342F90A0200006D0015BB30@prv-mh.provo.novell.com> References: <534306C8.8070501@oracle.com> <5342F90A0200006D0015BB30@prv-mh.provo.novell.com> Message-ID: Mark, Thanks. But what is the SDK? -- Transcribed by cheapest tiny elves in my pocket. Mistake are possible. On April 7, 2014 7:14:18 PM EDT, Mark Post wrote: >>>> On 4/7/2014 at 04:12 PM, Allan Graves >wrote: >> In sles11 this was in the libattr-devel package. >> >> Is this package still available for sles12, or has the file moved to >> another rpm? >> >> I don't see any libattr-devel in DVD1, although libattr is there. > >The libattr-devel package has been moved to the SDK. When I looked, it >did contain /usr/include/attr/xattr.h > > >Mark Post > >_______________________________________________ >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 Arun.Singh at suse.com Mon Apr 7 18:38:23 2014 From: Arun.Singh at suse.com (Arun Singh) Date: Mon, 07 Apr 2014 18:38:23 -0600 Subject: [sles-beta] xattr.h? In-Reply-To: References: <534306C8.8070501@oracle.com> <5342F90A0200006D0015BB30@prv-mh.provo.novell.com> Message-ID: <5342F09F020000420009034E@prv-mh.provo.novell.com> Hi Allan, >>> On 4/7/2014 at 4:19 PM, Allan Graves wrote: > Mark, > Thanks. But what is the SDK? You need to download additional iso image containing SUSE development related packages (SLE-12-SDK-Beta4) SLE-12-SDK-DVD-x86_64-Beta4-DVD1.iso Let us know if you don't see above in your Beta download access. Thanks, Arun > -- > Transcribed by cheapest tiny elves in my pocket. Mistake are possible. > > On April 7, 2014 7:14:18 PM EDT, Mark Post wrote: >>>>> On 4/7/2014 at 04:12 PM, Allan Graves >>wrote: >>> In sles11 this was in the libattr-devel package. >>> >>> Is this package still available for sles12, or has the file moved to >>> another rpm? >>> >>> I don't see any libattr-devel in DVD1, although libattr is there. >> >>The libattr-devel package has been moved to the SDK. When I looked, it >>did contain /usr/include/attr/xattr.h >> >> >>Mark Post >> >>_______________________________________________ >>sles-beta mailing list >>sles-beta at lists.suse.com >>http://lists.suse.com/mailman/listinfo/sles-beta From allan.graves at oracle.com Tue Apr 8 09:19:50 2014 From: allan.graves at oracle.com (Allan Graves) Date: Tue, 08 Apr 2014 11:19:50 -0400 Subject: [sles-beta] xattr.h? In-Reply-To: <5342F09F020000420009034E@prv-mh.provo.novell.com> References: <534306C8.8070501@oracle.com> <5342F90A0200006D0015BB30@prv-mh.provo.novell.com> <5342F09F020000420009034E@prv-mh.provo.novell.com> Message-ID: <53441396.5070601@oracle.com> Ah! Thanks! Allan On 4/7/2014 8:38 PM, Arun Singh wrote: > Hi Allan, > >>>> On 4/7/2014 at 4:19 PM, Allan Graves wrote: >> Mark, >> Thanks. But what is the SDK? > You need to download additional iso image containing SUSE development related packages (SLE-12-SDK-Beta4) > > SLE-12-SDK-DVD-x86_64-Beta4-DVD1.iso > > Let us know if you don't see above in your Beta download access. > > Thanks, > Arun > > >> -- >> Transcribed by cheapest tiny elves in my pocket. Mistake are possible. >> >> On April 7, 2014 7:14:18 PM EDT, Mark Post wrote: >>>>>> On 4/7/2014 at 04:12 PM, Allan Graves >>> wrote: >>>> In sles11 this was in the libattr-devel package. >>>> >>>> Is this package still available for sles12, or has the file moved to >>>> another rpm? >>>> >>>> I don't see any libattr-devel in DVD1, although libattr is there. >>> The libattr-devel package has been moved to the SDK. When I looked, it >>> did contain /usr/include/attr/xattr.h >>> >>> >>> Mark Post >>> >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sles-beta > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From etso_srva_linux at mpsa.com Tue Apr 8 03:30:40 2014 From: etso_srva_linux at mpsa.com ( etso-srva-linux) Date: Tue, 8 Apr 2014 09:30:40 +0000 Subject: [sles-beta] Problem with LVM and BTRFS Message-ID: Hi all ! In Beta4 (and also Beta3) I try to install my server with the following disk configuration: LVM with BTRFS for system and no separate partition for /home (so I have /home as a BTRFS subvolume). This configuration seems good for our case because it's easier to manipulate VG/LV instead of device name or UUID. I saw during the installation that's YaST has created a partition for /boot (sounds strange because I was thinking that GRUB2 can boot on LV) and another partition for the entire BTRFS volume. The problem is that /boot/grub2/i386-pc and /boot/grub2/x86_64-efi are BTRFS subvolumes on top of a ext4 filesystem and that don't work! And so the boot is hanging (on the /boot mount and the /boot/grub2/* subvolume too). So, are BTRFS subvolumes on LVM supported? And is there a way to boot from LV? Regards, _______________________________ PSA Peugeot Citro?n Equipe Syst?me SuSE Devulder Lo?c DP/DSIN/ASTI/ETSO/SRVA T?l. Permanence N3?: 33 09 01 T?l. Permanence N4 : 22 92 40 _______________________________ Ce message peut contenir des informations confidentielles. S'il ne vous est pas destin?, merci de le d?truire et d'informer imm?diatement son ?metteur. Pour plus d'informations relatives ? la confidentialit? et ? la s?curit? veuillez consulter http://disclaimer.psa-peugeot-citroen.com. This message may contain confidential information. If you are not the intended recipient, please advise the sender immediately and delete this message. For further information on confidentiality and the risks inherent in electronic communication see http://disclaimer.psa-peugeot-citroen.com. From etso_srva_linux at mpsa.com Tue Apr 8 03:33:57 2014 From: etso_srva_linux at mpsa.com ( etso-srva-linux) Date: Tue, 8 Apr 2014 09:33:57 +0000 Subject: [sles-beta] Kernel not found in boot In-Reply-To: <53429708.7010403@aol.com> References: <53429708.7010403@aol.com> Message-ID: <3CBFA7CC2505A74B9C172B35128B88630A36854A@YLAV4460.INETPSA.com> Hi all, I have the same problem but I'm not using the default layout. I use LVM and so the /boot is ext4. This problem was not in Beta3. Regards, _______________________________ PSA Peugeot Citro?n Devulder Lo?c (loic.devulder at mpsa.com) Ing?nieur Syst?me LINUX Senior / Sp?cialiste LINUX domaine Calcul DP/DSIN/ASTI/ETSO/SRVA Adresse postale : SX.BES.12 T?l. Permanence : 33 09 01 ou 22 92 40 T?l. : +33 (0)3 84 46 95 84 (22) Mobile : +33 (0)6 87 72 47 31 _______________________________ Ce message peut contenir des informations confidentielles. S'il ne vous est pas destin?, merci de le d?truire et d'informer imm?diatement son ?metteur. Pour plus d'informations relatives ? la confidentialit? et ? la s?curit? veuillez consulter http://disclaimer.psa-peugeot-citroen.com. This message may contain confidential information. If you are not the intended recipient, please advise the sender immediately and delete this message. For further information on confidentiality and the risks inherent in electronic communication see http://disclaimer.psa-peugeot-citroen.com. -----Message d'origine----- De?: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] De la part de Franz Bernasek Envoy??: lundi 7 avril 2014 14:16 ??: sles-beta at lists.suse.com Objet?: [sles-beta] Kernel not found in boot Hi all if have install SLE 12 Beta 4 with default setup and hdd layout, after reboot when sucessful install message no Kernel 3.12.X found in /boot ? /boot is ext4 file system , maybe this the problem ? Thanks for Feedback Best Regards Franz _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From aginies at suse.com Wed Apr 9 01:46:57 2014 From: aginies at suse.com (Antoine Ginies) Date: Wed, 9 Apr 2014 09:46:57 +0200 Subject: [sles-beta] SLES12 beta4 book.sle.admin_en.pdf wicked Documentation? In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0EFAB74B@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0EFAB74B@HXMB12.pnet.ch> Message-ID: <20140409074657.GA2568@linux-w520.guibland.com> urs.frey at post.ch: > Hi > > I am trying to get deeper into wicked. > When looking at book.sle.admin.pdf delivered with SLES12 Beta4 I cannot find a description of wicked > > Am I to early ? > > Thank you very much for your feedback Yes you are :) Doc team is currently working on many manuals. You can find all needed information in the /usr/share/doc/packages/wicked directory of the installed system. regards -- Antoine Ginies Project Manager SUSE France From dvosburg at suse.com Wed Apr 9 06:47:47 2014 From: dvosburg at suse.com (Donald Vosburg) Date: Wed, 09 Apr 2014 06:47:47 -0600 Subject: [sles-beta] Kernel not found in boot In-Reply-To: <3CBFA7CC2505A74B9C172B35128B88630A36854A@YLAV4460.INETPSA.com> References: <53429708.7010403@aol.com> <3CBFA7CC2505A74B9C172B35128B88630A36854A@YLAV4460.INETPSA.com> Message-ID: <5344ED13020000C20014A697@prv-mh.provo.novell.com> Same issue here - chose the LVM default layout, and grub found no kernel at boot. Don Vosburg Sales Engineer SUSE Linux dvosburg at suse.com cell 765.278.2505 >>> " etso-srva-linux" 04/09/14 3:31 AM >>> Hi all, I have the same problem but I'm not using the default layout. I use LVM and so the /boot is ext4. This problem was not in Beta3. Regards, _______________________________ PSA Peugeot Citro?n Devulder Lo?c (loic.devulder at mpsa.com) Ing?nieur Syst?me LINUX Senior / Sp?cialiste LINUX domaine Calcul DP/DSIN/ASTI/ETSO/SRVA Adresse postale : SX.BES.12 T?l. Permanence : 33 09 01 ou 22 92 40 T?l. : +33 (0)3 84 46 95 84 (22) Mobile : +33 (0)6 87 72 47 31 _______________________________ Ce message peut contenir des informations confidentielles. S'il ne vous est pas destin?, merci de le d?truire et d'informer imm?diatement son ?metteur. Pour plus d'informations relatives ? la confidentialit? et ? la s?curit? veuillez consulter http://disclaimer.psa-peugeot-citroen.com. This message may contain confidential information. If you are not the intended recipient, please advise the sender immediately and delete this message. For further information on confidentiality and the risks inherent in electronic communication see http://disclaimer.psa-peugeot-citroen.com. -----Message d'origine----- De : sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] De la part de Franz Bernasek Envoy? : lundi 7 avril 2014 14:16 ? : sles-beta at lists.suse.com Objet : [sles-beta] Kernel not found in boot Hi all if have install SLE 12 Beta 4 with default setup and hdd layout, after reboot when sucessful install message no Kernel 3.12.X found in /boot ? /boot is ext4 file system , maybe this the problem ? Thanks for Feedback Best Regards Franz _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta _______________________________________________ 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 ihno at suse.de Wed Apr 9 08:46:26 2014 From: ihno at suse.de (Ihno Krumreich) Date: Wed, 9 Apr 2014 16:46:26 +0200 Subject: [sles-beta] SLES12 Beta 3 on s390x (System z) Boot Problem In-Reply-To: <6435F4C0DB8D4449BFD282C83A9F650601555B20@mso-e14mbx1.afcucorp.local> References: <6435F4C0DB8D4449BFD282C83A9F650601555B20@mso-e14mbx1.afcucorp.local> Message-ID: <20140409144626.GA3907@wotan.suse.de> Hi, just hit the return key two times.. Something is reading from the console. Ny entering return the boot continues. Regards Ihno Krumreich On Tue, Apr 08, 2014 at 07:02:05PM +0000, Gerard Howells wrote: > Greetings all, > > I'm having some trouble booting the SLES12 beta under z/VM 6.2. I'm using the default parm file, initial ramdisk and reader boot image (linux, formerly vmrdr.ikr in > Here's the entire boot sequence pasted from my 3270 console just FYI: > > 0000003 FILES PURGED > RDR FILE 0074 SENT FROM LNXMAINT PUN WAS 0074 RECS 118K CPY 001 A NOHOLD NOKEEP > RDR FILE 0078 SENT FROM LNXMAINT PUN WAS 0078 RECS 0001 CPY 001 A NOHOLD NOKEEP > RDR FILE 0082 SENT FROM LNXMAINT PUN WAS 0082 RECS 421K CPY 001 A NOHOLD NOKEEP > 0000003 FILES CHANGED > 0000003 FILES CHANGED > Initializing cgroup subsys cpuset > Initializing cgroup subsys cpu > Initializing cgroup subsys cpuacct > Linux version 3.12.14-1-default (geeko at buildhost) (gcc version 4.8.2 20140306 ?g > cc-4_8-branch revision 208375? (SUSE Linux) ) #1 SMP Mon Mar 17 13:28:33 UTC 201 > 4 (121c7d3) > setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit mode > setup.0cb929: Address spaces switched, mvcos available > Zone ranges: > DMA ?mem 0x00000000-0x7fffffff? > Normal empty > Movable zone start for each node > Early memory node ranges > node 0: ?mem 0x00000000-0x5fffffff? > PERCPU: Embedded 12 pages/cpu @0000000004555000 s18176 r8192 d22784 u49152 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 387840 > Kernel command line: TERM=dumb Manual=1 > PID hash table entries: 4096 (order: 3, 32768 bytes) > Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) > Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) > Memory: 1499400K/1572864K available (4611K kernel code, 567K rwdata, 2728K rodata, 300K init, 1107K bss, 73464K reserved) > Write protected kernel read-only data: 0x100000 - 0x82afff > Hierarchical RCU implementation. > CONFIG_RCU_FANOUT set to non-default value of 32 > RCU dyntick-idle grace-period acceleration is enabled. > RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=64. > NR_IRQS:260 > console ?ttyS0? enabled > allocated 6291456 bytes of page_cgroup > please try 'cgroup_disable=memory' option if you don't want memory cgroups > pid_max: default: 65536 minimum: 512 > Security Framework initialized > AppArmor: AppArmor initialized > Mount-cache hash table entries: 256 > Initializing cgroup subsys memory > Initializing cgroup subsys devices > Initializing cgroup subsys freezer > Initializing cgroup subsys blkio > Initializing cgroup subsys perf_event > Initializing cgroup subsys hugetlb > cpu.33a262: 1 configured CPUs, 0 standby CPUs > Brought up 1 CPUs > devtmpfs: initialized > NET: Registered protocol family 16 > bio: create slab at 0 > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > > > Thanks, > > Gerard Howells > zLinux System Administrator > Enterprise Systems > America First Credit Union > TEL: 801-827-8353 > ghowells at americafirst.com > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Best regards/Mit freundlichen Gr??en Ihno Krumreich "Never trust a computer you can lift." -- Ihno Krumreich Ihno at suse.de Projectmanager S/390 & zSeries Maxfeldstr. 5 +49-911-74053-439 D-90409 N?rnberg http://www.suse.de SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From ihno at suse.de Wed Apr 9 08:48:37 2014 From: ihno at suse.de (Ihno Krumreich) Date: Wed, 9 Apr 2014 16:48:37 +0200 Subject: [sles-beta] vmrdr.ikr In-Reply-To: References: Message-ID: <20140409144837.GB3907@wotan.suse.de> Hi, please take the file boot/s390x/linux Regards Ihno Krumreich On Wed, Apr 09, 2014 at 09:18:01AM -0400, Gary Ernst wrote: > I must have missed something somewhere. > I can't locate vmrdr.ikr to begin the Beta4 install under Z/VM.

Best Regards,

Gary Ernst
MainLine
FL 727-376-6807
IL 630-242-6604 > This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message. Thank You. > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Best regards/Mit freundlichen Gr??en Ihno Krumreich "Never trust a computer you can lift." -- Ihno Krumreich Ihno at suse.de Projectmanager S/390 & zSeries Maxfeldstr. 5 +49-911-74053-439 D-90409 N?rnberg http://www.suse.de SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From S.M.Flood at ucs.cam.ac.uk Thu Apr 10 06:20:58 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Thu, 10 Apr 2014 13:20:58 +0100 Subject: [sles-beta] OpenSSL Heartbleed Message-ID: <53468CAA.7000109@ucs.cam.ac.uk> I'm sure it's in hand but just to note that the version of OpenSSL included in SLES12 Beta 4 appears to be 1.0.1f without protection from CVE-2014-0160. I guess ditto for SLED12 too. HTH. -- Simon Flood Novell/SUSE/NetIQ Knowledge Partner From mge at suse.com Thu Apr 10 06:23:29 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Thu, 10 Apr 2014 14:23:29 +0200 Subject: [sles-beta] OpenSSL Heartbleed In-Reply-To: <53468CAA.7000109@ucs.cam.ac.uk> References: <53468CAA.7000109@ucs.cam.ac.uk> Message-ID: <20140410122329.GB11666@suse.com> Hello Simona and all, On 2014-04-10 T 13:20 +0100 Simon Flood wrote: > I'm sure it's in hand but just to note that the > version of OpenSSL included in SLES12 Beta 4 appears > to be 1.0.1f without protection from CVE-2014-0160. > > I guess ditto for SLED12 too. well, we don't assume that anybody uses SLE 12 Beta4 on a machine which provides a service to the public internet (beyond probably ssh, which is safe). That said, a fix in SLE 12 Beta5 is sufficient in our perspective, and will be provided. Or am I mistaken with my assumption above? 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) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From gjn at gjn.priv.at Thu Apr 10 06:30:14 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 10 Apr 2014 14:30:14 +0200 Subject: [sles-beta] Secure Boot and ASUS Message-ID: <4029489.dsjxTjWnxj@gjn.priv.at> Hello, I have a question to secure Boot with ASUS Boards. I have a small asus Server and test it with SLES 12 Beta 4 installing with active Secure Boot. This is not working. Then I test it with last ubuntu server, this is normal booting from CD? I found in the NVRAM a asus, microsoft and canonical Key., I mean this is the answer that ubuntu is booting. Is it possible to create SUSE DVDs that have the same functionality without a key in the NVRAM? Thanks for a answer, -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From meissner at suse.de Thu Apr 10 06:31:43 2014 From: meissner at suse.de (Marcus Meissner) Date: Thu, 10 Apr 2014 14:31:43 +0200 Subject: [sles-beta] OpenSSL Heartbleed In-Reply-To: <53468CAA.7000109@ucs.cam.ac.uk> References: <53468CAA.7000109@ucs.cam.ac.uk> Message-ID: <20140410123143.GB30598@suse.de> On Thu, Apr 10, 2014 at 01:20:58PM +0100, Simon Flood wrote: > I'm sure it's in hand but just to note that the version of OpenSSL included > in SLES12 Beta 4 appears to be 1.0.1f without protection from > CVE-2014-0160. > > I guess ditto for SLED12 too. The next beta will have the updated version. We will also try to push it as online update, if the system turns out to work. Ciao, Marcus From S.M.Flood at ucs.cam.ac.uk Thu Apr 10 06:33:59 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Thu, 10 Apr 2014 13:33:59 +0100 Subject: [sles-beta] OpenSSL Heartbleed In-Reply-To: <20140410122329.GB11666@suse.com> References: <53468CAA.7000109@ucs.cam.ac.uk> <20140410122329.GB11666@suse.com> Message-ID: <53468FB7.9030807@ucs.cam.ac.uk> On 10/04/2014 13:23, Matthias G. Eckermann wrote: > Hello Simona and all, ?! > well, we don't assume that anybody uses SLE 12 Beta4 on > a machine which provides a service to the public > internet (beyond probably ssh, which is safe). I can't speak for others but my testing (so far) is being done with virtual machines on a private network. > That said, a fix in SLE 12 Beta5 is sufficient in our > perspective, and will be provided. > > Or am I mistaken with my assumption above? I just wanted to make sure it's in hand as sometimes the obvious can be overlooked. Thanks, Simon -- Simon Flood Novell/SUSE/NetIQ Knowledge Partner From mge at suse.com Thu Apr 10 06:52:33 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Thu, 10 Apr 2014 14:52:33 +0200 Subject: [sles-beta] OpenSSL Heartbleed In-Reply-To: <53468FB7.9030807@ucs.cam.ac.uk> References: <53468CAA.7000109@ucs.cam.ac.uk> <20140410122329.GB11666@suse.com> <53468FB7.9030807@ucs.cam.ac.uk> Message-ID: <20140410125233.GG11666@suse.com> Hello Simon (:-) and all, On 2014-04-10 T 13:33 +0100 Simon Flood wrote: > On 10/04/2014 13:23, Matthias G. Eckermann wrote: > > >Hello Simona and all, > > ?! juggling too many mails in parallel. Sorry. > >well, we don't assume that anybody uses SLE 12 Beta4 > >on a machine which provides a service to the public > >internet (beyond probably ssh, which is safe). > > I can't speak for others but my testing (so far) is > being done with virtual machines on a private > network. > > >That said, a fix in SLE 12 Beta5 is sufficient in > >our perspective, and will be provided. > > > >Or am I mistaken with my assumption above? > > I just wanted to make sure it's in hand as sometimes > the obvious can be overlooked. Sure. Thanks! See Marcus' statement also.... 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 Apr 10 08:26:48 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Thu, 10 Apr 2014 16:26:48 +0200 Subject: [sles-beta] Secure Boot and ASUS In-Reply-To: <4029489.dsjxTjWnxj@gjn.priv.at> References: <4029489.dsjxTjWnxj@gjn.priv.at> Message-ID: <1397140008.13812.4.camel@par-r81vxc7.par.novell.com> Le jeudi 10 avril 2014 ? 14:30 +0200, G?nther J. Niederwimmer a ?crit : > Hello, > > I have a question to secure Boot with ASUS Boards. > > I have a small asus Server and test it with SLES 12 Beta 4 installing with > active Secure Boot. This is not working. > > Then I test it with last ubuntu server, this is normal booting from CD? > > I found in the NVRAM a asus, microsoft and canonical Key., I mean this is the > answer that ubuntu is booting. > > Is it possible to create SUSE DVDs that have the same functionality without a > key in the NVRAM? You don't need a key in NVRAM, since our shim loader has been signed with Microsoft key. However, it looks like some systems are not booting properly with SLES 12 Beta4 on Secure Boot. Could you test SLES 11 SP3 ISO and see if they were working or not ? And please open a service request to ensure we check your problem is the same we identified internally or another one. Thanks ! -- Frederic Crozat Project Manager Enterprise Desktop SUSE From fcrozat at suse.com Thu Apr 10 10:21:59 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Thu, 10 Apr 2014 18:21:59 +0200 Subject: [sles-beta] SLES12 beta4 systemd compatibility mode for sysvinit startup files? In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0EFABFEE@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0EFABFEE@HXMB12.pnet.ch> Message-ID: <1397146919.13812.19.camel@par-r81vxc7.par.novell.com> Le jeudi 10 avril 2014 ? 16:13 +0000, urs.frey at post.ch a ?crit : > Hi > > I have SLES12 Beta4 x86_64 installed on HP Proliant DL380-G7. > I am trying to work with systemd service > > When installing a sysvinit rc-startup script under /etc/init.d, I > thought it would be possible to run it in compatibility mode. It should work out of the box. Let's try to debug what is going wrong. > So I try to invoke the sysvinit rc-startscript as it is working on > SLES11-SP3. > But startup fails on SLES12 Beta4 x86_64 > > v03er9:~ # ls -lsa /etc/init.d/redis > 8 -rwxr-xr-x 1 root root 7679 Apr 10 16:50 /etc/init.d/redis > v03er9:~ # /etc/init.d/redis start > redirecting to systemctl start redis.service > Failed to start redis.service: Access denied > v03er9:~ # > v03er9:~ # service redis start > Job for redis.service failed. See 'systemctl status redis.service' and > 'journalctl -xn' for details. Could you attach both systemctl status redis.service and journalctl -xn output ? You'll need to remove /etc/systemd/system/redis.service file you created, since it will be used instead of /etc/init.d/redis. You must also run "systemctl daemon-reload" after remove the redis.service file. If you could also share the initscript, that would be helpful. -- Frederic Crozat Project Manager Enterprise Desktop SUSE From allen at ua.edu Fri Apr 11 12:33:14 2014 From: allen at ua.edu (Beddingfield, Allen) Date: Fri, 11 Apr 2014 18:33:14 +0000 Subject: [sles-beta] Heads up about a strange message Message-ID: Just an FYI, I got this message, although I'm obviously on the list for sles, sled, and typing this from a beta 4 install :) Looks like it must have been an "oops" that went out to some people. ----start copied text---- Dear Sir/Madam, Thank you for your interest in the SUSE Linux Enterprise 12 beta program. Due to the overwhelming response, our program is now full. We will keep your request on file, and get back to you should some additional space open up. Thank you again for your interest. SUSE Linux Enterprise Beta Team ----end copied text---- -- Allen Beddingfield Systems Engineer The University of Alabama