== Unix's _/usr_ split and standards (and practice) In [[Rob Landley about the /usr split https://blog.w1r3.net/2018/01/06/rob-landley-about-usr-split.html]], Rob Landley doesn't have very good things to say about how the split between _/bin_ and _/usr/bin_ (and various other directories) has continued to exist, especially in various standards. One of my views on this is that the split continuing to exist was always inevitable, regardless of why the split existed and what reasons people might have for preserving it (such as [[diskless workstations benefiting from it DisklessUnixAndUsr]]). As far as standards go, Unix standards have pretty much always been mostly [[documentation standards ../tech/WaysToStandards]], codifying existing practice with relatively little invention of new things. The people trying to create Unix standards are not in a position to mandate that existing Unixes change their practices and setup, and existing Unixes have demonstrated that they will just ignore attempts to do so. Writing a Unix filesystem hierarchy standard that tried to do away with _/bin_ and mandated that _/usr_ was on the root filesystem would have been a great way to it to fail. (POSIX attempted to mandate some changes in the 1990s, and Unix vendors promptly exiled commands implementing those changes off to obscure subdirectories in _/usr_. Part of this is because being backward compatible is the path of least resistance and fewest complaints from customers.) For actual Unixes in practice, conforming to the historical weight of existing other Unixes (including their own past releases) has always been the easiest way. There are countless people and scripts and so on that expect to find some things in _/bin_ and some things in _/usr/bin_ and so on, and the less you disrupt all of that the easier your life is. Inventing new filesystem layouts and pushing for them takes work; any Unix has a finite amount of work it can do and must carefully budget where that work goes. Reforming the filesystem layout is rarely a good use of limited time and work, partly because the returns on it are so low (and people will argue with you, which is its own time sink). (Totally reinventing Unix from the ground up has been tried, by the people arguably in the best position possible to do it, and the results did not take the world by storm. [[Plan 9 from Bell Labs https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs]] still has its fans and some of its ideas have leaked out to mainstream Unix, but that's about it.) The modern irony about the whole issue is that recent versions of Linux distributions are increasingly requiring _/usr_ to be on the root filesystem and merging _/bin_, _/lib_, and so on into the _/usr_ versions, but this has been accomplished by the 800 pound gorilla of systemd, which many people are not happy about in general. [[The monkey's paw https://en.wikipedia.org/wiki/The_Monkey%27s_Paw]] hopes you're happy with sort of achieving the end of this split. (A clean end to the split would be to remove one or the other of _/bin_ and _/usr/bin_, and similarly for the other duplicated directories.)