On Sun, Apr 10, 2011 at 01:54:41PM +0200, Jan Stary wrote: > On Nov 08 00:54:29, Joel Sing wrote: > > For a user's perspective you want to look at the -current man pages for > > fstab(5), disklabel(8) and mount(8). > > I finally got around to it. Thank you very much for diskmap, > I am using it everywhere I can now. > > While editing my fstabs, I noticed that some "disks" do not really > have a DUID; for example the disklabel of my M-Audio Microtrack > handheld recorder says 'duid: 0000000000000000'. > > Rereading the manpage of disklabel, I see the new feature: > > i Change the disklabel UID, specified as a 16-character > hexadecimal string. If set to all zeros, a new UID > will automatically be allocated when the disklabel > is written to disk. > > So I specified all zeroes, and disklabel now says > 'duid: 40d4301bbd5721c6'. Now I can use the following fstab line: > 40d4301bbd5721c6.i /micro msdos rw,noauto,noatime,nodev,noexec > > The newly assigned DUID survives the powercycle > of both the computer and the recorder. > > I tried the same with my Android (Samsung GT-I5519); that became > 2f6f4a8461a75bf8 and I can mount 2f6f4a8461a75bf8.i - but after > umount and replug (or even "turn off USB storage / turn on USB storage" > on the phone) the DUID is again zero. > > Is the duid something that is physically stored in the device/disk, > and should therefore stay accross reboots? Should I consider this > a bug of the android phone? > > Thank you for your time > > Jan
The DUID is stored in the disklabel on the physical device. If the device fiddles with it, all bets are off. :-). Android phone would be prime candidate for a fiddler. .... Ken
