From Dick.Waite at softwareag.com Mon Aug 24 10:35:13 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 24 Aug 2015 16:35:13 +0000 Subject: [sles-beta] SLES 12 SP1 BETA2 - journalctl -xb Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0B7D14E@hqmbx6.eur.ad.sag> Grand Wet Afternoon, Not having happy hours updating some SLES12 -SP1 Beta1 to Beta2. In fact three VMware configs which have run Okay with Beta1 are stopping and telling me to use journalctl -xb to see what's up. I would like to send these logs to people who's eyes would be excited with the contents. How do I do this ? The machines are x86_64 with LVM and EXT3 or XFS file systems. The log says it's using EXT4 to mount the ext3's but is having a real bad hair day with the LVM stuff. If I switch back to the Beta1 snapshot then they load and run like happy VMware Workshop machine they are. I was going to have a run with my s390x machines tomorrow but I'd like to have my x86_64's running to check the big one small one interfaces. __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 From fcrozat at suse.com Mon Aug 24 10:41:07 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 24 Aug 2015 18:41:07 +0200 Subject: [sles-beta] SLES 12 SP1 BETA2 - journalctl -xb In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0B7D14E@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B7D14E@hqmbx6.eur.ad.sag> Message-ID: <1440434467.12502.0.camel@par-r81vxc7.par.novell.com> Le lundi 24 ao?t 2015 ? 16:35 +0000, Waite, Dick (External) a ?crit : > Grand Wet Afternoon, > > Not having happy hours updating some SLES12 -SP1 Beta1 to Beta2. In fact three VMware configs which have run Okay with Beta1 are stopping and telling me to use journalctl -xb to see what's up. I would like to send these logs to people who's eyes would be excited with the contents. How do I do this ? > The machines are x86_64 with LVM and EXT3 or XFS file systems. The log says it's using EXT4 to mount the ext3's but is having a real bad hair day with the LVM stuff. Please open a service request from SUSE Customer Center. Thanks ! -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Dick.Waite at softwareag.com Wed Aug 26 01:37:30 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Wed, 26 Aug 2015 07:37:30 +0000 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> Grand Sunny Morning, Just checking the head is Okay... I should be able to update from SLES11-SP4 to SLES12-SP1 (beta1 or Beta2) ? Can I update from SLES11-SP3 or SP4 to SLES12-SP1 or must I go to SLES12-SP0 first ? Anyone having issues with LVM when updating from SLES12-SP1Beta1 to Beta2 on x86_64 __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 From kukuk at suse.de Wed Aug 26 01:38:54 2015 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 26 Aug 2015 09:38:54 +0200 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> Message-ID: <20150826073854.GA6049@suse.de> On Wed, Aug 26, Waite, Dick (External) wrote: > Grand Sunny Morning, > > Just checking the head is Okay... > > I should be able to update from SLES11-SP4 to SLES12-SP1 (beta1 or Beta2) ? > > Can I update from SLES11-SP3 or SP4 to SLES12-SP1 or must I go to SLES12-SP0 first ? Insert your DVD, boot, select upgrade. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From S.M.Flood at uis.cam.ac.uk Wed Aug 26 04:14:01 2015 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Wed, 26 Aug 2015 11:14:01 +0100 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. In-Reply-To: <20150826073854.GA6049@suse.de> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> <20150826073854.GA6049@suse.de> Message-ID: <55DD9169.4090506@uis.cam.ac.uk> On 26/08/2015 08:38, Thorsten Kukuk wrote: > Insert your DVD, boot, select upgrade. Is it supported to go from SLES11 SP3 to SLES12 SP1? If it's like previous releases I expect the supported route is to first upgrade to SLES11 SP4. Are there some beta docs that we can have access to? Thanks, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom www.linkedin.com/in/simonflood SUSE Knowledge Partner From jrd at netlab1.net Wed Aug 26 09:44:17 2015 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 26 Aug 2015 16:44:17 +0100 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. In-Reply-To: <55DD9169.4090506@uis.cam.ac.uk> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> <20150826073854.GA6049@suse.de> <55DD9169.4090506@uis.cam.ac.uk> Message-ID: <55DDDED1.6070401@netlab1.net> Upgrading from SLES11SP3, my part of the story. As Thorsten said: insert DVD, select Upgrade, pray. I followed that advice. SLES11SP3 was the starting point, with loads of Apache apps installed and whatnot, a faithful test machine. I inserted the SLES12SP1 beta 2 iso (doing this in ESXi). This time I elected to register and receive updates during installation, something which I normally avoid. "Some time later" the process finished with no complaints. Testing. GUI works (if one can call Gnome working). Apache rebelled. The reason is it changed from v2.2 to 2.4 and Apache folks changed regular "Order allow,deny" to less useful terminology, just because they could I presume. Similar Apache annoyances pop up as we smooth things. I added module access_compat, but there remains many other version specific changes to Apache config files, thus prepare for a bit of rewriting. My iptables material works. The network functions (copper, static addressing). The mouse no longer works in the GUI, and it does not appear in text mode YaST. So, while SUSE normally does a terrific job with in-place upgrades this combination (beta 2) is a little over-stretched. Apache changes are in addition to this, naturally. Thanks, Joe D. On 26/08/2015 11:14, Simon Flood wrote: > On 26/08/2015 08:38, Thorsten Kukuk wrote: > >> Insert your DVD, boot, select upgrade. > > Is it supported to go from SLES11 SP3 to SLES12 SP1? If it's like > previous releases I expect the supported route is to first upgrade to > SLES11 SP4. > > Are there some beta docs that we can have access to? > > Thanks, > Simon From fcrozat at suse.com Wed Aug 26 09:54:43 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Wed, 26 Aug 2015 17:54:43 +0200 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. In-Reply-To: <55DDDED1.6070401@netlab1.net> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> <20150826073854.GA6049@suse.de> <55DD9169.4090506@uis.cam.ac.uk> <55DDDED1.6070401@netlab1.net> Message-ID: <1440604483.31154.6.camel@par-r81vxc7.par.novell.com> Le mercredi 26 ao?t 2015 ? 16:44 +0100, Joe Doupnik a ?crit : > Upgrading from SLES11SP3, my part of the story. Thanks for your report. > As Thorsten said: insert DVD, select Upgrade, pray. > I followed that advice. SLES11SP3 was the starting point, with > loads of Apache apps installed and whatnot, a faithful test machine. I > inserted the SLES12SP1 beta 2 iso (doing this in ESXi). This time I > elected to register and receive updates during installation, something > which I normally avoid. "Some time later" the process finished with no > complaints. > Testing. GUI works (if one can call Gnome working). Apache > rebelled. The reason is it changed from v2.2 to 2.4 and Apache folks > changed regular "Order allow,deny" to less useful terminology, just > because they could I presume. Similar Apache annoyances pop up as we > smooth things. I added module access_compat, but there remains many > other version specific changes to Apache config files, thus prepare for > a bit of rewriting. > My iptables material works. The network functions (copper, static > addressing). > The mouse no longer works in the GUI, and it does not appear in > text mode YaST. Hmm, strange. Could you open two separate SR for this ? - for text mode in yast, I would assume gpm is not running (or it was not properly enabled, if it was enabled before) - for GUI, I don't know. Maybe an issue with open-vm-tools ? -- Frederic Crozat Enterprise Desktop Release Manager SUSE From jrd at netlab1.net Wed Aug 26 10:04:22 2015 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 26 Aug 2015 17:04:22 +0100 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. In-Reply-To: <1440604483.31154.6.camel@par-r81vxc7.par.novell.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> <20150826073854.GA6049@suse.de> <55DD9169.4090506@uis.cam.ac.uk> <55DDDED1.6070401@netlab1.net> <1440604483.31154.6.camel@par-r81vxc7.par.novell.com> Message-ID: <55DDE386.6010806@netlab1.net> On 26/08/2015 16:54, Frederic Crozat wrote: > Le mercredi 26 ao?t 2015 ? 16:44 +0100, Joe Doupnik a ?crit : >> Upgrading from SLES11SP3, my part of the story. > Thanks for your report. > >> As Thorsten said: insert DVD, select Upgrade, pray. >> I followed that advice. SLES11SP3 was the starting point, with >> loads of Apache apps installed and whatnot, a faithful test machine. I >> inserted the SLES12SP1 beta 2 iso (doing this in ESXi). This time I >> elected to register and receive updates during installation, something >> which I normally avoid. "Some time later" the process finished with no >> complaints. >> Testing. GUI works (if one can call Gnome working). Apache >> rebelled. The reason is it changed from v2.2 to 2.4 and Apache folks >> changed regular "Order allow,deny" to less useful terminology, just >> because they could I presume. Similar Apache annoyances pop up as we >> smooth things. I added module access_compat, but there remains many >> other version specific changes to Apache config files, thus prepare for >> a bit of rewriting. >> My iptables material works. The network functions (copper, static >> addressing). >> The mouse no longer works in the GUI, and it does not appear in >> text mode YaST. > Hmm, strange. Could you open two separate SR for this ? > - for text mode in yast, I would assume gpm is not running (or it was > not properly enabled, if it was enabled before) > - for GUI, I don't know. Maybe an issue with open-vm-tools ? > > ------------ Yes, I can do that. Before taking that step, tomorrow I will repeat the exercise, without the real time updates. This is done with ESXi snapshot enabled so that I can retreat to the SLES11 starting point. On the mouse. I note that in /etc/sysconfig the VMware tools (not the open source variety) tweaked the mousetype setting from "imps2" to imps2. It was thus changed in SLES11SP3. Returning the quotes and restarting SLES12 made no improvement. Thus there is something else causing the mouse difficulty, and competition between VMware and open source tools is a possibility to be explored (i.e., turn off the VMware tools version before starting the upgrade). The mouse runs correctly in the SLES11 starting point. More tomorrow when that test completes. Thanks, Joe D. From jrd at netlab1.net Wed Aug 26 12:34:17 2015 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 26 Aug 2015 19:34:17 +0100 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. In-Reply-To: <55DDE386.6010806@netlab1.net> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> <20150826073854.GA6049@suse.de> <55DD9169.4090506@uis.cam.ac.uk> <55DDDED1.6070401@netlab1.net> <1440604483.31154.6.camel@par-r81vxc7.par.novell.com> <55DDE386.6010806@netlab1.net> Message-ID: <55DE06A9.9040009@netlab1.net> On 26/08/2015 17:04, Joe Doupnik wrote: > On 26/08/2015 16:54, Frederic Crozat wrote: >> Le mercredi 26 ao?t 2015 ? 16:44 +0100, Joe Doupnik a ?crit : >>> Upgrading from SLES11SP3, my part of the story. >> Thanks for your report. >> >>> As Thorsten said: insert DVD, select Upgrade, pray. >>> I followed that advice. SLES11SP3 was the starting point, with >>> loads of Apache apps installed and whatnot, a faithful test machine. I >>> inserted the SLES12SP1 beta 2 iso (doing this in ESXi). This time I >>> elected to register and receive updates during installation, something >>> which I normally avoid. "Some time later" the process finished with no >>> complaints. >>> Testing. GUI works (if one can call Gnome working). Apache >>> rebelled. The reason is it changed from v2.2 to 2.4 and Apache folks >>> changed regular "Order allow,deny" to less useful terminology, just >>> because they could I presume. Similar Apache annoyances pop up as we >>> smooth things. I added module access_compat, but there remains many >>> other version specific changes to Apache config files, thus prepare for >>> a bit of rewriting. >>> My iptables material works. The network functions (copper, static >>> addressing). >>> The mouse no longer works in the GUI, and it does not appear in >>> text mode YaST. >> Hmm, strange. Could you open two separate SR for this ? >> - for text mode in yast, I would assume gpm is not running (or it was >> not properly enabled, if it was enabled before) >> - for GUI, I don't know. Maybe an issue with open-vm-tools ? >> >> > ------------ > Yes, I can do that. Before taking that step, tomorrow I will > repeat the exercise, without the real time updates. This is done with > ESXi snapshot enabled so that I can retreat to the SLES11 starting point. > On the mouse. I note that in /etc/sysconfig the VMware tools (not > the open source variety) tweaked the mousetype setting from "imps2" to > imps2. It was thus changed in SLES11SP3. Returning the quotes and > restarting SLES12 made no improvement. Thus there is something else > causing the mouse difficulty, and competition between VMware and open > source tools is a possibility to be explored (i.e., turn off the > VMware tools version before starting the upgrade). The mouse runs > correctly in the SLES11 starting point. > More tomorrow when that test completes. > Thanks, > Joe D. ======== Adding a postscript tonight. I returned to the SLES11SP3 starting point. I disabled VMware tools, shut down the machine, and then repeated the installation process in Upgrade mode. Install time updates were enabled again. Thus only VMware tools changed in this test. Same results. No mouse in the Gnome GUI. Again, this is a virtual machine in ESXi. A btw, as systemd obscures things which we need, I looked about and found the rcWhatever scripts, and started GroupWise 2014. It ran! I did not test GW further because Apache material needs much changing for Apache v2.4 and I am out of time. SR writing is for tomorrow. Tonight we know that VMware tools is not the guilty party for mouse problems. Thanks, Joe D. From peter.czanik at balabit.com Thu Aug 27 07:32:40 2015 From: peter.czanik at balabit.com (=?UTF-8?B?Q3phbmlrLCBQw6l0ZXI=?=) Date: Thu, 27 Aug 2015 15:32:40 +0200 Subject: [sles-beta] legacy repo Message-ID: Hi, I'd like to ask, what is the status of the "legacy" repo. Some of the extra repositories already have "SP1" in their description, while the "legacy" repo and some others don't. I'm asking, as i'm from BalaBit, developers of syslog-ng. Syslog-ng was the default logging solution in SLES until recently and now it's part of the "legacy" repo. Next to other features I'd like to test syslog-ng on SLES 12 SP1. Bye, Peter Czanik (CzP) BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik -------------- next part -------------- An HTML attachment was scrubbed... URL: From kukuk at suse.de Thu Aug 27 07:45:24 2015 From: kukuk at suse.de (Thorsten Kukuk) Date: Thu, 27 Aug 2015 15:45:24 +0200 Subject: [sles-beta] legacy repo In-Reply-To: References: Message-ID: <20150827134524.GA17781@suse.de> On Thu, Aug 27, Czanik, P?ter wrote: > Hi, > > I'd like to ask, what is the status of the "legacy" repo. Some of the extra > repositories already have "SP1" in their description, while the "legacy" > repo and some others don't. No Module as a "SP1" in their description. No module will ever get a SP1 in their description. That modules differ from the SLES lifecycle is documented in the SLES 12 GA release notes: "SUSE Linux Enterprise Server Modules offer a choice of supplemental packages, ranging from tools for Web Development and Scripting, through a Cloud Management module, all the way to a sneak preview of SUSE's upcoming management tooling called Advanced Systems Management. Modules are part of your SUSE Linux Enterprise Server subscription, are technically delivered as online repositories, and differ from the base of SUSE Linux Enterprise Server only by their lifecycle. " > I'm asking, as i'm from BalaBit, developers of syslog-ng. Syslog-ng was the > default logging solution in SLES until recently and now it's part of the > "legacy" repo. Next to other features I'd like to test syslog-ng on SLES 12 > SP1. You can test it, just install and use it ;) Regards, Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From peter.czanik at balabit.com Thu Aug 27 07:54:06 2015 From: peter.czanik at balabit.com (=?UTF-8?B?Q3phbmlrLCBQw6l0ZXI=?=) Date: Thu, 27 Aug 2015 15:54:06 +0200 Subject: [sles-beta] off: /etc/default vs. /etc/sysconfig Message-ID: Hi, A slightly offtopic question, but I could not find anything about it in the documentation. What is the difference between /etc/default and /etc/sysconfig? Which to use in which situation? On a quick look my theory is, that both define environment variables, those in /etc/sysconfig are used by YaST and startscripts, those in /etc/default are the leftovers :-) In other words, for a 3rd party software, which of these two directories should be used? Bye, Peter Czanik (CzP) BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik -------------- next part -------------- An HTML attachment was scrubbed... URL: From kukuk at suse.de Thu Aug 27 08:03:48 2015 From: kukuk at suse.de (Thorsten Kukuk) Date: Thu, 27 Aug 2015 16:03:48 +0200 Subject: [sles-beta] off: /etc/default vs. /etc/sysconfig In-Reply-To: References: Message-ID: <20150827140348.GA18144@suse.de> Hi, On Thu, Aug 27, Czanik, P?ter wrote: > Hi, > > A slightly offtopic question, but I could not find anything about it in the > documentation. What is the difference between /etc/default and > /etc/sysconfig? Which to use in which situation? On a quick look my theory > is, that both define environment variables, those in /etc/sysconfig are > used by YaST and startscripts, those in /etc/default are the leftovers :-) Your quick look is wrong. This are not environment variables and /etc/default/ are no leftover ones. In /etc/sysconfig, there are configuration variables used by several tools/scripts. Beside some exceptions, they are not under control of RPM, but fillup. But the mandatory format is, that you can source them from a shell script. /etc/sysconfig is >>15 years old and available in more or less the same form on most distributions. /etc/default did come much later from projects coming from Solaris, there is no definition for the format of the files, and their are under control of RPM. > In other words, for a 3rd party software, which of these two directories > should be used? Depends on, on which systems this 3rd party software should run and if they want to follow the fillup rules or not. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From S.M.Flood at uis.cam.ac.uk Thu Aug 27 08:32:36 2015 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Thu, 27 Aug 2015 15:32:36 +0100 Subject: [sles-beta] off: /etc/default vs. /etc/sysconfig In-Reply-To: <20150827140348.GA18144@suse.de> References: <20150827140348.GA18144@suse.de> Message-ID: <55DF1F84.3050603@uis.cam.ac.uk> On 27/08/2015 15:03, Thorsten Kukuk wrote: > /etc/sysconfig is >>15 years old and available in more or less the same > form on most distributions. > /etc/default did come much later from projects coming from Solaris, > there is no definition for the format of the files, and their are under > control of RPM. Note /etc/sysconfig doesn't exist with Ubuntu/Debian which instead use /etc/default. HTH, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom www.linkedin.com/in/simonflood SUSE Knowledge Partner From Dick.Waite at softwareag.com Fri Aug 28 02:40:35 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 28 Aug 2015 08:40:35 +0000 Subject: [sles-beta] SLES 12 SP1 BETA2 - Install new using LVM XTS Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0B8272E@hqmbx6.eur.ad.sag> Grand Day, I'm having issues updating a SLES12-SP1 Beta1 to Beta2 if the file system is LVM with XTS. If it's all EXT3 then the update runs Okay.There is a SR on this. So I tried this morning to create a new install with a LVM and XTS. All goes well until I amend the size of the /home and create a /opt. When ones selects accepts one is told, on your bike, there is no "/" defined. Go back and leave all alone and one gets a file system... Anyone used the "Expert Partitioner" to create there own layout with XTS ? This is part of trying to find why a SLES12 SP1 Beta1 runs happy but will not update to Beta2. I am of course using VMware Workshop 12.0, but I don't see that giving the partitioner an issues. I'll let it build with a big /home and try amending after the build. I'll create a SR for the partitioner if it's not a know issue. __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 From kukuk at suse.de Fri Aug 28 02:44:29 2015 From: kukuk at suse.de (Thorsten Kukuk) Date: Fri, 28 Aug 2015 10:44:29 +0200 Subject: [sles-beta] SLES 12 SP1 BETA2 - Install new using LVM XTS In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0B8272E@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B8272E@hqmbx6.eur.ad.sag> Message-ID: <20150828084429.GA10729@suse.de> Hi, On Fri, Aug 28, Waite, Dick (External) wrote: > Grand Day, > I'm having issues updating a SLES12-SP1 Beta1 to Beta2 if the file system is LVM with XTS. If it's all EXT3 then the update runs Okay.There is a SR on this. So I tried this morning to create a new install with a LVM and XTS. All goes well until I amend the size of the /home and create a /opt. When ones selects accepts one is told, on your bike, there is no "/" defined. Go back and leave all alone and one gets a file system... Anyone used the "Expert Partitioner" to create there own layout with XTS ? This is part of trying to find why a SLES12 SP1 Beta1 runs happy but will not update to Beta2. I am of course using VMware Workshop 12.0, but I don't see that giving the partitioner an issues. I'll let it build with a big /home and try amending after the build. I'll create a SR for the partitioner if it's not a know issue. LVM in Beta2 is broken as you already found out, so as long as you use LVM, everything around this will not work, too. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From lli at vmware.com Sun Aug 30 20:14:55 2015 From: lli at vmware.com (Linhua (Linda) Li) Date: Mon, 31 Aug 2015 02:14:55 +0000 Subject: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. In-Reply-To: <55DE06A9.9040009@netlab1.net> References: <46AC8C81C10B8C48820201DF2AE1D76DF0B80BED@hqmbx6.eur.ad.sag> <20150826073854.GA6049@suse.de> <55DD9169.4090506@uis.cam.ac.uk> <55DDDED1.6070401@netlab1.net> <1440604483.31154.6.camel@par-r81vxc7.par.novell.com> <55DDE386.6010806@netlab1.net> <55DE06A9.9040009@netlab1.net> Message-ID: Here're the release notes and KB with workarounds for your reference. Thanks. https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#InstUpgrade.Upgrade http://kb.vmware.com/kb/2120590 Best Regards, -Linhua -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Joe Doupnik Sent: Thursday, August 27, 2015 2:34 AM To: sles-beta at lists.suse.com Subject: Re: [sles-beta] SLES 12 SP1 BETA2 - Update from path .. On 26/08/2015 17:04, Joe Doupnik wrote: > On 26/08/2015 16:54, Frederic Crozat wrote: >> Le mercredi 26 ao?t 2015 ? 16:44 +0100, Joe Doupnik a ?crit : >>> Upgrading from SLES11SP3, my part of the story. >> Thanks for your report. >> >>> As Thorsten said: insert DVD, select Upgrade, pray. >>> I followed that advice. SLES11SP3 was the starting point, >>> with loads of Apache apps installed and whatnot, a faithful test >>> machine. I inserted the SLES12SP1 beta 2 iso (doing this in ESXi). >>> This time I elected to register and receive updates during >>> installation, something which I normally avoid. "Some time later" >>> the process finished with no complaints. >>> Testing. GUI works (if one can call Gnome working). Apache >>> rebelled. The reason is it changed from v2.2 to 2.4 and Apache folks >>> changed regular "Order allow,deny" to less useful terminology, just >>> because they could I presume. Similar Apache annoyances pop up as we >>> smooth things. I added module access_compat, but there remains many >>> other version specific changes to Apache config files, thus prepare >>> for a bit of rewriting. >>> My iptables material works. The network functions (copper, >>> static addressing). >>> The mouse no longer works in the GUI, and it does not appear >>> in text mode YaST. >> Hmm, strange. Could you open two separate SR for this ? >> - for text mode in yast, I would assume gpm is not running (or it was >> not properly enabled, if it was enabled before) >> - for GUI, I don't know. Maybe an issue with open-vm-tools ? >> >> > ------------ > Yes, I can do that. Before taking that step, tomorrow I will > repeat the exercise, without the real time updates. This is done with > ESXi snapshot enabled so that I can retreat to the SLES11 starting point. > On the mouse. I note that in /etc/sysconfig the VMware tools (not > the open source variety) tweaked the mousetype setting from "imps2" to > imps2. It was thus changed in SLES11SP3. Returning the quotes and > restarting SLES12 made no improvement. Thus there is something else > causing the mouse difficulty, and competition between VMware and open > source tools is a possibility to be explored (i.e., turn off the > VMware tools version before starting the upgrade). The mouse runs > correctly in the SLES11 starting point. > More tomorrow when that test completes. > Thanks, > Joe D. ======== Adding a postscript tonight. I returned to the SLES11SP3 starting point. I disabled VMware tools, shut down the machine, and then repeated the installation process in Upgrade mode. Install time updates were enabled again. Thus only VMware tools changed in this test. Same results. No mouse in the Gnome GUI. Again, this is a virtual machine in ESXi. A btw, as systemd obscures things which we need, I looked about and found the rcWhatever scripts, and started GroupWise 2014. It ran! I did not test GW further because Apache material needs much changing for Apache v2.4 and I am out of time. SR writing is for tomorrow. Tonight we know that VMware tools is not the guilty party for mouse problems. Thanks, Joe D. _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.suse.com_mailman_listinfo_sles-2Dbeta&d=BQIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=QZVPu3M49AeoCqa67OycZQ&m=3zrlKJyh4lPMHgZ61wMPOF_wUFrcnSCBHGfVEZsops8&s=jF95uoF7vtAPSa-zJq8_1ZG4Ugd7WL0Qt5bqSdFiMzQ&e=