Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Aug 2019 11:33:38 +0000 (UTC)
From:      Paul Pathiakis <pathiaki2@yahoo.com>
To:        Andrea Venturoli <ml@netfence.it>, hw <hw@adminart.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Firefox or what?
Message-ID:  <314331581.5193473.1565782418212@mail.yahoo.com>
In-Reply-To: <871rxorh4y.fsf@toy.adminart.net>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
 Did you read that bug?
It really has nothing to do with NFS.=C2=A0 It has everything to do with In=
tel NICs and the IFLIB functionality.=C2=A0 NFS usage is a symptom that exp=
oses it and nothing more.

He may never run into that bug.
Everything I read on that bug report seems to point that it is specific to =
Intel chipset NICs and NOTHING else.=C2=A0 So, any of the incredible amount=
 of non-Intel type NICs out there, will, more than likely, never experience=
 the 'BAD" bug 220004.
Also, since FreeBSD follows standards like POSIX, it is more than likely th=
at it is the Linux implementation not following standards, again, that is a=
 problem when dealing with an issue (not related to this bug) of NFS compat=
ibility.
Linux clients have had multiple problems talking to NFS server implementati=
ons that aren't Linux.=C2=A0 That's called 'platform or function incompatib=
ility'.
Again, I point to NetApp being the largest seller of NFS based appliances.=
=C2=A0 Numerous times over the last decade Linux clients have had bugs expo=
sed in their NFSv3 and NFSv4 implementations usually due to not following t=
he specifications for implementation and/or being 'liberal' with the interp=
retation of it.
Finally, again, you're pointing out something that is irrelevant to make yo=
ur point.=C2=A0 Try to do some objective research and ask relevant question=
s.=C2=A0 The list will help.=C2=A0 Please stop throwing up your hands and s=
aying this is 'BAD' 'BROKEN' etc
Objectively state what you are doing and what the environment and setup is.=
=C2=A0 No one can read your mind, know your setup, etc.
Here's a list:
hardware in use on BOTH sides=C2=A0 (when you boot FreeBSD what does it sho=
w?)=C2=A0 Post the dmesg or /var/run/dmesg.bootexplain the configuration of=
 both the client and the server and connecting hardwarelocation of the info=
rmation being accessed (local or NFS)
what is being done when the error is encountereddebugging information - log=
 files, errors being generated, debug mode turned on for those processes, w=
hat flags when you started the processes, etc
So, please, although this list is VERY helpful, you have to present your is=
sue so others can understand it.=C2=A0 Also, getting on a list that deals w=
ith a specific project and bashing it right off the bat, not very helpful. =
It's like walking up to a girl's father after your first date and telling h=
im she's ugly, stupid and wouldn't put out.=C2=A0 Don't expect the father t=
o be very receptive to you getting a second date.=C2=A0 There is netiquette=
 and many here still practice it.=C2=A0 I have breached netiquette because =
I find you aren't responsive to it.
Again, please start posting relevant information, or just please stop posti=
ng as people are starting to get annoyed with the bandwidth consumption.=C2=
=A0 If there is indeed an issue, the list will help you solve it and write =
up a RELEVANT bug.=C2=A0 However, we don't even know if the bug posted is r=
elevant to your situation.
P.





    On Tuesday, August 13, 2019, 5:35:56 PM EDT, hw <hw@adminart.net> wrote=
: =20
=20
 Andrea Venturoli <ml@netfence.it> writes:

> On 8/12/19 9:46 PM, hw wrote:
>
>> And now you say you got it to work with NFS.=C2=A0 How?=C2=A0 Neither v3=
, nor v4
>> work.
>
> Strange.
> I've been using FireFox with my home on NFS since about... 15 years or so=
.
> Now I learn it doesn't work...

So how did you get it to work?

After all this, I wouldn't be surprised if FreeBSD-NFS is incompatible
with Centos-NFS.=C2=A0 Have you tried that?=C2=A0 What will you do when you=
 run
into bug 220004?
_______________________________________________
freebsd-questions@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org=
"
 =20
