2020-03-04 09:35:06 +00:00
|
|
|
#!/usr/bin/env bash
|
2021-10-01 11:04:32 +00:00
|
|
|
# SPDX-License-Identifier: LGPL-2.1-or-later
|
2021-05-10 18:29:08 +00:00
|
|
|
set -eo pipefail
|
|
|
|
|
|
|
|
out="${1:?}"
|
|
|
|
systemd_efi="${2:?}"
|
|
|
|
boot_stub="${3:?}"
|
|
|
|
splash_bmp="${4:?}"
|
2017-04-16 16:04:46 +00:00
|
|
|
|
2021-05-10 18:35:31 +00:00
|
|
|
efi_dir="$(bootctl -p)"
|
|
|
|
entry_dir="${efi_dir}/$(cat /etc/machine-id)/$(uname -r)"
|
|
|
|
|
2015-02-08 11:25:35 +00:00
|
|
|
# create GPT table with EFI System Partition
|
2017-04-16 16:04:46 +00:00
|
|
|
rm -f "$out"
|
|
|
|
dd if=/dev/null of="$out" bs=1M seek=512 count=1 status=none
|
|
|
|
parted --script "$out" "mklabel gpt" "mkpart ESP fat32 1MiB 511MiB" "set 1 boot on"
|
2015-02-08 11:25:35 +00:00
|
|
|
|
|
|
|
# create FAT32 file system
|
2021-05-10 18:29:08 +00:00
|
|
|
LOOP="$(losetup --show -f -P "$out")"
|
|
|
|
mkfs.vfat -F32 "${LOOP}p1"
|
2015-02-08 11:25:35 +00:00
|
|
|
mkdir -p mnt
|
2021-05-10 18:29:08 +00:00
|
|
|
mount "${LOOP}p1" mnt
|
2015-02-08 11:25:35 +00:00
|
|
|
|
bootctl: Always use upper case for "/EFI/BOOT" and "/EFI/BOOT/BOOT*.EFI".
If the ESP is not mounted with "iocharset=ascii", but with "iocharset=utf8"
(which is for example the default in Debian), the file system becomes case
sensitive. This means that a file created as "FooBarBaz" cannot be accessed as
"foobarbaz" since those are then considered different files.
Moreover, a file created as "FooBar" can then also not be accessed as "foobar",
and it also prevents such a file from being created, as both would use the same
8.3 short name "FOOBAR".
Even though the UEFI specification [0] does give the canonical spelling for
the files mentioned above, not all implementations completely conform to that,
so it's possible that those files would already exist, but with a different
spelling, causing subtle bugs when scanning or modifying the ESP.
While the proper fix would of course be that everybody conformed to the
standard, we can work around this problem by just referencing the files by
their 8.3 short names, i.e. using upper case.
Fixes: #3740
[0] <http://www.uefi.org/specifications>, version 2.6, section 3.5.1.1
2016-07-21 00:29:54 +00:00
|
|
|
mkdir -p mnt/EFI/{BOOT,systemd}
|
2017-04-16 16:04:46 +00:00
|
|
|
cp "$systemd_efi" mnt/EFI/BOOT/BOOTX64.efi
|
2015-02-08 11:25:35 +00:00
|
|
|
|
2021-05-10 18:29:08 +00:00
|
|
|
if [ -e /boot/shellx64.efi ]; then
|
|
|
|
cp /boot/shellx64.efi mnt/
|
|
|
|
fi
|
2015-02-08 11:25:35 +00:00
|
|
|
|
|
|
|
mkdir mnt/EFI/Linux
|
2017-04-16 16:04:46 +00:00
|
|
|
echo -n "foo=yes bar=no root=/dev/fakeroot debug rd.break=initqueue" >mnt/cmdline.txt
|
2015-02-08 11:25:35 +00:00
|
|
|
objcopy \
|
scripts: use 4 space indentation
We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed.
4 sp was the most common, in particular the majority of scripts under test/
used that. Let's standarize on 4 sp, because many commandlines are long and
there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp
also seems to be the default indentation, so this will make it less likely
that people will mess up if they don't load the editor config. (I think people
often use vi, and vi has no support to load project-wide configuration
automatically. We distribute a .vimrc file, but it is not loaded by default,
and even the instructions in it seem to discourage its use for security
reasons.)
Also remove the few vim config lines that were left. We should either have them
on all files, or none.
Also remove some strange stuff like '#!/bin/env bash', yikes.
2019-04-04 12:10:42 +00:00
|
|
|
--add-section .osrel=/etc/os-release --change-section-vma .osrel=0x20000 \
|
|
|
|
--add-section .cmdline=mnt/cmdline.txt --change-section-vma .cmdline=0x30000 \
|
|
|
|
--add-section .splash="$splash_bmp" --change-section-vma .splash=0x40000 \
|
2021-05-10 18:35:31 +00:00
|
|
|
--add-section .linux="${entry_dir}/linux" --change-section-vma .linux=0x2000000 \
|
|
|
|
--add-section .initrd="${entry_dir}/initrd" --change-section-vma .initrd=0x3000000 \
|
scripts: use 4 space indentation
We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed.
4 sp was the most common, in particular the majority of scripts under test/
used that. Let's standarize on 4 sp, because many commandlines are long and
there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp
also seems to be the default indentation, so this will make it less likely
that people will mess up if they don't load the editor config. (I think people
often use vi, and vi has no support to load project-wide configuration
automatically. We distribute a .vimrc file, but it is not loaded by default,
and even the instructions in it seem to discourage its use for security
reasons.)
Also remove the few vim config lines that were left. We should either have them
on all files, or none.
Also remove some strange stuff like '#!/bin/env bash', yikes.
2019-04-04 12:10:42 +00:00
|
|
|
"$boot_stub" mnt/EFI/Linux/linux-test.efi
|
2015-02-08 11:25:35 +00:00
|
|
|
|
|
|
|
# install entries
|
|
|
|
mkdir -p mnt/loader/entries
|
2015-02-25 14:56:54 +00:00
|
|
|
echo -e "timeout 3\n" > mnt/loader/loader.conf
|
2015-02-26 18:51:08 +00:00
|
|
|
echo -e "title Test\nefi /test\n" > mnt/loader/entries/test.conf
|
2015-02-08 11:25:35 +00:00
|
|
|
echo -e "title Test2\nlinux /test2\noptions option=yes word number=1000 more\n" > mnt/loader/entries/test2.conf
|
|
|
|
echo -e "title Test3\nlinux /test3\n" > mnt/loader/entries/test3.conf
|
|
|
|
echo -e "title Test4\nlinux /test4\n" > mnt/loader/entries/test4.conf
|
|
|
|
echo -e "title Test5\nefi /test5\n" > mnt/loader/entries/test5.conf
|
|
|
|
echo -e "title Test6\nlinux /test6\n" > mnt/loader/entries/test6.conf
|
|
|
|
|
|
|
|
sync
|
|
|
|
umount mnt
|
|
|
|
rmdir mnt
|
2021-05-10 18:29:08 +00:00
|
|
|
losetup -d "$LOOP"
|