On 01/30/2012 11:10 AM, Wesley M. wrote:
Hi,
I have a question, i read faq "14 - Disk Setup (DiskLabel Unique
Identifiers) ".
It is a pretty feature. We can start OpenBSD OS from the
disk put anywhere(order).
But what's about after a dump/restore
Boot in
single user : backup the disk using 'dump -0af /mnt/root.dump /dev/wd0a'
...
How to restore a disk using DUID ? keeping duid in
/etc/fstab ?
Thank you very much.
Cheers,
Wesley.
So, you want to restore a disk and magically have the duid of the new
disk assume the old disk's value? I think you haven't thought this
through. _You_ want to replace your existing disk, fine, it might be
reasonable to have the same DUID magically restored to the replacement
disk...
But...what if that's not what you are doing? Maybe you want to use
dump/restore to copy data to another part of your existing system?
Maybe after you upgrade to your bigger disk, you want to put the old
disk back on the same system...
*DUID = Disklabel Unique I Dentifier.*
if you do something where you change the DUID of a disk to make it
convenient for you, it's no longer... (all together now, class) "UNIQUE!"
If you are using DUIDs and you change your disk, you will be changing
the fstab. That's how it works, that's how things stay...unique. This
is not only a feature, not a bug, it is THE WHOLE IDEA.
Note: there are a lot of places where DUIDs may be LESS convenient than
simple device names. Keep your brain engaged, one solution does not fit
all. There are also places where you may wish to mix DUIDs with
conventional device names (for example, the root partition of a softraid
mirror).
Nick.
