2017-04-13 Linux on z Systems - Kernel 4.10 related updates on developerWorks

Please refer to http://www.ibm.com/developerworks/linux/linux390/whatsnew.html for several updates to the 'Development stream': * description of upstream kernel 4.10 features that were contributed by Linux on z Systems development * kernel 4.10 patch for kernel message catalog * updated

Re: Anomaly of EDEV mdisk attachment in SLES12

On 12.04.2017 20:54, juha.vu...@pp2.inet.fi wrote: Trying to add fba mdisk from EDEVICE to sles12.2 guest, and dasd_fba driver does not create the full partition node, /dev/dasdh1, for it for some reason: zlnx030:~ # vmcp link '*' 305 a305 mr zlnx030:~ # chccwdev -e a305 Setting device

Re: [IBMVM] Linux on Z, RHEL 7.2 Bonding Problem

On Wednesday, 04/12/2017 at 10:38 GMT, canzon...@verizon.net wrote: > Hi Mark, > Thank you. I want both slaves active at the same time. The testing is done dropping link2 so that > the link2 pick it up. And, when that link1 is bought up and drop link2. > > I would appreciate if you can give

Re: Anomaly of EDEV mdisk attachment in SLES12

On Thursday, 04/13/2017 at 11:05 GMT, Stefan Haberland wrote: > So you always have to take care if you recycle previously used disks. One of the tenets of a secure system is the idea that you do not leave residual data on a device that has been removed from a server.

Re: Anomaly of EDEV mdisk attachment in SLES12

On 13.04.2017 14:03, Stefan Haberland wrote: You have to mention that the partition detection process is - independent of the disk type - a hierarchical process. Those partition detection parts high in the hierarchy are asked first if they would like to try and possibly take the disk as theirs.

Re: Anomaly of EDEV mdisk attachment in SLES12

On 13.04.2017 17:43, Alan Altmark wrote: One of the tenets of a secure system is the idea that you do not leave residual data on a device that has been removed from a server. It should be formatted immediately after de-provisioning, prior to placing in the 'available' pool. The primary