From owner-freebsd-questions@freebsd.org Sat May 16 18:56:28 2020 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 410C42FA68B for ; Sat, 16 May 2020 18:56:28 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (mail.covisp.net [65.121.55.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49PZHv4s0Cz3P96 for ; Sat, 16 May 2020 18:56:27 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life Date: Sat, 16 May 2020 12:56:25 -0600 References: <20200217231452.717FA1E820@freefall.freebsd.org> <85E7C97E-EF8B-4FC7-8EF1-758B7BCBAE90@kreme.com> <05112EEC-7FA3-4E18-974B-263A58058E01@kicp.uchicago.edu> <332714B8-2798-42CF-A082-9EDA180CC65B@kreme.com> <20200516201923.8676289a.freebsd@edvax.de> To: FreeBSD In-Reply-To: <20200516201923.8676289a.freebsd@edvax.de> Message-Id: <257EF587-92B5-4671-B6F4-89E86CC2ACA0@kreme.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49PZHv4s0Cz3P96 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of kremels@kreme.com designates 65.121.55.42 as permitted sender) smtp.mailfrom=kremels@kreme.com X-Spamd-Result: default: False [-0.49 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.968,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MISSING_MIME_VERSION(2.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[kreme.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; IP_SCORE(-0.12)[ip: (-0.32), ipnet: 65.112.0.0/12(-0.06), asn: 209(-0.17), country: US(-0.05)]; TO_DN_ALL(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; RCVD_IN_DNSWL_LOW(-0.10)[42.55.121.65.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:65.112.0.0/12, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 May 2020 18:56:28 -0000 On 16 May 2020, at 12:19, Polytropon wrote: > And it runs and runs and runs and runs. Older hardware could do this. = And older software, in combination with that hardware, could do this. As = long as the requirements don't change, it's not a problem, especially = not when _not_ connected to the Internet - yes, I'm quite aware that = _this_ is a significant problem in considering system security. If the computer is not connected to any other computers and no person = ever has access to it, that=E2=80=99s fine. Otherwise, old OSes are porous insecure botnets-in-wait with dozens or = hundreds or thousands of exploits. And if your machine is not connected to the Internet and no human uses = it, go ahead an run FreeBSD 1.0. Who=E2=80=99s stopping you? But that=E2=80=99s an even smaller tiny tiny percentage than desktop = FreeBSD users and should have no bearing on the EOL schedule of the = current versions of the OS. The issue has been (but hopefully is not any lonher?) is that upgrading = from one version to another can be =E2=80=A6 well, sometimes impossible = is the best result. More than once I=E2=80=99ve had to completely setup = anew because the upgrade path either did not work or had been shut-off = (like version x.4 can be upgraded to only from x.3, but x.3 cannot be = installed now because it is EOL so you have no path forward from x.0 x.1 = and x.2 but to start afresh and you installed x.2 6 months ago). --=20 I'm dangerous when I know what I'm doing.