[SOLVED] push button upgrade of a machine's kernel

_peter · 10-29-2016, 06:14 AM

alo,
upgrading the kernel by pushing a button is useful to me, maybe it is useful to others: ie moving from 4.4.14 to 4.4.28.

Deliberate limitations requires to stick to the kernel base shipped with 14.2.
No interest in diverging to something different than 4.4.x

The script below can be made better as I am not a software pal

Code:

#!/bin/sh

ZCATC=/usr/bin/zcat
MAKEC=/usr/bin/make
MKINITRDC=/sbin/mkinitrd
TARC=/usr/bin/tar
RSYNCC=/usr/bin/rsync
WGETC=/usr/bin/wget
LNC=/usr/bin/ln
CPC=/usr/bin/cp
AWKC=/usr/bin/awk
ECHOC=/usr/bin/echo
LILOC=/sbin/lilo
GPGC=/usr/bin/gpg
UNXZC=/usr/bin/unxz
F=https

if [ ! -z "$1" ]; then

	RELEASE=$1

	if [ ! -f "linux-$RELEASE.tar" ]; then
	
		if [ $F == rsync ]; then
		FETCH=rsync://rsync.kernel.org/pub/linux/kernel/v4.x/linux-$RELEASE.tar.xz
		FETCHS=rsync://rsync.kernel.org/pub/linux/kernel/v4.x/linux-$RELEASE.tar.sign
			$ECHOC "fetching kernel checksum w/ $RSYNCC -av $FETCHS"
			$RSYNCC -av $FETCHS ./
			$ECHOC "done fetching kernel checksum"
		
			$ECHOC "fetching kernel source w/ $RSYNCC -av $FETCH"
			$RSYNCC -av $FETCH ./
			$ECHOC "done fetching kernel source"
		fi
		
		
		if [ $F == https ]; then
		FETCH=https://www.kernel.org/pub/linux/kernel/v4.x/linux-$RELEASE.tar.xz
		FETCHS=https://www.kernel.org/pub/linux/kernel/v4.x/linux-$RELEASE.tar.sign
			$ECHOC "fetching kernel checksum w/ $WGETC -nv $FETCHS"
			$WGETC -nv $FETCHS
			$ECHOC "done fetching kernel checksum"
		
			$ECHOC "fetching kernel source w/ $WGETC -nv $FETCH"
			$WGETC -nv $FETCH
			$ECHOC "done fetching kernel source"
		fi

			$ECHOC "verifying kernel source integrity w/ $GPGC --verify linux-$RELEASE.tar.sign"
			$UNXZC linux-$RELEASE.tar.xz
			$GPGC --verify linux-$RELEASE.tar.sign
			$ECHOC "done verifying kernel source integrity"

			$ECHOC "extracting kernel source w/ $TARC -xf linux-$RELEASE.tar" 
			$TARC -xf linux-$RELEASE.tar 
			$ECHOC "done fetching kernel source"

	else
		$ECHOC "extracting kernel source w/ $TARC -xf linux-$RELEASE.tar" 
		$TARC -xf linux-$RELEASE.tar 
		$ECHOC "done fetching kernel source"
	fi		
	
	cd linux-$RELEASE

	$ECHOC "0) $ZCATC /proc/config.gz > ./.config"
	$ECHOC "1) $CPC /tmp/.config ./"

	read choice
	case $choice in
		0)
		$ZCATC /proc/config.gz > ./.config;;
		1)
		$CPC /tmp/.config ./;;	
		*)
		$ECHOC "you must choose between option 0 and 1"
		exit
		;;
	esac

	$ECHOC "$MAKEC oldconfig"
	$MAKEC oldconfig
	
	$ECHOC "$MAKEC bzImage modules"
	$MAKEC bzImage modules
	
	$ECHOC "$MAKEC modules_install"
	$MAKEC modules_install

	$ECHOC "$CPC arch/x86/boot/bzImage /boot/vmlinuz-$RELEASE"
	$CPC arch/x86/boot/bzImage /boot/vmlinuz-$RELEASE
	
	$ECHOC "$CPC System.map /boot/System.map-$RELEASE"
	$CPC System.map /boot/System.map-$RELEASE
	
	$ECHOC "$CPC .config /boot/config-$RELEASE"
	$CPC .config /boot/config-$RELEASE
	
	$ECHOC "$MKINITRDC -c -k $RELEASE-smp -m ext4"
	$MKINITRDC -c -k $RELEASE-smp -f ext4 -r /dev/sda1 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz.$RELEASE

	$ECHOC "append the file lilo.conf"
	$ECHOC "image = /boot/vmlinuz-$RELEASE
		initrd=/boot/initrd.gz.$RELEASE
		root = /dev/sda1
		label = s$RELEASE
		read-only" >> /etc/lilo.conf
	
	$ECHOC "$LILOC -v"
	$LILOC -v

else

