It's either non-transparancy _or_ the exclusion of one of
both access methods to non-albod-aware apps.
If we make it non-transparent (maybe with some magic required
from the user), we can at least grant the user the possibility
of accessing the albod as a file _and_ as a directory.
I don't know what you want, but I take flexibility over
newbie-friendlyness every day...
Rik -- Open Source: you deserve to be in control of your data.
+-------------------------------------------------------------------+
| Le Reseau netwerksystemen BV: http://www.reseau.nl/ |
| Linux Memory Management site: http://www.linux.eu.org/Linux-MM/ |
| Nederlandse Linux documentatie: http://www.nl.linux.org/ |
+-------------------------------------------------------------------+
-
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/