From owner-freebsd-advocacy@FreeBSD.ORG Mon Dec 16 16:43:25 2013 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99955B87 for ; Mon, 16 Dec 2013 16:43:25 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7C665118E for ; Mon, 16 Dec 2013 16:43:25 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VsbGG-0001wg-Ut for freebsd-advocacy@freebsd.org; Mon, 16 Dec 2013 08:43:17 -0800 Date: Mon, 16 Dec 2013 08:43:16 -0800 (PST) From: Beeblebrox To: freebsd-advocacy@freebsd.org Message-ID: <1387212196855-5869061.post@n5.nabble.com> Subject: Correction for MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 16:43:25 -0000 The post below shows up at #7 in google search for "freebsd pf version". The title of the post is "Do not use FreeBSD 9.0 as a PF firewall " Probably a "known issue", but it could be useful to demand a follow-up post along the lines "9.2 is now the norm and sysutils/pftop is no longer broken". Failing that, lets set up a "FreeBSD malicious sites" page, where deliberately misleading content or sites witch refuse to correct their slander are listed and pushed on to search engines. Just as a newspaper must retract erroneous news reports, Blogs are also obligated to publish corrective measures taken by the companies or organizations which they have accused. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Correction-for-tp5869061.html Sent from the freebsd-advocacy mailing list archive at Nabble.com. From owner-freebsd-advocacy@FreeBSD.ORG Tue Dec 17 02:43:07 2013 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B92DADF1 for ; Tue, 17 Dec 2013 02:43:07 +0000 (UTC) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3EFC11D28 for ; Tue, 17 Dec 2013 02:43:06 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBFF6F.dip0.t-ipconnect.de [217.251.255.111]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id rBH2goPU049172; Tue, 17 Dec 2013 02:42:50 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id rBH2gjEJ032838; Tue, 17 Dec 2013 03:42:45 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id rBH2gVwV014884; Tue, 17 Dec 2013 03:42:38 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201312170242.rBH2gVwV014884@fire.js.berklix.net> To: freebsd-advocacy@freebsd.org Subject: Re: Correction for From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 16 Dec 2013 08:43:16 PST." <1387212196855-5869061.post@n5.nabble.com> Date: Tue, 17 Dec 2013 03:42:31 +0100 Sender: jhs@berklix.com Cc: Beeblebrox X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 02:43:07 -0000 Beeblebrox wrote: > The post below shows up at #7 in google search for "freebsd pf version". > The title of the post is "Do not use FreeBSD 9.0 as a PF firewall " http://www.pantz.org/software/pf/do_not_use_freebsd_9.0_as_a_pf_firewall.html "Posted on 02-20-2012 02:59:21 UTC | Updated on 03-29-2012 02:35:09 UTC" Near 2 years old. Most readers of PD src OSs know a .0 release is adventurous (though page author didnt mention that). Most readers long since would know to search for newer FreeBSDs, & probably see 9.0 was dropped 2013-03-31, 8.5 month back. http://www.freebsd.org/security/unsupported.html > Probably a "known issue", but it could be useful to demand a follow-up post > along the lines "9.2 is now the norm and sysutils/pftop is no longer > broken". Only Request not Demand, else you'll fail, annoy yourself & provoke strife. > Failing that, lets set up a "FreeBSD malicious sites" page, where No! It's just some guy who tried another UX, who ran out of time before he learned all the differences. Better not divert to create & maintain a growing set of correctons to ever more ancient non freebsd.org blogs. > deliberately misleading content or sites witch refuse to correct their ...........................................which is a different word not a typo. It is not obvious he deliberately got things wrong IMO, (When I last tried Linux for interest, I'm sure I got things wrong). > slander are listed and pushed on to search engines. Just as a newspaper must Wrong law. Slander is spoken, Libel is written. > retract erroneous news reports, Blogs are also obligated to publish > corrective measures taken by the companies or organizations which they have > accused. Forget law : - Of near 200 sovereign global nations independent legal systems, few might "obligate" web page corrections, & fewer enforce it, & only then if You pay a lawyer. - If something is not a page claiming to be a maintained current comparison, but merely a Blog (= b[.+]log ?) Log of experiences at Date, (as that page does) I see no obligation to waste time updating it. - Don't "Demand" a fix, Offer author a friendly short update ready to drop in, with href= to wherever your research with http://www.freebsd.org/send-pr.html shows fixes were made. - Target MS for strife, not a BSD or a Linux. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Interleave replies below like a play script. Indent old text with "> ". Send plain text, not quoted-printable, HTML, base64, or multipart/alternative.