On Tue, Apr 24, 2001 at 09:15:03AM -0700, Hisashi T Fujinaka wrote:
> Aha! Thanks. This just got me to the NEXT problem (the reason vnd0d was
> assigned before). Do I need to make the ramdisk bigger or have I hosed
> something else up?
> 
> SPECIAL gzip -9 -c ${CURDIR}/../../../../etc/etc.i386/MAKEDEV > MAKEDEV.gz
> COPY    ${DESTDIR}/usr/mdec/biosboot.sym        usr/mdec/biosboot.sym
> COPY    ${DESTDIR}/usr/mdec/mbr                 usr/mdec/mbr
> COPY    ${DESTDIR}/usr/mdec/mbr_bootsel         usr/mdec/mbr_bootsel
> COPY    ${CURDIR}/termcap.mini          usr/share/misc/termcap
> SPECIAL sh ${CURDIR}/../../../../distrib/sets/makeobsolete -b -s
> ${CURDIR}/../../../../distrib/sets -t ./dist
> 
> /mnt: write failed, file system is full

Neat. This means that some one of the floppies (which one were you
in the middle of? Is this i386 or something else?) has grown too
large to fit in a floppy. (This recently happened with the macppc
port... We haven't fixed it the ideal way there, which would be to
split the boot floppy there into several, but there are some
OpenFirmware considerations.)

Increasing the size of the vnd would mask the problem, but the
produced image wouldn't fit on a floppy.

Erm, unless I'm confused and that's not actually from the middle of
a floppy build, but rather a dosboot build. (In which case, you may
still be screwed--or, rather, some renovation needs to be done to
make dosboot fit again--presuming that there's some silly size limit
on that too.)

       ~ g r @ eclipsed.net