All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.cz>
Cc: autofs@linux.kernel.org
Subject: Re: autofs & system libnss* libraries
Date: Wed, 24 Sep 2008 14:47:04 +0200	[thread overview]
Message-ID: <48DA36C8.4040403@s3group.cz> (raw)
In-Reply-To: <1222258619.1280.31.camel@raven.themaw.net>

>
> No!
>
> I considered that at the outset of version 5 development and decided
> against it after working on integrating the outdated code that was
> included in the nss_ldap distribution. Unless the situation changes
> significantly then I'm not likely to change my mind on this.
>   
Does it mean that the nss_ldap is heavily outdated then?
> I would have to write the nss code for "all" the possible sources
> against a an API that is difficult to write for, partly because the
> interface documentation is lousy. Not to mention that I'd then be at the
> mercy of nss_ldap changes and bugs, and autofs would depend on a
> configuration file that it doesn't control.
>   
My primary concern was why should we (linux distro maintainers) support
2 things essentially doing the same?
I did not mean you specifically. Maintaining the libnss* libraries
should be (probably) job for someone else - you keep focused on the
autofs-specific tasks.
And if you think your nss_ldap is better, why should not it serve other
purposes (like gathering user info from LDAP repository), too?

I mean, from the longer perspective, I believe we should merge these
things. It is neither elegant nor transparent for normal sysadmins.
>  
> Ian
>
>
>   
Ondrej

  reply	other threads:[~2008-09-24 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  9:57 autofs & system libnss* libraries Ondrej Valousek
2008-09-24 12:16 ` Ian Kent
2008-09-24 12:47   ` Ondrej Valousek [this message]
2008-09-24 13:31     ` Jeff Moyer
2008-09-24 14:00       ` Ondrej Valousek
2008-09-24 13:33     ` Ian Kent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48DA36C8.4040403@s3group.cz \
    --to=webserv@s3group.cz \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.