I’d say “check your shell documentation” but they’re both almost impossible to search for. They both work in Bash. Both skip aliases and shell functions and go straight to shell builtins or things in the $PATH.
Oh, I was just remarking that I don’t have anything but env installed in there. I wouldn’t be able to run sl by its full path unless I go searching for wherever that is
Whoa. What distro is it that puts everything in /bin, or at least, practically nothing in /usr/bin?
I use a Debian that actually symlinks /bin to /usr/bin so that they’re one and the same (annoying some purists), but even on systems where they are (or were) used for separate purposes, I thought that each had a significant number of commands in them.
(To paraphrase man hier, /bin is for necessary tools and /usr/bin is for those that are nice to have.)
NixOS, all packages are in /nix/store/, where each package had its own folder (simplified because there’s the hashing stuff but idk how to explain that)
This allows you to have multiple versions of the same package, on the same system, for example.
But how would you run sl, the steam locomotive?
I know you’re joking but:
\slorcommand sl.I’d say “check your shell documentation” but they’re both almost impossible to search for. They both work in Bash. Both skip aliases and shell functions and go straight to shell builtins or things in the
$PATH.There’s also
/usr/bin/slbut you knew that.$ ls /usr/bin envI guess I could
env sl?Caught the NixOS user
😳
Dangit. I always forget about
env. Yes, that ought to work.Oh, I was just remarking that I don’t have anything but
envinstalled in there. I wouldn’t be able to runslby its full path unless I go searching for wherever that isWhoa. What distro is it that puts everything in /bin, or at least, practically nothing in /usr/bin?
I use a Debian that actually symlinks /bin to /usr/bin so that they’re one and the same (annoying some purists), but even on systems where they are (or were) used for separate purposes, I thought that each had a significant number of commands in them.
(To paraphrase
man hier, /bin is for necessary tools and /usr/bin is for those that are nice to have.)NixOS, all packages are in
/nix/store/, where each package had its own folder (simplified because there’s the hashing stuff but idk how to explain that)This allows you to have multiple versions of the same package, on the same system, for example.
They’re likely using NixOS. It makes
/usr/bin/envand/bin/shfor compatibility but nothing else goes in those dirs