Re: [ldapext] DBIS commentary

Simo Sorce <> Wed, 02 December 2015 01:06 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0A9851B2FE8 for <>; Tue, 1 Dec 2015 17:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LoFSdYLyyuWO for <>; Tue, 1 Dec 2015 17:06:11 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4F25A1B2FDF for <>; Tue, 1 Dec 2015 17:06:11 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTPS id 06D8CC0CC623; Wed, 2 Dec 2015 01:06:11 +0000 (UTC)
Received: from ([]) by (8.14.4/8.14.4) with ESMTP id tB2169ZP032383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 1 Dec 2015 20:06:10 -0500
Message-ID: <>
From: Simo Sorce <>
To: "Bannister, Mark" <>
Date: Tue, 01 Dec 2015 20:06:09 -0500
In-Reply-To: <>
References: <> <> <> <>
Organization: Red Hat, Inc.
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on
Archived-At: <>
Cc: "''" <>
Subject: Re: [ldapext] DBIS commentary
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 02 Dec 2015 01:06:13 -0000

On Tue, 2015-12-01 at 10:13 +0000, Bannister, Mark wrote:
> <rant>
> Wait.  NIS permitted this.  If folk have done what NIS allowed them to
> do, and it fitted their working practice, then you can't blame them
> for that.  If you don't like it and want to label it "a mess", that's
> fine you can do that, but I do not want to leave people behind.  If
> you wish to call it a mess, then Sun Microsystems created the mess,
> but it's infrastructure and we're stuck with it.

Bugs happen, even in specifications.

> Imagine if the electronics industry in America
> started selling devices with only English three-pin
> plugs<>, citing that the original was a “bad design” and anyone who has found themselves in such a mess as to have incompatible wall sockets, well very sorry for them but that’s just tough luck.

Funny you bring up this example, because these kind of changes happened
quite a few times in history, just on power plugs:

I've used converters from one type to another for many years in Italy
given there we are still supposedly at the end of a multi-decades long
transition from this:
to this:
or this:
by way of this:

> Right.  You’d cause an outcry.

If enough people thought it was the end of the world, yeah, but it
didn't happen, and in most cases it isn't happening in the Unix/Linux
world. Most people are just happy to use case-preserving names (ie
case-insensitive names were the name is preserved in the form entered in
most cases).

>   Same thing applies here.  With NIS a particular working practice was
> absolutely fine.  Now it isn’t.  And people are left to fix it
> themselves.  I think that’s very bad.  (And for those who say “NIS is
> dead”, that’s absolutely not true, there are large organisations still
> using NIS and who haven’t yet migrated to LDAP, perhaps because the
> migration to LDAP is too hard for them in the present climate).

There is always some holdout with every technology, that's not a reason
to stop the evolution of standards in the direction everyone else is

> </rant>

Simo Sorce * Red Hat, Inc * New York