Code: Select all

***
Sidux has a very well documented page about installation of sidux on a USB-device:
http://manual.sidux.com/en/hd-install-opts-en.htm
***

The archive contains the iso2usb.sh script for antiX, and a copy of the original
sidux script: fll-iso2usb.sh

To run the script (iso2usb.sh):

On your everyday system (I use Mepis-M8), where you have already downloaded an antiX
iso file, say antiX-M8-public-test1.iso (other versions should work):

Run the script, as root:

======================================================================
# ./iso2usb.sh -I ~/My-Downloads/antiX-M8-public-test1.iso -D /dev/sdc
======================================================================

of course you will change the device arg name /dev/sdc to the device name under 
which **your** device appears.
 
You may want to use the option -d (--debug) to collect some more information on 
what happens. The -x option traces also shell commands execution (set -x).
A log file is written under /tmp/iso2usb.log

Tested:
=======
1) The script, run from Mepis-8, writes correctly the USB device.
My target system (eeePC 701) boots correctly from the USB-thumb.

If you list the content of the USB key, after mounting it, you should have:
<<<============================================================================
# ls -R /media/antiXUSB
/media/antiXUSB:
antiX-M8-rc2.iso  boot  boot.catalog  cdrom.ico  lost+found  version

/media/antiXUSB-1/boot:
grub  initrd.gz  memtest  vmlinuz

/media/antiXUSB-1/boot/grub:
default     e2fs_stage1_5  iso9660_stage1_5  menu.lst  minix_stage1_5     stage1  xfs_stage1_5
device.map  fat_stage1_5   jfs_stage1_5      message   reiserfs_stage1_5  stage2

/media/antiXUSB-1/lost+found:
>>>============================================================================

...and for menu.lst:
<<<============================================================================
# cat /media/antiXUSB-1/boot/grub/menu.lst
default 0
timeout 10
color cyan/blue white/blue
foreground ffffff
background 003f7d
gfxmenu /boot/grub/message

##ISO boot
title antiX (LiveUSB)
kernel /boot/vmlinuz nosplash vga=791 fromhd=UUID=4b081ee3-8d07-483a-8ca2-f73e0c595ad6 fromiso=antiX-M8-rc2.iso aufs
initrd /boot/initrd.gz

title antiX-memtest (test system memory)
kernel /boot/memtest

>>>============================================================================

Note:
I think the"fromhd=UUID=the-uuid-of-your-device" is not supported as a valid 
kernel line option: when booting from the live-USB, a long list of devices are 
scanned (maybe devices fetched in /sys/blocks ?) before the iso file is found in 
/dev/sdX1 partition. It is not really time consuming, but gives a ugly output.

2) Also tested:
From the live-USB I got, after transferring the script, run the command:

==========================
# ./iso2usb.sh -D /dev/sdx
==========================

...without giving the name of the iso you booted on
(really you may ask what it is worth, since you already got it...)
you get a second antiX"fromiso" USB-thumb drive

To test:
========
1) run the script from a live antiX CDrom
2) test the additional option to the command line, appened to the kernel line
in menu.lst
3) test the -n --noformat option for installing on an already formatted bootable
   partition
My todo list:
=============
1) add an option vga=xxxx that will supersede the default
2) add a second menu.lst entry for booting in quiet mode
3) build a second partition ext2, ext3 or vfat on the space left, and give the
   size of the install partition as argument of the command line
4) write a GUI 

Bug reports, suggestions are warmly welcome

Yves