From: john slee <indigoid@higherplane.net>
To: J Sloan <joe@tmsusa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tux officially in kernel?
Date: Thu, 14 Feb 2002 00:58:41 +1100 [thread overview]
Message-ID: <20020213135841.GB4826@higherplane.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0202111313100.28040-100000@mustard.heime.net> <3C67F327.8010404@tmsusa.com>
In-Reply-To: <3C67F327.8010404@tmsusa.com>
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.
--
R N G G "Well, there it goes again... And we just sit
I G G G here without opposable thumbs." -- gary larson
next prev parent reply other threads:[~2002-02-14 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 12:49 tux officially in kernel? Roy Sigurd Karlsbakk
2002-02-11 16:36 ` J Sloan
2002-02-13 13:58 ` john slee [this message]
2002-02-14 23:33 ` J Sloan
2002-02-14 23:54 ` Robert Love
2002-02-15 1:00 ` Ken Brownfield
2002-02-15 12:36 ` john slee
2002-02-15 21:11 ` David Lang
2002-02-15 21:35 ` Benny Sjostrand
2002-02-15 23:48 ` Luigi Genoni
2002-02-16 18:59 ` Jason Czerak
2002-02-16 19:25 ` jjs
-- strict thread matches above, loose matches on Subject: below --
2002-02-15 16:37 Dan Kegel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020213135841.GB4826@higherplane.net \
--to=indigoid@higherplane.net \
--cc=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox