I did like you said and it all went smoothly. Now I've got /dev/hdc1
mounted as /usr/lib so that my libraries aren't symbolic links.
Unfortunately, I am still getting those errors. And the funny thing
is that they are warning me that certain libraries are _not_
symlinks. I know good and well
On Tue, Sep 26, 2000 at 09:47:40PM -0500, Uncle Meat wrote:
Since /usr/lib is on a partition by itself, it can be mounted as /usr/lib
and not need a symlink. You just need a directory in /usr named lib and an
fstab entry defining it, much like the way I do a few. A couple of examples:
On Wed, 27 Sep 2000, you opined:
On Tue, Sep 26, 2000 at 09:47:40PM -0500, Uncle Meat wrote:
Since /usr/lib is on a partition by itself, it can be mounted as /usr/lib
and not need a symlink. You just need a directory in /usr named lib and an
fstab entry defining it, much like the way I do a
Greetings,
I recently installed qt-2.2.0 (via rpm) in order to make licq-0.85 work.
Licq still wouldn't work, exiting with a complaint about not finding
the qt library. So I made a symlink from where it was looking for the
library to where the library actually was, and Licq works. However,
On 27-Sep-2000 Ben Logan spoke something to the effect:
Greetings,
I recently installed qt-2.2.0 (via rpm) in order to make licq-0.85 work.
Licq still wouldn't work, exiting with a complaint about not finding
the qt library. So I made a symlink from where it was looking for the
library
