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 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.