3 ms·
The purpose of `/usr/sbin` does not seem to be understood here. It is (as far as I know) for statically linked binaries. If you use dynamically-linked libraries
by wakawaka28 1y ago
The purpose of `/usr/sbin` does not seem to be understood here. It is (as far as I know) for statically linked binaries. If you use dynamically-linked libraries, those can potentially be manipulated via LD_PRELOAD or something. So admin software is probably something that should be in this category. There might be other reasons I'm not aware of for having a category for statically linked stuff. This means little if nobody is checking on the distro side to make sure that sbin is filled with statically linked stuff.
I don't want to attribute this change to malice because it is a rather arcane detail, but let's just say that I don't approve of IBM's recent activities related to Linux and FOSS.
- joshstrange 1y ago> It is (as far as I know) for statically linked binaries. No, it’s for system binaries or superuser binaries (depending on which you prefer, I’ve heard people say it both ways). I’m see people say it’s because they are statically linked but the Filesystem Hierarchy Standard says it’s “system” [0]. [0] https://en.m.wikipedia.org/wiki/Filesystem_Hierarchy_Standard https://en.m.wikipedia.org/wiki/Filesystem_Hierarchy_Standar...