1) Can the system boot from a USB device?
Yes. I'm attempting to modify an existing process. Right now we have to send the flash media to our Pittsburgh location to have them loaded. We want to do this here in SC. The systems we're booting will boot from flash media already; we're just changing the location of the flash drive configuration.
2) Does the flash drive support running software?
The flash media will be used as a component of a product we produce. It's the same make and model we send to PA.
The are about three differences between the way PA does it and the way I want to do it. First, they do it booting from a Knoppix Live CD. I want to boot from the hard drive but Knoppix' web site recommended against installing Knoppix as bootable on an HD. They recommended Debian so that's what I'm using. Why don't I go with a flash-specific distro? The product is part of a railroad safety system, and I'm not able to tell if the differences between distributions could cause a (potentially life-threatening) problem.
Second, PA says they type the commands in manually. At this end the work will be done by factory floor employees with minimal typing skills. Expecting them to type will be a demo in user frustration. I want to put all the commands in one file and have them run it from a GUI shortcut.
Third, apparently the Knoppix box in PA refers to the flash drive as /dev/hde. I believe it's a laptop with built-in flash media slots; maybe those slots aren't SCSI.
As I understand it after I chroot I've set the file system on the flash drive as my root and I'm seeing it's directory structure; how can I still refer to it as /dev/sda when that's now the root? I've changed /hde to /sda for every other command and reference in the procedure, but it makes no difference in lilo.conf. Whether I use /dev/hde or /dev/sda, I still get:
Reading boot sector from /dev/xxx
Fatal: open /dev/xxx: No such device or address
If I
NAME:~# chroot /mnt/sda1
NAME:/# cd /dev
NAME:/# ls hde*
NAME:/# ls sda*
I get listing for hde and partitions hde1 to 16. I get no listings for sda, so that at least explains why that doesn't work in the lilo.conf, but I don't know why lilo reports "No such device" when /hde is clearly there.
Maybe the word 'Reading' in the error message is what's confusing me, but that makes me think lilo is trying to /dev/hde as a source. Since /hde has a size of zero, I'm unsure what is to be read from it.
Fortunately, this is the last step in the process. If I can lick this one I'll have something I can had to the product test lab and have them see if it works.