Live data from Hacker News

Apple File System

developer.apple.com

141–150 of 406 posts

Re: Apple File System

#141
post #60

Earlier quoted context omitted.

Presumably as with today, you'll have the option. I don't have a strong opinion on case sensitivity of file names, but I suspect they'll keep it case insensitive by default. I think for the average non-technical user that two files, "MyFile.txt" and "myfile.txt", being different could lead to some confusion, and Apple historically has apparently considered that confusion unacceptable.

Steam relies on the filesystem being insensitive.

No it doesn't. How would it work on Linux if it did?

Re: Apple File System

#144
post #31

Earlier quoted context omitted.

ZFS is on a completely open source license. Oracle's beef with Google comes from actions that occurred before Java was open sourced. It's hard to see how the two scenarios are even remotely related, other than "Oracle"

Gruber, who usually has good inside sources, on Apple dropping ZFS[1]: > Word on the street in Cupertino is that dropping ZFS wasn’t an engineering decision, but a legal one, and it might have had something to do with Oracle’s acquisition of Sun. I don’t know if it was a problem with the terms of the CDDL license, general distrust/dislike for Oracle, or what — only that the word came down from legal that ZFS was a no…

The unofficial word is that Apple wanted Sun to sign an indemnification agreement, Sun had agreed to sign it on the day that Oracle's acquisition of them closed and Oracle refused to sign it.

Re: Apple File System

#145
post #76

It would be really nice is there was a modern file system that "just worked" regardless of device. I'm tired of having exFAT/FAT being the only filesystem I can reliably use on multiple different OS-es painlessly, and even then I can't use it for all the functions of those OS-es (No time machine). Hopefully this will be open enough to enable that, though who knows how it will shake out.

https://en.wikipedia.org/wiki/Universal_Disk_Format ? That looked hopeful last I was juggling with this sort of thing, but that was long enough ago that WinXP support was the killer.

Getting UDF to work with rewritable media, like usb sticks, is an unholy pain in the arse. It involves trying to remember an arcane combination of versions and feature flags to get the universal format to actually be universal. I managed it once, but after that, realized that the network was fast enough for most of what I needed and I tend to not have the four gig files that cause problems with FAT filesystems.

Re: Apple File System

#146
post #121
post #87

Uh interesting thought: With Space sharing and multiple logical volumes there will probably be a shift to encrypting users home directories separately. Probably even an unencrypted System Base, which is read-only and protected by rootless anyway, so the system can boot without user interaction. This also finally allows the most user friendly implementation of file encryption: Encrypted Folders, supported by the OS. S…

The point of encrypting the base system image is mostly to make it part of the Secure Boot chain. rootless is a policy control to stop processes from modifying the OS from inside. An encrypted system image stops things with hardware access (but not the unlock key) from modifying the OS from the outside . You can trust any disk whose blocks you can decrypt with key X, to have been only written to by someone with key X…

Why would you need encryption for the Secure Boot chain? Would you not rather sign the base system image for that purpose?

Re: Apple File System

#147
post #113
post #102

Earlier quoted context omitted.

Is compression really that big a deal any more?

While they're still shipping machines with < 1TB SSDs (read: for a long time), yes - why not take the relatively free space and I/O savings?

Because you can upsell a larger iCloud subscription to your customers using the new built in automatic cloud archival function. Then use compression server-side. $$$

Re: Apple File System

#149
post #130

Earlier quoted context omitted.

Just like they promised to open source FaceTime and iMessages? Apple has a history of making false promises in regards to open sourcing products.

Not sure why you're being downvoted. Too many fanboys I guess. I would hope the community is more enlightened than that.

Because it's just kind of lazy and incorrect, that's why.

Apple did promise to open FaceTime, and was promptly sued – that's why it's not open. AFAIK there was no promise to open iMessage.

Re: Apple File System

#150
post #128
post #57

Earlier quoted context omitted.

ZFS gobbles RAM and almost certainly couldn't be made to run acceptably on the Apple Watch. No, this seems like something developed from scratch to meet their particular needs.

ZFS needs very little memory to run. Performance is definitely better with more RAM, but the overwhelming use of memory in ZFS is for cache. Eviction is not particularly efficient due to the cache being allocated from the SLAB allocator, but that is changing later this year. Getting ZFS to run on the Apple Watch is definitely possible. I am not sure what acceptably means here. It is an ambiguous term.

The FreeBSD wiki (https://wiki.freebsd.org/ZFSTuningGuide) still claims:

> To use ZFS, at least 1 GB of memory is recommended (for all architectures) but more is helpful as ZFS needs lots of memory.

Is that inaccurate?

Post reply on HN