From owner-freebsd-current@FreeBSD.ORG  Tue Jun 29 22:42:00 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 D487616A4CE
	for <current@freebsd.org>; Tue, 29 Jun 2004 22:42:00 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3CB9543D4C
	for <current@freebsd.org>; Tue, 29 Jun 2004 22:41:58 +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 i5TMfh6Y012025;
	Wed, 30 Jun 2004 00:41:43 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Charles Swiger <cswiger@mac.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 29 Jun 2004 13:10:52 EDT."
             <46A7D8A4-C9EF-11D8-99F8-003065ABFD92@mac.com> 
Date: Wed, 30 Jun 2004 00:41:43 +0200
Message-ID: <12024.1088548903@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 22:42:01 -0000

In message <46A7D8A4-C9EF-11D8-99F8-003065ABFD92@mac.com>, Charles Swiger write
s:

>> 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:
>[ ...cvs annotate... ]
>> Searching the major mailing lists (bugs, stable, current etc) failed
>> to return any hits about this.
>
>End-users may not read /usr/src/UPDATING or the published release notes 
>either, but at least those are the places they are _expected_ to look 
>at if they want to know what is changing.  I don't think we can 
>reasonably expect an end-user to look though the output of "cvs 
>annotate"...  :-)

The warning would appear if you tried to config a kernel containing
COMPAT_SVR4, and since there is no email, I conclude that nobody
who cared about COMPAT_SVR4 (in -current) has done that since the
message was added.


-- 
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.