Tech Insider					     Technology and Trends


		     Kerberos V5 Mailing List Archives

Date: Tue, 23 Oct 90 14:04:51 -0400
From: John T Kohl <jtkohl@ATHENA.MIT.EDU>
To: krbdev@ATHENA.MIT.EDU

I am trying to plan out the remainder of Kerberos V5 work, and to do so
I will need information on your planned absences (if any) between now and
Christmas.

Thanks,

John

Date: Wed, 24 Oct 90 09:51:40 -0400
From: John T Kohl <jtkohl@ATHENA.MIT.EDU>
To: tytso@ATHENA.MIT.EDU, prb@ATHENA.MIT.EDU, don@ATHENA.MIT.EDU,
Cc: krbdev@ATHENA.MIT.EDU

I'd like to have a meeting on Friday to discuss scheduling for the
remainder of the year, in order to get kerberos v5 "out the door".

Can you make it on Friday at 3:30pm in E40-316 (small conf. room), for
about an hour?

>>> Please respond either "yes, I can make it" or "no, but I
>>> can make it at xxx time on Friday".

Thanks,

John

Date: Thu, 25 Oct 90 09:57:09 -0400
From: John T Kohl <jtkohl@ATHENA.MIT.EDU>
To: tytso@ATHENA.MIT.EDU, prb@ATHENA.MIT.EDU, don@ATHENA.MIT.EDU,
Cc: krbdev@ATHENA.MIT.EDU
In-Reply-To: [362] John T Kohl's message of Wed, 24 Oct 90 09:51:40 -0400,

Everybody except Jon Rochlis can make the meeting, so it's a "go".

I'd appreciate if you would be prepared to give a short status update
and a rundown of your planned absences.

I will circulate later today a draft schedule for the remainder of the
work.

John Carr will circulate later today a write-up of the v4/v5 conversion
issues.

John

Date: Thu, 25 Oct 90 10:40:55 -0400
From: John T Kohl <jtkohl@ATHENA.MIT.EDU>
To: krbdev@ATHENA.MIT.EDU

TENTATIVE SCHEDULE:

as of 25 October 1990:
DRAFT:  nothing here is hard and/or fast!

5 useful weeks before end of year:
Oct
28 29 30 31  1  2  3	[-5]
Nov
 4  5  6  7  8  9 10	[-4]
11 12 13 14 15 16 17	[-3]
[t-day week]
25 26 27 28 29 30  1	[-2]
Dec
 2  3  4  5  6  7  8	[-1]
 9 10 11 12 13 14 15	[0]
16 17 18 19 20 21 22	d-day

Need to do release engineering/code check/cleanup starting 10 December [0],
until years end.  release target: week of 17 December

Proposed schedules:
		-5			-4			-3
tytso:		edit, kprop		edit, kprop done	etypes
					db etypes		nfs

prb:		cray/sun stuff		cray/sun stuff		ISODE issues
		telnet			telnet finished

don:		v4/v5 server		

jon:		admin server		admin server		admin server

jtkohl:		alpha admin		alpha admin		alpha admin
		[alpha2]		RFC work		RFC work
		RFC work

raeburn:	cc/stdio		liblogin		liblogin
		liblogin

jfc:		gss			gss/user2user		user2user
								X11
-------------------------------------------------------------------
		-2			-1
prb:		gone			gone

tytso:		nfs, pop

don:

jon:		

jtkohl:		beta admin		beta admin
		RFC work		RFC work

raeburn:	threaded issues

jfc:

vacations (excepting T-day):

don:		12/24 -> 1/5
jtkohl:		12/22 -> 1/2


THINGS NEEDING WORK (/mit/krb5/src/TODO):

sorted by priority:
-------------------

KDC v4 compatibility (don)

slave server (tytso)

Finish code; look for XXX and make things proper; usually there are
comments indicating what needs to be done (all)

admin server (jon)

user2user/GSS stuff

finish up & polish the RFC

klist better

multi-thread warnings in pseudo-code (in the document)

Convert the rcache to be thread-safe; verify other code is thread-safe
(raeburn)

applications, applications, applications:
	login library
	pop
	nfs
	discuss (?)

compatibility libraries

portability & clean up configuration (site.def) (prb?)

general POSIX cleanup defines:
	POSIX_VOIDSIG
	POSIX_TERMIOS
	POSIX_TYPES
	POSIX_FILE_LOCKS
	???

mem* vs. b*

real man pages

on-hold:
-------

"true" session keys rather than multi-session keys

temporary allocation

test suite

			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO vs IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or
research.

Electronic mail:			       WorldWideWeb:
   tech-insider@outlook.com			  http://tech-insider.org/