Re: crashes / khttpd

"Alex Kramarov" <[email protected]>
Newsgroups gmane.network.tux
Message-ID <[email protected]>
This is as i suspected. Ingo didn't advance version numbers with the new
patches. 

trust me, the patch in redhat's kernel is a year old - you don't want to run
this in production, and even if you do, it won't work as well as you would
like to expect, unless you like your cpu to go 99% every few days/weeks.

i suspect that redhat do not integrate the new patch into their kernel
because they are pushing their tux-based product they sell...
 
-------Original Message-------
 
From: [email protected]
Date: éåí ùìéùé 15 àå÷èåáø 2002 23:15:22
To: [email protected]
Subject: Re: crashes / khttpd
 
> and please, please, do not state that the version of tux you are running
is
> 2.2.7 or any other such number. This is the version of the userspace
> utilities ONLY. Tux version is in the /include/tux.u.h file of the kernel,
> and the latest is 2.1.1, although i am not sure that it get's updated
> whenever a new kernel patch is released, so the best way is just to state
> that you are running the
> tux2-full-2.4.18-final-A3 patch.
 
Sorry! You are right. My version is 2.1.1. I didn't patch the kernel by
myself 
so I don't know which patch was used, but I think they just got the vanilla 
2.4.18 and the tux2-full-2.4.18-final-A3 patch.
I didn't recognize that the version numbering sheme is differing between the

TUX-kernelmodule Version and the userspace programs.
 
Thanks
Marco.
 
 
 
_______________________________________________
tux-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/tux-list
 
.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.