NASLite-2/M2 uses a compact, read-only root filesystem that boots from a small FAT boot partition and runs in ramdisk. It cannot be written to so a persistent config must be available elsewhere. In other words, the boot and config devices don't have to be the same and often cannot be the same. Example of that would be booting from CD
When NASlite-2/M2 boots, it no longer cares which drive is the boot drive. Is simply begins scanning available resources for a config and loads the first it finds. Under normal circumstances, the only config will be found on the boot drive. By having multiple drives with NASLite installed on them, then it's up to your BIOS to boot the one it deems bootable and then up to our kernel to determine which device to scan first for config. They don't always agree and that is what causes confusion for people when they install on a number of devices in the chain and loose track of what boots and what configures.
This capability may seem haphazard to the novice, but once you master it you'll find that it can be quite powerful indeed. You can boot on just about anything-x86 using anything USB, FireWire, SATA/PATA, SCSI, RAID, CD/DVD, etc. as allowed by your BIOS. You can also configure to any of the above or a floppy. In addition, you can have different configurations that you can "plug in" as required using floppy or USB key for various conditions or locations you may need to accommodate. Point here is that the NASLite-2/M2 installer is flexible enough to accommodate just about any boot/config scenario if applied properly
Hopefully the above makes sense.
Now to address yous suggestion:
tony a wrote:
I suggest that it be fixed so it does work, no matter how many drives are in the system.
The installer will install the boot and config on the drive you target NO MATTER WHAT, regardless of how many drives you have attached at the time. I'm not sure what it is that you suggest we fix.