From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: khttpd beaten by boa
Date: 12 Jan 2001 02:03:32 -0800 [thread overview]
Message-ID: <93mkpk$98k$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101071655090.1110-100000@home.lameter.com> <Pine.LNX.4.21.0101112214040.22231-100000@home.lameter.com> <20010112084259.B441@marowsky-bree.de> <14942.48157.259491.78067@pizda.ninka.net>
Followup to: <14942.48157.259491.78067@pizda.ninka.net>
By author: "David S. Miller" <davem@redhat.com>
In newsgroup: linux.dev.kernel
>
> Lars Marowsky-Bree writes:
> > This just goes on to show that khttpd is unnecessary kernel bloat
> > and can be "just as well" handled by a userspace application, minus
> > some rather very special cases which do not justify its inclusion
> > into the main kernel.
>
> My take on this is that khttpd is unmaintained garbage.
>
> TUX is evidence that khttpd can be done properly and
> beat the pants off of anything done in userspace.
>
Then why don't we unload khttpd and put in Tux?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-12 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0101071655090.1110-100000@home.lameter.com>
2001-01-11 7:22 ` Kernel HTTP server: Patch for name based virtual domains Christoph Lameter
2001-01-12 6:20 ` khttpd beaten by boa Christoph Lameter
2001-01-12 7:42 ` Lars Marowsky-Bree
2001-01-12 8:11 ` David S. Miller
2001-01-12 10:03 ` H. Peter Anvin [this message]
2001-01-12 10:22 ` Alan Cox
2001-01-12 13:36 ` Arjan van de Ven
2001-01-12 16:25 ` Ingo Oeser
2001-01-12 9:10 ` lies, lies and web benchmarks :-) Ingo Molnar
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='93mkpk$98k$1@cesium.transmeta.com' \
--to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.