On Mon, Apr 29, 2002 at 07:56:09AM -0700, Matt Kraai wrote: > I've fixed this. Does this also need to be done for > parmfile.example1:
Please undo your changes. Attaching the DASD 191 and 192 will confuse dboostrap because these are typically CMS disks on VM systems which can't be read by Linux. If you then select "partition a hard disk" dboostrap will ask you to low-level format your DASDs which will cause data loss! I'm not use it a valid range (say just 0001) will work. It might cause trouble if this device is not a DASD at all so we decided to use an invalid range and let the kernel just probe the DASDs without attaching them. Sorry, I didn't find time to read the s390-specific bug reports earlier. I think this is documented somewhere that you should use an invalid DASD range. Anyhow, this parmfile is only used during the installation process - a new one with a correct DASD range is created for the installed system. -- Stefan Gybas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
