
Jiri Slaby composed on 2022-07-18 10:42 (UTC+0200):
Michal Suchánek wrote:
If the update is done by plain rpm it is not logged by zypper, and you need to do the logging (and snapshots) yourself.
(Or install .rpm files using zypper. It can handle them.)
That's how I do Leap. With both Leap and TW I download kernels manually to my LAN server. But with Leap, I copy the kernels to the target's zypp cache before installing with zypper. With TW, I've been installing with rpm directly from the server, in part because of the non-scrollback kernels since 5.11, and another part the busier I/O with zypper, pausing for the kernel lock answer, and giving 3 choices instead of 2 when it announces the new kernel twice, once on the mirrors, and the other on the server, making the "remove" lock option #3, compared to #2 when using my Leap procedure. rpm doesn't even have to ask, since (thankfully) it knows nothing about zypp locks. I do what I do in part because I have >30 TW installations, and nearly as many of each supported Leap. I have a TW cache on the LAN server that I bind mount to each installation's zypp cache before duping. The zypp locks keep kernels out of that cache. I keep kernel rpms segregated from other cached rpms, and I control that cache differently. All my TWs are on EXT3 or EXT4. The only BTRFS snapshotting available here is on a laptop with Leap only. Everything else here is multi-, multiboot, between 10 and 60 partitions per disk. I repeat: the $SUBJECT behavior has occurred on two different installations, one Friday, one Sunday night. zypper dup excluded kernel on each, which is SOP here. Latest prior kernel was 5.17.9 on the Friday PC, 5.18.2 on the later. rpm -ivh caused the 5.18.9-2 installations that removed all the older kernels. Due to immutable flags, present due to absence of available configuration option to prevent automatic rebuilding of initrds proven to work, the "removed" initrds remain: # ls -1 /disks/stw/boot/initrd-5* /disks/stw/boot/initrd-5.15.12-1-default /disks/stw/boot/initrd-5.16.15-1-default /disks/stw/boot/initrd-5.17.9-1-default /disks/stw/boot/initrd-5.18.9-2-default /disks/stw/boot/initrd-5.7.11-1-default On the other PC on which this happened, without a similar freespace limitation, installed kernel versions went back to 5.4.14, which is the installed kernels situation most TW installations here still have. I can proceed with other installations in like manner if this thread encourages it, or adjust as may be suggested to try to pin down the blame. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata