From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Arjan van de Ven <arjan@fenrus.demon.nl>
Cc: Lars Marowsky-Bree <lmb@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: khttpd beaten by boa
Date: Fri, 12 Jan 2001 17:25:45 +0100 [thread overview]
Message-ID: <20010112172545.H10035@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0101071655090.1110-100000@home.lameter.com> <m14H4Nl-000OY9C@amadeus.home.nl>
In-Reply-To: <m14H4Nl-000OY9C@amadeus.home.nl>; from arjan@fenrus.demon.nl on Fri, Jan 12, 2001 at 02:36:41PM +0100
On Fri, Jan 12, 2001 at 02:36:41PM +0100, Arjan van de Ven wrote:
> > 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.
> Regarding wether either khttpd or TuX should be in the kernel: I take it
> that it is your oppinion that neither should be in the kernel. I disagree
> with that and I think having a http-server-engine (or even a more generic
> file-serving engine) in the kernel can make sense for high-end uses. The
> average desktop-user doesn't profit from it, sure. But that also holds for
> things like hardware-raid or even SCSI. We still want those in though.
This thingie is nice for embedded use, where you need a webserver
for some stuff, but don't wan't to include one, because you need
it only to represent some machine values of a process
computer[1].
But we need a more generic one, which has the functionality of a
read only entry of /proc.
That would be _very_ useful.
Regards
Ingo Oeser
[1] Don't know the right translation for "Prozessrechner", Sorry ;-(
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< come and join the fun >>>>>>>>>>>>
-
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 15:26 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 [this message]
2001-01-12 8:11 ` David S. Miller
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=20010112172545.H10035@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=arjan@fenrus.demon.nl \
--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®