Fwd: Error when running ./build.sh

Fwd: Error when running ./build.sh

[Derek Johansen]

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

Additional info: (Note that when I do a sudo ./build.sh clean the
/dev/loop0 filesystem listed below is removed.)
:
Build script has terminated with error 8
djohanse@djohanse-VirtualBox:~/elk2/elks$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        61G   42G   17G  72% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            1.1G  4.0K  1.1G   1% /dev
tmpfs           213M  1.1M  212M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            1.1G  156K  1.1G   1% /run/shm
none            100M   36K  100M   1% /run/user
ELKS            456G  196G  260G  44% /media/sf_ELKS
/dev/loop0      1.2M  1.2M  3.0K 100% /mnt/elks

Re: Fwd: Error when running ./build.sh

[Jody Bruchon]

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.

Re: Error when running ./build.sh

[Georg Potthast]

I always use the full3 target and have not tested any different target. So 
"sudo make full3" in elkscmd works. You may have to change the owner of the 
resulting full3 file to use that with qemu.

Georg

-----Ursprüngliche Nachricht----- 
From: Jody Bruchon
Sent: Monday, February 27, 2017 7:42 AM
To: Derek Johansen ; linux-8086@vger.kernel.org
Subject: Re: Fwd: Error when running ./build.sh

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html 

Re: Fwd: Error when running ./build.sh

[Marc-François LUCCA-DANIAU]

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@jodybruchon.com>:
> 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html