[OpenAFS] re: my afs wish list

[John Rudd]

It would seem to me that the best choice would be to "not chose one, 
instead support many".  Allow the site to chose for itself whether it 
will store its account info in file, NIS, Hesiod, or LDAP.  And maybe 
even support hooks for people to extend it for their own mechanisms 
(NIS+ and NetInfo come to mind).  If you do it right, you could even 
use the existing nsswitch libraries that are already out there.


On Wednesday, Apr 30, 2003, at 13:29 US/Pacific, Derek Atkins wrote:

> The problem is that every site does it differently.  Some sites use NIS
> for their NSS info.  MIT uses Hesiod for its NSS info.  Some sites use
> Hesiod for their NSS info.  What are the OpenAFS developers supposed
> to do?  Choosing any one solution is just wrong, because it alienates
> the users that already deployed something else.
>
> -derek
>
> Deniz Akkus Kanca <deniz@arayan.com> writes:
>
>> I have seen the discussions previously on the list, especially about 
>> LDAP, but
>> it is cumbersome to have to create AFS user, Kerberos principal and 
>> LDAP
>> entry.   It can be scripted of course, but it does make AFS adoption a
>> slightly bigger hurdle than it already is. Something that reads AFS 
>> user info
>> for use in NSS would go a long way and alleviate the need for LDAP 
>> (or local
>> user creation).
>>
>> Best regards,
>> Deniz
>>
>>
>>
>> _______________________________________________
>> OpenAFS-info mailing list
>> OpenAFS-info@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-info
>
> -- 
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        warlord@MIT.EDU                        PGP key available
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info