Slax author's Blog (RSS)

Suggestions:
_ Use MENU HELP entry and F1 entry for basic help instructions for Syslinux (for both boot prompt and menu usage).

_ Use MENU AUTOBOOT Press ESC for options or boot SLAX in # second{,s}

_ Until it is completely tested, please use dates in released filenames if possible, such as:

slax-7.0-core-i486-20120924.iso (YYYYMMDD)

md5 checked OK.
Tested slax-7.0-core-i486.iso in VBox VM. Error while booting (for any selected boot options):
...
...
...
Live Kit done, starting Slax
sh: can't execute 'usr/bin/chroot': Exec format error

Same error as seen by Ady for me too while running on virtualbox.

Jason

Hi Tomas, I think I know the problem, your chroot is 64 bit in the 32 bit iso!

bin/chroot: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, stripped

Ah yes! I'm sorry for this. Thank you very much for reporting. I misplaced 64bit squashfs data (core.sq) for 32bit version. I've uploaded new ISOs now and updated the blog post links. Please redownload. Thank you

A suggestion: warn user if there is not enough free memory for copying data to RAM.

An example script to do this:
local DM_SIZE FREE_MEM
DM_SIZE=$(du -sm "$DM" | cut -f1)
FREE_MEM=$(free -m | awk '(FNR==3){print $4}')
[ $DM_SIZE -gt $((FREE_MEM - 64)) ] && \
header "Warning: possibly not enough free memory for 'toram' option!" >&2

Thank you very much for suggestion, will do it.

Suggestion:
In HOWTOUSE.TXT, replace the current instruction
extlinux -d /slax/boot /dev/sdb1
with:
syslinux --directory /slax/boot --install /dev/sdb1

which is the appropriate one for unmounted filesystems for Syslinux 4+ (EXTLINUX is for mounted fs).

That's in addition to the suggestions (posted above) for syslinux.cfg:

MENU AUTOBOOT Press ESC for options or boot SLAX in # second{,s}
# Above this is just one line (the blog may show it in 2)
F1 /slax/boot/help.txt
LABEL Help
MENU HELP /slax/boot/help.txt

Thank you, HOWTOUSE.TXT updated. I'm considering F1 help for syslinux but currently I don't have any help.txt file, thus it needs to be written first ;)

un win7 64bit> virtualbox>
kernel panic>
some proces try to access harwdare directlz and stop to boot live