On Dec 23, 2019 4:42 PM, rgci...@disroot.org wrote: > > December 24, 2019 4:42 AM, "Dumitru Moldovan" <du...@gmx.com> wrote: > > > On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote: > > > >> So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64. > >> Later that got updated to 6.2, then 6.3, 6.4… > >> > >> Yesterday I updated it to 6.5, then 6.6… now I'm trying to run syspatch: > > > > I have a similar issue with my desktop. I tried to outsmart the > > automatic installer to squeeze as much space as possible for /home on a > > desktop with an 80GB SSD. Which worked out OK for a few upgrade cycles, > > always from stable version to next stable version. > > > > However, after a couple of years, I had to unbreak an update that didn't > > fit any more in /usr. To my surprise, I had lots of old libs from > > previous releases left on disk. Had to manually remove a few of the > > older unused libs from /usr to be able to redo the update successfully. > > > > My understanding is that this is by design. In an update, some libs are > > overwritten (if they keep the same file name), but others are left on > > disk (theoretically unused) when lib versions are incremented. I can > > see a few ways in which this eases updates for people following > > -current, such as the OpenBSD devs, so it's a small price to pay. > > one thing that is useful is sysclean(8) > > my process now after a doas sysupgrade is > 1) doas sysclean; and review the output > 2) vise /etc/sysclean.ignore; so that sysclean ignores special files i created
Just wanted to emphasize step 2 above or else you will delete stuff you shouldn't. > 3) doas sysclean | xargs doas rm -rf > > yorosiku ~ > +1 for sysclean
