[2110] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Krb5-1.0 and t_kdb - It works on HP

daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Tue Dec 10 18:57:11 1996

Date: Tue, 10 Dec 1996 18:55:08 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Ezra Peisach <epeisach@MIT.EDU>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>, Ken Hornstein
	<kenh@cmf.nrl.navy.mil>,
        deengert@anl.gov, krbdev@MIT.EDU, Paul
	A Vixie <paul@vix.com>,
        Andrew Hobson <ahobson@mindspring.com>,
        Dave McGuire <mcguire@neurotica.com>, Joe Gross
	<jgross@uiuc.edu>
In-Reply-To: Ezra Peisach's message of Tue, 10 Dec 1996 07:23:41 EST,
	<9612101223.AA05989@kangaroo.mit.edu>

   Date: Tue, 10 Dec 1996 07:23:41 EST
   From: Ezra Peisach <epeisach@MIT.EDU>

   The real problem is that for database locking - you need a filesystem with
   more specific characteristics - which may be more difficult to determine.

True; however, I don't feel bad about not supporting the use of a
Kerberos database located in AFS and accessed via NFS through a NFS/AFS
gateway.  :-)

And as far as the test suite is concerned, if it doesn't pass because
someone is using a filesystem that doesn't have the full POSIX locking
semantics, that's not a problem that I think we should stress over.

							- Ted


home help back first fref pref prev next nref lref last post