On Sun, Sep 7, 2008 at 10:53 AM, David Brown <[EMAIL PROTECTED]> wrote:
>
> SYSLINUX should boot from any of them. As long as there is a FAT
> filesystem available, and BIOS calls to read the data. I haven't
> found a machine yet that tried to boot USB that wouldn't boot it.
>
> That's only part of the problem, though. SYSLINUX will load the
> kernel and initrd. The next step is figuring out how to the
> distribution to be able to find the USB device instead of a CDROM.
> You could use ISOLINUX, but as you say not all BIOS's will boot from a
> USB drive that has a CD image on it, since some treat it as a Zip
> drive or a HD.
>
> I still don't understand why this tool wants to hack your bootloader?
> mkusb.sh (part of RIP Linux) is just a shell script. It has to be run
> as root to get access to the device node for the USB drive, but it
> otherwise just runs ordinary utilities.
>
>
> <http://ftp.cvut.cz/mirrors/rip/www.tux.org/pub/people/kent-robotti/looplinux/rip/>
>
> The 'mkusb.sh' script is down a ways on the page.
>
Without looking into it extensively, I find that 'mkusb.sh' is
specialized to loading a CD image that is laid out the way that
RIPLinuX.iso is. i.e. all files in directory /boot, and a Linux
kernel named /boot/kernel. If it doesn't find this it quits.
I will look at it some more to see if it can be generalized.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
