Bug#2816: boot-floppies have some small glitches

[Chris Fearnley <cjf@netaxs.com>]

Package: boot-floppies
Version: 1.1.1-3

I had to add the line to basedisks.sh:
  chroot $B /etc/init.d/sysklogd stop
before the line to umount /proc.

rootdisks.sh fails:
# Zero the entire disk, so that when I compress the raw disk image,
# unused blocks will compress well.
dd if=/dev/zero of=$floppy bs=1k count=${blocks}
dd: /dev/fd0: No such device

I needed to add the line to rootdisks.sh to fix it:
  (modprobe floppy; exit 0)
so that the dd command would work.  Is this a kernel bug that the
device isn't immediately ready (kerneld doesn't honor the request that
loaded the module)?

[Actually, I need to run depmod -a to get it loaded.  modprobe complained:
"No dependancy information for module /lib/modules/current/block/floppy.o"]

Finally, since I ran ./makdisks.sh so often, I learned that the
base_floppies are appended to when the script is rerun.  I think it
would be best to test if there are any 1[24][04]0_base_floppies-?
files around and remove them rather than building 2.8 Meg floppy
images :)

--
Christopher J. Fearnley            |    Linux/Internet Consulting
cjf@netaxs.com                     |    UNIX SIG Leader at PACS
http://www.netaxs.com/~cjf         |    (Philadelphia Area Computer Society)
ftp://ftp.netaxs.com/people/cjf    |    Design Science Revolutionary
"Dare to be Naive" -- Bucky Fuller |    Explorer in Universe