Hi all,
On Tue, Jul 25, 2006 at 03:09:56PM -0300 Avi Alkalay wrote:
> Patrice, pluggable backends were implemented to satisfy the
> open source community's desire for flexibility, and introduced
> a considerable amount of administration complexity. But it made
> Elektra be more modularized and fancy.
>
> We discussed before how to define a default backend, the use of
> environment etc, and we found that and envvar is not secure
> enough. The other option was to have a configuaration file for
> Elektra, which doesn't makes much sense for a system that wants
> to eliminate configuration files. Anyway, the simplest and most
> secure way we could think was to create a symlink.
[...]
> Do you have a better idea on how to define a default backend ?
Since this is type of a chicken-egg-problem,
I think, _one_ configuration file (that for elektra) would
be ok, i.e. one per "service". I think of something like
/etc/pam.d/ ....
But as I probably missed most of the discussion, please help
me by providing some links back to the discussion, so that I can
better understand the arguments against one central config file.
Thanks in advance!
Best regards -
MgE
--
Voluminous documentation | Matthias G. Eckermann <[EMAIL PROTECTED]>
is part of the problem | Marienburger Straße 5A
not part of the solution | 10405 Berlin
(Tom DeMarco) | phone +49-30-44315730
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Registry-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/registry-list
