From owner-freebsd-arch  Tue Nov 12  9:14:49 2002
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4EFD737B401
	for <arch@freebsd.org>; Tue, 12 Nov 2002 09:14:48 -0800 (PST)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7732743E4A
	for <arch@freebsd.org>; Tue, 12 Nov 2002 09:14:47 -0800 (PST)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3])
	by fledge.watson.org (8.12.4/8.12.4) with SMTP id gACHE4Oo042294;
	Tue, 12 Nov 2002 12:14:04 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Date: Tue, 12 Nov 2002 12:14:03 -0500 (EST)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: The Anarcat <anarcat@anarcat.ath.cx>
Cc: Mike Heffner <mheffner@vt.edu>,
	Garance A Drosihn <drosih@rpi.edu>, arch@freebsd.org
Subject: Re: Status of lukemftpd? (was: cvs commit: src/etc inetd.conf (fwd))
In-Reply-To: <20021112170102.GA32440@xtanbul.studio.espresso-com.com>
Message-ID: <Pine.NEB.3.96L.1021112121308.38530G-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG


On Tue, 12 Nov 2002, The Anarcat wrote:

> How hard would it be to pull to plug on lukemftp[d] and (say) put it
> back in -ports, for now? 

At this point I see no reason to pull the plug on lukemftp; my concerns
lie primarily with lukemftpd.  From a purely technical perspective, it
would be trivial to remove lukemftpd from the tree, or even from the
build.  The social engineering issues are where you'd probably find the
challenges.

> On Tue Nov 12, 2002 at 09:09:48AM -0500, Robert Watson wrote:
> [...]
> > 
> > You do realize that we're in a feature freeze right now, and will be in a
> > code freeze within days, right?  You're coming up a dollar short, and a
> > day late.  This is the reason I've trying to press for a resolution for
> > weeks now.  I'm deeply concerned that we've imported software without
> > doing any of the necessary mergework and adaptation, and are now
> > apparently planning to ship it.
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message