> What does this have to do with capabilities? If a solution is found
> for storing meta-data (capabilities) for arbitrary executables and
> scripts, then a direction is in place to store other meta-data. For
> example, why do we have to have icons, configuration files, logs,
> and whatever splattered all over the file system(s)?
For elf executables it is easy: just add NOTE segments and put
whatever you want into it. Elf executables already _have_ structure
inside. It is not easy to manipulate but it can be done.
Why not add NOTE sections for icons? I could create nice filesystem
into podfuk to manipulate NOTE sections as easily as files... Would it
solve your troubles?
If you did some hack with adding tar files at the end of executables,
you could do your proposed things with minimal changes! Take a look at
podfuk.
Pavel
PS: Or you may go for tar files. On my system [this already works]:
cat file.tar | uuenpipe | mail you
will work, and even
cat file.tar#utar/some.file | uuenpipe | mail you.
Without modification on kernel! This might be solution for many of
your
problems. (http://atrey.karlin.mff.cuni.cz/~pavel/podfuk/podfuk.html).
-- I'm really pavel@ucw.cz. Look at http://195.113.31.123/~pavel. Pavel Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/