Date: Mon, 30 Mar 2009 13:07:48 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Gordon Tetlow <gordon@tetlows.org> Cc: freebsd-arch@freebsd.org Subject: Re: Unique machine identifier for nfsv4 client Message-ID: <Pine.GSO.4.63.0903301304510.4576@muncher.cs.uoguelph.ca> In-Reply-To: <4e571dd70903300825q63b4344bhdee6ba7c54c2deab@mail.gmail.com> References: <Pine.GSO.4.63.0903301057020.13442@muncher.cs.uoguelph.ca> <4e571dd70903300825q63b4344bhdee6ba7c54c2deab@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Mar 2009, Gordon Tetlow wrote: > > There is a uuid that is generated at first boot and persistent. Check > /etc/rc.d/hostid. It sets kern.hostuuid and kern.hostid. > Duh (as Homer S might say;-). Yep, that should work just fine. From a quick glance at the rc.d script, the sysctl that loads it into the kernel happens before any nfs client stuff. (I also noticed that kern_uuid.c has a routine that gets a MAC, but I won't even need it.) Thanks everyone for the replies, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0903301304510.4576>