That was the 1st thing I tried. Won't accept the link saying one already
exists, yet there's nothing there. Zilch. I remember somewhere that there
can be symlink dependencies remaining even after a file's deleted, but not
how to clear them. Errata slips away sometimes. Tho when all is said & done
I'm trying to decide why I even want Nautilus in the 1st place. It's sort of
the challenge thing now - not the ultimate use. It seems way too featureless
for a file manager - but this from someone who absolutely can't do without
mc.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Altoine B.
Sent: Tuesday, January 30, 2001 10:59 PM
To: [EMAIL PROTECTED]
Subject: Re: [expert] Nautilus
Bill Piety wrote:
>
> I've just upgraded Nautilus to the latest build. Quite a number of hoops
> to jump thru. I had installed a Mozilla rpm the 1st go round. I
> subsequently installed the latest daily build (which is ver. 7, as
> needed by nautilus), leaving the rpm in place for Nautilus purposes. I
> then uninstalled the Mozilla rpm with this upgrade, hoping to avoid
> having to download the Eazel rpm over my 56K. Nautilus opens & all is
> fine as far as the file manager portion & connecting to Eazel services.
> URL's are not being read evidently cause nautilus is not finding the
> Mozilla library path, ie to libgtkembedmoz.so, located in
> /usr/local/mozilla instead of /usr/lib/mozilla.
>
> Is this just a matter of setting a Mozilla environment variable of some
> sort? Can I avoid dl'ing the older rpm? If it's possibly an environment
> issue, please suggest the proper syntax. Tks.
Make a symlink
Type
ln -s /usr/local/mozilla /usr/local/mozilla
Cheers
-- Al
