Re: [Helidelinux-devel] Linux registry

[Rolf V. <rol...@he...>]

Hui Zhou wrote:

>> My (old) idea was to create a /data directory and a dpath command 
>> so that we could have:
> 
> I don't see the reason why you have to put everything into a specific
>  folder. The root directory info can be the root node of the path
> construction, so dpath will always know where to look.

I'm thinking about a clean name space, not depending on the particular
system design: you may like to put all system data in /etc, I may
like to have package info in /pkg/<package>/data, and so on. For
each particular system design, a set of rules would apply.

> I am thinking on that. There must be some schemes so dpath can tell 
> easily whether a text file is an ogdl file and an binary is safe to 
> execute and produce ogdl stream. Otherwise, how can it prevent it 
> from executing wrong binary and crashing the system or corrupting the
>  data?

dpath should only access OGDL directory trees, not any directory (That
functionality can be left for gpath). I'm thinking about these
sub-namespaces for my implementation:

system.*          -> $SYSDATA/*
pkg.<package>.*   -> $PKG/<package>/$DATADIR/*
user.*            -> $HOME/$DATADIR/*
users.<user>.*    -> /home/<user>/$DATADIR/*

Anything in these trees should be 'dpath compatible'.

> And as an alternative, how does a data base compared with registry?

In terms of ?

Registry uses no additional database so as to minimize dependencies
and gain simplicity and editability. For large data sets databases
can be faster.

> What is ACL?

ACL stands for Access Control Lists. It allows finer grained
security. A good explanation is:

http://www.suse.de/~agruen/acl/chapter/fs_acl-en.pdf

Rolf.