Hans Ekbrand wrote:
> Dear list!

Hi,

> Parallel mksquashfs: Using 1 processor
> Creating little endian 3.1 filesystem on filesystem.squashfs, block size 
> 131072.
> [=======                                                                      
>                 ]  6183/72751   8%/usr/share/live-helper/functions/chroot.sh: 
> line 13: 11939 Killed                  ${LH_ROOT_COMMAND} chroot chroot 
> /usr/bin/env -i HOME="/root" 
> PATH="/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin" 
> TERM="${TERM}" ftp_proxy="${LH_APT_FTP_PROXY}" 
> http_proxy="${LH_APT_HTTP_PROXY}" DEBIAN_FRONTEND="${LH_DEBCONF_FRONTEND}" 
> DEBIAN_PRIORITY="${LH_DEBCONF_PRIORITY}" 
> DEBCONF_NOWARNINGS="${LH_DEBCONF_NOWARNINGS}" XORG_CONFIG="custom" ${COMMANDS}
> # 
> 
> This box has not much RAM (40 MB) and a swap partition of 100MB, might
> that be why the process was killed?

yep; welcome to oomkiller :)

> Suppose I increase the swap available to the OS, can I then retry only
> the last step (the step that failed above), or do I have to restart
> the lh_build process from the beginning?

if you are lazy, then do 'lh_clean --binary && lh_binary' will do the trick.

if you want to it 'by hand' and know what you do, you can open lh_binary
in an editor and execute each and every helper listed there, starting
(and including) from lh_binary_rootfs.

I personally wouldn't do this, since the whole thing is pretty fragile
regarding interruptions, and therefore I would just clean the whole
binary stage and redo that one from scratch (but I also have a bit
faster machines than you, so..).

Regards,
Daniel

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          [EMAIL PROTECTED]
Internet:       http://people.panthera-systems.net/~daniel-baumann/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to