zlacker

[return to "Understanding the bin, sbin, usr/bin, usr/sbin split (2010)"]
1. pauldd+To[view] [source] 2026-01-04 16:26:40
>>csmant+(OP)
1. The title says “understanding sbin” but the content gives zero understanding of that. If someone has a historical explanation, please provide it.

2. “Then somebody decided /usr/local wasn't a good place to install new packages, so let's add /opt”

Not exactly. /usr/local exists so you don’t accidentally mess up your distro/package manager by changing its files. It’s “local” to your installation. But it is still structured — /usr/local/bin, /usr/local/lib, etcetera — divided into binaries, shared libraries, manpages.

Whereas /opt has no structure. It’s “the wild west”…application binaries, libraries, configuration, data files, etcetera with no distinction. Apps with “universal” packaging, or sometimes secondary package managers.

For example /usr/local/bin is normally part of PATH, but /opt is not (unless eg homebrew adds it to your bashrc).

◧◩
2. vntok+fp[view] [source] 2026-01-04 16:29:00
>>pauldd+To
What do you mean?
◧◩◪
3. pauldd+js[view] [source] 2026-01-04 16:48:19
>>vntok+fp
I mean the article doesn’t explain sbin. The author symlinks it to bin but doesn’t explain why it exists.
[go to top]