I already figured a approach, and it kinda work, however it simply feels incorrect. Is there a extra correct method to do it?
So, I just lately upgraded from Mojave to Ventura and instantly realized I misplaced all my root folders, and I am not in a position to create one anymore. I dug by means of Q&A and located data about /and so forth/artificial.conf – however it may simply create symlinks solely, and I discovered that typescript-eslint for instance can not work with root symlinks, it wants actual listing.
My future analysis resulted in both native NFS share or macFUSE bindfs. I attempted first, as a result of it’s already put in and appears simpler. I had /work and /information directories and I moved them to /choose/work and /choose/information.
Created NFS share:
/choose/information /choose/work 127.0.0.1 ::1
sudo launchctl begin com.apple.rpcbindsudo nfsd allowsudo nfsd ceasesudo nfsd begin
Created empty mount factors in root listing:
information
work
Restarted, checked, mount factors are created, and showmount -e is okay.
Guide NFS mounting is okay too sudo mount -t nfs 127.0.0.1:/choose/information /information, checked, sudo umount /information
Now I am attempting to mount these on startup.
First
I attempted /and so forth/fstab – it isn’t mounted on restart, and sudo automount -cv reveals bizarre error automount: /information factors to surprising location /information, as a substitute of /System/Volumes/Knowledge/information and it additionally creates symlink /System/Volumes/Knowledge/information -> /choose/information. Root /information stays empty. Right here is my a part of /and so forth/fstab
127.0.0.1:/choose/information /information nfs rw,actimeo=1,laborious,bg
127.0.0.1:/choose/work /work nfs rw,actimeo=1,laborious,bg
Second
I attempted /and so forth/auto_master. I obtained the identical error as above, and after a whole lot of trial and error I got here to this answer:
- my a part of
/and so forth/auto_master
/- /and so forth/auto_nfs
/System/Volumes/Knowledge/../../../information -fstype=nfs,rw,actimeo=1,laborious,bg 127.0.0.1:/choose/information
/System/Volumes/Knowledge/../../../work -fstype=nfs,rw,actimeo=1,laborious,bg 127.0.0.1:/choose/work
It really works, continued between reboots and sudo automount -cv reveals correct
automount: /System/Volumes/Knowledge/house up to date (/house -> /System/Volumes/Knowledge/house)
automount: /information up to date
automount: /work up to date
automount: no unmounts
Is there a correct not hacky approach to do that? Why it disallows to mount at root, and expects /System/Volumes/Knowledge? I discovered some data that you are able to do information /System/Volumes/Knowledge/information in /and so forth/artificial.conf after which mount NFS to /System/Volumes/Knowledge/information – however once more – there will probably be symlink at root.
