Even though packages that are from /opt install binaries to all the libraries and binaries in /usr ?
Without /opt being in there the rollbacks might not be complete since /usr is a snapshot?
The 1980's requirements were that /opt had its own /opt/bin and /opt/lib so that system files were not touched. What happened because of that is PATH ended up with multiple /opt/bin appended to it (one for each package that went to /opt) I saw systems become unusable because the environment was 100% full and deleting the excess entries in PATH was required to get past that. I was out of the loop as to when that requirement was dropped. It was in the Motorola 68000 Unix distro. I ended up with the PC 386 Unix and that requirement was gone. So it is OK to put 3rd part parts in /usr/bin and /usr/ lib64 (via symlink) but not the other files.
I was
UNIX when it fit in 10MB and had lots of Panic code in the
kernel.
On Mon, Jun 07, Larry Len Rainey wrote:In Tumbleweed, /bin /sbin /lib /lib64 are symbolic links to /usr/bin /usr/sbin /usr/lib and / usr/lib64 I can see that but why is /opt not a link to /usr/opt and all /usr/opt not there too? Am I missing the reason or has no one thought of this yet?/usr is for the OS of the distribution /opt is for third party packages Since the stuff is different and follows different policies, it got separated many, many years ago for good reasons (read the FHS for more). Merging them now again doesn't make much sense and would only create new problems for transactional-updates, image based installations and many more. Thorsten