Hello!

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

[m@teufel ~]$ cat /etc/os-release
NAME=FreeBSD
VERSION="14.2-RELEASE-p3"
VERSION_ID="14.2"
ID=freebsd
ANSI_COLOR="0;31"
PRETTY_NAME="FreeBSD 14.2-RELEASE-p3"
CPE_NAME="cpe:/o:freebsd:freebsd:14.2"
HOME_URL="https://FreeBSD.org/"
BUG_REPORT_URL="https://bugs.FreeBSD.org/"
[m@teufel ~]$

[m@teufel ~]$ freebsd-version
14.3-RELEASE
[m@teufel ~]$

[m@teufel ~]$ sysctl -n kern.osrelease
14.3-RELEASE
[m@teufel ~]$

Is that a bug or did the upgrade fail at any point?

--
kind regards
Marco

Send spam to [email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Marco Moock <[email protected]> writes:

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

Is your /etc/os-release a soft link to /var/run/os-release?

What does your /var/run/os-release say?

Did you remember to run "freebsd-update install" (and reboot)
the second time to install the user-land parts?
-WBE

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 12.06.2025 12:43 Uhr Winston wrote:

Marco Moock <[email protected]> writes:

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

Is your /etc/os-release a soft link to /var/run/os-release?

Yes.

Did you remember to run "freebsd-update install" (and reboot)
the second time to install the user-land parts?

I did and IIRC I was asked a few questions if something sounds
reasonable.

I tried again and it gives me no updates to install.

--
kind regards
Marco

Send spam to [email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <[email protected]>,
Marco Moock <[email protected]> wrote:

Hello!

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

[m@teufel ~]$ cat /etc/os-release
NAME=FreeBSD
VERSION="14.2-RELEASE-p3"
VERSION_ID="14.2"
ID=freebsd
ANSI_COLOR="0;31"
PRETTY_NAME="FreeBSD 14.2-RELEASE-p3"
CPE_NAME="cpe:/o:freebsd:freebsd:14.2"
HOME_URL="https://FreeBSD.org/"
BUG_REPORT_URL="https://bugs.FreeBSD.org/"
[m@teufel ~]$

[m@teufel ~]$ freebsd-version
14.3-RELEASE
[m@teufel ~]$

[m@teufel ~]$ sysctl -n kern.osrelease
14.3-RELEASE
[m@teufel ~]$

Is that a bug or did the upgrade fail at any point?

A bug.

eeing the same thing here.

--
kind regards
Marco

Send spam to [email protected]

--
Member - Liberal International This is [email protected] Ici [email protected]
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism ;
All I want to hear from JEsus Christ is WEll done Good and Faithful servant

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <[email protected]>,
Marco Moock <[email protected]> wrote:

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

...

[m@teufel ~]$ cat /etc/os-release
NAME=FreeBSD
VERSION="14.2-RELEASE-p3"
VERSION_ID="14.2"

...

PRETTY_NAME="FreeBSD 14.2-RELEASE-p3"

Is that a bug or did the upgrade fail at any point?

to which [email protected] (The Doctor) replied:

A bug.

eeing the same thing here.

Curious. A 14.2 system I upgraded has 14.3-RELEASE in os-release,
so it's not all systems.
-WBE

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <[email protected]>,
Marco Moock <[email protected]> wrote:

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

I saw this bug on one system.
I fixed it this way:
# service os-release onestart

If I can reproduce, I'll file a bug.
The mechanism to populate this file isn't documented but Bugzilla
did point to the original PR: <URL:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238953>
John
[email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Yo,

On 13/06/2025 02:20, John D Groenveld wrote:

In article <[email protected]>,
Marco Moock <[email protected]> wrote:

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

I saw this bug on one system.
I fixed it this way:
# service os-release onestart

If I can reproduce, I'll file a bug.
The mechanism to populate this file isn't documented but Bugzilla
did point to the original PR: <URL:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238953>
John
[email protected]

As FYI/Support for Marco:

I had two systems with the sympton:
The first did not update at all, the second one had a stale link in
/etc, which was just fixed with unlink/ln. In both instances I folled
the official guide (install -> reboot -> install).


--

Cheers,
G.

Quis custodiet ipsos custodes? ---------------------------->8------------------------------
/"\
\ / ASCII Ribbon Campaign
X against HTML e-mail
/ \
---------------------------->8------------------------------

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <[email protected]>,
Goetz Schultz <[email protected]> wrote:

I had two systems with the sympton:
The first did not update at all, the second one had a stale link in
/etc, which was just fixed with unlink/ln. In both instances I folled
the official guide (install -> reboot -> install).

By default on illumos /var/run is tmpfs(4FS) <URL:https://github.com/illumos/illumos-gate/blob/master/usr/src/cmd/svc/milestone/fs-minimal>
Any experience here mounting /var/run tmpfs(5)?
John
[email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Marco Moock <[email protected]> wrote:

Hello!

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

[m@teufel ~]$ cat /etc/os-release
NAME=FreeBSD
VERSION="14.2-RELEASE-p3"
VERSION_ID="14.2"

Could a port have overlaied /etc/os-release ?

IIRC, /etc/os-release is a Linux thing and may be
needed just for some ports.

Is that a bug or did the upgrade fail at any point?

YMMV,
My FreeBSD server had a heat death a while ago (my fault) and
I never got around to replacing it. So, is /etc/os-release
now part of FreeBSD base ? It was not back then.

--
[t]csh(1) - "An elegant shell, for a more... civilized age."
- Paraphrasing Star Wars

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 13/06/2025 13:52, John D Groenveld wrote:

In article <[email protected]>,
Goetz Schultz <[email protected]> wrote:

I had two systems with the sympton:
The first did not update at all, the second one had a stale link in
/etc, which was just fixed with unlink/ln. In both instances I folled
the official guide (install -> reboot -> install).

By default on illumos /var/run is tmpfs(4FS) <URL:https://github.com/illumos/illumos-gate/blob/master/usr/src/cmd/svc/milestone/fs-minimal>
Any experience here mounting /var/run tmpfs(5)?
John
[email protected]

I might miss something here, but how is this related to FBSD? My
/var/run(s) is(are) on a ufs slice.

--

Cheers,
G.

Quis custodiet ipsos custodes? ---------------------------->8------------------------------
/"\
\ / ASCII Ribbon Campaign
X against HTML e-mail
/ \
---------------------------->8------------------------------

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 13/06/2025 18:25, John D Groenveld wrote:

In article <[email protected]>,
Goetz Schultz <[email protected]> wrote:

I might miss something here, but how is this related to FBSD? My
/var/run(s) is(are) on a ufs slice.

# uname -srv
FreeBSD 14.3-RELEASE FreeBSD 14.3-RELEASE releng/14.3-n271432-8c9ce319fef7 GENERIC
# mount -p | grep /var/run
tmpfs /var/run tmpfs rw 0 0

So far no issues with a KDE workstation.

Browsing FreeBSD.ORG suggests some ports may incorrectly expect
/var/run to persist across reboots.
John
[email protected]

Just to return the courtesy:

bash-5.2# uname -srv
FreeBSD 14.3-RELEASE FreeBSD 14.3-RELEASE
releng/14.3-n271432-8c9ce319fef7 GENERIC
bash-5.2# mount -p | grep /var/run
bash-5.2#

Does not effect me, as I consider it to be a Linux Thing :-)

--

Cheers,
G.

Quis custodiet ipsos custodes? ---------------------------->8------------------------------
/"\
\ / ASCII Ribbon Campaign
X against HTML e-mail
/ \
---------------------------->8------------------------------

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <[email protected]>,
Goetz Schultz <[email protected]> wrote:

I might miss something here, but how is this related to FBSD? My
/var/run(s) is(are) on a ufs slice.

# uname -srv
FreeBSD 14.3-RELEASE FreeBSD 14.3-RELEASE releng/14.3-n271432-8c9ce319fef7 GENERIC
# mount -p | grep /var/run
tmpfs /var/run tmpfs rw 0 0

So far no issues with a KDE workstation.

Browsing FreeBSD.ORG suggests some ports may incorrectly expect
/var/run to persist across reboots.
John
[email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 13 Jun 2025 13:23:17 -0000 (UTC) John McCue
<[email protected]> wrote:

Marco Moock <[email protected]> wrote:

Hello!

Yesterday I upgraded to 14.3, but /etc/os-release still shows 14.2.

[m@teufel ~]$ cat /etc/os-release
NAME=FreeBSD
VERSION="14.2-RELEASE-p3"
VERSION_ID="14.2"

Could a port have overlaied /etc/os-release ?

IIRC, /etc/os-release is a Linux thing and may be
needed just for some ports.

Is there a way to query which package provides that file?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 13 Jun 2025 10:23: Goetz Schultz wrote:

The first did not update at all, the second one had a stale link in
/etc, which was just fixed with unlink/ln.

Where did it point in the error condition and where when everything was
fine?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Marco Moock <[email protected]> asked:

Is there a way to query which package provides that file?

pkg which /path/to/file, such as "pkg which /etc/os-release".
-WBE

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Yo,

On 14/06/2025 10:41, Marco Moock wrote:

On 13 Jun 2025 10:23: Goetz Schultz wrote:

The first did not update at all, the second one had a stale link in
/etc, which was just fixed with unlink/ln.

Where did it point in the error condition and where when everything was
fine?

Pointing to /var/run/os-release, as meantioned by others. I did not
notice any misbehaviour (that box serves as mailserver only plus some
cron's from my home-dir)

--

Cheers,
G.

Quis custodiet ipsos custodes? ---------------------------->8------------------------------
/"\
\ / ASCII Ribbon Campaign
X against HTML e-mail
/ \
---------------------------->8------------------------------

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 14.06.2025 07:40 Uhr Winston wrote:

Marco Moock <[email protected]> asked:

Is there a way to query which package provides that file?

pkg which /path/to/file, such as "pkg which /etc/os-release".

[m@teufel ~]$ pkg which /etc/os-release
/etc/os-release was not found in the database
[m@teufel ~]$

Does that only show the files directly provided by a package or also
stuff that is being generated by a package's install scripts?

--
kind regards
Marco

Send spam to [email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <[email protected]>,
Marco Moock <[email protected]> wrote:

Does that only show the files directly provided by a package

Yes.

or also
stuff that is being generated by a package's install scripts?

My WAG is that /etc/os-release will no longer be generated
by /etc/rc.d/os-release once FreeBSD moves to pkgbase. <URL:https://wiki.freebsd.org/PkgBase>

John
[email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 15.06.2025 13:05 John D Groenveld wrote:

My WAG is that /etc/os-release will no longer be generated
by /etc/rc.d/os-release once FreeBSD moves to pkgbase. <URL:https://wiki.freebsd.org/PkgBase>

Is that intended or a bug?

If it is intended, why is that file not being deleted?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <[email protected]>,
Marco Moock <[email protected]> wrote:

Is that intended or a bug?

If it is intended, why is that file not being deleted?

I think I prefer /etc/os-release not be generated by the host, but
instead be an artifact of the build delivered as part of pkgbase.
We'll see what happens with FreeBSD 15.

John
[email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)