Date: Wed, 25 Sep 1996 12:27:33 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: terry@lambert.org (Terry Lambert) Cc: stesin@gu.net, ulf@Lamb.net, jhs@FreeBSD.org, current@FreeBSD.org, serious@FreeBSD.org, commercial@FreeBSD.org Subject: Re: Licensing Software Message-ID: <199609251927.MAA09117@GndRsh.aac.dev.com> In-Reply-To: <199609251748.KAA06278@phaeton.artisoft.com> from Terry Lambert at "Sep 25, 96 10:48:14 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > '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. Yea, so, I put a third box called a dummy router/NAT between them and make them talk. Novell Netware servers can be fooled into operating this way (thats how I do server to server upgrades of Netware, just put a router between them and spoof a few things, works great, and no inplace upgrade risk, and no need for a second license.) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609251927.MAA09117>