zlacker

[return to "Understanding the bin, sbin, usr/bin, usr/sbin split (2010)"]
1. Waterl+k7[view] [source] 2022-05-11 07:26:21
>>taubek+(OP)
Speaking of this, is there a good resource that elegantly but succinctly describes the intent of each of linux’s (Unix’s?) root directories?

I’ve spent like eight years with Ubuntu and realize it’s all symbol manipulation to me. I learn what is and goes where but all in practice and never because I understand the semantics.

◧◩
2. drothl+A9[view] [source] 2022-05-11 07:48:23
>>Waterl+k7
Many distros, including Debian & Ubuntu, have merged /bin and /usr/bin, with symlinks for backwards compatibility: /bin -> /usr/bin (and similarly for /usr/lib etc).

https://www.freedesktop.org/wiki/Software/systemd/TheCaseFor...

◧◩◪
3. pabs3+Ke[view] [source] 2022-05-11 08:34:27
>>drothl+A9
The Debian/Ubuntu merged-/usr is incomplete, various things are broken by the way this was achieved:

https://wiki.debian.org/Teams/Dpkg/MergedUsr

◧◩◪◨
4. faho+sK[view] [source] 2022-05-11 12:57:50
>>pabs3+Ke
Note: This is the dpkg maintainer arguing an apparently fairly unpopular position of linking the specific files inside of /bin instead of /bin directly, in opposition to what appears to be the majority of linux distros.

He's even added a warning to dpkg and a "usrunmess" tool to switch a system to his preferred way of doing things.

It's not clear to me where the breakage lies and I've not seen any actual reports of it.

For more context see https://lwn.net/Articles/890219/

◧◩◪◨⬒
5. jeroen+Lf1[view] [source] 2022-05-11 15:17:23
>>faho+sK
As far as I know, the breakage is theoretical.

Suppose a package has a boot-time, size-optimized, limited binary in /bin/runk and a user-optimized, feature-complete binary that requires the entire system to be up in /usr/bin/runk. When /bin and /usr/bin link to the same directory, the package manager will extract these files and run into a problem.

Things become even more complicated when these tools are split into different packages (say runk-boot and runk-user). Tracking which file comes from which package can become near impossible.

Of course this can be resolved relatively easily; make the package manager link-aware by handling the merged-bin setup as a special case and warn or error when files conflict. People don't seem to want to do that for various reasons, some good, some based in opinion only. It's a mess.

◧◩◪◨⬒⬓
6. naniwa+Or2[view] [source] 2022-05-11 21:10:07
>>jeroen+Lf1
This can also be resolved externally by controlling the repos and not fucking it up. Package conflicts are already a thing, Debian already has all the infra, you've always been able to cause the "theoretical" "breakage". Frankly, it's already a non-problem.
[go to top]