From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lennart Poettering Date: Tue, 20 Apr 2010 19:10:43 +0000 Subject: Re: Extracting system UUID... Message-Id: <20100420191042.GA2434@tango.0pointer.de> List-Id: References: <20100420185205.GA5138@mcpierce-desktop.usersys.redhat.com> In-Reply-To: <20100420185205.GA5138@mcpierce-desktop.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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