(EDITED for specificity)
When I use terminal in recovery mode (on a MacBook Pro with Apple silicon) a lot of bash commands seem to be missing and give me "command not found" errors when I try to run them. This goes for less basic commands like
systemsetup that problem aren't standard bash, but also some really core ones like
du (but not
df). What causes this? I looked up another question (sudo: command not found) that suggested maybe there was an issue with my PATH, but the steps that were suggested to fix it didn't change anything:
-bash-3.2# /usr/bin/nano ~/.bash_profile
-bash: /usr/bin/nano: No such file or directory
-bash-3.2# /bin/cat /etc/paths
cat: /etc/paths: No such file or directory
-bash-3.2# export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
-bash-3.2# sudo echo test
-bash: sudo: command not found
Is recovery mode running a super stripped down bash that doesn't recognize these commands? Or does this have to do with the way my system was damaged somehow? Or something else?