From: Lennart Poettering <lennart@poettering.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Extracting system UUID...
Date: Tue, 20 Apr 2010 19:10:43 +0000 [thread overview]
Message-ID: <20100420191042.GA2434@tango.0pointer.de> (raw)
In-Reply-To: <20100420185205.GA5138@mcpierce-desktop.usersys.redhat.com>
On Tue, 20.04.10 14:52, Darryl L. Pierce (dpierce@redhat.com) wrote:
> Does anything return the UUID for the host system? Such as what was
> returned by hal with:
>
> (mcpierce@mcpierce-desktop:~)$ hal-get-property --udi \
> /org/freedesktop/Hal/devices/computer --key system.hardware.uuid
> 00DD19E3-DD3A-DE11-90DA-812C97507C34
That's the product UUID key from the DMI data, which you also can read
from sysfs:
/sys/devices/virtual/dmi/id/product_uuid
Not sure what you want to use this for, but given that many BIOS vendors
just write rubbish to that field, it's mostly useless.
The D-Bus machine ID is usually more useful, as stored in
/var/lib/dbus/machine-id. It's nowadays available on virtually all
systems and considered part of the D-Bus API, and hence can be reliably
be used to identify a system. There's no need to actually use libdbus to
read that file.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2010-04-20 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 18:52 Extracting system UUID Darryl L. Pierce
2010-04-20 19:10 ` Lennart Poettering [this message]
2010-04-20 19:11 ` Greg KH
2010-04-20 19:30 ` Darryl L. Pierce
2010-04-20 19:39 ` Greg KH
2010-04-20 19:49 ` Darryl L. Pierce
2010-04-20 20:11 ` Greg KH
2010-04-20 20:16 ` Lennart Poettering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100420191042.GA2434@tango.0pointer.de \
--to=lennart@poettering.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).