Bug#666399: s390-dasd fails to work with >20 devices visible (mostly in LPAR mode)

[Hendrik Brueckner <brueckner@linux.vnet.ibm.com>]

On Sun, Feb 14, 2016 at 05:46:39PM +0100, Philipp Kern wrote:
> On Wed, Dec 16, 2015 at 02:15:10PM +0100, Hendrik Brueckner wrote:
> > Honestly, I would propose a different approach to limit the DASD device
> > available to the Debian installer.   I believe that typical customer
> > environments have set up their LPARs (and z/VM guest virtual machines)
> > to limit the number of devices to those required/designated for the LPAR.
> > 
> > Of course, there can be the case where LPARs almost have access to (almost)
> > every device.  For this case, the solution is to use "cio_ignore" kernel
> > parameter.  With this kernel parameter you can control the devices that
> > are visible to the Linux instance.
> > 
> > For example,
> > 
> > 	cio_ignore=all,!ipldev,!condev,!0.0.da00-0.0.da10
> > 
> > ignores all devices except the console device, the IPL device, and the
> > range of devices from 0.0.da00 to 0.0.da10 that might be DASDs or any
> > other devices.  Note that you can change the cio_ignore settings at runtime,
> > so you can later make additional devices visible.
> > 
> > With this solution, there is no hardcoded limit necessary and the user
> > can still see the list of DASDs to be configured.
> > 
> > What do you think?
> 
> it'd be nice to see that in the installation manual, I think, so that
> it's at least documented.

How are installation manual changes are handled?

Thanks and kind regards,
  Hendrik