From owner-freebsd-current Wed Sep 25 10:53:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA07207 for current-outgoing; Wed, 25 Sep 1996 10:53:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA07022; Wed, 25 Sep 1996 10:53:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA06278; Wed, 25 Sep 1996 10:48:15 -0700 From: Terry Lambert Message-Id: <199609251748.KAA06278@phaeton.artisoft.com> Subject: Re: Licensing Software To: stesin@gu.net (Andrew Stesin) Date: Wed, 25 Sep 1996 10:48:14 -0700 (MST) Cc: rgrimes@GndRsh.aac.dev.com, ulf@Lamb.net, jhs@FreeBSD.org, current@FreeBSD.org, serious@FreeBSD.org, commercial@FreeBSD.org In-Reply-To: from "Andrew Stesin" at Sep 25, 96 10:19:16 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > 'course. Pity Intel didn't think on burning a unique CPU > ID into each chip they made. Even PDP11 had this. > What can be thought to become a unique FreeBSD machine ID, anyway? > > I can think on a MD5 checksum of the following > things together: > > CPU type; > motherboard chipset ID (if available); > manufacturer's ID of a primary HDD; > primary disk controller' ID (if available); > OS kernel version (?); > canonical hostname. Network address. Really. You will never get two machines setting the same network address because if you did, they would fail to operate as network nodes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.