1. The A1 patch has a small error - after patching your kernel your makefile will have a line with : HOSTCC gcc296 you should change it back to HOSTCC gcc if you want your kernel to compile (in most cases). ingo should fix this soon. 2. The new release also contains a fix to a buffer overflow i posted about at 22/1/02 http://www.redhat.com/mailing-lists/tux-list/msg01607.html The risk of it being used is low, but it exist. 3. since there is no documentation about how to use the expires header functinality yet, available in the new patch, here is a propused update to the docs i sent Ingo : TUX supports "Cache-Control: max-age=x" http extention starting with version 2.2.1 and kernel patch 2.4.17-A1, in addition to the basic cache-control properties like "ETag" and "Last-Modified" http headers. While the basic properties allow the client browser to know wheither the content in it's cache is up-to-date while communicating with the server, this new feature allows browsers and proxies to cache the server's response for the specified time without the need to reconfirm with the server every time the content in it's cache is accessed, reducing content load time for users, bandwidth and server resources usage. Expiration time is set on a per file extention basis, in /etc/tux.mime.types discusses in previous paragraph. While a standard entry may look like below : text/html htm html you should use the following format to assign expiration time to a file extention : text/html htm|1800 html|1800 This will set the expiration time for htm and html files to 1800 seconds, or half an hour. If no expiration time provided for a file extention, no "Cache-Control" directive will be issued while serving the file. You may set different expiration time for every extention, even if they belong to the same mime type : text/html htm|1800 html|3600 or text/html htm|1800 html * you may disable this feature on a server-wide basis by setting the generate_cache_control parameter in /proc/sys/net/tux to 0 Enjoy.