[lkml]   [2002]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Tux in main kernel tree? (was khttpd rotten?)
On Tue, May 07, 2002 at 03:42:47PM +0100, Alan Cox wrote:
> Tux has a lot of other things that make it questionable for merging -
> incredibly so for 2.4 - it sticks its fingers into task structs, dcache

I don't buy that, so you may want to give us an answer for why is it
included into the redhat 2.4 kernel if according to you it's incredibly
questionable for merging into 2.4?

I merged it and it's trivial to merge, all "questionable" patches are
obviously safe.

If Marcelo accepts my patches, I will be very glad to replace khttpd
with tux into mainline 2.4. The two products are completly equivalent
and risking to increase the khttpd userbase just because tux isn't in
mainline doesn't make any sense to me, it can only waste resources.
(despite it makes much more sense to use zope, apache, servlets and php
instead of tux for anything real, first of all for security reasons, but
that's another issue, here the issue is khttpd vs tux and this one is a
no brainer)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.091 / U:0.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site