Re: SLES12 - yast does not create a udev rule

>>> On 11/10/2015 at 08:08 AM, "Davis, Larry (National VM Capability)" wrote: > I have the same problem with Network and DASD devices that I add, I am not > sure of the proper procedure but I had to add the network device to the Rules > files in >

Re: SLES12 - yast does not create a udev rule

That may be true, like I have said I am not an expert but until I did that I would have to manually activate the network device each time Linux was booted. Larry Davis, VM Capability -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post

Re: SLES12 - yast does not create a udev rule

>>> On 11/10/2015 at 04:57 AM, Christer Solskogen wrote: > Hi! > > I've setup the network in YaST, but the device does not start > automagicly when I reboot the machine (running as a guest in z/VM). I > was pretty sure that YaST would create a file under

Forbes article about Spark on z

Sigh. Hard to know where to start with how much they got wrong-well, I suppose I'd start with the name of the platform; I understand that the various rebrandings caused some confusion; but making up a name isn't even close. It also never mentions whether this is for z/OS or Linux on z or what,

Re: Forbes article about Spark on z

Here is a video of the LinuxOne Spark demo from LinuxCon earlier this year: https://www.youtube.com/watch?v=VWBNoIwGEjo Kurt Acker IBM Smarter Planet, Smarter Data Centers Virtualization and Enterprise System Management Technologies From: Mark Post To:

Re: Forbes article about Spark on z

>>> On 11/10/2015 at 04:34 PM, Phil Smith wrote: > It also never mentions whether this is for z/OS or Linux on z or what, which > kind of matters. It only matters to people who know the difference. When IBM was making a lot of noise about LinuxONE recently, they talked

SLES12 - yast does not create a udev rule

Hi! I've setup the network in YaST, but the device does not start automagicly when I reboot the machine (running as a guest in z/VM). I was pretty sure that YaST would create a file under /etc/udev/rules.d called 51-qeth-0.0.0603.rules (or something) - the address is 603,604 and 605. I can get

Re: Forbes article about Spark on z

On 11/11/2015 6:35 AM, Mark Post wrote: On 11/10/2015 at 04:34 PM, Phil Smith wrote: It also never mentions whether this is for z/OS or Linux on z or what, which kind of matters. It only matters to people who know the difference. When IBM was making a lot of noise about

Redbook draft: "Getting Started with KVM for IBM z Systems"

This draft 'gives a broad explanation of KVM for IBM z™ Systems and how it exploits the architecture of IBM z Systems" See http://www.redbooks.ibm.com/redpieces/abstracts/sg248332.html?Open -Mike MacIsaac -- For LINUX-390

Re: SLES12 - yast does not create a udev rule

I have the same problem with Network and DASD devices that I add, I am not sure of the proper procedure but I had to add the network device to the Rules files in /etc/udev/rules.d/70-persistent-net.rules I have also had to add rules for each new DASD device so it is available after an

Re: SLES12 - yast does not create a udev rule

Larry, Check out https://www.mail-archive.com/linux-390@vm.marist.edu/msg66460.html. I found this issue when I was initially testing SLES 12 (still haven't implemented SLES 12 in production). Your new devices may need to be added to the cio_ignore file. Harley -Original Message-