Hi aus9
... I did the test without full reboot and needed full pathway to /usr/local/bin as reported OP ...
Sometimes after loading an extension you will get a "No such file or directory" message. In cases
where the extension contains GNU versions of busybox commands, you may find the busybox
commands being executed instead of the newly loaded GNU versions.
This seems to happen when loading an extension while working in an already open terminal. I've
never really looked into it, but I think it has something to do with command history being cached
and hashed. So basically when you run grep, it finds busyboxes /usr/grep and remembers grep
means /usr/grep. You then load grep.tcz but the terminal still has grep cached as /usr/grep
and executes that instead. It's possible if you try to run a command that does not exist, it may
cache the it doesn't exist.
If that happens, try running this to fix it:
hash -r
Opening a new terminal to work in should fix it too.
... Please mark as solved
Done.
Subject lines are limited to ~80 characters, so I had to modify yours so [Solved] would fit.