--- web/www/libstatgrab/index.xhtml 2005/03/09 10:43:07 1.37 +++ web/www/libstatgrab/index.xhtml 2006/10/09 15:09:07 1.44 @@ -41,6 +41,7 @@ +

What is libstatgrab?

@@ -80,6 +81,56 @@ freshmeat?

+ Monday 20 March 2006 +

+

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

+

+ Sunday 31 July 2005 +

+

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

+

+ Tuesday 26 April 2005 +

+

+ Official libstatgrab packages for Debian now + available. +

+

+ Thanks to the work of + Bartosz Fenski + libstatgrab is now available on debian. This replaces our + unofficial debian packages which will no longer be + updated. +

+

Thursday 3 March 2005

@@ -214,7 +265,7 @@ Here are links to bindings for higher level languages that provide access to libstatgrab. If you've written a binding for another language, please get - in touch so we + in touch so we can add a link here.

@@ -231,9 +282,12 @@ Solaris (Blastwave)
  • - Debian (unofficial) + Solaris (SunFreeware)
  • + Debian +
  • +
  • NetBSD
  • @@ -272,50 +326,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: