From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 6 May 2002 23:01:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 6 May 2002 23:01:01 -0400 Received: from flrtn-4-m1-42.vnnyca.adelphia.net ([24.55.69.42]:37775 "EHLO jyro.mirai.cx") by vger.kernel.org with ESMTP id ; Mon, 6 May 2002 23:01:00 -0400 Message-ID: <3CD7436B.4060405@tmsusa.com> Date: Mon, 06 May 2002 20:00:59 -0700 From: J Sloan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020505 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Stoffel CC: linux kernel Subject: Re: Tux in main kernel tree? (was khttpd rotten?) In-Reply-To: <3CD5ECEE.E6C0B894@kegel.com> <15574.52864.321544.44124@gargle.gargle.HOWL> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org John Stoffel wrote: >Or maybe we should include kDNS and kftpd as well now? > We do have knfsd - and FWIW, tux does ftp as well as http - > > >An httpd server is a *user space* issue, not a kernel issue. > What about nfs? also a user space issue? If a userspace httpd could come anywhere near the performance of tux, your protest might be just a little more beleivable. google "specweb champ" for a gentle heads-up on the subject. Joe