Re: what's next for the linux kernel?

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Wed, Oct 05, 2005 at 01:05:30PM -0700, Marc Perkel wrote:
> What you don't understand is that Netware's permissions mechanish is 
> totally different that Linux. A hard link in Netware wouldn't inherit 
> rights the way Linux does. So the user would have rights to their hard 
> link to delete that link without having rights to unlink the file.
> 
> This is an important concept so pay attention. Linux stores all the 
> permission to a file with that file entry. Netware doesn't. Netware 
> calculates effective rights from the parent directories and it is all 
> inherited unless files or directoies are explicitly set differently. So 
> if files are added to other people folders then those people get rights 
> to it automatically without having to go to the second step of changing 
> the file's permissions.

So if you were to moint a partition on /mnt, does the mounted thing now
have to inherit permissions from / and /mnt or from it's own root or
what?

If you chroot something, does it have access to checking permissions
past it's 'virtual' root?

Can users make hardlinks themselves on netware or does an admin have to
do it?

It seems rather inefficient to have to read 8 directories worth of
permissions and calculate them together if you have a file 8 directories
deep compared to doing a single read and compare against a 16bit value +
uid/gid check (ACL of course makes this more complex, but still only
involves reading permissions in one place since inherited permissions
are for create time, not access time).

Unix offers features netware doesn't and some of them require
permissions to work a certain way.

Len Sorensen
-
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/