On 5/3/06, Chuck Tuffli <[EMAIL PROTECTED]> wrote:
Unfortunately, DragonFly (and most of the other *BSDs I think) doesn't have a good answer for persistent binding. You can setup the kernel to "wire down" a particular bus/target/lun to a specific device, but I don't think this would work for SANs.
More on the same topic! Here's an excerpt from the linux fstab(5) manpage: --- snip --- Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label (cf. e2label(8) or xfs_admin(8)), writing LABEL=<label> or UUID=<uuid>, e.g., `LABEL=Boot' or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. This will make the system more robust: adding or removing a SCSI disk changes the disk device name but not the filesystem volume label. --- snip --- Wonder if something like this would make sense for DragonFly? Cheers, K.