mkimage-profiles/features.in/build-vm/image-scripts.d/07-kernel

#!/bin/sh
# predictable file locations make bootloader configuration simple;
# this script relates to features.in/stage2/stage1/scripts.d/81-make-initfs

kver="$(rpm -qa 'kernel-image*' \
            --qf '%{installtime} %{version}-%{name}-%{release}\n' \
        | sort -n \
        | cut -f 2 -d ' ' \
        | sed 's/kernel-image-//')"

[ -n "$kver" ] || { echo "** unable to deduce kernel version" >&2; exit 1; }

cd /boot
echo "$kver" > .origver	# for tar2fs

make-initrd -N -k "$kver" AUTODETECT= \
  FEATURES+="$GLOBAL_VM_INITRDFEATURES" \
  MODULES_ADD+="$GLOBAL_VM_INITRDMODULES"

# NB: e2k kernel builds "image" instead of "vmlinuz"
[ -f vmlinuz-$kver ] && ln -s vmlinuz-$kver vmlinuz ||:
ln -s initrd-$kver.img initrd.img	# missing at this stage
:
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration 2012-06-18 22:00:32 +04:00			`#!/bin/sh`
			`# predictable file locations make bootloader configuration simple;`
build-vm: update referenced script name It's probably a good year to get rid of this reference practice resulting in a known sort of misdocumentation over time :-/ 2015-01-04 15:45:56 +03:00			`# this script relates to features.in/stage2/stage1/scripts.d/81-make-initfs`
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration 2012-06-18 22:00:32 +04:00
			`kver="$(rpm -qa 'kernel-image*' \`
			`--qf '%{installtime} %{version}-%{name}-%{release}\n' \`
			`\| sort -n \`
			`\| cut -f 2 -d ' ' \`
			`\| sed 's/kernel-image-//')"`

build-vm, tar2fs: unify kver handling No need to deduce kernel version again, just save it in a temporary file. The main reason to change what worked is that e2k kernel-image package has Linux bits named as image-$kver and not vmlinuz-$kver; the guessing logic taking all of this into account resulted in non-aesthetic patch. NB: there's a duplicating script within kernel feature; it wasn't easy to avoid this and it might differ when handling multiple kernels, I didn't think much about this now as vm images tend to ship with the sole one. 2017-08-02 15:44:57 +03:00			`[ -n "$kver" ] \|\| { echo "** unable to deduce kernel version" >&2; exit 1; }`

			`cd /boot`
			`echo "$kver" > .origver # for tar2fs`

build-vm, kernel, tar2fs: make-initrd happens now in build-vm NB: 07-kernel change breaks multi-kernel setup! Breaks: 650e92bf7fe7bcec939d4512b275ad843268bba4 2019-05-07 19:17:55 +03:00			`make-initrd -N -k "$kver" AUTODETECT= \`
			`FEATURES+="$GLOBAL_VM_INITRDFEATURES" \`
			`MODULES_ADD+="$GLOBAL_VM_INITRDMODULES"`

build-vm, tar2fs: unify kver handling No need to deduce kernel version again, just save it in a temporary file. The main reason to change what worked is that e2k kernel-image package has Linux bits named as image-$kver and not vmlinuz-$kver; the guessing logic taking all of this into account resulted in non-aesthetic patch. NB: there's a duplicating script within kernel feature; it wasn't easy to avoid this and it might differ when handling multiple kernels, I didn't think much about this now as vm images tend to ship with the sole one. 2017-08-02 15:44:57 +03:00			`# NB: e2k kernel builds "image" instead of "vmlinuz"`
			`[ -f vmlinuz-$kver ] && ln -s vmlinuz-$kver vmlinuz \|\|:`
			`ln -s initrd-$kver.img initrd.img # missing at this stage`
			`:`