Earlier quoted context omitted.
ext4 and Btrfs are only well supported on Linux; they are not universal standards. NTFS was only supported well on Windows until recently; but extensions like NTFS Encryption (BitLocker) are still Windows only. Mac still does not let you write to an NTFS volume. APFS and HFS+ are obviously Apple file systems. FreeBSD does not support ext4 or Btrfs well; but instead prefers UFS2 or ZFS despite also being an open-sourc…
Is there a single filesystem in the world (besides "simple" ones like FAT) that both has an open standard AND is licensed in a "usable" codebase (MIT or other "non-copyleft" license)?
macOS Tahoe brings a new disk image format
31–40 of 152 posts
Re: macOS Tahoe brings a new disk image format
#32Earlier quoted context omitted.
3rd party supporting a file system would be one of the last things on a list of all software I’d ever want a 3rd party writing instead of the OS maker. Nightmare to evaluate the options, pure stress testing the options, difficult to know if it didn’t mess something up.
Question, who maintains NTFS support for Linux? Microsoft? The kernel? The distros? Genuinely asking.
I was going to add some additional comments about this, but then I found that Paragon's website has an FAQ that covers everything I was going to say (and more): https://www.paragon-software.com/us/home/ntfs3-driver-faq/
Re: macOS Tahoe brings a new disk image format
#33Earlier quoted context omitted.
Is there a single filesystem in the world (besides "simple" ones like FAT) that both has an open standard AND is licensed in a "usable" codebase (MIT or other "non-copyleft" license)?
zfs?
Re: macOS Tahoe brings a new disk image format
#34Earlier quoted context omitted.
Is there a single filesystem in the world (besides "simple" ones like FAT) that both has an open standard AND is licensed in a "usable" codebase (MIT or other "non-copyleft" license)?
I think UDF was meant to be this, though I don't think it supports everything you'd want. Does NTFS have licensing issues though?
Re: macOS Tahoe brings a new disk image format
#35Earlier quoted context omitted.
ext4 and Btrfs are only well supported on Linux; they are not universal standards. NTFS was only supported well on Windows until recently; but extensions like NTFS Encryption (BitLocker) are still Windows only. Mac still does not let you write to an NTFS volume. APFS and HFS+ are obviously Apple file systems. FreeBSD does not support ext4 or Btrfs well; but instead prefers UFS2 or ZFS despite also being an open-sourc…
Is there a single filesystem in the world (besides "simple" ones like FAT) that both has an open standard AND is licensed in a "usable" codebase (MIT or other "non-copyleft" license)?
if GPL is a non-starter for you, youre missing the point of the open standard. apple already discloses a litany of various GPL it ships. XFS would be no different.
Re: macOS Tahoe brings a new disk image format
#36Any chance this will reduce the space needed for major OS updates? Those have always been desperately inefficient.
No. Disk images aren't involved in the OS update process.
Re: macOS Tahoe brings a new disk image format
#37Earlier quoted context omitted.
3rd party supporting a file system would be one of the last things on a list of all software I’d ever want a 3rd party writing instead of the OS maker. Nightmare to evaluate the options, pure stress testing the options, difficult to know if it didn’t mess something up.
Question, who maintains NTFS support for Linux? Microsoft? The kernel? The distros? Genuinely asking.
Re: macOS Tahoe brings a new disk image format
#38Earlier quoted context omitted.
This article describes a new disk image format (on which a filesystem can be put, APFS in the article), not a filesystem, or did I misunderstand? edit: added the word "image", which I apparently forgot to type. Mentioning the edition because otherwise it would make an answer to this comment difficult to understand.
This is a new disk image format. Not even a disk format. For virtualizing a disk. On which you can put a filesystem, yes. There seems to be an extraordinary amount of confusion in many of the comments, I don't know why.
We really don't have enough disk formats in this space. Is this bringing something new ? Or is just polluting the namespace.
Re: macOS Tahoe brings a new disk image format
#39Earlier quoted context omitted.
Apple recently made FSKit a supported/documented API, which should allow third-parties to add support for other filesystems: https://developer.apple.com/documentation/fskit?language=obj...
3rd party supporting a file system would be one of the last things on a list of all software I’d ever want a 3rd party writing instead of the OS maker. Nightmare to evaluate the options, pure stress testing the options, difficult to know if it didn’t mess something up.
Re: macOS Tahoe brings a new disk image format
#40Earlier quoted context omitted.
This article describes a new disk image format (on which a filesystem can be put, APFS in the article), not a filesystem, or did I misunderstand? edit: added the word "image", which I apparently forgot to type. Mentioning the edition because otherwise it would make an answer to this comment difficult to understand.
This is a new disk image format. Not even a disk format. For virtualizing a disk. On which you can put a filesystem, yes. There seems to be an extraordinary amount of confusion in many of the comments, I don't know why.
https://developer.apple.com/documentation/virtualization/vzd...