Re: Tux Patch for Linux-2.4.21-rc1

Xose Vazquez Perez <[email protected]> Mon, 14 Jul 2003 05:52:20 +0200

Newsgroups	gmane.network.tux
Message-ID	<[email protected]>

Shane Allen wrote:

> I hit http://people.redhat.com/mingo/TUX-patches/ and see that the
> userspace modules in there are version 2.2.7 (5/5/02), and the latest
> kernel patch is 2.4.18-A3 (2/4/02)...
> 
> Why then is rawhide using 2.4.15, and where did 2.2.10 user-space utils
> come from?

looks like someone inside redhat is maintaining TuX.

--tux.spec--
[...]
* Fri May 30 2003 Michael K. Johnson <[email protected]> x.2.12-1
- Fixed protocol version 3 support, then re-fixed version 2 support to match.

* Fri May 09 2003 Michael K. Johnson <[email protected]> x.2.11-1
- Added support for 32-bit userland with 64-bit kernel
   o Requires new protocol version 3
   o major version of package matches protocol version
   o Package can be built to support protocol versions 2 and 3.

* Wed Mar 12 2003 Michael K. Johnson <[email protected]> 2.2.10-1
- add hammer support #86025
[...]
--end--

latest tux at rawhide:
tux-3.2.12-2.src.rpm 13-Jun-2003 20:20 68K

and latest kernel code, *with rh support*, is inside the red_hat_9
kernel 2.4.20-18.x (linux-2.4.15-tux2.patch)

but I think that there is newer code in Advance_Server-3 beta.

regards,
-- 
Software is like sex, it's better when it's bug free.

NEWS (text/plain, 2.3 KB)

NEWS since tux 1.0

In preparation for future multi-protocol support, the /proc/net/http
and /proc/sys/net/http directories have been renamed to
/proc/net/tux and /proc/sys/net/tux, respectively.  In addition,
max_cached_filesize was changed to max_object_size, and several
new entries were added, as well as obsolete entries removed.  There will be
future changes as well as new protocols are added, be aware.  See the
manual for information on the currently available tunable parameters.

The tux daemon's command line arguments have changed; tux now uses popt
to manage its command line so you can use standard popt option handling
mechanisms like /etc/popt.  You do not need to know about these changes
if you use the standard tux init script, only if you run the tux daemon
by hand.

TUX now has support for gziped data streams.  The manual describes
how to make use of it; basically, under certain stringent circumstances
TUX will fulfill a request for a URL foo with the contents of foo.gz.
This features is disabled by default.

TUX now uses /etc/tux.mime.types as its source of mime types.

The counttux program has been replaced by the -c option of tux2w3c.

The stoptux program has been replaced by the -s (--stop) option of tux.

TUX modules no longer must reside in the docroot, they can be put
anywhere you like.

TUX modules are now executed by default as user/group "nobody".
However, this does not mean that you should execute untrusted
modules -- they are opened as user/group root, which means that
the _init() function, if it exists, is run as root.  This feature
is only designed to help protect from programming mistakes; it
is NOT really a security mechanism.

As of TUX protocol major version 3, TUX can now function on systems
with a 64-bit kernel and a 32-bit userland.  When using TUX protocol
major version 3, you MUST put the line
TUXAPI_declare;
in some part of your module, after you #include <tuxmodule.h>
If you are writing a module which may be used with TUX protocol
major version 2, you MUST use ifdef to protect that declaration:
#ifdef TUXAPI_declare
TUXAPI_declare;
#endif
You must include this exactly once in your module.  It flags the
protocol version supported by the module.  Modules without a
protocol version are assumed to be using TUX protocol major
version 2.