Padding drivers disks
Hi,
it occurred to me that there is a problem with padding of our drivers
disk images.
The uploaded drivers images are not zero-padded:
auric!joey(pts/23):/org/ftp-master.debian.org/ftp/dists/proposed-updates> l disks-i386/2.2.22-2001-04-09/images-1.44/driv*
-rw-rw-r-- 1 troup debadmin 1474560 Apr 2 13:25 disks-i386/2.2.22-2001-04-09/images-1.44/driver-1.bin
-rw-rw-r-- 1 troup debadmin 1474560 Apr 2 13:25 disks-i386/2.2.22-2001-04-09/images-1.44/driver-2.bin
-rw-rw-r-- 1 troup debadmin 1474560 Apr 2 13:25 disks-i386/2.2.22-2001-04-09/images-1.44/driver-3.bin
-rw-rw-r-- 1 troup debadmin 689152 Apr 2 13:25 disks-i386/2.2.22-2001-04-09/images-1.44/driver-4.bin
However, when I create new images they will be:
klecker!joey(pts/6):~/tmp/boot-floppies> l drv*
[..]
-rw-r--r-- 1 root root 1474560 Apr 15 05:32 drv14-1.bin
-rw-r--r-- 1 root root 1474560 Apr 15 05:32 drv14-2.bin
-rw-r--r-- 1 root root 1474560 Apr 15 05:32 drv14-3.bin
-rw-r--r-- 1 root root 1474560 Apr 15 05:32 drv14-4.bin
I've checked driverdisks.sh:
info "splitting drivers into floppy-sized chunks"
case $arch in
i386)
if [ -z "$revext" ] ; then
./utilities/floppy_split $outfile drv12$revext 1200
pad_last_image drv12$revext 1200
fi
./utilities/floppy_split $outfile drv14$revext 1440
pad_last_image drv14$revext 1440
;;
pad_last_image () is from common.sh.
Adam, do you have an explanation for that? Can you check the cvs status
of your driverdisks.sh and common.sh?
Regards,
Joey
--
GNU GPL: "The source will be with you... always."
Reply to: