×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello,
I regularly download and try to use software that was compiled for AIX.
Frequently, that software expects files to be in their standard Unix
locations /usr/local/bin, /usr/local/lib, /usr/local/share, et al. But
the IBM tools expect them to be in /QOpenSys/usr/local -- thus creating
a conflict and breaking the software.
So I always have /usr/local and /qopensys/usr/local symlinked.
It's true that case-sensitivity doesn't work as expected, but I have yet
to run into a software package that gets broken by this. The packages
are all careful to maintain case, but that doesn't /hurt/ anything if
they're running in a case-insensitive filesystem... it's just not
necessary. Granted, if one of them had files that had the same name
where the only diff was the upper vs. lower case characters, then
something would break.
But I have not yet run into a package that does that.
Dennis Lovelady wrote:
This belongs in the midrange-l forum.
I have installed 7Zip to my i, and add the symbolic link as bellow
ln -s /usr/local /QOpenSys/usr/local
And BTW, I wouldn't make a symbolic link from the root file system into
the QOpenSys file system. The root file system has not he same features
as the QOpenSys file system (f. e. case sensitivity).
In general, this is OK if you know what you're doing. However, I agree that
you shouldn't try to create a link between /QOpenSys/usr/local and
/usr/local.
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Tried to play my shoehorn... all I got was footnotes!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.