17 ms·
I've pretty much given up on Asahi because of the years-long delays, and because there's no performant way to share disk space for data with MacOS. By running
by dreamcompiler 20d ago
I've pretty much given up on Asahi because of the years-long delays, and because there's no performant way to share disk space for data with MacOS.
By running Linux in a VM on MacOS on Apple silicon, you sacrifice some raw speed but in return you still get to run MacOS apps occasionally and have access to the same data from either MacOS or Linux without having to duplicate everything. And battery life is reasonable, which is not true yet with Asahi.
- xoa 20d agoNot saying your VM approach isn't right for you, but: >and because there's no performant way to share disk space for data with MacOS Have you tried a ZFS partition? If it's a desktop system use iSCSI to network storage (I'm not running Linux directly on my Studio or M4 mini but I still put my Home folder on the network)?
- dreamcompiler 20d agoI haven't. ZFS might be the answer for my laptops.
- xoa 20d agoIt's worth a spin. Before moving to iSCSI I had my home folder as well as lots of projects and data on ZFS for macOS for almost a decade, and it was extremely reliable and performant within reason [0]. ZoL of course is also quite solid at this point too. Life gets a lot more complex if you want to boot off of it, but a shared data partition for two separate OS boots could be a good match. ---- 0: By which I mean, for equivalent features. It's possible to go really far out of the normal with ZFS in terms of silly compression and multiple copies of data even within a single OS and checksumming and so on in ways that add computational overhead, but I don't hold that against it vs APFS.
- zbentley 20d agoOr good old FAT+symlinks from the MacOS partition might be sufficient, if you don’t need large files. NTFS, ironically, is pretty stable via FUSE on Mac if you need more than FAT allows.