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/80-make-initfs

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

ln -s vmlinuz-$kver /boot/vmlinuz
ln -s initrd-$kver.img /boot/initrd.img
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;`
documentation: use paths relative to toplevel dir This change is done to reduce ambiguity in some cases; the previous intention has been to ease navigation when staying in a particular directory, now it's been changed in favour of convenient toplevel `git grep' in fact. Both variants have their pros and cons, I just find myself leaning to this one by now hence the commit. Feel free to provide constructive criticism :) Some path-related bitrot has also been fixed while at that. 2014-03-05 18:09:56 +04:00			`# this script relates to features.in/stage2/stage1/scripts.d/80-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 \`
			`\| tail -n 1 \`
			`\| cut -f 2 -d ' ' \`
			`\| sed 's/kernel-image-//')"`

			`ln -s vmlinuz-$kver /boot/vmlinuz`
			`ln -s initrd-$kver.img /boot/initrd.img`