[net.usenix] 2.9 and 4.x BOFs

lmc@denelcor.UUCP (Lyle McElhaney) (01/30/85)

Summary for those who weren't there.

2.9 - A LOT of discussion on the problems with 2.9 (most particularly,
the networking code). Several of the group do have networking running.
They have agreed to put together a complete release containing the working
software, and distribute it both to Berkeley and to anyone else who wants
it. The group is led by someone at seismo (wrote his name down & immediately
lost it). He will be sending something to everyone on his list (of attendees)
about the tape. Harvard is also doing a bunch with 2.9.

Lots of enthusiasm.

4.x - Didn't happen. No one from Berkeley came (did anyone tell them?).
After 1/2 hour, one of the attendees mentioned that he had talked with
McKusick earlier, and that he said that 4.3 was ready to release (bug fix
and performance enhancements only), but was tied up in some legal stew
that would probably last into the second quarter (read Summer). Unknown
whether a System V license would be required.

Lyle McElhaney
-- 
Lyle McElhaney
{hao, stcvax, brl-bmd, nbires, csu-cs} !denelcor!lmc

jmoore@opus.UUCP (Jim Moore) (02/04/85)

> 
> 4.x - Didn't happen. No one from Berkeley came (did anyone tell them?).
> After 1/2 hour, one of the attendees mentioned that he had talked with
> McKusick earlier, and that he said that 4.3 was ready to release (bug fix
> and performance enhancements only), but was tied up in some legal stew
> that would probably last into the second quarter (read Summer). Unknown
> whether a System V license would be required.
> 
> Lyle McElhaney
> -- 

Why not release 4.2+ with the requirement of a System V license?
It is the only kind available from now on, and this might help the
standards effort if all commercial UN*X vendors possessed the same
sources and source licenses.

Jim Moore
NBI, Boulder Co.
[ucbvax|hao|amd]!nbires!jmoore