From owner-freebsd-arch Tue Jul 17 10:22:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from spirit.jaded.net (shortbus.groupofnine.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id DEEDA37B41F; Tue, 17 Jul 2001 10:22:34 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.11.4/8.11.4) id f6HHMX901053; Tue, 17 Jul 2001 13:22:33 -0400 (EDT) (envelope-from dan) Date: Tue, 17 Jul 2001 13:22:33 -0400 From: Dan Moschuk To: Mike Heffner Cc: arch@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: Importing lukemftpd Message-ID: <20010717132232.A1010@spirit.jaded.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mheffner@novacoxmail.com on Mon, Jul 16, 2001 at 09:24:54PM -0400 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG | a) our ftpd and NetBSD ftpd be merged as best as possible to keep features of | both, but try to follow NetBSD's ftpd development in our tree? | | b) we import NetBSD's ftpd AS IS and treat it like vender code with regular | imports, but break backwards compatibility? | | c) we not do anything at all and leave our ftpd as it is? Why not start with lukem's code, add in PAM support and other FreeBSDisms, and then track NetBSD from that point? -Dan -- There is nothing wrong with Southern California that a rise in the ocean level wouldn't cure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message