You have to put in some sanity checks to avoid the directory fork
getting messy for regular files. I'd recommend a "restricted"
directory which can't contain
(a) non-regular files, including directories and symlinks
(b) files with more than one link (think about why).
It also doesn't need the . and .. entries and should not be allowed to
chdir() or chroot() into.
Other than that, the idea looks particularly good because it avoids
the need for a resource manager library to put structure in.
> Only requires figuring out semantics for the
> struct-stat.st_mode field.
That's simple: it defines the default for open() and the checks
mentioned above.
olaf
-
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/