[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libss collision ( for from FSH compliance)

Guys, please continue here, on separate thread.

---------- Forwarded message ----------
From: Brandon S. Allbery KF8NH <allbery@ece.cmu.edu>
Date: Dec 5, 2007 11:30 PM
Subject: Re: FSH compliance.
To: heimdal-discuss@sics.se, Russ Allbery <rra@stanford.edu>

On Dec 5, 2007, at 15:17 , Russ Allbery wrote:

> "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> writes:
>> My understanding is that this is known and there's ongoing
>> discussions
>> between the MIT Kerberos folks, the e2fs folks (these  overlap), the
>> Heimdal folks, and the OpenAFS folks over this (well,  not for
>> OpenAFS I
>> think) and com_err.  It's a somewhat painful  situation all around.
> ss should have fewer problems than com_err since there aren't the same
> thread safety issues.  Can Heimdal just use the e2fsprogs libss if
> it's
> already present?

Does libss have the same "multiple APIs in the wild" problem though?

brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com
system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu
electrical and computer engineering, carnegie mellon university    KF8NH