Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 16 Feb 2002 14:00:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 16 Feb 2002 13:59:51 -0500 Received: from erasure.jasnik.net ([207.148.204.33]:6322 "HELO erasure.jasnik.net") by vger.kernel.org with SMTP id ; Sat, 16 Feb 2002 13:59:36 -0500 Subject: Re: tux officially in kernel? From: Jason Czerak To: john slee Cc: J Sloan , linux-kernel@vger.kernel.org In-Reply-To: <20020213135841.GB4826@higherplane.net> In-Reply-To: <3C67F327.8010404@tmsusa.com> <20020213135841.GB4826@higherplane.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: 16 Feb 2002 13:59:42 -0500 Message-Id: <1013885982.1680.2.camel@neworder> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2002-02-13 at 08:58, john slee wrote: > On Mon, Feb 11, 2002 at 08:36:55AM -0800, J Sloan wrote: > > If that's not part of the roadmap I'd be surprised, > > since tux is so much more capable than the > > khttpd which is currently part of the tree. > > > > Tux has clearly demonstrated it's performance > > and low resource consumption. > > it has also been demonstrated that equal performance can be had in > userland (search archives for "X15"). most of tux' improvements have > been generalised and absorbed into the mainline kernel anyway. > > j. > If I"m not mistaken, Tux needs SSL and V-domains support. then I can use it instead of Apache with mod_proxy (static) --> Apache mod_perl (dynamic content) dual apache setup. Once this happens. My little PII-350 should surly keep up with, if not be faster then that Dual 733 NT box for static content :) -- Jason Czerak. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/