From gjn at gjn.priv.at Mon Mar 31 06:02:37 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Mon, 31 Mar 2014 14:02:37 +0200 Subject: [sles-beta] Kernel Config CONFIG_EFI_VARS= Message-ID: <7717062.gQr6Uan4LS@gjn.priv.at> Hello, is this a known Problem In default config is CONFIG_EFI_VARS=y int the XEN config is CONFIG_EFI_VARS=m the defaut is starting with efivars, with Xen I can't start with efivars and no instert it. -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From mge at suse.com Tue Apr 1 07:40:47 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Tue, 1 Apr 2014 15:40:47 +0200 Subject: [sles-beta] SLES12 beta3 question concerning XFS boot In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0EFAA3E1@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0EFAA3E1@HXMB12.pnet.ch> Message-ID: <20140401134047.GB23609@suse.com> Hello Urs and all, On 2014-04-01 T 13:22 +0000 urs.frey at post.ch wrote: > I still have some saying in my ears XFS would not be > supported as boot partition. this was and remains correct for SLE 11, as the grub1 bootloader does not successfully interacts with xfs in all situations. For SLE 12, we have grub2 now, and thus: > I was looking in book.sle.admin.pdf, GRUB2 and did > also some googling, noting found yet When testing > SLES12 Beta3 XFS on /boot, GRUB2 in MBR I can boot > without problems > > So I assume XFS as boot partition /boot, GRUB2 in MBR > is supported. Yes, xfs is supported "everywhere" in SLE 12, including /boot. Our recommended filesystem for the OS is btrfs though, as detailed in the presentation 3 weeks ago. > Thank you very much for your most welcome feedback HTH - 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 Tue Apr 1 07:53:21 2014 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 1 Apr 2014 13:53:21 +0000 Subject: [sles-beta] SLES12 beta3 question concerning XFS boot In-Reply-To: <20140401134047.GB23609@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0EFAA3E1@HXMB12.pnet.ch> <20140401134047.GB23609@suse.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0EFAA41A@HXMB12.pnet.ch> Hi Matthias Thank you very much > this was and remains correct for SLE 11, as the grub1.. This is exactly what "dr google" showed me. > Yes, xfs is supported "everywhere" in SLE 12, including /boot. Superbe! >Our recommended filesystem for the OS is btrfs though, >as detailed in the presentation 3 weeks ago. Yes of course, I joined this most welcome and very informative presentation. I am looking at BtrFs on one of my test servers and I already replayed snapshots after applying zypper changes. Works really perfect and in an amazing very fast way! It is also already very well documented in book.sle.admin.pdf, chapter 4. I would like to have a detailed look at all filesystems coming with SLES12, just to be able to know "what I am talking about" ;-D Reason for this is, that some of our application architects like to have /opt for their special purposes (Weblogic, TC-Server ,etc.) But when using BtrFS /opt should be a subvolume for snapshot purposes. 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: Tuesday, April 01, 2014 3:41 PM An: Frey Urs, IT222; sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLES12 beta3 question concerning XFS boot Hello Urs and all, On 2014-04-01 T 13:22 +0000 urs.frey at post.ch wrote: > I still have some saying in my ears XFS would not be > supported as boot partition. this was and remains correct for SLE 11, as the grub1 bootloader does not successfully interacts with xfs in all situations. For SLE 12, we have grub2 now, and thus: > I was looking in book.sle.admin.pdf, GRUB2 and did > also some googling, noting found yet When testing > SLES12 Beta3 XFS on /boot, GRUB2 in MBR I can boot > without problems > > So I assume XFS as boot partition /boot, GRUB2 in MBR > is supported. Yes, xfs is supported "everywhere" in SLE 12, including /boot. Our recommended filesystem for the OS is btrfs though, as detailed in the presentation 3 weeks ago. > Thank you very much for your most welcome feedback HTH - 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 allen at ua.edu Tue Apr 1 08:01:39 2014 From: allen at ua.edu (Beddingfield, Allen) Date: Tue, 1 Apr 2014 14:01:39 +0000 Subject: [sles-beta] SLES12 beta3 question concerning XFS boot In-Reply-To: <533AC562.4070702@netlab1.net> References: <40637DBB36AF3941B243A286A432CA0B0EFAA3E1@HXMB12.pnet.ch>, <533AC562.4070702@netlab1.net> Message-ID: Joe, I also remember getting burned with XFS systems with no separate /boot, so I've been using the same config you mention. I will probably keep a more cautious approach and stay with the separate /boot and XFS / for a while, although I'm experimenting with BTRFS here... Just my $0.02 worth... Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama ________________________________ From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Joe Doupnik [jrd at netlab1.net] Sent: Tuesday, April 01, 2014 8:55 AM To: sles-beta at lists.suse.com Subject: Re: [sles-beta] SLES12 beta3 question concerning XFS boot Matthias has just given the formal word on this. It can be useful to remember what happened to us in the past. Back then we could use XFS for a /boot partition (or no /boot at all, just XFS for /). That worked fine, until we upgraded the kernel. Then, as Matthias points out, grub's rebuilding of initrd could not handle XFS. A dead machine. This particular situation led me to create a separate /boot partition, and to format it as ext2 (non-journalling as grub could not replay the journal to a read-only mount point). Whether grub2 can do such replays is unknown to me at this time. I do use XFS for / and relatives, for now, then move to BTRFS. Joe D. On 01/04/2014 14:22, urs.frey at post.ch wrote: Hi I still have some saying in my ears XFS would not be supported as boot partition. I was looking in book.sle.admin.pdf, GRUB2 and did also some googling, noting found yet When testing SLES12 Beta3 XFS on /boot, GRUB2 in MBR I can boot without problems So I assume XFS as boot partition /boot, GRUB2 in MBR is supported. Thank you very much for your most welcome feedback 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 _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From mge at suse.com Tue Apr 1 08:12:05 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Tue, 1 Apr 2014 16:12:05 +0200 Subject: [sles-beta] SLES12 beta3 question concerning XFS boot In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0EFAA41A@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0EFAA3E1@HXMB12.pnet.ch> <20140401134047.GB23609@suse.com> <40637DBB36AF3941B243A286A432CA0B0EFAA41A@HXMB12.pnet.ch> Message-ID: <20140401141205.GB23742@suse.com> On 2014-04-01 T 13:53 +0000 urs.frey at post.ch wrote: > I would like to have a detailed look at all filesystems > coming with SLES12, just to be able to know "what I am > talking about" ;-D Reason for this is, that some of our > application architects like to have /opt for their > special purposes (Weblogic, TC-Server ,etc.) But when > using BtrFS /opt should be a subvolume for snapshot > purposes. Well, yes, but:-) Even if we mount "/opt" as a separate subvolume, you _can_ decide to put the whole "/opt" on another filesystem, such as xfs. Please do NOT do this for "/var", "/usr" or other parts, if you want to enjoy snapshotting. For "/opt" you will be safe, as no parts of the SUSE deliverable should put anything onto "/opt" by default. Now, why did we put "/opt" on a separate subvolume nevertheless? We want to be proactively careful. Imagine this: someone would put Oracle + data on "/opt" and it would be part of "/" on btrfs. If the "someone" would roll back, the data would be rolled back as well. -> "Not good"? Thus the safe bet is to put "/opt" on a separate subvolume, and an experienced administrator, who knows what he does, can decide to have "/opt" separately on e.g. xfs. Enjoy! so logn - 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 Tue Apr 1 08:23:47 2014 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 1 Apr 2014 14:23:47 +0000 Subject: [sles-beta] SLES12 beta3 question concerning XFS boot In-Reply-To: <20140401141205.GB23742@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0EFAA3E1@HXMB12.pnet.ch> <20140401134047.GB23609@suse.com> <40637DBB36AF3941B243A286A432CA0B0EFAA41A@HXMB12.pnet.ch> <20140401141205.GB23742@suse.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0EFAA451@HXMB12.pnet.ch> Thank you Perfect! Another piece of jigsaw puzzle which is going to complete in image ;-D 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: Tuesday, April 01, 2014 4:12 PM An: Frey Urs, IT222 Cc: sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLES12 beta3 question concerning XFS boot On 2014-04-01 T 13:53 +0000 urs.frey at post.ch wrote: > I would like to have a detailed look at all filesystems > coming with SLES12, just to be able to know "what I am > talking about" ;-D Reason for this is, that some of our > application architects like to have /opt for their > special purposes (Weblogic, TC-Server ,etc.) But when > using BtrFS /opt should be a subvolume for snapshot > purposes. Well, yes, but:-) Even if we mount "/opt" as a separate subvolume, you _can_ decide to put the whole "/opt" on another filesystem, such as xfs. Please do NOT do this for "/var", "/usr" or other parts, if you want to enjoy snapshotting. For "/opt" you will be safe, as no parts of the SUSE deliverable should put anything onto "/opt" by default. Now, why did we put "/opt" on a separate subvolume nevertheless? We want to be proactively careful. Imagine this: someone would put Oracle + data on "/opt" and it would be part of "/" on btrfs. If the "someone" would roll back, the data would be rolled back as well. -> "Not good"? Thus the safe bet is to put "/opt" on a separate subvolume, and an experienced administrator, who knows what he does, can decide to have "/opt" separately on e.g. xfs. Enjoy! so logn - 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 Tue Apr 1 08:31:07 2014 From: jrd at netlab1.net (Joe Doupnik) Date: Tue, 01 Apr 2014 15:31:07 +0100 Subject: [sles-beta] SLES12 beta3 question concerning XFS boot In-Reply-To: <20140401141205.GB23742@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0EFAA3E1@HXMB12.pnet.ch> <20140401134047.GB23609@suse.com> <40637DBB36AF3941B243A286A432CA0B0EFAA41A@HXMB12.pnet.ch> <20140401141205.GB23742@suse.com> Message-ID: <533ACDAB.2020906@netlab1.net> On 01/04/2014 15:12, Matthias G. Eckermann wrote: > On 2014-04-01 T 13:53 +0000 urs.frey at post.ch wrote: > >> I would like to have a detailed look at all filesystems >> coming with SLES12, just to be able to know "what I am >> talking about" ;-D Reason for this is, that some of our >> application architects like to have /opt for their >> special purposes (Weblogic, TC-Server ,etc.) But when >> using BtrFS /opt should be a subvolume for snapshot >> purposes. > > Well, yes, but:-) > > Even if we mount "/opt" as a separate subvolume, you > _can_ decide to put the whole "/opt" on another > filesystem, such as xfs. > > Please do NOT do this for "/var", "/usr" or other parts, > if you want to enjoy snapshotting. For "/opt" you will be > safe, as no parts of the SUSE deliverable should put > anything onto "/opt" by default. > > Now, why did we put "/opt" on a separate subvolume > nevertheless? > > We want to be proactively careful. > > Imagine this: someone would put Oracle + data on "/opt" > and it would be part of "/" on btrfs. If the "someone" > would roll back, the data would be rolled back as well. > -> "Not good"? > > Thus the safe bet is to put "/opt" on a separate > subvolume, and an experienced administrator, who knows > what he does, can decide to have "/opt" separately on > e.g. xfs. > > Enjoy! > > so logn - > MgE > ----------- Yes, indeed. The same reasoning applies to virtual machines where a host level snapshot can do the whole machine or omit certain disk drives (e.g., VMware independent drives). Back in the olden days, /usr/local was for personally installed material on BSD, external to the o/s installation. AT&T used /opt for the same purpose. Safe havens. Back then /usr was optional at boot time, rightly so, and led to /bin, /sbin, and /lib as areas to support booting and emergency recovery. /usr was to support interactive mode as the name implies. Today the Linux community has forgotten all about that, as well that /*/lib were for "lib*" files rather than be "general dumping grounds." Ah, how times change. Listen to Matthias. Joe D. From mge at suse.com Tue Apr 1 17:37:14 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 2 Apr 2014 01:37:14 +0200 Subject: [sles-beta] SLES12 beta3 ftp client does not work In-Reply-To: References: Message-ID: <20140401233711.GA31770@suse.com> On 2014-04-01 T 23:26 +0000 Guang Su wrote: > > I tried to ftp some error log from the beta3 setup and the client return unknown command 'open'. Has anyone seem this error? > > m6800-251:/var/log # ftp 10.130.60.46 > Wrapper for lftp to simulate compatibility with lukemftp > Unknown command `open'. > m6800-251:/var/log # Yes, the wrapper is broken. I think, it won't be fixed in Beta4, hopefully soon after. 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 gjn at gjn.priv.at Wed Apr 2 04:39:56 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Wed, 02 Apr 2014 12:39:56 +0200 Subject: [sles-beta] Btrfs SLES 11 SLES 12 Message-ID: <3494554.QgeZnbZGMe@gjn.priv.at> Hello, Question: why is it not possible to mount a Btrfs Partition created with SLES 11 from a SLES 12 in r/w mode, I can mount in read only mode with warnings ? is this a ACL Problem, the Partition is a root (/) Partition from SLES 11. -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From mge at suse.com Wed Apr 2 05:23:35 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 2 Apr 2014 13:23:35 +0200 Subject: [sles-beta] Btrfs SLES 11 SLES 12 In-Reply-To: <3494554.QgeZnbZGMe@gjn.priv.at> References: <3494554.QgeZnbZGMe@gjn.priv.at> Message-ID: <20140402112335.GC16489@suse.com> On 2014-04-02 T 12:39 +0200 G?nther J. Niederwimmer wrote: > Question: why is it not possible to mount a Btrfs > Partition created with SLES 11 from a SLES 12 in r/w > mode, I can mount in read only mode with warnings ? try mounting this way: mount -o subvolid=256 [DEVICE] [MOUNTPOINT] > is this a ACL Problem, the Partition is a root (/) > Partition from SLES 11. I don't think, it's an ACL thing. so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From mge at suse.com Wed Apr 2 07:22:52 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 2 Apr 2014 15:22:52 +0200 Subject: [sles-beta] Btrfs SLES 11 SLES 12 In-Reply-To: <20140402112335.GC16489@suse.com> References: <3494554.QgeZnbZGMe@gjn.priv.at> <20140402112335.GC16489@suse.com> Message-ID: <20140402132252.GA17540@suse.com> On 2014-04-02 T 13:23 +0200 Matthias G. Eckermann wrote: > On 2014-04-02 T 12:39 +0200 G?nther J. Niederwimmer wrote: > > > Question: why is it not possible to mount a Btrfs > > Partition created with SLES 11 from a SLES 12 in r/w > > mode, I can mount in read only mode with warnings ? > > try mounting this way: > mount -o subvolid=256 [DEVICE] [MOUNTPOINT] I this does not help, please open a Service Request an attach the LogFiles with the Warnings. TIA - MgE > > is this a ACL Problem, the Partition is a root (/) > > Partition from SLES 11. > > I don't think, it's an ACL thing. -- 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 behlert at suse.com Fri Apr 4 06:39:47 2014 From: behlert at suse.com (Stefan Behlert) Date: Fri, 4 Apr 2014 14:39:47 +0200 Subject: [sles-beta] Update regarding Beta4 Message-ID: <20140404123947.GC5531@suse.de> Hi all, I want to update you about the current status of SLES 12 Beta4. We struggled with some last minute bugfixes during this week, which took more time than expected. But as the bugs included some serious issues that would have impacted quite a lot of people, we decided to rather be late with Beta 4 than to be on time but faulty. But finally we have an image that is currently checked thoroughly by our QA. If no show stoppers are found, we expect the release from QA later today. Given that uploading and distributing the images on the Servers will take a while, we recommend not to wait for Beta4 today. People in the US might see the images appear on the Beta download page today, but we cannot gurantee it. We are sorry for the delay, but - even accepting that a Beta image has issues - we wanted to be in a better shape than we were on Monday. If we found a show stopper, we will inform you about a new delivery date, but currently we are not expecting anything. Thanks for your understanding and sorry for the inconvenience the delay may cause, Stefan -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From behlert at suse.com Fri Apr 4 06:59:56 2014 From: behlert at suse.com (Stefan Behlert) Date: Fri, 4 Apr 2014 14:59:56 +0200 Subject: [sles-beta] SLES12 x86_64 Beta3 autoyast issue /etc/hosts no hostname entry In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0EFA96AF@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0EFA8953@HXMB12.pnet.ch> <53328745.5060006@suse.de> <40637DBB36AF3941B243A286A432CA0B0EFA8B2C@HXMB12.pnet.ch> <53354838.604@suse.de> <40637DBB36AF3941B243A286A432CA0B0EFA96AF@HXMB12.pnet.ch> Message-ID: <20140404125956.GF5531@suse.de> Hi Urs, On Mar 28, 14 10:14:49 +0000, urs.frey at post.ch wrote: > Hi Marius > > Thank you very much > Yes I opened a service request > > Service Request # 10885376321 has been created. > > SUMMARY OF SR # 10885376321 > * SR Severity Level: Medium > * SR Brief Description: SLES12-Beta3, autoyast not writing IP-address and hostname to /etc/hosts we have updated the autoyast2 package for Beta4, but as far as I can see at the moment this is not fixed yet. Sorry, Stefan bug number 870998 > -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From john.dallman at siemens.com Fri Apr 4 07:18:04 2014 From: john.dallman at siemens.com (Dallman, John) Date: Fri, 4 Apr 2014 13:18:04 +0000 Subject: [sles-beta] Update regarding Beta4 In-Reply-To: <20140404123947.GC5531@suse.de> References: <20140404123947.GC5531@suse.de> Message-ID: Stefan Behlert wrote: > We struggled with some last minute bugfixes during this week, > which took more time than expected. But as the bugs included > some serious issues that would have impacted quite a lot of > people, we decided to rather be late with Beta 4 than to be > on time but faulty. Thanks for the update, and for the sensible decision. -- John Dallman Technology & Innovation Siemens Industry Sector Siemens Industry Software Limited Francis House, 112 Hills Road, Cambridge CB2 1DP, United Kingdom Tel. :+44 (1223) 371554 Fax :+44 (1223) 371700 john.dallman at siemens.com www.siemens.com/plm ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. From behlert at suse.com Fri Apr 4 14:48:17 2014 From: behlert at suse.com (Stefan Behlert) Date: Fri, 4 Apr 2014 22:48:17 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 12 Beta4 is available Message-ID: <20140404204817.GF21154@suse.de> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta participants, we are happy to announce the forth Beta of SUSE Linux Enterprise Server 12. ISO images are now available for download now. Please go to http://www.novell.com/beta and select "View my beta page". Here you should see all Beta's you are part of. Note that the directory contains the images for the SDK as well as for SLED. We offer 3 DVD ISOs: DVD1 contains the binaries, the second DVD the sources and the third DVD the debuginfo packages. The final product will not contain the debuginfo packages on the media. For installation purposes you just need Media 1 for your architecture. Please verify the md5sum of the ISO using the MD5SUMS file, which can be found in the same directory on the download servers. Known issues: 871178 - No network during upgrade 871880 - snapper does not call grub-plugin 872012 - Adding Extensions/Modules after registration during installation fails 870625 - No addon dialog without registration 871852 - ppc64le rescue missing grub2 871857 - No console available to OS when booting Xen Hypervisor 869359 - formatting partition (ext3) got system error code -3006 If you select ext3 filesystem in the expert partitioner, you get an error popup. You can safely click "continue" there, the installation will succeed. In the installed system, you should change in /etc/fstab the entry for the partition from ext2 to ext3, if you want to use ext3-specific features. - several issues with chzdev on s390x - autoyast2 still with some issues - upgrading from SLE 11 SP3 is not working flawlessly, requiring manual interaction Hint: - "GNOME Classic" (patched to be similar to SLE11 GNOME) has been renamed "SLE Classic", allowing users to use "upstream" GNOME Classic, in addition to our own flavor. Although migrating from one Beta to another is often possible, it's not supported. For this Beta, we want to point out the following: If you are migrating a SLE12 Beta2/3 system to Beta4, you will need to select the session as "SLE Classic" in gdm, otherwise you'll end-up in "GNOME Classic" upstream flavor. This migration issue is valid only for this Beta upgrade. With this Beta4 snapshot we have reached several milestones: o Milestone: All updated device drivers are verified and proven to be stable o Continue system test. o Fix problems found during update or certification tests. For the next Beta-Release we are targeting these actions and milestones: o Milestone: All features are verified to work. o Milestone: System test completed. o Start performance and regression tests. o Continue to fix problems found during update, performance or certification tests. Thanks in advance for all your testing Your SUSE Linux Enterprise Team -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From Dick.Waite at softwareag.com Sat Apr 5 08:24:15 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Sat, 5 Apr 2014 14:24:15 +0000 Subject: [sles-beta] - Beta4 - SR 10884981671 Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53784C4E@hqmbx6.eur.ad.sag> Grand Day, I tried to update from a simple basic SUSE 11-3 to SUSE 12-0 Beta4 and still get issues with network configuration and then after the re-ipl a "blank" screen One can load the rescue system and an update will run but gives an ERROR at the same place as the first update. I have updated the SR. A new install of v12 Beta 4 runs Okay on the same VMware enviroment with the same network config.. __R ___________________________________________ Dick Waite Senior R&D Consultant Phone: +49 6151 92-1505 Mobile: +49 171 8393 769 Software AG Uhlandstr. 12 | 64297 Darmstadt | Germany www.softwareag.com ___________________________________________ Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From fcrozat at suse.com Fri Apr 4 08:43:29 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 04 Apr 2014 16:43:29 +0200 Subject: [sles-beta] [ANNOUNCE] SLED Extension 12 Beta4 is available Message-ID: <1396622609.2818.144.camel@par-r81vxc7.par.novell.com> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta participants, we are happy to announce the first release to beta testers (but fourth Beta) of SUSE Linux Enterprise Desktop Extension 12. ISO images are now available for download now. Please go to http://www.novell.com/beta and select "View my beta page". Here you should see all Beta's you are part of. We offer 2 DVD ISOs: DVD1 contains the binaries and sources, the second DVD the debuginfo packages. The final product will not contain the debuginfo packages on the media. To use this extension (together with SLES 12 Beta4): - start SLES installation - you MUST register to SCC and then only choose "use add-ons from media" to select the Add-on ISO image (retrieving the extension for SCC is not enabled yet). Highlights: - "GNOME Classic" (modified to be one panel setup, similar to SLE11 GNOME) has been renamed "SLE Classic", allowing users to use "upstream" GNOME Classic, in addition to SUSE flavor. See below about migration from previous betas. - Firefox 28 - upgrade from 11 SP3 improved - autoyast2 improved Known problems: bnc#869127 - keyboard focus lost in gdm (keyboard focus lost in gdm, workaround is to press "Ctrl-Alt-Tab" until you have focus again) bnc#866055 - switching from runlevel 5 to runlevel 3 doesn't terminate Xorg bnc#861543 - ICAClient not installable Happy testing! Your SUSE Linux Enterprise Team -- Frederic Crozat Project Manager Enterprise Desktop SUSE From gjn at gjn.priv.at Sun Apr 6 04:12:10 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sun, 06 Apr 2014 12:12:10 +0200 Subject: [sles-beta] Grub2-efi Installation Message-ID: <5015731.oFiQVVxUvY@gjn.priv.at> Hello, Question: the grub2-efi installation is broken again in Beta4 or ? The /boot/efi/EFI/suse/grub2/x86_64/ directory is blank on my system and more ;) -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer