🚀 go-pugleaf

As if more confirmation was needed, you do indeed need the right flavor
of license to get the BSD source. We were lucky - AT&T told me about this
in a conversation with an account rep; I figured since they just came
up with it Berkeley might not have heard about it yet, so I quickly
rushed our order through and received the BSD tape, even though we
had a 68k license only. I can talk about it now because we went ahead
and got the VAX license within a couple of months, so it is all square
(this was at my previous company, by the way, not Fortune).

The point is, AT&T decided that processor families are different for
purposes of code sharing. If you buy a 16000 family (National; I
know they cal it 32000 these days, but s does AT&T with the WE chips..)
you can't give your derived source to somebody with an Intel family
port, and neither of you can get the BSD code which is Vax-derived.

I excerpt the following "Q&A" dialog from the latest AT&T $echo
magazine, which covers the topic:

Question: If I am approached by another licensee to exchange source
code, what are my restrictions?

Answer: Both licensees must be licensed in the same family of
technology (i.e., VAX, 3B, Motorola, etc.), and at the same version
and release level. For example, System V Release 2 Version 1 is
not the same as System V Release 2 Version 2. The company
supplying the source should call the AT&T UNIX Software Sales and
Licensing organization to verify the licensing status of the
recipient's status within the United States and written verification
for all other countries.....(bla, bla, bla).

Notice that this really means that to get BSD you need only to have 
something later than 32V (as long as it is for the VAX), since a 
later release entitles you to receive source based on an earlier one.

Don't you just love it?

    Mats Wichmann
    Fortune Systems
    {ihnp4,hplabs,dual}!fortune!mats