From owner-freebsd-questions@freebsd.org Sun Mar 21 19:16:53 2021 Return-Path: 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 0A9165A8B42 for ; Sun, 21 Mar 2021 19:16:53 +0000 (UTC) (envelope-from kh@panix.com) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F3S6r3G91z3pZp for ; Sun, 21 Mar 2021 19:16:52 +0000 (UTC) (envelope-from kh@panix.com) Received: from rain.home (pool-173-48-64-3.bstnma.fios.verizon.net [173.48.64.3]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4F3S6q2Nk4zgwV for ; Sun, 21 Mar 2021 15:16:51 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1616354211; bh=2xKdvn2P+A47XmUyNNoxsOtwzCNNMFrxKdXFisWRNPc=; h=Subject:To:References:From:Date:In-Reply-To; b=Q0eksIRlxZk91ms9D2ZOIeoYLn6T2YZBD/DhnNG64nDbVtfFZEem6wgJGfrOvEElM LbrcAludwgFcf8/1lZYgh2mn2Zkzz8GoQnAE6tS0KbUPNtxK5+5Yr2sok752DH/pq9 nzd+b9yepfFKLRgyRCUj0yl92GSVOMkpM+fycFQE= Subject: Re: OS to replace FreeBSD To: freebsd-questions@freebsd.org References: <20210320132339.00004d9a@seibercom.net> <38EDD406-3EC4-4F71-B990-DDD1E753D091@kreme.com> <20210321113403.00004056@seibercom.net> <20210321120633.00004136@seibercom.net> <20210321142553.000046d6@seibercom.net> From: Kurt Hackenberg Message-ID: Date: Sun, 21 Mar 2021 15:16:49 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <20210321142553.000046d6@seibercom.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4F3S6r3G91z3pZp X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=panix.com header.s=panix header.b=Q0eksIRl; dmarc=none; spf=pass (mx1.freebsd.org: domain of kh@panix.com designates 166.84.1.89 as permitted sender) smtp.mailfrom=kh@panix.com X-Spamd-Result: default: False [-5.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[166.84.1.89:from]; R_SPF_ALLOW(-0.20)[+ip4:166.84.0.0/16]; TO_DN_NONE(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[166.84.1.89:from]; DKIM_TRACE(0.00)[panix.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2033, ipnet:166.84.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[173.48.64.3:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[panix.com:s=panix]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[panix.com]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[panix.com:dkim]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2021 19:16:53 -0000 On 2021/03/21 14:25, Jerry wrote: > [irritation] Jerry, 35 years of unhappy experience has shown us that the only effective way to deal with Internet flamers is to ignore them. Don't even read their messages, and, ideally, make your reader software not even show you messages from them. Usenet readers added that automatic filtering long ago, for that reason. Some mail readers can also do something like that. I suggest that you ignore Mr. Friedman. You might also moderate your tone slightly, in one way: be less absolutist. You say FreeBSD is wrong and all other OSes are right. I get the impression that it's more like this: there's an obscure hardware error, and some OSes either don't trigger it or work around it, but FreeBSD currently has a problem with it. But nobody knows for sure. Now that somebody has volunteered to debug this, maybe it will get somewhere.