New Remote Configuration App For Linux

Whyte Wolf writes: "Olympus is a new remote administration suite for Linux. Its currently in development by Mount Linux a company based out of Calgary, Alberta. This is a really neat little product, with some cool ideas (I especially like the NetMessage class) and ofcourse, it's Open Source. They're looking at developing a Windows client to allow Win32 users to administer a Linux system remotely."

Comments

Hrmmmm

[Guitarzan]

The obvious sarcastic comment is..."Who wants a win32 user to admin a linux system?"

cheers :)

A config idea

[Metrol]

It seems to me that one of the things that will forever dog linuxconf is it's inability to keep up with server changes. The manner in which they build modules has them constantly changing a rapidly moving target. It seems that this concept these folks are working on may fall into the same category.

This is something I proposed in a Slashdot article a while ago, but it was way late in the conversation. Since this appears to be on topic again, gonna try once again to see what you guys think of it.

The concept revolves around a similar notion to linuxconf in that the idea is to provide a GUI tool for configuring network properties. Instead of trying to develop a unique graphical module for each possible daemon, build an API that looks to definition files. Each of these def files (most likely XML) would contain what text file is used to config a service, what are the possible attributes of that service, and what are the valid values of those attributes. I imagine one could also include the same kind of help text you would normally find in most .conf files.

Rather than trying to reinvent the GUI for all this, instead provide this API as a means for config GUI's to be written. So whether you're writing a config file for KDE, Gnome, or just X they all call to the same API. The API would handle reading the definition files, and writing to the config files as defined.

From what I'm thinking, the .conf files would still be editable from a text editor or be got at with this somewhat more automated process. Instead of having the author of this API be responsible for keeping up to date with every possible daemon out there, it would be up to the daemon writers to provide a definition file to this API.

Good idea, or am I full of it?