From: "David S. Miller" <davem@redhat.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Christoph Lameter <christoph@lameter.com>,
khttpd-users@zgp.org, linux-kernel@vger.kernel.org
Subject: Re: khttpd beaten by boa
Date: Fri, 12 Jan 2001 00:11:09 -0800 (PST) [thread overview]
Message-ID: <14942.48157.259491.78067@pizda.ninka.net> (raw)
In-Reply-To: <20010112084259.B441@marowsky-bree.de>
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>
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.
Later,
David S. Miller
davem@redhat.com
-
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 8:11 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 13:36 ` Arjan van de Ven
2001-01-12 16:25 ` Ingo Oeser
2001-01-12 8:11 ` David S. Miller [this message]
2001-01-12 10:03 ` H. Peter Anvin
2001-01-12 10:22 ` Alan Cox
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=14942.48157.259491.78067@pizda.ninka.net \
--to=davem@redhat.com \
--cc=christoph@lameter.com \
--cc=khttpd-users@zgp.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/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
all inboxes | Powered by JetHome®