public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john slee <indigoid@higherplane.net>
To: Ken Brownfield <brownfld@irridia.com>
Cc: Robert Love <rml@tech9.net>, J Sloan <joe@tmsusa.com>,
	linux-kernel@vger.kernel.org
Subject: Re: tux officially in kernel?
Date: Fri, 15 Feb 2002 23:36:42 +1100	[thread overview]
Message-ID: <20020215123642.GB5996@higherplane.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0202111313100.28040-100000@mustard.heime.net> <3C67F327.8010404@tmsusa.com> <20020213135841.GB4826@higherplane.net> <3C6C4942.4050305@lexus.com> <1013730883.807.251.camel@phantasy> <20020214190003.B1518@asooo.flowerfire.com>
In-Reply-To: <20020214190003.B1518@asooo.flowerfire.com>

On Thu, Feb 14, 2002 at 07:00:03PM -0600, Ken Brownfield wrote:
> The problem with X15 is that it's unavailable.  I've tried for months
> and months to get someone at that company to respond or get a copy to
> try.  Also, is it GPL?  Free?

i believe it was free for noncommercial use, a restriction imposed by
the author's company.  i didn't bother to read back on the archives
though so don't accept this as verified fact :-)

> As for TUX, I would certainly prefer user-space if it was indeed as fast

also thttpd is very very fast on linux.  really to need this sort of
performance on modern hardware is quite unusual at least in the public
internet.

> in all cases.  But I don't think X15 is really a factor in TUX's

maybe not x15 on its own.  but the existence of multiple userspace
servers that can provide similar performance may be a good reason to not
include it, as well as ...

> inclusion.  I'd say replacing khttpd with TUX2 is a no-brainer unless
> X15's performance has been proven and it's GPL.  And while khttpd is an

there's no reason why it can't stay as an external patch.  redhat provide
tux rpms for example.  i think khttpd should be removed altogether from
the standard kernel and not replaced with tux.

j.

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

  reply	other threads:[~2002-02-15 12:36 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
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 [this message]
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=20020215123642.GB5996@higherplane.net \
    --to=indigoid@higherplane.net \
    --cc=brownfld@irridia.com \
    --cc=joe@tmsusa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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