From owner-freebsd-current@FreeBSD.ORG  Tue Jun 29 08:28:31 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CCD8D16A4CE
	for <current@freebsd.org>; Tue, 29 Jun 2004 08:28:31 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3DF3243D41
	for <current@freebsd.org>; Tue, 29 Jun 2004 08:28:31 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i5T8SSlq034707;
	Tue, 29 Jun 2004 10:28:29 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Chuck Swiger <cswiger@mac.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sun, 27 Jun 2004 15:54:47 EDT."
             <40DF2607.5020409@mac.com> 
Date: Tue, 29 Jun 2004 10:28:28 +0200
Message-ID: <34706.1088497708@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: current@freebsd.org
Subject: Re: HEADSUP: ibcs2 and svr4 compat headed for history 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2004 08:28:31 -0000

In message <40DF2607.5020409@mac.com>, Chuck Swiger writes:

>In other words, I care quite a bit about how "working, supported 
>functionality" gets transitioned to "no longer available".  I'm not happy with 
>the notion of "supported" -> "HEADS UP" -> one week -> gone.

I don't think anybody would be happy with that, and that is not what
was proposed in this case.

The future of ibcs2 and svr4 has been in doubt for a long time (and
still is pending developer attention), but appearantly most of the
previous discussion and warnings have not been noticed:

	critter phk> cvs -R annotate files.i386 | grep SVR4

	Annotations for files.i386
	***************
	1.413        (peter    20-Aug-02):      warning "COMPAT_SVR4 is broken and should be avoided"


Searching the major mailing lists (bugs, stable, current etc) failed
to return any hits about this.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.