osxfuse VS archinstall

Install macFUSE, thank me later: https://osxfuse.github.io

I didn't exactly use any 'tutorial'. Assumming you can already SSH to the target machine, you just need to install both these pkgs then reboot to 1TR Recovery Mode and choosing Reduced Security and choose to enable Kernel Extension and then reboot again goto Security & Privacy and Allow the extension, and that's it you can now use it.

Yeah, FUSE is Linux only. But for completeness, for macs there is macFUSE, and for Windows there is winfsp. Both of these have fewer filesystems than FUSE, and I've used neither so I don't know how well they work.

https://github.com/osxfuse/osxfuse/wiki/List-of-macFUSE-File...

https://winfsp.dev/doc/Known-File-Systems/

Weird. Where did you download (lat/new)est MacFuse from? https://osxfuse.github.io/ I hope!

I lead a project that included shipping a filesystem driver and a virtual disk on Windows.

What I did to learn the lower-level APIs, and perform initial testing on the driver, was write a "mirror" drive. The user-mode code pointed to a folder on disk, the driver made a virtual disk drive, and all reads and writes in the virtual disk drive went to the mirror folder.

On Windows, you can implement something like that using Dokany, Dokan, or Winfsp. On linux, there's the Fuse API. On Mac, there's MacFUSE.

Even if you don't do a "mirror" drive, understanding the callbacks that libraries like Dokany, Dokan, Winfsp, and Fuse do helps you understand how IO happens in the driver. Many IO methods provided in popular languages provide abstractions above what the OS does. (For example, the Windows kernel has no concept of the "Stream" that's in your C# program. The "Stream"'s Position property is purely a construct within the .Net framework.)

https://dokan-dev.github.io/

https://github.com/dokan-dev/dokany

https://osxfuse.github.io/

Another place to start is the OS's documentation itself. For example, you can start with Window's CreateFileA function. This typically is what gets called "under the hood" in most programming languages when you open or create a file: https://learn.microsoft.com/en-us/windows/win32/api/fileapi/...

"FUSE-T is a kext-less implementation of FUSE for macOS that uses NFS v4 local server instead of a kernel extension. The main motivation for this project is to replace macfuse (https://osxfuse.github.io/) that implements its own kext to make fuse work. With each version of macOS it's getting harder and harder to load kernel extensions. Apple strongly discourages it and, for this reason, software distributions that include macfuse are very difficult to install. Additionally, the macfuse kext is unstable, may cause frequent system crashes and kernel lock-ups. Given those limitations many software publishers are unable to use macfuse anymore. FUSE-T doesn't make use of kernel extension, it implements its own userspace server that converts between FUSE protocol and NFS calls and let macOS mount NFS volume instead of a kernel filesystem."

MacFuse (ntfs-3g) and a Foolproof way of getting it working via Homebrew.

macos doesn’t support many Linux file system formats. You’ll have to use something like macFUSE https://osxfuse.github.io/

In any case, have you studied https://wiki.archlinux.org/title/Archinstall and https://github.com/archlinux/archinstall. While archinstall is new and has the expected bugs, I've not had your issues before. You might try an earlier ISO, like Oct 2023, though it's not clear if you're using an ISO or the archinstall installed package.

I'm using my laptop as dual boot between Manjaro and Windows 10, I tried for months to install ArchLinux using archinstall tool but the operation always fails with random errors, because I want to install it on a single ext4 partition like how Manjaro is installed. Is there any trusted GUI installer that uses calamares and can install pure ArchLinux ?

The related issue https://github.com/archlinux/archinstall/issues/1111 implies it's fixed, but either way, you can just securely delete your password after the install.

Mount that partition as /efi. Change this in your /etc/fstab as well. This is a good time to remove all the weird carriage returns that archinstall puts in your fstab file (https://github.com/archlinux/archinstall/issues/1399).

Most distros have a nice graphical installer which does make things less of a hassle. But these days Arch also bundles archinstall which is quite easy to use and supports a few display environments for automatic setup right out the gate which is nice.

Or just use archinstall which is official part of the iso file.

You can post an issue at: https://github.com/archlinux/archinstall to get the attention of the developer. He's represented here but I forget his user id.

If you're still suffering with this problem: Maybe try to find the file/module on your system. If it's present, you might want to try to run this pacman -Sy python archinstall (found it here: https://github.com/archlinux/archinstall/issues/1810) to reinstall python and the archinstall script. I hope that this helps you.

Still feels that it is in rapid development phase, rather than just maintenance, last month I encountered this bug