All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Simo Sorce <simo@redhat.com>
Cc: samba-technical@lists.samba.org,
	fedfs-utils Developers <fedfs-utils-devel@oss.oracle.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: Interoperable junctions on Linux
Date: Tue, 23 Apr 2013 14:43:01 -0400 (EDT)	[thread overview]
Message-ID: <189824864.86.1366742581325.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1366742262.7239.131.camel@willson.li.ssimo.org>


----- "Simo Sorce" <simo@redhat.com> wrote:

> 
> Well I have some knowledge in this field, and I do not find it very
> fiddly, but I may be biased as I have been working for the past 7
> years
> to make LDAP+Kerberos simple to manage within the FreeIPA project.
> Your requirement to set an objectclass on the base suffix is something
> I
> find particularly unappealing, and no other tool that I know of
> requires
> this (because it is unnecessary).

Yes.  Thank you.

> > 
> 
> I think you should allow the broadest possibilities of course, which
> is
> why I am picking on things like allowing SSAL/GSSAPI explicitly in
> the
> RFC language. Whether people will integrate into existing LDAP server
> or
> not remains to be seen, if we can avoid the need to add an objectlass
> on
> the root suffix I see that we can easily add this a standard feature
> for
> FreeIPA as well (we already provide automount data for example) and
> provide management tools in our framework around it.

I noted this point on a FedFS concall 2 years ago.  I dont understand why
not -permit- easy integration with existing LDAP infrastructure.


-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

  reply	other threads:[~2013-04-23 18:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 20:39 Interoperable junctions on Linux Chuck Lever
2013-04-23 14:51 ` Simo Sorce
2013-04-23 15:42   ` Chuck Lever
2013-04-23 15:51     ` Myklebust, Trond
2013-04-23 16:19       ` Simo Sorce
2013-04-23 16:24         ` Myklebust, Trond
2013-04-23 16:28           ` Simo Sorce
2013-04-23 16:30             ` Myklebust, Trond
2013-04-23 16:54     ` Simo Sorce
2013-04-23 18:11       ` Chuck Lever
2013-04-23 18:37         ` Simo Sorce
2013-04-23 18:43           ` Matt W. Benjamin [this message]
2013-04-23 19:52           ` Chuck Lever
2013-04-23 20:33             ` Simo Sorce

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=189824864.86.1366742581325.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@linuxbox.com \
    --cc=chuck.lever@oracle.com \
    --cc=fedfs-utils-devel@oss.oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=simo@redhat.com \
    /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.