Re: Thinking outside the box on file systems



Kyle Moffett wrote:
Basically any newly-created item in such a directory will get the
permissions described by the "default:" entries in the ACL, and
subdirectories will get a copy of said "default:" entries.

This would work well, although I would give write permissions to a group
so the entire dir wouldn't need to be re-ACLed when a user is added. I
may give this a shot; I've been avoiding ACLs because they have always
sounded incomplete/not useful, but the inheritance aspect sounds rather
nice.

So yes, such functionality is nice; even more so because we already have
it. I think if you were really going to "extend" a UNIX filesystem it
would need to be in 2 directions:
(A) Handling disk failures by keeping multiple copies of important
files.

This is ZFS' bailiwick, no? I'd love to see the licensing issues
resolved, because if it can control level of redundancy on a
per-file/directory basis, I would be a very happy man.

(B) Have version-control support

This might be pushing it, but hey, we *are* talking about the future here.

(C) Allowing distributed storage (also lazy synchronization and
offline modification support)

I'd really love to see distributed storage not suck. Everything I've
seen requires myriad daemons and ugly configuration.

With some appropriate modifications and hooks, GIT actually comes pretty
close here. For larger files it needs to use a "list-of-4MB-chunks"
approach to minimize the computation overhead for committing a
randomly-modified file. The "index" of course would be directly read
and modified by vfs calls and via mapped memory. Merge handling would
need careful integration, preferably with allowing custom
default-merge-handlers per subtree. There would be lots more design
issues to work out, but it's something to think about

Now you're just being silly ;)

Cheers,
Kyle Moffett

-- m. tharp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: Win2k - Account Operator not working properly
    ... You very likely have other ACL issues other than what was mentioned and I can point them out here for you for free or you can pay someone $200-500 an hour to come check it out. ... In order for that to result in inheritence protection it means the schema had to be modified. ... set the account in the GUI to inherit from its parents. ... Used the delegation wizard, on the top level OU, to assign the desired permissions. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrationn from Exch 5.5 on NT to Exch 2003 on 2003
    ... Jason Tan wrote: ... Security translation is a function of ADMT 2.0 that updates access control lists when migrating objects across domains. ... subinacl is recommended to reset the permissions in this scenario. ... you may use subinacl to replace the ACL. ...
    (microsoft.public.windows.server.migration)
  • Re: Security Group Keeps getting removed???
    ... ACL on all security principals (users, groups, and machine accounts) present ... Delegated permissions are not available and inheritance is automatically ... AdminSDHolder Object Affects Delegation of Control for Past Administrator ...
    (microsoft.public.windows.server.active_directory)
  • Re: cant delete USB registry items...
    ... I used SHDeleteKey and RegDeleteKey without any problem, ... proper permissions are set for the Enum key. ... >> registry entries are created... ...
    (microsoft.public.development.device.drivers)
  • Re: Permissions resetting in Blocked Inheritance OUs
    ... If the ACL that is on the AdminSDHolder object is ... Delegated permissions are not available and inheritance is automatically ... "You do not have sufficient permissions in the Domain" error message occurs ... This user account is in an OU that has Blocked ...
    (microsoft.public.windows.server.active_directory)