Since it is not at all obvious how to use this after install with a scripted mount command.
From inside the build folder, copy code to opt directory (or replace with /usr/local/bin if you know what you're doing):
sudo cp .. /opt/apfs-fuse
Add the opt directory to the PATH variable within the bash profile script belonging to the root user, so system commands can access it during startup and in apps:
echo "export PATH=\"/opt/apfs-fuse/build:${PATH}\"" | sudo tee -a /root/.bash_profile
To check it, use sudoedit /root/.bash_profile to see if it's been created. If it is, then hit Ctrl+X to exit.
Add the .bash_profile to the .bashrc file (to include it during read):
echo "if [ -f ~/.bash_profile ]; then . ~/.bash_profile fi" | sudo tee -a /root/.bashrc
I am not sure if adding to root's PATH is the correct approach, or if it would work to add it to the user's .bash_profile
Since it is not at all obvious how to use this after install with a scripted
mountcommand.From inside the
buildfolder, copy code to opt directory (or replace with /usr/local/bin if you know what you're doing):Add the opt directory to the PATH variable within the bash profile script belonging to the root user, so system commands can access it during startup and in apps:
I am not sure if adding to root's PATH is the correct approach, or if it would work to add it to the user's .bash_profile