Apple doesn't support trash directories (or temporary item directories) on
network volumes and hasn't for quite a while because there is no good mechanism
to clean up trash on network volumes (i.e., if a user mounts a network volume,
moves files to the trash, unmounts the network volume, and
> On Jun 30, 2016, at 6:49 PM, tridiak wrote:
> Some questions concerning APFS
Have you looked at an APFS file system in the WWDV seed? Have you watched the
WWDC presentation? Those would answer a lot of your questions.
> - My guess is resource forks are being dropped.
Q_MOUNT kernel event and that's what causes the kNotifyVFSMount BSD
notification to be sent. At that time, file systems must be ready to respond to
requests correctly. If they don't, they have a bug.
> On Sat, 1 Apr 2017, Jim Luther wrote:
>> Scott, if you walk through that code
As -[NSURL getResourceValue:forKey:error:] is documented, "If this method
returns YES and the value is populated with nil, it means that the resource
property is not available for the specified resource, and that no errors
occurred when determining that the resource property was unavailable."
>> the FUSE kext thus far. It seems to be setting VOL_CAP_FMT_2TB_FILESIZE
>> when it should be.
>> On Mon, 3 Apr 2017, Jim Luther wrote:
>>> On Apr 3, 2017, at 8:56 AM, Scott Talbert <s...@techie.net>
FSCatalogSearch is part of the deprecated Carbon File Manager API. The Carbon
File Manager API exposes file IDs and directory IDs as 32-bit values and so
FSCatalogSearch will never be supported on APFS (which use 64-bit file IDs and
• PBCatSearch on APFS volumes will
As things work today...
When a user drags a file system volume out the Devices sidebar list, the
Visibility is set to NeverVisible for that device in the list (as you can see
below). The Bookmark is a URL bookmark object (serialized) used to determine
which file system volume should be hidden
le byte chars. So it
> is curious that the working HFS somehow ends up with 2 byte chars.
> When trying to parse the Alias data, it will fail as the string length 36,
> being longer than the rest of the data, presumably because the length 18
> (0x12) as been doubled in anticipation of
Here's something that is kind of related that I ran into recently.
If you have code that is checking the ownership and permissions of a file
system object and attempting to correct the ownership and permissions if it is
wrong, don't bother if the MNT_IGNORE_OWNERSHIP mount flag is set --
In contentsOfDirectoryAtURL, instead of "includingPropertiesForKeys:nil", use
"includingPropertiesForKeys:@[NSURLVolumeIdentifierKey]" (and add whatever
other property keys you know you'll need). The whole purpose of the
includingPropertiesForKeys argument is so the enumerator code can
> On Apr 29, 2019, at 1:19 PM, Thomas Tempelmann wrote:
> In contentsOfDirectoryAtURL, instead of "includingPropertiesForKeys:nil", use
> "includingPropertiesForKeys:@[NSURLVolumeIdentifierKey]" (and add whatever
> other property keys you know you'll need). The whole purpose of
I don’t really have time to look at the current fts implementation, but… it has
several options that effect performance (in particular, the FTS_NOCHDIR,
FTS_NOSTAT, FTS_NOSTAT_TYPE, and FTS_XDEV options). If you are trying to
compare fts to CFURLEnumerator (for example), use FTS_NOCHDIR and
> There's also a test project trying out the various methods.
> Any comments, insights, clarifications and bug reports are most welcome.
> Thomas Tempelmann
>> On 12. Jan 2015, at 17:33, Jim Luther > <mailto:luthe...@apple.com>
Mail list logo