#macfuse — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #macfuse, aggregated by home.social.
-
Which local file systems does macOS 26 support?
-
Which local file systems does macOS 26 support?
-
Versión 5.0 de macFuse, aplicación que permite ampliar macOS mediante sistemas de archivos de terceros: https://www.dekazeta.net/foro/files/file/3269-macfuse-ex-osxfuse/
-
macFUSE va tirer parti de FSKit pour faciliter l’ajout de systèmes de fichiers à macOS http://dlvr.it/TK8Ykm #macFUSE #FSKit
-
Just noticed that #VeraCrypt has been updated to version 1.26.14 a few days ago 🙂
On #macOS they added support for FUSE-T (https://www.fuse-t.org) as an alternative to #macFUSE.
What’s interesting about #FUSET is that it works without using kernel extensions, which makes it way easier (and probably safer) to install and use.
-
macFuse (ex osxFUSE) 4.6.1 https://www.dekazeta.net/foro/files/file/3269-macfuse-ex-osxfuse/
-
TIL about FUSE-T.
This is a FUSE implementation for macOS. Rather than implementing a kernel module like #macFUSE, this implements FUSE on top of NFSv4.
macOS then natively mounts the NFS.
Sadly unfree too just like #macFUSE :/
Unlike #macFUSE however, this is something that someone could reasonably built and, more importantly, maintained as a FOSS project as both "ends" are very stable and well defined here. Something like this could also theoretically be used on platforms other than macOS.
-
Hat Jemand einen Tipp zur effektiven Nutzung von #VeraCrypt am #MAC (M1)?
Das läuft zwar mit #MacFuse auch auf neuestem Betriebssystem - aber es ist extrem viel langsamer als am #Windows oder Linux Rechner.
Dateisystem innerhalb des Containers ist wohl noch #NTFS.Anwendung: Offsite Backups auf externer HDD die dann anderswo in ne Schublade kommen.
Bei suche nach "MAC Veracrypt langsam" - nur dieses gefunden: https://www.randombrick.de/veracrypt-funktioniert-mit-macos-big-sur-und-m1-macs/
-
This turned out to be a hardcoded limit in #macFUSE of 64 mounts.
https://github.com/osxfuse/osxfuse/issues/533
Thankfully I was able to switch a few mounts back to NFS and increase the number of chroots back up.
With that, and another fix to run bindfs with increased file descriptors, I think we might be back in business with reliable and fast #macOS #pkgsrc builds.
-
I knew I should have tempered expectations:
mount_macfuse: failed to open device
Seems like #macFUSE doesn't like creating multiple concurrent chroots. Doesn't even like creating more than around 4 in series.
Will have to see how many I can get away with reliably, and put up with slower builds I guess.
-
Thanks to #macFUSE and bindfs, it looks like we're able to continue to support #pkgsrc on #macOS #Ventura.
I really don't like having to enable third-party kernel extensions, but with #Apple breaking NFS-based chroots in Ventura I'm left with no choice.
Will kick off some builds over the weekend and hopefully have the repositories updated by Monday.