From behlert at suse.com Mon Aug 10 00:37:47 2015 From: behlert at suse.com (Stefan Behlert) Date: Mon, 10 Aug 2015 08:37:47 +0200 Subject: [sles-beta] Some additional information about downloads Message-ID: <20150810063747.GB21390@suse.de> Moin, since quite some emails received me directly, let me give you two pieces of information about the Beta milestones: If you have an issue with downloading the images or accessing the beta page, be so kind to contact the Beta program managers at beta-programs at lists.suse.com - they can help you where the Release Managers cannot. We announce the isos normally a little bit of time after we have uploaded them to the download servers. But as it is a network of download servers, there might be some servers that have not all the images yet when we announce. We try to make the announcement as late as possible, but sometimes it's still too early to have the images on all download servers deployed :( We recommend if you see only soem but not all images to wait a little bit longer before you contact beta-programs at lists.suse.com. We are sorry for that inconvenience, but hope that for most of you the tinming works. ciao, Stefan -- Stefan Behlert, SUSE LINUX Release Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX GmbH, Nuernberg; GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nuernberg) From behlert at suse.com Mon Aug 10 00:22:34 2015 From: behlert at suse.com (Stefan Behlert) Date: Mon, 10 Aug 2015 08:22:34 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 12 SP1 Beta1 is available In-Reply-To: <55C760C7020000C20016DA17@prv-mh.provo.novell.com> References: <20150807133603.GH21390@suse.de> <1439033697.7135.2.camel@par-r81vxc7.par.novell.com> <55C760C7020000C20016DA17@prv-mh.provo.novell.com> Message-ID: <20150810062234.GA21390@suse.de> Moin, On Aug 09, 15 14:16:39 -0600, Donald Vosburg wrote: > What about testing modules? > I have to admit that we still have one bug there with the modules, as when they were created they were bound too tight to 12 GA. So we have to release some bugfix update for most of them first before you can use them with SP1. We are sorry for that, and strive to have this fixed as soon as possible. Stefan > > > >>> Frederic Crozat 08/08/15 7:35 AM >>> > Le samedi 08 ao?t 2015 ? 08:26 +0200, Czanik, P?ter a ?crit : > > Hi, > > > > > > On Fri, Aug 7, 2015 at 3:36 PM, Stefan Behlert > > wrote: > > > > Known issues: > > * Registration is not working with your regular SLE key, > > special regcode is required > > > > > > Where is this special regcode available? (/me just downloading the > > iso...) > > It will be provided to you soon. In the mean time, just skip > registration during installation (we weren't planning to push any > updates for Beta1 anyway, so no harm done). > > -- > Frederic Crozat > Enterprise Desktop Release Manager > SUSE > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Stefan Behlert, SUSE LINUX Release Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX GmbH, Nuernberg; GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nuernberg) From pokorra at uni-siegen.de Mon Aug 10 21:01:21 2015 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Tue, 11 Aug 2015 05:01:21 +0200 Subject: [sles-beta] LWL links from Intel NIC get lost during boot Message-ID: <1439262081.1785.7.camel@uni-siegen.de> In a DELL PowerEdge R730 we have the integrated NIC: Intel(R) 2P x520/2P l350 rNDC The two 10-Gigabit LWL links get lost und will not come back during the installation. -- Gerd Pokorra University Siegen H?lderlinstr. 3 D-57076 Siegen Germany Phone +49 271 740 4379 From vmoutoussamy at suse.com Tue Aug 11 10:05:32 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 11 Aug 2015 18:05:32 +0200 Subject: [sles-beta] [ANNOUNCE] Beta test Subscription key for SLE 12 SP1 Beta Message-ID: Good news everyone, We are happy to announce the availability of ?Beta Registration key? for our SLE 12 SP1 Beta program. We have generate separate private keys for each product : SLES, SLED, HA. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear customers and partners, by now you should have received a private email with your private keys and the FAQ of the Beta Test Subscription. If you did not received this email or if you have any issue regarding the Beta Test Subscription and key, please contact us at beta-programs at lists.suse.com !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! @SUSE employees, we did not forget you! More information will reach you soon. Of course you can also contact us at beta-programs at lists.suse.com for any report. ===================== FAQ ================================== Please read the following FAQ for more information about the Beta test Subscription and registration key : 1. What is a Beta Test Subscription? A Beta Subscription is a new concept that SUSE will test starting with the Beta Program for SLE 12. The Beta subscription will provide you with access to all the products and will allow you to test the online migration and the registration flow. 2. Will a Beta Subscription allow me to register a SLES/SLED 12 GA? Yes, the Beta Subscriptions allows you access previously released versions of SLES. 3. I want SLES, SLED and HA keys, why did I receive only the SLES one ? We do not have unlimited keys for this beta, so we provide the key according to your SLE 12 SP1 beta survey preferences. If you said that you only wanted to test SLES 12 SP1, we only send the SLES Beta keys. Please contact me at beta-programs at lists.suse.com if you would like to request a different product key. 4. How should the migration from SLE 12 GA to SLE 12 SP1 (with registration) be tested? All your current subscriptions don't have yet access to SLES 12 SP1, only the new beta subscription provide you access to these products. Due to this limitation, if you are testing the online migration, please register machine/instances using only the beta subscriptions. 5. How can I use a Beta Subscriptions? Before using the registration key on your system, please take 2 min and active the subscription. The steps are the following: - Go to https://scc.suse.com and login - Access "Manually activate my subscription" from the dashboard - Read and Accept Terms and Conditions - Select the organization under which you would like to activate the subscription. You can create a new organization, if you want. Once the subscription has been activated, you will be able to use it to either directly register the system against SUSE Customer Center or access the Beta products via tools like SMT. The simple way to register your system against SUSE Customer Center is by using the SUSEConnect command line (you can also do it via YaST): # SUSEConnect -r regkey -e myemailaddress --url https://scc.suse.com 6. The registration process is not working, what should I do ? If you have the following error message : Error: SCC returned 'The subscription with the provided regcode does not include the requested product' (422) It means that you tried to register a key attached to a specific product to a server with another specific product. Keep in mind that there is specific key for the each product SLES, SLED and HA. For instance you will face the error (422) if you try to register a SLED with a SLES Beta registration key. /!\ If you have any other issues please contact me at beta-programs at lists.suse.com. 7. Which is the lifespan of a Beta Subscriptions? A Beta subscription is available for 6 months. 8. How many system am I allowed to register using a Beta Subscription? The limit is set to 1 system with unlimited VMs running on the same systems. 9. Can I de-register a system that's using a Beta Subscription? Yes, you can de-register the system via the SCC user interface. Soon we'll able you to de-register a system using SUSEConnect command line. I hope this FAQ helps you to understand what?s the purpose of the Beta subscription for SLE 12 SP1 Beta, to setup your system to test the SP migration, and to you test the scc registration. Do not hesitate to contact me for further information or any logistic issues at beta-programs at lists.suse.com. Happy beta testing ! Kind regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From vmoutoussamy at suse.com Tue Aug 11 10:19:52 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 11 Aug 2015 18:19:52 +0200 Subject: [sles-beta] LWL links from Intel NIC get lost during boot In-Reply-To: <1439262081.1785.7.camel@uni-siegen.de> References: <1439262081.1785.7.camel@uni-siegen.de> Message-ID: <21B3C1C5-DC00-43EA-B02A-1E5C962F69FB@suse.com> Hi, I would like to have some details about what happens: Were you able to complete the installation ? Do you see the issue after the installation ? Did you see any interesting error messages on the console ? Thank you, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 11 Aug 2015, at 05:01, Gerd Pokorra wrote: > > In a DELL PowerEdge R730 we have the integrated NIC: > > Intel(R) 2P x520/2P l350 rNDC > > > The two 10-Gigabit LWL links get lost und will not come back during the > installation. > > > -- > Gerd Pokorra > > University Siegen > H?lderlinstr. 3 > D-57076 Siegen > Germany > > Phone +49 271 740 4379 > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From pokorra at uni-siegen.de Wed Aug 12 01:46:49 2015 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Wed, 12 Aug 2015 09:46:49 +0200 Subject: [sles-beta] LWL links from Intel NIC get lost during boot In-Reply-To: <21B3C1C5-DC00-43EA-B02A-1E5C962F69FB@suse.com> References: <1439262081.1785.7.camel@uni-siegen.de> <21B3C1C5-DC00-43EA-B02A-1E5C962F69FB@suse.com> Message-ID: <1439365609.1490.17.camel@uni-siegen.de> Am Dienstag, den 11.08.2015, 18:19 +0200 schrieb Vincent Moutoussamy: > Hi, > > I would like to have some details about what happens: > > Were you able to complete the installation ? The installation completed normal. > > Do you see the issue after the installation ? After the installation the behavior is the same. During the boot of the OS the links get lost. I see the two network interfaces as not connected: 82599EB 10-Gigabit SFI/SFP+ Network Connection (Not connected) > Did you see any interesting error messages on the console ? No, there are no error messages displayed. -- Gerd From vmoutoussamy at suse.com Wed Aug 12 02:28:29 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 12 Aug 2015 10:28:29 +0200 Subject: [sles-beta] LWL links from Intel NIC get lost during boot In-Reply-To: <1439365609.1490.17.camel@uni-siegen.de> References: <1439262081.1785.7.camel@uni-siegen.de> <21B3C1C5-DC00-43EA-B02A-1E5C962F69FB@suse.com> <1439365609.1490.17.camel@uni-siegen.de> Message-ID: <18257829-4CC1-47B8-9323-6B7E1E96BE45@suse.com> Hi, hum the DELL PowerEdge R730 is part of our yescertified hardware (certified on SLES11SP3 : https://www.suse.com/nbswebapp/yesBulletin.jsp?bulletinNumber=141865). By any chance, in the past did you installed a SLES 12 GA on this hardware ? I think it is important to investigate a little bit more on that issue. Could you please open a support Service Request for this ? Do not forget to provide a supportconfig and any technical details you have. This will allow us to analyse what?s going on during and after the installation. Regards, PS : the how to report an issue is available on this page https://www.novell.com/beta/auth/beta.jsp?id=5585&type=3 -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 12 Aug 2015, at 09:46, Gerd Pokorra wrote: > > Am Dienstag, den 11.08.2015, 18:19 +0200 schrieb Vincent Moutoussamy: >> Hi, >> >> I would like to have some details about what happens: >> >> Were you able to complete the installation ? > > The installation completed normal. > >> >> Do you see the issue after the installation ? > > After the installation the behavior is the same. During the boot of the > OS the links get lost. I see the two network interfaces as not > connected: > > 82599EB 10-Gigabit SFI/SFP+ Network Connection (Not connected) > >> Did you see any interesting error messages on the console ? > > No, there are no error messages displayed. > > -- Gerd > > . From pokorra at uni-siegen.de Wed Aug 12 07:30:29 2015 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Wed, 12 Aug 2015 15:30:29 +0200 Subject: [sles-beta] LWL links from Intel NIC get lost during boot In-Reply-To: <18257829-4CC1-47B8-9323-6B7E1E96BE45@suse.com> References: <1439262081.1785.7.camel@uni-siegen.de> <21B3C1C5-DC00-43EA-B02A-1E5C962F69FB@suse.com> <1439365609.1490.17.camel@uni-siegen.de> <18257829-4CC1-47B8-9323-6B7E1E96BE45@suse.com> Message-ID: <1439386229.1490.40.camel@uni-siegen.de> Hi, Am Mittwoch, den 12.08.2015, 10:28 +0200 schrieb Vincent Moutoussamy: > Hi, > > hum the DELL PowerEdge R730 is part of our yescertified hardware > (certified on SLES11SP3 : https://www.suse.com/nbswebapp/yesBulletin.jsp?bulletinNumber=141865). > > By any chance, in the past did you installed a SLES 12 GA on this hardware ? by installing SLES 12 GA the issue was the same. I simple execute the command: ifconfig em1 up Suddenly it works. Currently we have running it with bonding and it works like it should so I would like to stop with this issue. slc3:~ # cat /etc/sysconfig/network/ifcfg-bond0 BONDING_MASTER='yes' BONDING_MODULE_OPTS='mode=802.3ad miimon=100 xmit_hash_policy=layer3+4' BONDING_SLAVE0='em1' BONDING_SLAVE1='em2' BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='xx.xx.xx.xx/xx' MTU='' NAME='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' We removed the ifcfg- slave files. My colleague said that he did not change anything at the switch configuration. -- Gerd Pokorra > > > I think it is important to investigate a little bit more on that issue. > Could you please open a support Service Request for this ? > Do not forget to provide a supportconfig and any technical details you have. > This will allow us to analyse what?s going on during and after the installation. > > Regards, > > PS : the how to report an issue is available on this page https://www.novell.com/beta/auth/beta.jsp?id=5585&type=3 > From Janos.Mattyasovszky at bmw.de Wed Aug 12 13:59:05 2015 From: Janos.Mattyasovszky at bmw.de (Janos.Mattyasovszky at bmw.de) Date: Wed, 12 Aug 2015 19:59:05 +0000 Subject: [sles-beta] LWL links from Intel NIC get lost during boot In-Reply-To: <1439386229.1490.40.camel@uni-siegen.de> References: <1439262081.1785.7.camel@uni-siegen.de> <21B3C1C5-DC00-43EA-B02A-1E5C962F69FB@suse.com> <1439365609.1490.17.camel@uni-siegen.de> <18257829-4CC1-47B8-9323-6B7E1E96BE45@suse.com>, <1439386229.1490.40.camel@uni-siegen.de> Message-ID: <095658B76C3A484CB6CC6943F45CD6184238EE@smucm55a> Hi 10G fibre nic works only (= has a link and enables the laser), when the interface is brought up by ifconfig up... Regards Janos Mattyasovszky -- BMW Group Janos Mattyasovszky Linux Solutions Sent from my Windows Phone FG-941 Unix/Linux Server Infrastructure Postanschrift: Bremer Strasse 6 80788 M?nchen Tel: +49-89-382-13280 Mail: janos.mattyasovszky at bmw.de Web: http://www.bmwgroup.com/ -------------------------------------------------------------------- Bayerische Motoren Werke Aktiengesellschaft Board of Management: Harald Kr?ger (Chairman), Milagros Cai?a Carreiro-Andree, Klaus Draeger, Friedrich Eichiner, Klaus Fr?hlich, Ian Robertson, Peter Schwarzenbauer, Oliver Zipse. Chairman of the Supervisory Board: Norbert Reithofer Registered in Germany: M?nchen HRB 42243 -------------------------------------------------------------------- ________________________________ From: Gerd Pokorra Sent: ?12.?08.?2015 15:35 To: Vincent Moutoussamy Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] LWL links from Intel NIC get lost during boot Hi, Am Mittwoch, den 12.08.2015, 10:28 +0200 schrieb Vincent Moutoussamy: > Hi, > > hum the DELL PowerEdge R730 is part of our yescertified hardware > (certified on SLES11SP3 : https://www.suse.com/nbswebapp/yesBulletin.jsp?bulletinNumber=141865). > > By any chance, in the past did you installed a SLES 12 GA on this hardware ? by installing SLES 12 GA the issue was the same. I simple execute the command: ifconfig em1 up Suddenly it works. Currently we have running it with bonding and it works like it should so I would like to stop with this issue. slc3:~ # cat /etc/sysconfig/network/ifcfg-bond0 BONDING_MASTER='yes' BONDING_MODULE_OPTS='mode=802.3ad miimon=100 xmit_hash_policy=layer3+4' BONDING_SLAVE0='em1' BONDING_SLAVE1='em2' BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='xx.xx.xx.xx/xx' MTU='' NAME='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' We removed the ifcfg- slave files. My colleague said that he did not change anything at the switch configuration. -- Gerd Pokorra > > > I think it is important to investigate a little bit more on that issue. > Could you please open a support Service Request for this ? > Do not forget to provide a supportconfig and any technical details you have. > This will allow us to analyse what?s going on during and after the installation. > > Regards, > > PS : the how to report an issue is available on this page https://www.novell.com/beta/auth/beta.jsp?id=5585&type=3 > _______________________________________________ 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 pokorra at uni-siegen.de Wed Aug 12 17:06:43 2015 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Thu, 13 Aug 2015 01:06:43 +0200 Subject: [sles-beta] getting InfiniBand interface working Message-ID: <1439420803.1754.2.camel@uni-siegen.de> The DELL PowerEdge R730 has also an InfiniBand interface from Mellanox. In the past I downloaded and installed OFED to get an InfiniBand interface running. Could you help me to get it running at the Beta release? -- Gerd Pokorra From behlert at suse.com Wed Aug 12 23:36:34 2015 From: behlert at suse.com (Stefan Behlert) Date: Thu, 13 Aug 2015 07:36:34 +0200 Subject: [sles-beta] getting InfiniBand interface working In-Reply-To: <1439420803.1754.2.camel@uni-siegen.de> References: <1439420803.1754.2.camel@uni-siegen.de> Message-ID: <20150813053634.GP21390@suse.de> Moin, On Aug 13, 15 01:06:43 +0200, Gerd Pokorra wrote: > The DELL PowerEdge R730 has also an InfiniBand interface from Mellanox. > > In the past I downloaded and installed OFED to get an InfiniBand > interface running. OFED is part of SLES, so I wonder what you had to download additionally. > Could you help me to get it running at the Beta release? Could you open a service request and add information about the hardware? This way it's easier to get the experts involved, and to distribute the required information to all parties involved. Thanks, Stefan > > -- Gerd Pokorra > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Stefan Behlert, SUSE LINUX Release Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX GmbH, Nuernberg; GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nuernberg) From pokorra at uni-siegen.de Thu Aug 13 02:10:30 2015 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Thu, 13 Aug 2015 10:10:30 +0200 Subject: [sles-beta] getting InfiniBand interface working Message-ID: <1439453430.1492.28.camel@uni-siegen.de> Moin, Am Donnerstag, den 13.08.2015, 07:36 +0200 schrieb Stefan Behlert: > Moin, > > On Aug 13, 15 01:06:43 +0200, Gerd Pokorra wrote: > > The DELL PowerEdge R730 has also an InfiniBand interface from Mellanox. > > > > In the past I downloaded and installed OFED to get an InfiniBand > > interface running. > > OFED is part of SLES, so I wonder what you had to download additionally. cool! I find the packages with zypper and installed them. The InfiniBand interface works with the packages out of the box. Thank you for the information and help Gerd Pokorra > > > Could you help me to get it running at the Beta release? > > Could you open a service request and add information about the hardware? > This way it's easier to get the experts involved, and to distribute the > required information to all parties involved. > > Thanks, > Stefan > > > > -- Gerd Pokorra > > > > _______________________________________________ > > sles-beta mailing list > > sles-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sles-beta > From behlert at suse.com Thu Aug 13 05:42:59 2015 From: behlert at suse.com (Stefan Behlert) Date: Thu, 13 Aug 2015 13:42:59 +0200 Subject: [sles-beta] getting InfiniBand interface working In-Reply-To: <1439453430.1492.28.camel@uni-siegen.de> References: <1439453430.1492.28.camel@uni-siegen.de> Message-ID: <20150813114259.GX21390@suse.de> On Aug 13, 15 10:10:30 +0200, Gerd Pokorra wrote: > Moin, > > Am Donnerstag, den 13.08.2015, 07:36 +0200 schrieb Stefan Behlert: [...] > > cool! I find the packages with zypper and installed them. The InfiniBand > interface works with the packages out of the box. Great, that was easy solved ;) Enjoy it! Stefan > > Thank you for the information and help > Gerd Pokorra -- Stefan Behlert, SUSE LINUX Release Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX GmbH, Nuernberg; GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nuernberg) From pokorra at uni-siegen.de Fri Aug 14 03:22:57 2015 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Fri, 14 Aug 2015 11:22:57 +0200 Subject: [sles-beta] changing default runlevel with systemctl command Message-ID: <1439544177.1484.9.camel@uni-siegen.de> The command 'systemctl set-default multi-user.target' returns without a message to the prompt, but the file link target of /usr/lib/systemd/system/default.target will not change from graphical.target to multi-user.target. Should I open a service request for this issue? # systemctl set-default multi-user.target # ls -l /usr/lib/systemd/system/default.target lrwxrwxrwx 1 root root 16 10. Aug 20:03 /usr/lib/systemd/system/default.target -> graphical.target -- Gerd Pokorra From kukuk at suse.de Fri Aug 14 03:51:44 2015 From: kukuk at suse.de (Thorsten Kukuk) Date: Fri, 14 Aug 2015 11:51:44 +0200 Subject: [sles-beta] changing default runlevel with systemctl command In-Reply-To: <1439544177.1484.9.camel@uni-siegen.de> References: <1439544177.1484.9.camel@uni-siegen.de> Message-ID: <20150814095144.GA19241@suse.de> Hi, On Fri, Aug 14, Gerd Pokorra wrote: > The command 'systemctl set-default multi-user.target' returns without a > message to the prompt, but the file link target > of /usr/lib/systemd/system/default.target will not change from > graphical.target to multi-user.target. If that link changes or not is completly irrelevant. Because you are looking at the wrong place. The question is: if you boot the next time, does the system come up in grpahical.target, or multi-user.target? > Should I open a service request for this issue? Only if the system comes up in graphical.target. 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 aj at suse.com Fri Aug 14 04:18:32 2015 From: aj at suse.com (Andreas Jaeger) Date: Fri, 14 Aug 2015 12:18:32 +0200 Subject: [sles-beta] changing default runlevel with systemctl command In-Reply-To: <1439544177.1484.9.camel@uni-siegen.de> References: <1439544177.1484.9.camel@uni-siegen.de> Message-ID: <55CDC078.7060907@suse.com> On 08/14/2015 11:22 AM, Gerd Pokorra wrote: > The command 'systemctl set-default multi-user.target' returns without a > message to the prompt, but the file link target > of /usr/lib/systemd/system/default.target will not change from > graphical.target to multi-user.target. > > Should I open a service request for this issue? > > # systemctl set-default multi-user.target > # ls -l /usr/lib/systemd/system/default.target > lrwxrwxrwx 1 root root 16 10. Aug > 20:03 /usr/lib/systemd/system/default.target -> graphical.target Run "systemd-delta" to see how your system is different from the freshly installed system. You're also looking at the wrong place, /usr/lib/systemd is read-only, changes are done in /etc/systemd to override /usr/lib/systemd. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From pokorra at uni-siegen.de Fri Aug 14 04:53:16 2015 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Fri, 14 Aug 2015 12:53:16 +0200 Subject: [sles-beta] changing default runlevel with systemctl command In-Reply-To: <20150814095144.GA19241@suse.de> References: <1439544177.1484.9.camel@uni-siegen.de> <20150814095144.GA19241@suse.de> Message-ID: <1439549596.1484.13.camel@uni-siegen.de> You are right. The system boots in runlevel 3. (/etc/systemd/system/default.target is changed.) -- Gerd Am Freitag, den 14.08.2015, 11:51 +0200 schrieb Thorsten Kukuk: > Hi, > > On Fri, Aug 14, Gerd Pokorra wrote: > > > The command 'systemctl set-default multi-user.target' returns without a > > message to the prompt, but the file link target > > of /usr/lib/systemd/system/default.target will not change from > > graphical.target to multi-user.target. > > If that link changes or not is completly irrelevant. > Because you are looking at the wrong place. > > The question is: if you boot the next time, does the > system come up in grpahical.target, or multi-user.target? > > > Should I open a service request for this issue? > > Only if the system comes up in graphical.target. > > Thorsten > From vmoutoussamy at suse.com Fri Aug 14 05:09:03 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Fri, 14 Aug 2015 13:09:03 +0200 Subject: [sles-beta] changing default runlevel with systemctl command In-Reply-To: <55CDC078.7060907@suse.com> References: <1439544177.1484.9.camel@uni-siegen.de> <55CDC078.7060907@suse.com> Message-ID: <3A54DC25-B2D9-4DFE-B7B2-AD8A6B979179@suse.com> Hi, > On 14 Aug 2015, at 12:18, Andreas Jaeger wrote: > > On 08/14/2015 11:22 AM, Gerd Pokorra wrote: >> The command 'systemctl set-default multi-user.target' returns without a >> message to the prompt, but the file link target >> of /usr/lib/systemd/system/default.target will not change from >> graphical.target to multi-user.target. >> >> Should I open a service request for this issue? >> >> # systemctl set-default multi-user.target >> # ls -l /usr/lib/systemd/system/default.target >> lrwxrwxrwx 1 root root 16 10. Aug >> 20:03 /usr/lib/systemd/system/default.target -> graphical.target > > Run "systemd-delta" to see how your system is different from the freshly installed system. > > You're also looking at the wrong place, /usr/lib/systemd is read-only, changes are done in /etc/systemd to override /usr/lib/systemd. To say it differently : "/usr/lib/systemd/system/? is the default configuration at the distribution level, and /etc/systemd/system/ is the configuration for your system. Thus configuration in /etc/systemd/system/ prevails over "/usr/lib/systemd/system/?. This setup (/usr/lib/systemd and /etc/systemd/) allow us to have useful command line like systemd-delta Snippet of systemd-delta man page : systemd-delta may be used to identify and compare configuration files that override other configuration files. Files in /etc have highest priority, files in /run have the second highest priority, ..., files in /lib have lowest priority. Regards, PS : It is easier to use ?# systemctl get-default? than ?# ls -l". -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From mpost at suse.com Sun Aug 16 10:05:20 2015 From: mpost at suse.com (Mark Post) Date: Sun, 16 Aug 2015 10:05:20 -0600 Subject: [sles-beta] sles-beta ; The vmrdr.ikr is missing on s390x DVD In-Reply-To: <8dac095e384e498ca42fe15039a7059b@THHSTE15D2BE5.hs20.net> References: <8dac095e384e498ca42fe15039a7059b@THHSTE15D2BE5.hs20.net> Message-ID: <55D07C800200006D00199ECF@prv-mh.provo.novell.com> >>> On 8/14/2015 at 07:21 AM, David Austin wrote: > Hi > > The vmrdr.ikr bootstrap file is missing from the /boot/s390x directory > > Has this been moved to some other file name? Yes. Starting with SLES12, it was renamed to match all our other architectures: /boot/s390x/linux Mark Post From mpost at suse.com Sun Aug 16 10:10:20 2015 From: mpost at suse.com (Mark Post) Date: Sun, 16 Aug 2015 10:10:20 -0600 Subject: [sles-beta] sles-beta Unable to create respository In-Reply-To: <3dbd982ad6784a04be7be05351f991fd@THHSTE15D2BE5.hs20.net> References: <3dbd982ad6784a04be7be05351f991fd@THHSTE15D2BE5.hs20.net> Message-ID: <55D07DAC0200006D00199ED4@prv-mh.provo.novell.com> >>> On 8/14/2015 at 09:56 AM, David Austin wrote: > After activating dasd and performing network Configuration it's trying to > initialise software manager and create a repo. > > Sorry my VNC viewer won't create a screen shot. Here are the details: > > Unable to create respository > > from URL 'ftp://ftpuser:PASSWORD at 192.168.150.60/%2F/srv/ftp/SU12SP1B' > > Deails: > > [ftp-192.168.150.60-0e80439d|ftp://ftpuser at 192.168.150.60/%2F/srv/ftp/SU12SP1B > ] Valid metadata not found at specified URL > > History: > > - > [ftp-192.168.150.60-0e80439d|ftp://ftpuser at 192.168.150.60/%2F/srv/ftp/SU12SP1B > ] Repository type can't be determined. > > Try Again Yes/NO? > > The URL password is incorrect unless it's just being masked, but looks like > it can't find something it needs. > > Retry Yes, puts up an edit repo window, retry NO aborts installation. Perhaps the easiest way to figure this out is to look at the log files on the FTP server itself. (One of the reasons I prefer using FTP for my installs.) Once you have those then you can see if there's something missing, etc. Mark Post