Subject: Re: Netscape communicator
To: Andrew Gillham <gillham@vaultron.com>
From: Fernando y Yohara <fvillalo@sinfo.net>
List: netbsd-help
Date: 03/10/2002 23:12:16
Thanks for the info, it solved the problems.
A few more questions from a newbie:
1. Is Communicator inestable on NetBSD?
2. Will you recommend another browser for UNIX?
Andrew Gillham wrote:
>
> On Sun, Mar 10, 2002 at 06:29:07AM +0100, Matthias Buelow wrote:
> > Andrew Gillham <gillham@vaultron.com> writes:
> >
> > >The lock file is actually under the Linux emulation tree, since there is
> > >a 'root' directory there. So look in:
> > > /emul/linux/root/.netscape
> >
> > I highly doubt that. Netscape (the linux-emulated one) was always
> > writing to my regular home directory under $HOME/.netscape, and
> > the "crash^Wlockfile" was always there also. A simple rm on the
> > lockfile in $HOME/.netscape should help. Mozilla, btw., doesn't
>
> Try it as 'root' and you'll see what I mean.
>
> > seem to leave such a lockfile, even though the latest version
> > is as instable as netscape on a bad day (the last version was
> > a lot better, hopefully the next will be better again...)
> >
> > In fact, except for a few directories (like, where emulation
> > libs and /etc, etc. (no pun intended) are found) linux emulation
> > seems to map to the normal filesystem tree. Very well done,
> > I have to say.
>
> It maps to the normal filesystem when it can't fine the path it is
> looking for in the emulation filesystem. If you're running Netscape
> as 'root', when it tries to do something in $HOME it is really in
> /emul/linux/root.
>
> -Andrew
--
A lot of people approach risk as if it's the enemy when it's really fortune's
accomplice. (Sting)
Choose well. Your choice is brief, and yet endless. (Goethe)