Yes, probable, the flopy images were already at the limit, so we will perform a little cleanup. Could you open an issue on Github, please, for this problem to be tracked ? MFLD 2017-02-27 7:42 GMT+01:00 Jody Bruchon <jody@xxxxxxxxxxxxxxx>: > On 2017-02-27 1:35 AM, Derek Johansen wrote: >> >> After pulling in the ethernet updates I try to run >> >> sudo ./build.sh >> >> and get the following error: >> >> for DEL in sbin/partype sbin/ramdisk bin/clock; do rm /mnt/elks/$DEL; >> done || true >> [ "yes" = "yes" ] && \ >> cp -p /home/djohanse/elk2/elks/elkscmd/ktcp/ktcp /mnt/elks/bin || true >> mkdir -p /mnt/elks/boot >> cp /home/djohanse/elk2/elks/elks/arch/i86/boot/Image /mnt/elks/boot/linux >> cp: error writing ‘/mnt/elks/boot/linux’: No space left on device >> cp: failed to extend ‘/mnt/elks/boot/linux’: No space left on device >> make[1]: *** [_build_bootable_target] Error 1 >> make[1]: Leaving directory `/home/djohanse/elk2/elks/elkscmd' >> make: *** [full5] Error 2 >> Build script has terminated with error 8 > > full5 is the 1.2M floppy image. Chances are that something in elkscmd will > need to be dropped from it to make it work in the default configuration. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-8086" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
