Date: Sun, 04 Dec 2022 01:09:35 +1100 From: Ian Smith <smithi@nimnet.asn.au> To: Steve O'Hara-Smith <steve@sohara.org>,paul beard <paulbeard@gmail.com> Cc: questions@freebsd.org Subject: Re: what am I missing RE: freebsd-update? Message-ID: <EC6EABA7-2E12-4B69-B19E-41F05BE5E499@nimnet.asn.au> In-Reply-To: <20221202062052.9dfa1ef99a8f78aee029a8e2@sohara.org> References: <CAMtcK2pNxAV72V0rm36UALDcRdG2J9Tv_3Q7UaQHKEqFMEm_uw@mail.gmail.com> <c8a9e74e-b787-bf2c-a685-a17eac3b9dc1@freebsd.org> <CAMtcK2ovr2Li-KSU73_Q8rnPCapiD2c726sGSKgPZju5%2B%2BPyvA@mail.gmail.com> <20221202062052.9dfa1ef99a8f78aee029a8e2@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 December 2022 5:20:52 pm AEDT, Steve O'Hara-Smith <steve@sohara=2Eorg>= wrote: > On Thu, 1 Dec 2022 16:44:37 -0800 > paul beard <paulbeard@gmail=2Ecom> wrote: >=20 > > Thank you for all the info=E2=80=A6it seems nothing is wrong, but wha= t > prompted > > this was a message about this release nearing EOL or end of > support=2E Not > > sure where I saw it now, perhaps at login but I don't see it now=2E It was the firsf message on screen in the freebsd-update process, and yes = it's rather trigger-happy=2E > The file with the EOL dates in got updated as part of the update=2E > The dates are a guess that gets refined as the release process of the > next > release progresses=2E It doesn't work too well it always alarms people > early=2E More definitive is https://www=2Efreebsd=2Eorg/security/#sup showing 12=2E3 EoL as 3 months after 12=2E4-RELEASE (which is immanent, li= kely this week), and that 12-STABLE will be EoL on 31st December 2023=2E > > So freebsd-version -kru > > 12=2E3-RELEASE-p6 > > 12=2E3-RELEASE-p6 > > 12=2E3-RELEASE-p10 > >=20 > > means that my installed and running kernel are the same and my > userland is > > a few patches ahead but they should sync up at some point? >=20 > Not quite - what it really means is that p7, p8, p9 and p10 did not > contain any kernel updates and so the kernel version didn't get > bumped in > them=2E So if there are no more kernel updates before EOL they'll never > "sync up"=2E Without a major security incident, p6 should be it for 12=2E3 kernel=2E M= aybe a few userland patches if needed =2E=2E=2E > This has historical reasons - once upon a time the kernel version > was the version and all updates were source builds but with binary > patch > updates it seems crazy to update the kernel just to change a number > so we > get the concept of userland version and the original version becomes > the kernel version=2E >=20 > There's a practical advantage to it, scripted updates can check for > a changed kernel version and decide whether to reboot or just restart s= ervices=2E Yes, though you (or scripts) need to know which services need restarting; = rebooting is always safer=2E cheers, Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC6EABA7-2E12-4B69-B19E-41F05BE5E499>