Richard Yao posted on Wed, 06 Apr 2016 10:04:05 -0400 as excerpted: > That being said, this is only useful for new installs where people want > to take advantage of the Solaris way of doing management. It should have > no benefit for existing installs.
I don't know enough about solaris to comment on that, but my (reverse) merging /usr and bin/sbin to / certainly had benefits for my existing install. The biggest one was no longer having the brain overhead of having to track whether something's in /usr or direct in /, or in the bin or sbin location in /usr or /. If it's an on-path executable that I didn't manually create/install myself, it's now in /bin as the fully dereferenced canonical path, tho /usr/bin /sbin, and /usr/sbin also work via symlinks, no questions asked. Similarly, libs are found in /lib64 as the fully dereferenced canonical path, tho /lib, /usr/lib64 and /usr/lib all work as well, via symlinks. =:^) There remains a slight down side in that the PM's idea of where the files are located may differ in that it's one of the symlinked versions, and various standard paths are slightly less efficient due to having to dereference possibly multiple symlinks, but automatic and fast tracking of such things while minimizing the wetware tracking load is what computers excel at, so on balance I consider it a pretty large benefit. So there's certainly benefit for existing installs. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
