Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
Bootable USB stick with G4L Oct 23rd, 2008, 10:54am I figured this might be usefull for some, this can be done in windows or linux
- I asume we have an empty usb stick, if not, we need about 55mb - I asume under windows the usb stick is drive F: - I asume under linux the usb stick is sdd1 - If your usb stick is another drive or device then adjust the guide below
- insert your usb stick - make a directory "boot" on the usb stick
- extract all the files from downloaded G4L ISO and place them into the "boot" directory on the usb stick: --- windows user can d/l and use http://www.magiciso.com/ to do this --- linux users simply mount the iso using mount -o loop g4l-v0.27.iso iso and cp the files over - in the "boot" directory delete syslinux.cfg - in the "boot" directory rename isolinux.cfg to syslinux.cfg - from the "boot" directory copy syslinux.cfg to the root of the usb stick (F: or /) - edit syslinux.cfg in the root directory, you now need to add "boot/" before each line that points to a file: --- DEFAULT vesamenu.c32 to DEFAULT boot/vesamenu.c32 --- MENU BACKGROUND test.png to MENU BACKGROUND boot/test.png --- KERNEL bzImage6 to KERNEL boot/bzImage6 --- APPEND initrd=ramdisk.gz.... to APPEND initrd=boot/ramdisk.gz.... ------- do this for all KERNEL lines and all APPEND lines just add boot/ dont change what is there already, till you reach the last line --- ONTIMEOUT bz26.5 and change that to ONTIMEOUT boot/bz26.5
- extract the syslinux-X.XX.zip you downloaded - windows users go into the win32 directory of the extracted file --- do syslinux.exe -m -a -d /boot F: - linux users go into the linux directory of the extraced file --- do ./syslinux /dev/sdd1
and that is it, you now have a bootable USB stick with G4L on it, and with todays huge sticks and usb drives you got it all in one, bootup with it and backup to it or restore from it.
note: If you rather not edit the syslinux.cfg then instead of making a "boot" directory, simply put everything in the root, but this way its a bit cleaner.
Printable version
