Re: Thinking outside the box on file systems

[alan <alan@clueserver.org>]

On Tue, 14 Aug 2007, Marc Perkel wrote:

> For example. If you list a directory you only see the
> files that you have some rights to and files where you
> have no rights are invisible to you. If a file is read
> only to you then you can't delete it either. Having
> write access to a directory really means that you have
> file create rights. You can also delete files that you
> have write access to. You would also allocate
> permissions to manage file rights like being able to
> set the rights of inferior users.

Imagine the fun you will have trying to write a file name and being told 
you cannot write it for some unknown reason.  Unbeknownst to you, there is 
a file there, but it is not owned by you, thus invisible.

Making a file system more user oriented would avoid little gotchas like 
this.  The reason it is "programmer oriented" is that those are the people 
who have worked out why it works and why certain things are bad ideas.

--
Refrigerator Rule #1: If you don't remember when you bought it, Don't eat it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/