Rocksolid Light

News from da outaworlds

mail  files  register  groups  login

Message-ID:  

Beware of a tall black man with one blond shoe.

comp / comp.unix.bsd.freebsd.misc / Re: Version Report Discrepancies (uname -a and freebsd-version)

SubjectAuthor
* Version Report Discrepancies (uname -a and freebsd-version)Louis Epstein
`* Re: Version Report Discrepancies (uname -a and freebsd-version)Louis Epstein
 `* Re: Version Report Discrepancies (uname -a and freebsd-version)Lowell Gilbert
  `* Re: Version Report Discrepancies (uname -a and freebsd-version)Jesse Rehmer
   `- Re: Version Report Discrepancies (uname -a and freebsd-version)Jesse Rehmer

1
Subject: Version Report Discrepancies (uname -a and freebsd-version)
From: Louis Epstein
Newsgroups: comp.unix.bsd.freebsd.misc
Organization: PANIX Public Access Internet and UNIX, NYC
Date: Thu, 2 Jan 2025 00:25 UTC
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!panix!.POSTED.main.lekno.ws!not-for-mail
From: le@lekno.ws (Louis Epstein)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Version Report Discrepancies (uname -a and freebsd-version)
Date: Thu, 2 Jan 2025 00:25:39 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vl4me3$f4n$1@reader2.panix.com>
Injection-Date: Thu, 2 Jan 2025 00:25:39 -0000 (UTC)
Injection-Info: reader2.panix.com; posting-host="main.lekno.ws:12.144.5.2";
logging-data="15511"; mail-complaints-to="abuse@panix.com"
User-Agent: tin/2.6.4-20241224 ("Helmsdale") (FreeBSD/13.4-RELEASE-p1 (amd64))
View all headers

Why are there occasional discrepancies in what is reported as the
running version?

After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
but 13.4-RELEASE-p2 as response to freebsd-version .

When the upgrade completed I was told -p1 was installed,
when I ran freebsd-update fetch I was told no updates
were available or needed to run -p2.

Do some patches only register with some programs and not others?

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
From: Louis Epstein
Newsgroups: comp.unix.bsd.freebsd.misc
Organization: PANIX Public Access Internet and UNIX, NYC
Date: Thu, 2 Jan 2025 21:04 UTC
References: 1
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!panix!.POSTED.main.lekno.ws!not-for-mail
From: le@lekno.ws (Louis Epstein)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
Date: Thu, 2 Jan 2025 21:04:02 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vl6v02$5ck$1@reader2.panix.com>
References: <vl4me3$f4n$1@reader2.panix.com>
Injection-Date: Thu, 2 Jan 2025 21:04:02 -0000 (UTC)
Injection-Info: reader2.panix.com; posting-host="main.lekno.ws:12.144.5.2";
logging-data="5524"; mail-complaints-to="abuse@panix.com"
User-Agent: tin/2.6.4-20241224 ("Helmsdale") (FreeBSD/13.4-RELEASE-p1 (amd64))
View all headers

Louis Epstein <le@lekno.ws> wrote:
> Why are there occasional discrepancies in what is reported as the
> running version?
>
> After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
> but 13.4-RELEASE-p2 as response to freebsd-version .
>
> When the upgrade completed I was told -p1 was installed,

This repeats at every login

> when I ran freebsd-update fetch I was told no updates
> were available or needed to run -p2.
>
> Do some patches only register with some programs and not others?
>
> -=-=-
> The World Trade Center towers MUST rise again,
> at least as tall as before...or terror has triumphed.

Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
From: Lowell Gilbert
Newsgroups: comp.unix.bsd.freebsd.misc
Organization: A noiseless patient Spider
Date: Fri, 3 Jan 2025 03:54 UTC
References: 1 2
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: lgusenet@be-well.ilk.org (Lowell Gilbert)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
Date: Thu, 02 Jan 2025 22:54:37 -0500
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <44ikqwpn5u.fsf@be-well.ilk.org>
References: <vl4me3$f4n$1@reader2.panix.com> <vl6v02$5ck$1@reader2.panix.com>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Fri, 03 Jan 2025 04:54:38 +0100 (CET)
Injection-Info: dont-email.me; posting-host="f2ed49872d3a53e3bf064c5b03af3856";
logging-data="3818411"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX187LPMJyYGEPK8lJQfTT0qS"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:xQRRXn24tvAx+3YAQRDcV1Fz8vQ=
sha1:Jwa8f2dME6++XbOnVq1vkV5mq7g=
View all headers

Louis Epstein <le@lekno.ws> writes:

> Louis Epstein <le@lekno.ws> wrote:
>> Why are there occasional discrepancies in what is reported as the
>> running version?
>>
>> After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
>> but 13.4-RELEASE-p2 as response to freebsd-version .
>>
>> When the upgrade completed I was told -p1 was installed,
>
> This repeats at every login

