Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 May 2020 12:56:25 -0600
From:      "@lbutlr" <>
To:        FreeBSD <>
Subject:   Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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).

I'm dangerous when I know what I'm doing.

Want to link to this message? Use this URL: <>