Live data from Hacker News

A Base Filesystem Project for macOS

kext.io

41–45 of 45 posts

Re: A Base Filesystem Project for macOS

#41
post #22

Earlier quoted context omitted.

You're an outlier. I live in an environment where I need to move files between several builds of Windows, Linux and macOS - and often where there is no network access because of security policy (misguided policy perhaps). Thumb Drives are the only way to function.

Can you say anything more about the environment? I'm curious.

I work in the public service industry - many of the systems I work on are isolated from the internet, and from other networks even - so I often have to sneakernet software updates and other things around to all these various machines. The no network thing is reasonable when you consider the requirements these systems operate under - its also an easy way for folks with no system administration abilities to ensure some security and stability.

Re: A Base Filesystem Project for macOS

#42
post #12

Earlier quoted context omitted.

You could call it a universal disk format. https://en.wikipedia.org/wiki/Universal_Disk_Format

I tried UDF for a few months on a macOS/Linux/Windows triple boot. It doesn't work reliably enough. I've switched to ext2 using e2fsd and Paragon (which I paid for) on Windows and macOS respectively. Fingers crossed. I wish someone would port F2FS to Windows and macOS. This could be a good starting point for macOS.

What sort of issues did you have with udf?

Re: A Base Filesystem Project for macOS

#43
post #2

It's always good to see open source projects published, especially for tricky and often under-documented stuff like file system kexts. Not to derail from this fine post, but I wanted to give a shoutout to FUSE for macOS (previously known as OSXFUSE). As an outsider from the project - merely a happy user - it seems to be a well maintained FUSE implementation for macOS, with signed kexts available. https://osxfuse.gith…

why are there kexts in file system user space extensions? in OSX multiple driver types can exist entirely in user space, with no kext. [ former Apple engineer here ]

Re: A Base Filesystem Project for macOS

#44
post #42

Earlier quoted context omitted.

I tried UDF for a few months on a macOS/Linux/Windows triple boot. It doesn't work reliably enough. I've switched to ext2 using e2fsd and Paragon (which I paid for) on Windows and macOS respectively. Fingers crossed. I wish someone would port F2FS to Windows and macOS. This could be a good starting point for macOS.

What sort of issues did you have with udf?

Windows threw up CRC errors. I am not blaming Windows here, that would be unfair. Perhaps it was the only one that checked CRCs on read and one of the others didn't write CRCs on write.

My use case was to store many large git repo clones and MP3s.

Re: A Base Filesystem Project for macOS

#45
post #2

It's always good to see open source projects published, especially for tricky and often under-documented stuff like file system kexts. Not to derail from this fine post, but I wanted to give a shoutout to FUSE for macOS (previously known as OSXFUSE). As an outsider from the project - merely a happy user - it seems to be a well maintained FUSE implementation for macOS, with signed kexts available. https://osxfuse.gith…

why are there kexts in file system user space extensions? in OSX multiple driver types can exist entirely in user space, with no kext. [ former Apple engineer here ]

Are you saying you can write a 100% user-space "driver" that allows for `mount`ing into the regular file system? How does that work? Can a non-root user supply the code running to serve /some/path that is visible for any process on the system, even root?
Post reply on HN