> Any implementation is fine really.
>
> There have been many stats projects in the past that have failed due to
> various reasons. A simple question is: How are you planning on making
> your idea/proposal not fail? ;)

As Dylan Hunt would say: "By making it right : )" ( with the smile ).

__

The simple answer :

The server:
- will wait for clients to send information about the system
- will tell about the statistics they want
- will print an overall statistic if nothing specified
- register clients, the registration will be optionally set with an
expire value, or by default
  one month ( the expiration timer is reseted on every update by the client )

The client ( a daemon on the client machine ):
- periodically will check different kind of interesting things
  - in cases of device checks, the daemon will check on start up, as
it is added as init
    script to default level
  - arch - again on start up
  - in case of installed packages, the daemon will check them
periodically. default will be
    one week or user defined ( no more than the defined expiration
date by the server )
- will choose, from a list of activated modules, what information to send

Optional:
- GUI interface to configure the daemon on the client machine using GTK.

__

I don't have anything specific in mind for the server configuration,
but it could be via a
simple text file.

I have been exposed to the MVC idea, so of course I intend to separate
logic, presentation,
and storage of information.

__

Some information about me:

I'm from Bulgaria ( GMT+2 ). First year in Informatics at an
university. I'm using gentoo
since 2007 and of course I intend to continue using it : )
I have experience with Perl and C/C++ ( I still haven't read the
second vol of Thinking in C++, but I feel ready for it ).

No experience with open source/ and free/ projects.

Ah, my name is ( by id card ) Ivaylo Ilionov and I'm 21 years old : )

Any questions or suggestions are welcomed. If I annoyed you with
something - sorry.