[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#66030: tries to read past end of driver-3.bin

	Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de> writes:

	> When installing Debian, the installation of the Driver disks reads past
	> the end of drivers-3.bin (that probably what tar/gzip allways try)
	> Normaly that wont be a problem, since a real floppy will have some spam
	> after the driver-3.bin, but when using the files via loopback or in an
	> emulator that results in an IO error and you are questioned to try the
	> disk again.

It was a problem to me ;) (using an external floppy of an IBM ThinkPad 560
laptop). Driver-1.bin and driver-2.bin were loaded without problem, but
at the end of driver-3.bin I got an error which caused me not to have any
modules available... After a few tries with some different diskettes, I
took a different approach and instead of using these images:


Y tried with theses ones:


The funny part was that diff said that both sources of driver-3.bin were
identical, although the one from above did not work...
If you take a look at the dates, the images that did not work were of
June 07, and the ones that worked were of June 10.

	> An aditional few blocks should be added to the drivers-3.bin, for example by:
	> dd if=/dev/zero bs=1k count=100 | cat >>driver-3.bin 
	> That resolves the problem and makes Debian installable under VMware.

	I agree we should pad these files out.  There is a more robust way to
	do it.  We already do that for the other images -- see the bottom of
	rescue.sh, the dd ... conv=notrunc stuff.

	Any objections to making this change?

Not from me. It's annoying to get such an error and I am sure it will cause
newbies not to install if they begin getting such difficulties...

Regards, Alvaro

Reply to: