--- web/www/libstatgrab/index.xhtml 2005/04/26 10:34:18 1.39 +++ web/www/libstatgrab/index.xhtml 2007/07/13 21:56:52 1.48 @@ -41,6 +41,7 @@ +
+ Version 0.15 of libstatgrab has been released.
+ Download it from one of our mirrors.
+
+ This release fixes a regression introduced on OpenBSD in + the last release - memory statistics were reported + incorrectly. Some other minor changes have been made, see + the NEWS file for more information. +
+
+ Version 0.14 of libstatgrab has been released.
+ Download it from one of our mirrors.
+
+ This release contains mainly bugfixes - see the NEWS file + in the distribution for a full list. It also brings a new + feature in saidar: colour support, which can be activated + with the -c runtime flag. +
+
+ Version 0.13 of libstatgrab has been released.
+ Download it from one of our mirrors.
+
+ This release mainly includes a bunch of bug fixes, but + also brings preliminary support for WIN32. We've also + added a few lines to the header file to make C++ linking + easier. Please see the NEWS file in the distribution for + full details. +
+
+ Version 0.12 of libstatgrab has been released.
+ Download it from one of our mirrors.
+
+ This release has some new features, bug fixes, and a minor + API change. More details have been added to the file + system statistics, linux partition detection has been + reworked, and compile errors on Linux 2.6 have been fixed. + Support has been added for Solaris 10 and FreeBSD 7. + There are also manual pages for all the tools. +
++ The duplex value in the network interface statistics has + changed name from "dup" to "duplex" - this breaks the API. + We plan to stabilise the API for a 1.0 release. As before, + the old name is available if SG_ENABLE_DEPRECATED is + defined. +
+@@ -194,7 +257,7 @@
pystatgrab, a new package containing a set of Python - bindings, has been released. Check out it's + bindings, has been released. Check out its project page.
These are various pre-packaged versions of libstatgrab @@ -286,50 +355,67 @@
The only online documentation we have at the moment is the - manual pages converted in to HTML format. It's probably - best to start with the overview manual page: + manual pages converted in to HTML format. First are the + manual pages for the command line tools:
+ We also have an overview page for the library: +
+Then we have the manual pages for each function: