hi Did any of you read the documentation of Elektra ?
http://elektra.sourceforge.net/ If you ask me , Elektra is not even remotely similar to MS's Registry. It's only an API to manage little (human-readable) text files. (I even sent a patch once to make text files more readable - to prepend # marks on comments and metadata, but i guess Avi didn't like it =\ oh well) The old name - "Linux Registry" gave me the creeps too, but now I understand it's a totally different thing. They already started writting patches for some programs/projects. AFAIK the XF86/xorg, fstab ... and some more patches are ready, apache is a work in progress some other patches will follow. So what's so bad about using Elektra ? I, for one, welcome our Elektra overlords. :) Regards, Shlomil. -------------------------------------- for the lazy ones: Few facts about Electra (quoted from the site) : It is much more an agreement then a piece of software. Relation is 99% to 1%. It is a simple and consistent API to help software developers programatically store and retrieve global and user-specific configuration parameters. All key-value pairs are stored in clear-text files, UTF-8 encoded. All old charsets are also supported, with automatic transparent conversion to and from UTF-8. API supports change notifications and multiple backends It provides a unique namespace for all values. Anywhere, anytime, any program can preciselly access keys by their names. Security restrictions may obviously apply. It is designed to be secure and lightweight, to let even early boot-stage programs like /sbin/init to use it, instead of /etc/inittab file. It is designed to be easy to administrate with regular command line tools like cat, vi, cp, ls, ln. Its storage is 100% open. It tries to set distribution-independent naming standards to store things like hardware configuration, networking, user's session configuration, system's mime-types, parameters for kernel modules, etc, that are generally stored under /etc. It requires existing software to be changed to use its API. This will substitute hundreds of configuration-text-file parsing code, into clear Elektra's API key-value access methods. It is POSIX compliant. If it doesn't compile and run easily on some POSIX system, it should be easily modified to do so. On Wed, 23 Mar 2005 23:48:52 +0200, Shachar Shemesh <[EMAIL PROTECTED]> wrote: > Nadav Har'El wrote: > > >One major difference in philosophy between the Windows registry and the > >Unix /etc is that the former was never ever meant to be manually read > >or modified by users, and the latter was mainly intended for manual > >modification. > > > > > Don't get me wrong. Not for one second. I will not try to claim that the > registry is a good solution. The very fact that it offers posix > semantics (changes are seen immediately, no locking) in a world that > does not work this way for the main data storage (files) will show you > it was probably not very well thought out. It also has no notion of > comments, which I find a crucial part of the Unix config system. Still, > you gotta agree that it does give a consistent view into stuff, and > eliminates the question of "where is my config". > > >And, if you insist on going the Registry way, why repeat Microsoft's > >mistake and create a second heirarchy of data with its own tools to > >modify it, when a heirarchy of data already exists - the file system? > > > > > Because it's not as convenient. Maybe it's because reiser didn't > eliminate ext. Maybe it's the way it's easier to search for things > inside a file than inside the file system, but I don't see that as > working as well. I will agree that it gives the same basic functionality. > > >registry file, XML file, or whatever. > > > > > Oh, I'll also mention that I'm with you on "XML is not for humans" and > "config files should be". > > Shachar > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
