Rich Shepard <[email protected]> writes:
> On Sat, 30 Oct 2010, Daniel Pittman wrote:
>
>> That means you want: blkid /dev/sda1 # or whatever raw device it is at.
>
> That's the conundrum: with the fstab entry linking a mount point to a UUID
> there is no entry in /dev/.
No *immediately obviously* device entry; it still exists.
However, that means your problem is the exact opposite of what you stated: you
want to find the device node based on the UUID, not the UUID based on the
device after all.
Someone else already suggested the /dev/disk/by-* directories; the easiest way
to map a UUID to a device node is, as they mentioned, 'ls -l /dev/disk/by-uuid/'
> What I read is that udevd does its thing based on UUID so, perhaps in the
> not-so-distant-future, the entire /dev directory will be deprecated.
....er, no. Using a stable identifier is the only sane thing to do with the
way that modern systems detect devices, but that is just a pointer on back to
the traditional device node.
(Specifically, the tree mentioned above is a tree of symlinks based on
persistent properties back to the actual owning node, and is what mount uses
to discover that detail.[1])
Regards,
Daniel
Footnotes:
[1] I believe. I should actually verify that one day.
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