$ECHOC "--"
$ECHOC "usage is $0 <version_of_the_kernel_archive>"
$ECHOC "example: is $0 4.4.14"
$ECHOC "--"

fi

SCerovec · 10-29-2016, 04:20 PM

I would put the initrid modules string in a var at the top?

As it varies among specific hosts...

Otherwise excellent "recipe"

Drakeo · 10-29-2016, 05:50 PM

the /usr/share/mkintrid script is the real issue it reads the running kernel so this is not going to help me. Been here before.
I am sure you can figure it out like I did.
re read your script now. and sorry your running the sbin script like I do sorry I miss read your script.

ttk · 10-29-2016, 06:23 PM

Very cool! Thank you for sharing this script :-)

I noticed you have a minor typo here, $ZCAT should be $ZCATC

Code:

$ECHOC "0) $ZCAT /proc/config.gz > ./.config"

slackb0t · 10-29-2016, 07:18 PM

This is pretty cool. thx

imjustkillingtime · 10-30-2016, 06:29 AM

Quote:

Originally Posted by _peter

alo,
self automation of the kernel upgrade is useful to me, maybe it is useful to others: ie moving from 4.4.14 to 4.4.28.

Deliberate limitations requires to stick to the kernel base shipped with 14.2.
No interest in diverging to something different than 4.4.x

The script below can be made better as I am not a software pal

hi _peter, thank you very much for sharing. This will save me from building my own kernel, in the light of the dirty cow. I dont want to sound too demanding but an additional how-to-apply-this-script will help many newbies like me. Would it be something like saving it to a file, place it to /etc/rc.d/rc.local/, make it executable?

_peter · 10-30-2016, 06:34 AM

thanks SCerovec, yes handling the initrd options in variable(s) is probably best, not even using uuid yet
thanks ttk for the typo catch
imjustkillingtime, inside /usr/src I run the thing like this

Code:

./kernel.sh 4.4.28

purposely executing it on demand rather than within /etc/rc.d, well it's not so automated after all

All this mkinitrd modules -m are still cryptic to me depending on the machine hw
I have been lost on linux mint and ubuntu to reproduce this, grub is not complicated but lilo with slackware feels right.

Closing.

slackb0t · 10-30-2016, 07:42 AM

What would be the best way to add the initrd options in variables?

kazzan · 10-30-2016, 09:12 AM

I think you probably should put a disclaimer on your script and not present it as an "automated kernel upgrade" for "newbies".
I'm sure the script works fine on your own system, but it makes too many general assumptions.
To create the initial ramdisk (and the lilo section), why not rely on mkinitrd_command_generator.sh instead?

Props for verifying kernel signatures though, that's rarely ever mentioned and really useful (especially if you have the public key).

tramni1980 · 10-30-2016, 10:02 AM

@_peter Thank you very much for the script. Just my two cent: I would find this much more useful if it provided installable Slackware .txz packages (like Pat distributes them upon kernel update) rather than directly writing in system directories.

SCerovec · 10-30-2016, 10:25 AM

Quote:

Originally Posted by slackb0t

What would be the best way to add the initrd options in variables?

My bet is: edit the /etc/mkinitrd.conf and have it handle the automated initrd creation.

Further add the exact kernel version to the file - sed comes to mind?

_peter · 10-30-2016, 03:07 PM

yes kazzan and SCerovec, using the unique mkinitrd_command_generator.sh and variables from /etc/mkinitrd.conf instead of hard-wiring them would be better, will try.

tramni1980, my intend is to push a button and get my kernel and lilo upgraded outside of the installpkg tools. Maybe i can wrap the script outputs to a txz file rather than individual files, will try.
I only want to run the stable official slackware release not the current one where Patrick already takes care of things: for instance not all kernels updates are needed or useful along the life of the stable release (14.2)

OldHolborn · 10-30-2016, 03:43 PM

If you intend on making this push-button simple please consider the bandwidth requirements on kernel.org and its mirrors.

If you use the patches you can simply

patch -R < current_patch
patch < new_patch
make mrproper

You'll then only be hitting kernel.org for a few hundred kilobytes each time instead of a hundred plus megabytes.

SCerovec · 10-31-2016, 07:02 AM

Or, pull a kernel off an mirror picked by locality

put the

Code:

K_SRC_URI="ftp://<some.nearby.server.net/tarball.tar.gz"

in the front section...
Maybe even put more (well known) mirrors as #comments ?

also, make it a /usr/local/sbin/kernel_updater.sh self contained command?
(rename as found appropriate)

just my 2c

OldHolborn · 10-31-2016, 02:19 PM

Perhaps if you donated that 2c for each time someone used the script?

Bandwidth and server resources have to be paid for by someone at some point, just because you don't know who it is does not make it cost zero for them to provide the service.

As an example from this very forum, Alien Bob had to look at alternative hosting because of the bandwidth requirements of his server.

Be kind to the net, where there is a simple, easy, way to reduce your impact on services provided to you for free, to do anything else is, at best, inconsiderate.