If I install cauldron to a USB stick on a machine that has an internal HD, diskdrake correctly identifies the internal drive as sda and the stick as sdb.  However, the part of the install that creates the bootloader writes the GRUB menu.lst and install.sh with the "hd0" device in spite of the fact that I select "/dev/sdb" in drakboot during Summary.

The resulting system won't boot, as GRUB goes looking on the internal HD rather than the stick.

If you manually change the menu.lst and install.sh to use "hd1" in a rescue boot with a chroot to the USB stick /dev/sdb1, install.sh fails when run because the rescue environment disk number assignment doesn't match the eventual runtime environment.  However, with the source changes alone, the system installed on the stick will now boot fine.

The obvious solution is to use "hd1" in GRUB if the boot sector is being written on /dev/sdb(X), but the above introduces some doubt that the resulting install.sh will run correctly.  I'm not sure if GRUB has a "do as I say don't do as I do" option that would make this work.

I imagine this isn't specific to a USB stick, but would occur with multiple HDDs as well.