xmlsysinfo-talk Mailing List for XMLSysInfo
Brought to you by:
grmo
You can subscribe to this list here.
2007 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Moritz G. <md...@gm...> - 2009-07-18 15:15:23
|
Hello subscribers, as it is now bleeding obvious, various reasons caused the XSI project to plunge into despair and neglect. I am now trying to "reboot" the whole thing. When I started it, my life circumstances allowed me to work on XSI almost full-time over long periods. This hasn't been the case for a long time now, and various other projects of higher immediate importance ate up all the remaining free time. XSI needs to adapt to these changes, to be able to move forward. As part of the cleaning process, I will shut down anything non-essential related to project management, soon. Among other things, these mailing lists have shown to be completely superfluous and will go away. All these SourceForge features are nice and shiny, but well ... something like XSI does not need community self-support, at least not now. If you have any inquiries, please feel free to contact me directly under my new address mgrimm at mrsserver dot net. In any case, thanks for being here! A few last words: - Unless something really unforeseen happens, XSI and related things are not dead. I for myself still have use for a networked system monitor that Just Works. - Still, no guarantees on the "when". Things will, overall, progress slowly. - There will be an extensive overhaul of the code base eventually, as well as an "XSI Aggregator" of sorts that collects information from hosts running XSI. - It is of high priority to achieve the former without changing the output XSL schema in a major-version-1 release. If that turns out to be impossible, there will be XSI 2 (with as few output changes as possible.) - *Maybe* some kind of front-end, but it'll be an ugly mock-up. I suck at GUIs. All the best, Moritz |
From: Fabrizio R. <fre...@gm...> - 2008-04-19 07:34:47
|
Hi everybody! Does anybody know if there's a client project for xmlsysinfo? I was looking for a program like this to grab system status informations to a flash client. Xml is the best choiche for such purpose, so I'm glad i found it. The thing I'd like to craft would be something like a 'multi server status control panel', which is probably not much different from what nagios already does. Nagios does a lot of stuff actually, and I was first wondering on how to translate nagios data file into xml to be pushed to the flash client. Then I found Xsi, which seems a better solution to me, and I'd like to invest some time on it. There's a lot of stuff to work on an I'd know if there's some thougth around it at the moment. Is the project willing to evolve, or is this the hadline? Thanks, bye |
From: tyju t. <jck...@ya...> - 2007-12-08 23:15:42
|
Hi Moritz, Thanks for the help ... it's working beautifully now! Thanks again, Ty ----- Original Message ---- From: Moritz Grimm <md...@gm...> To: xml...@li... Sent: Saturday, December 8, 2007 5:23:28 AM Subject: Re: [xmlsysinfo-talk] Unable to link with libxml Wow, hey, a user! :-) tyju tiui wrote: > I'm having some trouble compiling xsi on Red Hat Fedora Core 4. > When running the configure script I get "Unable to link with libxml"? > > I have libxml2-devel installed ... not sure what I'm doing wrong. > > Any help would be appreciated. From the looks of your configure.log file, I'd say that you're missing a C++ compiler. Try to find and install the appropriate g++ package for FC4. Hth, Moritz ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ XMLSysInfo-talk mailing list XML...@li... https://lists.sourceforge.net/lists/listinfo/xmlsysinfo-talk ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs |
From: Moritz G. <md...@gm...> - 2007-12-08 10:23:33
|
Wow, hey, a user! :-) tyju tiui wrote: > I'm having some trouble compiling xsi on Red Hat Fedora Core 4. > When running the configure script I get "Unable to link with libxml"? > > I have libxml2-devel installed ... not sure what I'm doing wrong. > > Any help would be appreciated. From the looks of your configure.log file, I'd say that you're missing a C++ compiler. Try to find and install the appropriate g++ package for FC4. Hth, Moritz |
From: tyju t. <jck...@ya...> - 2007-12-08 06:17:42
|
Hi, I'm having some trouble compiling xsi on Red Hat Fedora Core 4. When running the configure script I get "Unable to link with libxml"? I have libxml2-devel installed ... not sure what I'm doing wrong. Any help would be appreciated. Thanks, Ty ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping |
From: Moritz G. <gt...@gm...> - 2007-01-10 19:22:29
|
Hi, today, xsi-1.0-beta0.tar.gz has been released: This milestone release of XMLSysInfo comes with a large amount of changes, including new features, bug and consistency fixes, cleanups and other improvements. With the development status changed to "beta", the XML Schema is frozen and only bugfixes are allowed from now on. Both XMLSysInfo and the Schema have new versioning schemes, which provide more flexibility while retaining a strict meaning about compatibility between versions. The release note and the changes between 0.98.30 and 1.0-beta0 can be found here: http://sourceforge.net/project/shownotes.php?group_id=185140&release_id=477512 Moritz P.S.: The new versioning scheme is explained in xsi-output.html, in the "schema_version" and "xsi_version" attribute tables. |