Hi Philipp, Alexander (on CC) just reported ran into the same issue. His system has more than 20 DASDs and the dialog continues to show up. The <Go Back> triggers the special debconf return code and the "hardware-detection" dependency for this module is not satisfied. This reported when starting the partitioner. On Wed, Apr 04, 2012 at 10:16:24AM +0200, Philipp Kern wrote: > On Wed, Apr 04, 2012 at 09:32:50AM +0200, Bastian Blank wrote: > > On Fri, Mar 30, 2012 at 02:52:58PM +0200, Philipp Kern wrote: > > > I'm not sure about the rationale for this. > > s390 system can have hundreds or thousands of DASD devices. With the > > text frontend it is simply impossible to display such a long list, with I agree that the list of DASDs can be large. > > slang it is just not pretty. So this code should ask for the device id > > instead of showing a list. The dialog to enter the DASD makes sense... in the current implementation you will not get out of it with having the "hardware-detection" dependency fulfilled. The other side effect is that you will never see a list of DASDs which are currently online and configured. Of course, you would see them later in the partitioner. > > Aye. Text is indeed a good reason. As for the dialog interface you get via > the SSH installer I found it to be acceptable with two hundred devices. > > So the device ID picker should get an option to Finish. Can such a text input > field get an additional way out than Go Back and Ok? I do not think that another button is possible. One solution would be to literally enter "Finish" or something similar to complete the DASD module. 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? P.S. For the FCP configuration module, I documented this approach already in the README file. Thanks and kind regards, Hendrik
Attachment:
pgpTl6VW84Qtc.pgp
Description: PGP signature