public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john slee <indigoid@higherplane.net>
To: "David S. Miller" <davem@redhat.com>
Cc: dank@kegel.com, khttpd-users@alt.org, linux-kernel@vger.kernel.org
Subject: Re: khttpd rotten?
Date: Thu, 9 May 2002 21:40:09 +1000	[thread overview]
Message-ID: <20020509114009.GD3855@higherplane.net> (raw)
In-Reply-To: <3CD5CE35.3EF2B62E@kegel.com> <20020505.191422.11638807.davem@redhat.com>

On Sun, May 05, 2002 at 07:14:22PM -0700, David S. Miller wrote:
>    From: Dan Kegel <dank@kegel.com>
>    Date: Sun, 05 May 2002 17:28:37 -0700
>    
>    If I didn't need it for a demo this week (don't ask), I
>    wouldn't be messing with khttpd; I'd be switching to Tux.
>    
>    Seems like it's time to either fix khttpd or pull it from the kernel.
>    
> We are going to pull it from the kernel.
> 
> The only argument is whether to replace it with TUX or not.
> There is a lot of compelling evidence that suggests that
> reasonably close performance can be obtained in userspace.
> 
> I guess the decision on TUX is not a prerequisite for pulling
> khttpd though.

people who want tux are probably going to want some other related bits
and pieces.  this is a distribution issue.  remove khttpd (even if it is
suddenly maintained again) and let it and tux both be external entities.

tux is more an application than an interface or mechanism.  applications
historically haven't been distributed as part of the main kernel tree.

j.

-- 
R N G G   "Well, there it goes again... And we just sit 
 I G G G   here without opposable thumbs." -- gary larson

  parent reply	other threads:[~2002-05-09 11:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06  0:28 khttpd rotten? Dan Kegel
2002-05-06  2:14 ` David S. Miller
2002-05-06  2:39   ` Dan Kegel
2002-05-06 10:23     ` Christoph Hellwig
2002-05-06 11:28       ` [PATCH] " Dan Kegel
2002-05-06 17:23       ` Luigi Genoni
2002-05-09  9:49       ` David S. Miller
2002-05-09 10:09         ` Christoph Hellwig
2002-05-09 13:04           ` Luigi Genoni
2002-05-11  0:13             ` Ken Brownfield
2002-05-06 14:17     ` Tux in main kernel tree? (was khttpd rotten?) Roy Sigurd Karlsbakk
2002-05-06 16:08       ` Andy Carlson
2002-05-06 23:35         ` Anton Blanchard
2002-05-07 14:42         ` Alan Cox
2002-05-07 15:03           ` Andrea Arcangeli
2002-05-07 15:26             ` Alan Cox
2002-05-07 15:38               ` Andrea Arcangeli
2002-05-07 16:02             ` Luigi Genoni
2002-05-06 17:21       ` Dan Kegel
2002-05-06 18:42       ` John Stoffel
2002-05-06 19:07         ` Diego Calleja
2002-05-06 19:18           ` Cort Dougan
2002-05-06 20:47         ` Michael Rothwell
2002-05-09 11:20           ` Appications in kernelspace (was:Tux in main kernel tree?) Anders Peter Fugmann
2002-05-06 21:52         ` Tux in main kernel tree? (was khttpd rotten?) Paul Jakma
2002-05-09 11:28           ` john slee
2002-05-07  3:00         ` J Sloan
2002-05-09 11:40   ` john slee [this message]
2002-05-09 11:29     ` khttpd rotten? David S. Miller
2002-05-09 19:30       ` Andrew Morton
2002-05-09 19:35         ` David S. Miller
2002-05-09 19:39           ` Martin Dalecki
2002-05-10 10:20         ` Andi Kleen
2002-05-10 10:49           ` David S. Miller
2002-05-09 20:12     ` Ian Molton

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=20020509114009.GD3855@higherplane.net \
    --to=indigoid@higherplane.net \
    --cc=dank@kegel.com \
    --cc=davem@redhat.com \
    --cc=khttpd-users@alt.org \
    --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