what is necessary for directory hard links
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Horst H. von Brand
Joshua Hudson <[email protected]> wrote:
[...]
Quoted 8 lines
Quoted 4 lines
Maybe someday I'll work out a system by which much less is locked. Conceptually, all that is requred to lock for the algorithm to work is creating hard-links to directories and renaming directories cross-directory.
Some 40 years of filesystem development without finding a solution to that conundrum would make that quite unlikely, but you are certainly welcome to try.
There is a simple solution against loops: No directory may contain a directory with a lower inode number.
Off cause this would interfere with normal operations, so you'll allocate all normal inodes above e.g. 0x800000 and don't test between those inodes.
If you want to hardlink, you'll use a different (privileged) mkdir call that will allocate a choosen low inode number. This is also required for the parents of the hardlinked directories.
You can also use the generic solution: Allow root to shoot his feet, and make sure the gun works correctly.
Signature · 4 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren. http://david.woodhou.se/why-not-spf.html