initrdscripts: corrrect syntax typo

Signed-off-by: Hongxu Jia <[email protected]>

Merge pull request #12 from xzhang1/STARLINGX-9.0

data/debian/ostree: upgrade to 2022.2-1

lat genimage: support to customize sources by applying patches from b…

…bappend

Improve the sources generation of LAT genimage, move the operation
from do_unpack to do_patch, it allows to apply the patches from
bbappend, then user could customize LAT sources out of meta-lat
layer by bbappend

No changes on COPYING, just tweak location

Signed-off-by: Hongxu Jia <[email protected]>

init-ostree-install.sh: fix boot.env has multiple duplicate entries f…

…or console

Use variable OSTREE_CONSOLE to set console entries to boot.env, and
the variable OSTREE_CONSOLE is set in read_args.

First time, call read_args with input CMDLINE=/proc/cmdline,
And then, call read_args with input CMDLINE=/tmp/lat/cmdline.

But if /tmp/lat/cmdline does not exist, read_args will be called
with CMDLINE=/proc/cmdline at second time which caused boot.env
has multiple duplicate entries for console

root@(none):/# cat /sysroot/boot/efi/EFI/BOOT/boot.env
...
ostree_console= console=ttyS0,115200 console=tty1 console=ttyS0,115200 console=tty1
...

Do not call read_args if /tmp/lat/cmdline does not exist at second time

Signed-off-by: Hongxu Jia <[email protected]>

lat debian: improve kernel parameters configuration

Currently we support to set kernel parameters for installed OS at
build time, install time, ostree upgrade time and target installed
time. Two files boot.env and kernel.env save grub variable
kernel_params, kernel will load it by grub.cfg. If kernel_params
exists in both of kernel.env and boot.env, the one in kernel.env
overrides the one in boot.env

In this commit, do not make kernel.env overrides boot.env, make
them coexistence. Add a new grub variable kernel_params_ext to be
saved in kernel.env for kernel to load

At build time, use following yaml params to set kernel parameters
...
environment:
- KERNEL_PARAMS=xxxx xxx
...
It will be saved to kernel.env along with kernel image and could be
updated by ostree upgrade

At install time, use inst boot params `kernelparams=xxxx,xxx' to
set kernel parameters. It will be saved to boot.env, which is always
persisting and will not be changed by ostree upgrade

At target installed time, if user want to set persistent kernel params,
they could set it `kernel_params=xxxx xxx' to
/boot/efi/EFI/BOOT/boot.env; if user want to set kernel params for
specific kernel, they could find the specific kernel.env which is along
with the kernel, and set `kernel_params_ext=xxxx xxx' to /boot/1/kernel.env
or /boot/2/kernel.env

Signed-off-by: Hongxu Jia <[email protected]>

lat-installer: set default kernel and kernel param at OS install time

During lat OS installation, use boot param defaultkernel and
kernelparams to update default kernel and kernel parameters
in kernel.env

For defaultkernel, it supports filename wildcard, if multiple kernels
are matched, the last one will be used;

For kernelparams, in order to compat non-debian situation, still saves
it to boot.env. In grub.cfg of debian, kernel.env overrides boot.env.

For kernelparams, in order to support multiple kernel params, use `,'
as split symbol (such as kernelparams="a=b,c=d")

Signed-off-by: Hongxu Jia <[email protected]>

lat installer: add boot parameter efibootfirst=1

Due to commit [2bfd727 lat installer: set to boot from disk
as first order], it deleted old order 0 boot entry, and set
boot from disk entry as order 0.

In some host, old order 0 boot entry could not be deleted,
so add boot parameter efibootfirst=1 to control it

By default (without efibootfirst=1), it creates boot from disk
entry to append to the tail

Signed-off-by: Hongxu Jia <[email protected]>

lat installer: insert a hook to report error log

If install failed, try to call hook /tmp/lat/report_error_log.sh
if it is available, otherwise save install-fail.log to otaboot
partition

Correct variable naming: s/devs/_dev/g

Signed-off-by: Hongxu Jia <[email protected]>

lat installer && mttyexec: save output of install

Improve mttyexec to save output to log file.

Then save output of install to file /install.log in initramfs,
if installation succeed, save install.log to installed /root dir;
if failed, save install-fail.log to otaefi partition if the partition
is available

Signed-off-by: Hongxu Jia <[email protected]>

lat installer: improve kickstart hook position

The variable INSTDEV is used by lat installer to get the install
device, it changes in some cases, place `%pre-part' hook after
variable INSTDEV is parsed correctly. Then the `%pre-part' hook
will know which disk to install

In order to reduce the regression and side effect, add a new
`%ks-early' hook to place to `%pre-part' original position

Signed-off-by: Hongxu Jia <[email protected]>