Is this not just the normal thing where -p2
didn't need to update the kernel?

Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
From: Jesse Rehmer
Newsgroups: comp.unix.bsd.freebsd.misc
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sun, 5 Jan 2025 08:24 UTC
References: 1 2 3
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!tncsrv06.tnetconsulting.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: jesse.rehmer@blueworldhosting.com (Jesse Rehmer)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
Date: Sun, 5 Jan 2025 08:24:21 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <vldfjl$3i9$1@nnrp.usenet.blueworldhosting.com>
References: <vl4me3$f4n$1@reader2.panix.com> <vl6v02$5ck$1@reader2.panix.com> <44ikqwpn5u.fsf@be-well.ilk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=fixed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 5 Jan 2025 08:24:21 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="3657"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: Usenapp for MacOS
Cancel-Lock: sha1:QA1tzzqtYJ6bh4lbbboCJnFm7yc= sha256:4qgtNiQLffaJtFV2wEeDSUqo7l3mwKxvS451H2jHhUE=
sha1:RDnacc2DJf64dDscDfFw3hiJXk8= sha256:7S9ixa4OzmeHG81+TKTxX2qaNlf6TMZ03efbdgprups=
X-Usenapp: v1.27.4/d - Full License
View all headers

On Jan 2, 2025 at 9:54:37 PM CST, "Lowell Gilbert" <lgusenet@be-well.ilk.org>
wrote:

> Louis Epstein <le@lekno.ws> writes:
>
>> Louis Epstein <le@lekno.ws> wrote:
>>> Why are there occasional discrepancies in what is reported as the
>>> running version?
>>>
>>> After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
>>> but 13.4-RELEASE-p2 as response to freebsd-version .
>>>
>>> When the upgrade completed I was told -p1 was installed,
>>
>> This repeats at every login
>
> Is this not just the normal thing where -p2
> didn't need to update the kernel?

Most likely. I recommend using "freebsd-version -kru" to get the list of
versions, from the manpage:

-k Print the version and patch level of the installed kernel.
Unlike uname(1), if a new kernel has been installed but the
system has not yet rebooted, freebsd-version will print the
version and patch level of the new kernel.

-r Print the version and patch level of the running kernel.
Unlike uname(1), this is unaffected by environment variables.

-u Print the version and patch level of the installed userland.
These are hardcoded into freebsd-version during the build.

There are some patch releases that do not update the kernel, or only the
userland tools are updated. This causes confusion from time to time and this
comes up on the FreeBSD forums often.

Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
From: Jesse Rehmer
Newsgroups: comp.unix.bsd.freebsd.misc
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sun, 5 Jan 2025 08:25 UTC
References: 1 2 3 4
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: jesse.rehmer@blueworldhosting.com (Jesse Rehmer)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Version Report Discrepancies (uname -a and freebsd-version)
Date: Sun, 5 Jan 2025 08:25:59 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <vldfmn$4ug$1@nnrp.usenet.blueworldhosting.com>
References: <vl4me3$f4n$1@reader2.panix.com> <vl6v02$5ck$1@reader2.panix.com> <44ikqwpn5u.fsf@be-well.ilk.org> <vldfjl$3i9$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=fixed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 5 Jan 2025 08:25:59 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="5072"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: Usenapp for MacOS
Cancel-Lock: sha1:uS7Dp+VbdHgNNivOUe9+ainnOaE= sha256:1VJTJ4jj//oP+DQOGq9VVoTkZ71SenePo8Vn2MoqrAM=
sha1:SuB70M1GlBsBnyMEQg84hyq9EtA= sha256:5gnsqhTNxdRmrBG022n9Xw2mwkk4JFwzSE9UaMrgJ6c=
X-Usenapp: v1.27.4/d - Full License
View all headers

On Jan 5, 2025 at 2:24:21 AM CST, "Jesse Rehmer"
<jesse.rehmer@blueworldhosting.com> wrote:

> On Jan 2, 2025 at 9:54:37 PM CST, "Lowell Gilbert" <lgusenet@be-well.ilk.org>
> wrote:
>
>> Louis Epstein <le@lekno.ws> writes:
>>
>>> Louis Epstein <le@lekno.ws> wrote:
>>>> Why are there occasional discrepancies in what is reported as the
>>>> running version?
>>>>
>>>> After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
>>>> but 13.4-RELEASE-p2 as response to freebsd-version .
>>>>
>>>> When the upgrade completed I was told -p1 was installed,
>>>
>>> This repeats at every login
>>
>> Is this not just the normal thing where -p2
>> didn't need to update the kernel?
>
> Most likely. I recommend using "freebsd-version -kru" to get the list of
> versions, from the manpage:
>
> -k Print the version and patch level of the installed kernel.
> Unlike uname(1), if a new kernel has been installed but the
> system has not yet rebooted, freebsd-version will print the
> version and patch level of the new kernel.
>
> -r Print the version and patch level of the running kernel.
> Unlike uname(1), this is unaffected by environment variables.
>
> -u Print the version and patch level of the installed userland.
> These are hardcoded into freebsd-version during the build.
>
> There are some patch releases that do not update the kernel, or only the
> userland tools are updated. This causes confusion from time to time and this
> comes up on the FreeBSD forums often.

And I can confirm on my 13.4 system I see the following:

# freebsd-version -kru
13.4-RELEASE-p1
13.4-RELEASE-p1
13.4-RELEASE-p2

This is normal. In the p2 patch release the kernel was not updated.

1

rocksolid light 0.9.8
clearnet tor