Date: Thu, 23 Apr 2026 08:06:00 +0000 From: Anton Shterenlikht <lists@cmplx.uk> To: Mark Millard <marklmi@yahoo.com> Cc: stable@freebsd.org, pkgbase@freebsd.org Subject: Re: [HEADS UP] stable/15: new base packages for PAM, zstd Message-ID: <aenS6CzXehVy6qSP@cmplx.uk> In-Reply-To: <4d128a79-a9c0-4d03-8b5f-02255267511d@yahoo.com> References: <adTq6tMP4GWQS35e@amaryllis.le-fay.org> <aeedOZ7VcQAOsQCV@cmplx.uk> <3847a70c-f2d8-4c4a-a5f0-56a4a90168b0@yahoo.com> <aeh6ddAuDClL4YFn@cmplx.uk> <583fb3e0-0a81-4ad5-9d1a-34bf3f82a14f@yahoo.com> <aejfPFFoJtahvEbn@cmplx.uk> <4d128a79-a9c0-4d03-8b5f-02255267511d@yahoo.com>
index | next in thread | previous in thread | raw e-mail
On Wed, Apr 22, 2026 at 10:01:20AM -0700, Mark Millard wrote:
> It is too bad that the pkg upgrade and the pkg install man pages do not
> document the .pkgsave and .pkgnew behavior and how to handle handle
> them. The wiki is not part of what installs on the local FreeBSD system
> as documentation.
>
> Far more files than the wiki materials list can be affected, including
> scripts and such. I've also had examples of configuration files:
>
> /etc/group.pkgsave /etc/group
> /etc/hosts.pkgsave /etc/hosts
> /etc/sysctl.conf.pkgsave /etc/sysctl.conf
> /etc/shells.pkgsave /etc/shells
>
> /etc/ssh/sshd_config.pkgsave /etc/ssh/sshd_config
> So, after adjustment, also needing: service sshd restart
>
> /.profile.pkgsave /.profile
> /.shrc.pkgsave /.shrc
> /root/.profile.pkgsave /root/.profile
> /root/.shrc.pkgsave /root/.shrc
> /usr/home/root/.profile.pkgsave /usr/home/root/.profile
> /usr/home/root/.shrc.pkgsave /usr/home/root/.shrc
>
> /etc/rc.subr.pkgsave /etc/rc.subr
> /etc/rc.pkgsave /etc/rc
> /etc/defaults/rc.conf.pkgsave /etc/defaults/rc.conf
> /etc/kyua/kyua.conf.pkgsave /etc/kyua/kyua.conf
> /etc/periodic/daily/223.backup-zfs.pkgsave
> /etc/periodic/daily/223.backup-zfs
>
> /etc/mail/*.pkgsave
> /etc/mtree/*.pkgsave
>
> Most of those I've not had an example of in a long time.
>
> Even normal system programs/libraries can get such *.pkg* files. For
> example, if one has patched a program or library locally and then a
> later update has to deal with the patched file. The patched file can be
> saved (.pkgsave) or the new file can be separately saved (.pkgnew).
>
> Checking for such files via find or the like is a good idea.
>
> Similar points apply to any chroot worlds and/or jail worlds that happen
> to be pkgbase based.
yes, there are lots of those:
# find / -type f -name "*.pkgsave" | wc -l
155
most under /rescue:
root@aob:~ # find /rescue -type f -name "*.pkgsave" | wc -l
149
Anton
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aenS6CzXehVy6qSP>