Bug#252551: other possible tests

[Jack Carroll <dischord@myrealbox.com>]

	I've posted my latest results under the bug number above, and
supplied some additional information requested by Christian Perrier.
	Maybe you can suggest a direction for further tests.
	I noticed that after I booted from the floppies and configured a
network interface, it downloaded a large collection of installer components. 
I selected the "testing" branch.  If I had selected "unstable", would it
have downloaded a more recent version of the installer as well as a more
recent set of packages to install?
	If so, would it help the project if I did that and reported?
	I don't see a place to get daily builds of the floppies themselves,
or I'd give that a go.
	I've been a bit reluctant to burn CDs, for a couple of reasons. 
Libranet has recently started packing more bytes on a CD than machine #1's
older drive can read (not to mention my other older machine, an all-SCSI
486), and I'm not sure but what Debian may have also broken the boundaries
of the generic CD format that all drives can read.  It's also a long job to
download a set of images, and I use up disks each time, because these older
drives don't read CD-RWs.  And I need floppies anyway, because the SCSI CD
drives aren't bootable.  So booting from floppies into a network install is
perfect for my older server boxes.  (At some point, I'll probably read up on
creating a local Debian mirror to cut down on downloading.)
	Obviously, I don't have much of an understanding of the inner
workings of the installer, though I have done a manual network cross-install
under Gentoo on machine #2, and might try a Debian cross-install.
	So what do you think?  What should I test further?