From owner-freebsd-questions@freebsd.org  Wed Aug 14 12:06:22 2019
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 928DCA91EB
 for <freebsd-questions@mailman.nyi.freebsd.org>;
 Wed, 14 Aug 2019 12:06:22 +0000 (UTC)
 (envelope-from mafsys1234@gmail.com)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com
 [IPv6:2607:f8b0:4864:20::631])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (2048 bits) client-digest SHA256)
 (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 467pG53Bnnz4D4F
 for <freebsd-questions@freebsd.org>; Wed, 14 Aug 2019 12:06:21 +0000 (UTC)
 (envelope-from mafsys1234@gmail.com)
Received: by mail-pl1-x631.google.com with SMTP id c14so50528068plo.0
 for <freebsd-questions@freebsd.org>; Wed, 14 Aug 2019 05:06:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=subject:to:cc:references:from:message-id:date:user-agent
 :mime-version:in-reply-to:content-language:content-transfer-encoding;
 bh=kertZEFSXfJ48wIyyPMJvk7gYdbJjCvR4tboxdYBO7c=;
 b=j40sqiY9uRbhusiVEEDbeo50U6C/xINGmA1P7I+OCQRrTCTFaI/0pj0GsfwCbZ6qGa
 ZZjUMKE/WHnDo3EXNUtwZ3KCcWJxp7GZ0cvX8kv6jIl3HpYAYe5JMLs1zWAMF08bazje
 GLAoas9649XCBJHGKHbP0fEtVUDvDV5uvJlbQo4vqi8ltJvnSSA7VVD8izeY2lQUQyQL
 WfAepIUQnc+LFxVIln+nHfrYx4iDNkTuMiIzeQ0noCTImu3YqDr+mv9qHQIASgs7nagV
 s4P6GDz6a3OT1G+ZswRLqV4Cop8qCnGMk4qvRwE+y4HURLDYwobfzffhAvK3z5jCuJT3
 nQtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:subject:to:cc:references:from:message-id:date
 :user-agent:mime-version:in-reply-to:content-language
 :content-transfer-encoding;
 bh=kertZEFSXfJ48wIyyPMJvk7gYdbJjCvR4tboxdYBO7c=;
 b=JnClxqtfj33pR2LAQ734Gq3bPf24TrzeatEkedYBWH8zGR/tz+QyIsUsZh4CiBLM1R
 YtjUMUK4eHc6+DjnBmDNCEgTyaS+Nhnp5qLKx75VvVddmKB4k7WHT+Tt2U+JZUbhQ2NU
 KrKm0Gld4zpA9iaj0LkQbU46H8konoD/sPXpTubwJAW+9dFzI4cocLjRvP4jKlYhK96A
 COiDsj8tc81qCkSnOAldWNfsHVu6u154sTiH/dXddN9n/q6rQYBeqC7ULhH0q4h9KcIJ
 2XAbH7Azvuj4v1hMsVwQ/0HbEV6jrrf2Ba+DAGuRXU+dS0LVveiZyINppaz9uuJHh1bU
 mLvQ==
X-Gm-Message-State: APjAAAVOAW8YDaaWl6Cxi2bMd7jXR/e1+nX/Joj/FbdRvC+YnaAzyQyx
 pKSNtnA7Du7AEMZAHEh91/Zn69My
X-Google-Smtp-Source: APXvYqy1C1Ydd0d7t4Ma3X0c8c6jNuiZG8rlaxJc3V8y9d8YPpavPHJ6+RhM/1QjCfWHvRhKd4uPkA==
X-Received: by 2002:a17:902:b604:: with SMTP id
 b4mr26775503pls.94.1565784379531; 
 Wed, 14 Aug 2019 05:06:19 -0700 (PDT)
Received: from [192.168.1.10] (C-59-101-167-216.mel.connect.net.au.
 [59.101.167.216])
 by smtp.gmail.com with ESMTPSA id m20sm129728128pff.79.2019.08.14.05.06.17
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 14 Aug 2019 05:06:18 -0700 (PDT)
Subject: Re: Firefox or what?
To: Andrea Venturoli <ml@netfence.it>, hw <hw@adminart.net>
Cc: freebsd-questions@freebsd.org
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>
From: MJ <mafsys1234@gmail.com>
Message-ID: <3e27ec4d-65d0-063e-eb5e-4465aa4cbc84@gmail.com>
Date: Wed, 14 Aug 2019 22:05:30 +1000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <5be8adb1-cf57-9e24-4ce9-27a76cc3ece8@netfence.it>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 467pG53Bnnz4D4F
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org;
 dkim=pass header.d=gmail.com header.s=20161025 header.b=j40sqiY9;
 dmarc=pass (policy=none) header.from=gmail.com;
 spf=pass (mx1.freebsd.org: domain of mafsys1234@gmail.com designates
 2607:f8b0:4864:20::631 as permitted sender)
 smtp.mailfrom=mafsys1234@gmail.com
X-Spamd-Result: default: False [-2.99 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[];
 TO_DN_SOME(0.00)[];
 R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36];
 FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3];
 DKIM_TRACE(0.00)[gmail.com:+];
 DMARC_POLICY_ALLOW(-0.50)[gmail.com,none];
 NEURAL_HAM_SHORT(-0.99)[-0.994,0];
 RECEIVED_SPAMHAUS_PBL(0.00)[216.167.101.59.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net
 : 127.0.0.10]; FROM_EQ_ENVFROM(0.00)[];
 SUBJECT_ENDS_QUESTION(1.00)[];
 FREEMAIL_ENVFROM(0.00)[gmail.com];
 ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US];
 MID_RHS_MATCH_FROM(0.00)[];
 DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0];
 ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0];
 R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[];
 RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0];
 MIME_GOOD(-0.10)[text/plain];
 PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org];
 IP_SCORE_FREEMAIL(0.00)[]; MIME_TRACE(0.00)[0:+];
 TO_MATCH_ENVRCPT_SOME(0.00)[];
 RCVD_IN_DNSWL_NONE(0.00)[1.3.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org
 : 127.0.5.0]; 
 IP_SCORE(0.00)[ip: (-9.08), ipnet: 2607:f8b0::/32(-2.97), asn: 15169(-2.39),
 country: US(-0.05)]; RCVD_TLS_ALL(0.00)[]
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2019 12:06:22 -0000

Thanks Andrea for pointing this out.

On 14/08/2019 9:21 pm, Andrea Venturoli 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.

I have to agree. While this list is for questions and there are many 
here that are eager to help where they can, it's almost impossible to 
answer questions like "It doesn't work; therefore FreeBSD is a failure".




To hw@adminart.net may I suggest:

A) we don't know what doesn't work, what you have tried and what 
configuration you have. Examples of configuration files, log messages, 
error codes and the like will help. Most people here are not clairvoyant.

B) Searching through bug lists to find a potential bug that might occur 
in the sub-system you are utilising in FreeBSD seems a nonsensical 
approach. Your time would be better spent giving us the information 
needed to assist you.

C) State what actions you have taken, what you have read, what confuses 
you. People can help if they know what your problem is.

D) Be specific. There's never too much information that you can provide 
relevant to an issue.

In the end, you're free to ask vague questions; the list is free to give 
you vague replies.

Mark



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