Date: Thu, 01 Feb 2007 11:38:51 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: peterjeremy@optushome.com.au Cc: jon.passki@hursk.com, fbsd@metro.cx, freebsd-hackers@freebsd.org Subject: Re: unique hardware identification Message-ID: <20070201.113851.689651534.imp@bsdimp.com> In-Reply-To: <20070128181132.GR927@turion.vk2pj.dyndns.org> References: <45BC3624.3000608@pacbell.net> <3B777B32-AB3A-4244-BBE1-9E11B287D78B@hursk.com> <20070128181132.GR927@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20070128181132.GR927@turion.vk2pj.dyndns.org>
Peter Jeremy <peterjeremy@optushome.com.au> writes:
: On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote:
: >If the machine is a PXE-compliant device [2], it should have a GUID/
: >UUID [1] available. This can be exposed by sysutil/hal [3] via the
: >smbios.system.uuid field.
:
: You can also get it via kenv(8) without needing any ports:
: # kenv smbios.system.uuid
: 9F345F4F-BEFC-D431-1340-61235A56DEF9
I wonder why the smbios stuff isn't exported via sysctls as well...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070201.113851.689651534.imp>