From: J Sloan <joe@tmsusa.com>
To: tux-list@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: tux officially in kernel?
Date: Mon, 11 Feb 2002 08:36:55 -0800 [thread overview]
Message-ID: <3C67F327.8010404@tmsusa.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0202111313100.28040-100000@mustard.heime.net>
If that's not part of the roadmap I'd be surprised,
since tux is so much more capable than the
khttpd which is currently part of the tree.
Tux has clearly demonstrated it's performance
and low resource consumption.
I also think including tux in the mainline kernel
would further stimulate development, as folks
begin to realize what they can do with tux....
At least Red Hat seems committed to it.
IMHO of course...
Joe
Roy Sigurd Karlsbakk wrote:
>hi
>
>Are there any plans to move Tux into the official kernel?
>
>roy
>
>--
>Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
>
>Computers are like air conditioners.
>They stop working when you open Windows.
>
>
>
>
>
>_______________________________________________
>tux-list mailing list
>tux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/tux-list
>
next prev parent reply other threads:[~2002-02-11 16:37 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 [this message]
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
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=3C67F327.8010404@tmsusa.com \
--to=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tux-list@redhat.com \
/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