Searched hist:bc96e8f30cd209672c33293f0e5c71e81027d3e2 (Results 1 – 4 of 4) sorted by relevance
/haiku/src/tools/ |
H A D | rm_attrs.cpp | bc96e8f30cd209672c33293f0e5c71e81027d3e2 Fri Jun 07 00:27:48 UTC 2013 Ingo Weinhold <ingo_weinhold@gmx.de> Add more robust generic attribute emulation variant
The new configure option "--use-xattr-ref" enables an xattr assisted variant of the generic attribute emulation. Instead of using the inode ID of a node to identify its attribute directory, we use a reasonably unique random 128 bit number, which we generate and attach as an attribute to the node. This way, when a node changes its inode ID (defragmentation?) or the inode ID of a removed node with a left-over attribute directory is reused, attributes won't get mixed up.
The old method is still used for symlinks (since on Linux only priviledged users can write attributes on symlinks), but those usually only have a rather boring BEOS:TYPE attribute, so mix-ups wouldn't be that problematic anyway.
|
/haiku/src/build/libroot/ |
H A D | fs_attr_generic.cpp | bc96e8f30cd209672c33293f0e5c71e81027d3e2 Fri Jun 07 00:27:48 UTC 2013 Ingo Weinhold <ingo_weinhold@gmx.de> Add more robust generic attribute emulation variant
The new configure option "--use-xattr-ref" enables an xattr assisted variant of the generic attribute emulation. Instead of using the inode ID of a node to identify its attribute directory, we use a reasonably unique random 128 bit number, which we generate and attach as an attribute to the node. This way, when a node changes its inode ID (defragmentation?) or the inode ID of a removed node with a left-over attribute directory is reused, attributes won't get mixed up.
The old method is still used for symlinks (since on Linux only priviledged users can write attributes on symlinks), but those usually only have a rather boring BEOS:TYPE attribute, so mix-ups wouldn't be that problematic anyway.
|
/haiku/ |
H A D | configure | bc96e8f30cd209672c33293f0e5c71e81027d3e2 Fri Jun 07 00:27:48 UTC 2013 Ingo Weinhold <ingo_weinhold@gmx.de> Add more robust generic attribute emulation variant
The new configure option "--use-xattr-ref" enables an xattr assisted variant of the generic attribute emulation. Instead of using the inode ID of a node to identify its attribute directory, we use a reasonably unique random 128 bit number, which we generate and attach as an attribute to the node. This way, when a node changes its inode ID (defragmentation?) or the inode ID of a removed node with a left-over attribute directory is reused, attributes won't get mixed up.
The old method is still used for symlinks (since on Linux only priviledged users can write attributes on symlinks), but those usually only have a rather boring BEOS:TYPE attribute, so mix-ups wouldn't be that problematic anyway.
|
/haiku/build/jam/ |
H A D | BuildSetup | bc96e8f30cd209672c33293f0e5c71e81027d3e2 Fri Jun 07 00:27:48 UTC 2013 Ingo Weinhold <ingo_weinhold@gmx.de> Add more robust generic attribute emulation variant
The new configure option "--use-xattr-ref" enables an xattr assisted variant of the generic attribute emulation. Instead of using the inode ID of a node to identify its attribute directory, we use a reasonably unique random 128 bit number, which we generate and attach as an attribute to the node. This way, when a node changes its inode ID (defragmentation?) or the inode ID of a removed node with a left-over attribute directory is reused, attributes won't get mixed up.
The old method is still used for symlinks (since on Linux only priviledged users can write attributes on symlinks), but those usually only have a rather boring BEOS:TYPE attribute, so mix-ups wouldn't be that problematic anyway.
|