Date: Mon, 30 Mar 2009 16:14:11 +0100 From: Rui Paulo <rpaulo@freebsd.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-arch@freebsd.org Subject: Re: Unique machine identifier for nfsv4 client Message-ID: <3E2EA002-4C26-4D44-ACEE-AD0F782F268E@freebsd.org> In-Reply-To: <Pine.GSO.4.63.0903301057020.13442@muncher.cs.uoguelph.ca> References: <Pine.GSO.4.63.0903301057020.13442@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-2-273330164 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On 30 Mar 2009, at 16:09, Rick Macklem wrote: > An nfsv4 client needs a unique identifier that is persistent across > reboots. My code currently uses the MAC address of the first net > interface that it can find that has an Ethernet style MAC. > > There are two problems with this: > 1 - If it can't find a net interface with a MAC, it falls back on a > randomly generated identifier, which changes when it is rebooted. > 2 - The code that finds the MAC breaks layering (ie knows stuff about > the network code like struct ifnet) and only builds if > "options VIMAGE_GLOBALS" is set. This doesn't answer the question, but have you thought about the possibility of the using the UUID that the system provides? A lot of new machines come with UUIDs. -- Rui Paulo --Apple-Mail-2-273330164 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAknQ4cMACgkQfD8M/ASTygKW8wCgvZ5+kgElJgiAONT1TvAwIoaT tVIAn1ffeuex8Jb1xMdw9G5+Qb8Bko+D =hT3V -----END PGP SIGNATURE----- --Apple-Mail-2-273330164--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E2EA002-4C26-4D44-ACEE-AD0F782F268E>