Date: Mon, 12 Aug 2019 21:46:03 +0200 From: hw <hw@adminart.net> To: Steve O'Hara-Smith <steve@sohara.org> Cc: freebsd-questions@freebsd.org Subject: Re: Firefox or what? Message-ID: <875zn22mmc.fsf@toy.adminart.net> In-Reply-To: <20190812164800.1bc5581b40de9436a977ea02@sohara.org> (Steve O'Hara-Smith's message of "Mon, 12 Aug 2019 16:48:00 %2B0100") References: <20190812173754.9bbd34f75885d616ae5d074a@gc-24.de> <20190812164800.1bc5581b40de9436a977ea02@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve O'Hara-Smith <steve@sohara.org> writes: > On Mon, 12 Aug 2019 17:37:54 +0200 > hw <hw@gc-24.de> wrote: > >> Hi, >> >> does any of the Firefox versions that can be installed with pkg >> actually work? > > Yes I've been using Firefox on FreeBSD for a very long time now, > always installed from packages. Currently I'm running Firefox 68.01 on > FreeBSD 12 with no problems at all. ok >> Firefix continues to freeze, crash, being unable to >> remember its settings, > > None of this. > >> to not show up at all when starting it other >> than in the process list, > > Not sure what this means, I usually start it from a small script > in .wmx (that's just how my window manager works) that just > runs /usr/local/bin/firefox. Just typing firefox at a command prompt also > works fine. it means Firefox doesn't bring up a window or anything >> and it usually can't be killed even with >> kill -9. > > Never seen that, and my home directory is NFS mounted. Guess what, it turned out that the broken NFS implementation of FreeBSD is unable to handle file locks. Apparently it is using some unexpected ports --- I don't know which ones --- because it kinda worked when I stopped firewalld on the NFS server. That NFS server is serving the same directories and others to other clients perfectly well with no issues. Then error messages showed up in /var/log/messages apparently concerning file locks, leading me to a bug report about it. At the end of the day, I decided to ditch FreeBSD for the server part because its NFS implementation is unusable --- and who knows what other issues may come up. It's probably still fine for the clients because it can be nicely PXE booted. And now you say you got it to work with NFS. How? Neither v3, nor v4 work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?875zn22mmc.fsf>