Date: Sat, 20 Jun 2026 17:15:49 -0700 From: Mark Millard <marklmi@yahoo.com> To: Mike <the.lists@mgm51.com>, freebsd-pkgbase@FreeBSD.org Subject: Re: Moving to pkg-based in 15.1 ... Message-ID: <df3cb159-5661-45e5-bc2d-7f350aeaf912@yahoo.com> In-Reply-To: <db84590d-4284-4a65-83bd-65b517fb783d@mgm51.com>
index | next in thread | previous in thread | raw e-mail
On 6/20/26 16:25, Mike wrote:
>
> I have a couple of questions as I run a test environment ...
>
> For starters, I downloaded and installed the memstick image of 15.1
> AMD64. So that is what I am working with here.
>
> OK, under the prior environment when I wanted to update from, say, p5 to
> p6 of the current installed version (e.g., 14.3 p5 to 14.3 p6), I had a
> script that ran ...
>
> /usr/sbin/freebsd-update fetch
>
> then, after a yes/no prompt ...
>
> /usr/sbin/freebsd-update install
>
> then, when that completed the script ran ...
>
> InstalledKernelVersion=$( /bin/freebsd-version -k )
> RunningKernelVersion=$( /bin/freebsd-version -r )
> InstalledUserLandVersion=$( /bin/freebsd-version -u )
>
> echo "Running kernel: ${RunningKernelVersion}"
> echo "Installed kernel: ${InstalledKernelVersion}"
> echo "Installed userland: ${InstalledUserLandVersion}"
>
> and based upon that, I knew whether or not I needed to reboot.
Well, if you do not reboot, the live system processes would still be
based on the old userland files --if any of those were updated. The old
kernel would also be running.
>
> It was fairly simple. I just ran the script. No config file changes
> needed.
I expect that, while rare, needing to touch a configuration file is
still a possibility for a patch release.
>
>
> Now, as I understand the pkgbase system, it has gotten a bit more complex.
>
> I no longer see that easy ability to update from one patch level to the
> current patch level within the installed version.
>
> As I read...
>
> https://wiki.freebsd.org/PkgBase
>
> I see examples of "Minor version upgrades." But no examples of updating
> from one patch level to a subsequent patch level within a version.
>
> Is there a FreeBSD wiki article I have missed?
>
> thx.
>
>
>
>
Presuming that the updates have updated in what is accessed by, say,:
<https://pkg.freebsd.org/FreeBSD:15:amd64/base_release_1/>;
then:
# pkg upgrade -r FreeBSD-base
or:
# pkg-static upgrade -r FreeBSD-base
is a way intended for much of the activity. It will prompt unless you
supply specific command line options to avoid such.
The command may leave behind *.pkgnew files that should be considered
for merging or replacing the older file (the * part of the name). Any
*.pkgsave files are the other way around: a new file was put in place
and the old one has the new, longer name for consideration of merging
content. (Technically an upgrade can cause an install of something new.
Not likely for patch releases.)
pkgbase is not following the "kernel then reboot then world then reboot"
sort of protocol so far. A manual reboot afterwards is probably
appropriate unless you know that no file used by the live system was
updated.
The closest I know of for figuring out ahead of time if the update is
available is to use:
https://people.freebsd.org/~dbaio/pkg-master-report.html
looking for, say, freebsd:15:x86:64 with base_release_1 and seeing what
its Timestamp and Elapsed time are if it is 100% Synced with Sync
present for that context.
This can get into judging time relationships that are not obvious.
Otherwise just try the command and see what it reports.
--
===
Mark Millard
marklmi at yahoo.com
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?df3cb159-5661-45e5-bc2d-7f350aeaf912>