adff1e98b6
And this (for now at least) completes the epic journey of the "where's the kernel"? With this it's found solely in `/usr/lib/modules/$kver`. There are a few reasons to do this; most prominent is that it avoids duplicating the content as the locations may have different SELinux labels. Closes: #1773 Approved by: jlebon
27 lines
886 B
Bash
Executable File
27 lines
886 B
Bash
Executable File
#!/bin/bash
|
|
set -xeuo pipefail
|
|
|
|
dn=$(cd $(dirname $0) && pwd)
|
|
. ${dn}/libcomposetest.sh
|
|
|
|
prepare_compose_test "bootlocation-modules"
|
|
pysetjsonmember "boot_location" '"modules"'
|
|
runcompose
|
|
echo "ok compose"
|
|
|
|
# Nothing in /boot (but it should exist)
|
|
ostree --repo=${repobuild} ls -R ${treeref} /boot > bootls.txt
|
|
cat >bootls-expected.txt <<EOF
|
|
d00755 0 0 0 /boot
|
|
EOF
|
|
diff -u bootls{-expected,}.txt
|
|
# Verify /usr/lib/ostree-boot
|
|
ostree --repo=${repobuild} ls -R ${treeref} /usr/lib/ostree-boot > bootls.txt
|
|
assert_not_file_has_content bootls.txt vmlinuz-
|
|
assert_not_file_has_content bootls.txt initramfs-
|
|
# And use the kver to find the kernel in /usr/lib/modules
|
|
ostree --repo=${repobuild} ls -R ${treeref} /usr/lib/modules > modules-lsr.txt
|
|
assert_file_has_content modules-lsr.txt '/vmlinuz$'
|
|
assert_file_has_content modules-lsr.txt '/initramfs.img$'
|
|
echo "ok boot location modules"
|