A proposal about disallowing the "upgrade" of runtime kernel packages, and just to "install" them instead while using upgradepkg

teoberi · 06-07-2018, 01:21 AM

Quote:

Originally Posted by allend

This is horseshit. The only person able to update the kernel on a default Slackware system is the system administrator. If the system administrator screws up, there the blame lies.

Totally agree!
On a server system, updates are always installed manually by me with upgradepkg.
Often after updating, some settings need to be reconfigured.

chrisretusn · 06-07-2018, 03:38 AM

How I upgrade the kernel (Slackware-current).

I use lilo, I have two kernels defined. One labeled Slackware, the other labeled LastWorking. Since I happen to agree with "Automated upgrade of kernel packages aren't a good idea" especially with -current, the "kernel" is of course blacklisted. When a new kernel is indicated in ChangeLog.txt I normally take care of all updates first.

Then take care of the kernel. I edit my blacklist file as follows:

Code:

#kernel-generic
#kernel-headers
kernel-huge
#kernel-modules
#kernel-source

Next I use 'slackpkg download kernel' deselect kernel-firmware and download the rest.

Next I edit blacklist again to blacklist the kernel packages.

Next up... installpkg /var/cache/packages/slackware64/a/*.t?z
I repeat with the d and k series

I then remove those downloaded files.

Next I point the symlinks for my "working" kernel to point to the currently running kernel, the new generic kernel links are already pointed correctly from running installpkg.

As a side note: Rather than type to remove links and the link then again, I use mc to edit the links to my working kernel. Ctrl-X, Ctrl-S makes it easy.

Once that is done I run the following:

Code:

mkinitrd -F -k 1.14.47 
mkinitrd -F - k 1.14.44 -s initrd-working-tree -o initrd-working.gz 
lilo

At this point I reboot.

After the reboot, I remove the oldest kernel.

On Slackware 14.2 installs I don't bother with blacklisting (except for huge or generic as applicable). I let slackpkg do it thing, run mkinitrd if needed and then lilo after slackpkg is done, then reboot. I have never had a problem doing this.

I see no need to use upgradepkg to install a kernel. That is what installpkg is for, IMHO.

the3dfxdude · 06-07-2018, 12:48 PM

I need both operations for kernel packages. Sometimes I use installpkg, sometimes I use upgradepkg. Both are important for the chosen task. Intercepting the user intent is bad. Correct execution should be left to the admin, and higher level of automation designed for the system.

travis82 · 06-08-2018, 05:58 AM

I'm using huge kernel and have not had any problem with slackpkg upgrade-all so far. fortunately slackpkg is smart enough to ask for running lilo after every kernel upgrade.

slacker1337 · 06-11-2018, 08:44 PM

I'm not a huge fan of having multiple kernels installed in my systems, so I just upgrade everything. It's only burned me a few times where I've forgotten to rebuild the initrd or re-run lilo. Nothing that couldn't be fixed by booting into the installer from pxe or cdrom.

Quote:

Originally Posted by a4z

seems I did a lot wrong in the past.
always used slackpkg update , slackpkg upgrade-all
if there was a new kernel, it was installed,
manualy boot entry of course, if, than also initrd, but I became lazy recently and boot the huge kernel.
just works, never had any problem,

chrisretusn · 06-12-2018, 04:17 AM

Quote:

Originally Posted by slacker1337

I'm not a huge fan of having multiple kernels installed in my systems, so I just upgrade everything. It's only burned me a few times where I've forgotten to rebuild the initrd or re-run lilo. Nothing that couldn't be fixed by booting into the installer from pxe or cdrom.

Speaking of multiple kernels, I forgot to remove the old ones from the last couple of updates. Thanks for reminding me. I prefer to keep two kernels, the last working kernel and the current kernel. That said, I've only had to boot to the last working kernel maybe twice since I started doing this.

I don't forget to rebuild initrd or run lilo, only because I have in the past so... those two task are deeply burned in to my memory. <grin>