WordNet 3.0 for UNIX-like systems (including: Linux, Mac OS X, Solaris) Before you download: The WordNet 3.0 README file contains additional information about the release. You can read about the changes from version 2.1. Source code and binaries: Download tar-gzipped via HTTP: WordNet-3.0.tar.gz or FTP: WordNet-3.0.tar.gz Download tar-bzip2'ed via HTTP: WordNet-3.0.tar.bz2 or FTP: WordNet-3.0.tar.bz2 Download just database files via HTTP: WNdb-3.0.tar.gz or FTP: WNdb-3.0.tar.gz Prolog version of WordNet 3.0 ANSI Prolog version of the WordNet database. Download via HTTP: WNprolog-3.0.tar.gz or FTP: WNprolog-3.0.tar.gz

Scribd is the world’s largest document sharing community, and now you’re part of it. There are lots of things you can do on Scribd, and here are some things that will get you started: Upload and share your documents. Find interesting documents by category, by topic group, by searching, or by just browsing our library. Professional publishers and developers should check out the Scribd Platform. Get the latest announcements and updates at the Scribd Blog.

One thing to be wary of is the number of false-positives coming from chkrootkit. It seems to alert for just about every .* directory it can find on the system, including bits of JDK, volatile tmpfs, and is subject to race-conditions falsely complaining about “hidden” processes when all that’s happened is a few have died since it compared lists. Processes in detached screen sessions seem to show up based on their ttys not being found in utmp. It seems to think my init is `INFECTED’ which is complete hokum. All this because it’s a kludged-up load of shell-scripts relying on grep for ill-defined regexp-matches. So. I’m with rkhunter - it’s far more intelligent in operation, doing things like checking for changes in passwd and root-equivalent users between runs, for example. I can and do run both on all dozen-or-more debian boxes, but I take rkhunter far more seriously and only look for *changes* in output from chkrootkit.