Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Aug 2019 12:37:05 +0200
From:      hw <hw@gc-24.de>
To:        freebsd-questions@freebsd.org
Subject:   Re: Firefox or what?
Message-ID:  <20190815123705.4ac8a2d8c005971b83a5dceb@gc-24.de>
In-Reply-To: <5be8adb1-cf57-9e24-4ce9-27a76cc3ece8@netfence.it>
References:  <20190812173754.9bbd34f75885d616ae5d074a@gc-24.de> <20190812164800.1bc5581b40de9436a977ea02@sohara.org> <875zn22mmc.fsf@toy.adminart.net> <d968aa28-dd43-ba88-f1f7-846330e9ed0c@netfence.it> <871rxorh4y.fsf@toy.adminart.net> <5be8adb1-cf57-9e24-4ce9-27a76cc3ece8@netfence.it>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 14 Aug 2019 13:21:18 +0200
Andrea Venturoli <ml@netfence.it> wrote:

> On 8/13/19 11:34 PM, hw wrote:
> 
> > So how did you get it to work?
> 
> By following the instructions in the handbook and reading the manual pages.
> 
> I've had this working for years with NFSv3 and it's working now after I 
> switched to NFSv4.
> Perhaps if *you* post your configuration, we can look at it and see if 
> something is wrong.

That's what I did.  I tried lots of different configurations which I
don't have anymore, so I could only post the one that was active when
I gave up on it.

> > After all this, I wouldn't be surprised if FreeBSD-NFS is incompatible
> > with Centos-NFS.
> 
> Sorry, but you didn't say that in your first post.

It was neither relevant, nor known in the first post.  If Firefox
generally doesn't work with FreeBSD, that would have been an
explanation, and that was what I wanted to know.  Seeing that so many
things are missing from the version FreeBSD uses is not exactly
encouraging.

That NFS doesn't work right was unexpected and unknown, and I was
assuming that NFS is compatible with NFS since anything else doesn't
make sense.

> Again, this might be a problem with FreeBSD, a problem in CentOS, a 
> problem with how you configured them...
> We cannot tell if you don't provide info.
> Also, I'd be suprised if this only affected FireFox (which was the 
> original subject), as several other programs wouldn't work then...

Firefox was the one I tried to get to work; if others didn't work
either, I didn't get so far as to find it out other than a while ago
when it turned out that NFS in FreeBSD sucks because it's incapable of
exporting directories with the permissions as required.

> > Have you tried that?
> 
> No.
> Everything here is FreeBSD based.

So that is already a difference.

> > What will you do when you run into bug 220004?
> 
> I don't know.
> I'm not using 12 yet: I see .0 releases (of any software) as potentially 
> immature and buggy and I'm absolutely not switching until 12.1 is
> out.

Then why doesn't the documentation warn about this?  I was trying to
find out what the recommended stable version is, and that seems to be
12 release.  Why call it release when it's still beta?

> These are bugs I've heard of and are one more reason I'm NOT moving to 
> 12 yet.
> Then again, I'm happily working with 11.2 and 11.3 and I see no need to 
> upgrade for now.
> 
> If I ever run into it, I'll see what my options are.
> 
> If you are stuck with it, I suggest you seek help on freebsd-net.

Fortunately, I'm not stuck with it.  FreeBSD is fine for PXE booting
diskless clients, and I don't plan on using it for anything else
anymore.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190815123705.4ac8a2d8c005971b83a5dceb>