snowee It looks like somehow your PATH doesn't have any system binary directories. I would expect at least /usr/sbin, if not both /sbin and /usr/sbin. Those should get added to your PATH by profile setup scripts that run any time you log in. Edit to clarify: Those directories should already be on your path, and you shouldn't have to add them with your own changes to ~/.bashrc.
As far as how this happened: who knows? It didn't happen on my machine; I still have all those system binaries available because /usr/sbin is in my PATH. I suspect there is some offending piece of software that you have installed which I do not. The most likely explanation I can think of is that someone in the software supply chain made a mistake that got propagated to our packages, and thus to your system.
Now, there is a bit more troubleshooting we can do:
- Could you post the output of
eopkg hs -l1? That will give a list of the packages upgraded on your system in the previous sync, and could help identify a package which has a mistake.
- Could you post the output of
eopkg lr? If you happen to be on the unstable repo, that could explain some things. I don't think you are, but it never hurts to check.
