Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cadence!baeder
From: baeder@cadence.com (D. Scott Baeder; x299)
Newsgroups: comp.sys.amiga.tech
Subject: Re: I need Help with the A3000!
Message-ID: <1990Jul17.154103.7433@cadence.com>
Date: 17 Jul 90 15:41:03 GMT
References: <1027@tau.sm.luth.se> <13183@cbmvax.commodore.com> <1028@tau.sm.luth.se> <13236@cbmvax.commodore.com>
Sender: usenet@cadence.com (USENET News)
Organization: Cadence Design Systems, Inc.
Lines: 20

In article <13236@cbmvax.commodore.com> jesup@cbmvax (Randell Jesup)
writes: 
> 
>	As to hardware to explicitly limit copying, this seems unlikely, given 
>the Unix market and the hardware the most Unixes require.  I've never seen 
>a Unix with explicit hardware protection.
> 

By hardware protection, what do you mean...For example, the SUN
computers generate a UNIQUE, machine specific 32-bit number when you
use the "hostid" function.  While this is certainly not forced by
UNIX, (ie the man page for hostid just says it should be unique on a
network) this philosophy of causing the hostid to be fixed by the boot
rom was also adopted by NeXT when the went from rev 0.9 to 1.0 -
specifically to allow an easy way for vendors to license their
software.

Scott Baeder
baeder@cadence.com
.standard disclaimer.