Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Sat, Apr 27, 2002 at 05:55:43PM +0200, Jochen Hein wrote:
> dasd=192-191 ro
This was done on purpose. When the DASD range in invalid the kernel
just scans all DASD without attaching any of them. dbootstrap on s390
first asks the user to attach a DASD and uses the list the kernel
generated when it found an invalid DASD range.
If you use a valid range the kernel will attach the devices in this
range, in some cases even if they are not DASDs. So specifying a valid
range can cause all kind of trouble from attached CMS disks (191 is
typically a CMS disk on VM) to macine lockups while trying to scan
the devices at the specified range.
> Oh, and wouldn't it be nice to have a TDF file too? Something like:
The TDF file is on the CD, see the debian-cd package for the source of
the TDF files.
--
Stefan Gybas
--
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: