This commit switches to using the rewritten config file from the
upstream templates. This fixes the problem with writing the state file
to the workDirectory and uses modern syntax.
Resolves: RHEL-28654
Without this set rsyslogd will try to use / for things like
/imjournal.state.tmp, which will fail due to SELinux.
This also replaces the deprecated '~' discard action with 'stop'.
Resolves: rhbz#2160070
This reverts commit 09acfd978e.
rngd is installed in the initrd by dracut, and unconditionally started,
so this won't fix rngd slowdowns in the initrd.
Related: rhbz#2028720
rngd should no long be needed, recent kernels have enough entropy out of
the box. This leaves it in the boot.iso but only enables it if inst.rngd
is passed on the kernel cmdline.
Resolves: rhbz#2028720
scp in openssh 8.7 will change to use sftp protocol. See
https://github.com/openssh/openssh-portable/pull/194 for details.
This enables the sshd internal-sftp implementation so that newer scp
versions will continue to work as expected. Note that the sshd service
is only running during the installation if inst.sshd is passed on the
kernel cmdline.
Resolves: rhbz#2035049
anaconda in F34 and Rawhide recently stopped accepting params
without the inst. prefix, so 'rescue' does nothing except print
a warning now. We need to use `inst.rescue`. This has worked for
quite a long time so will be OK at least on all Fedoras and RHEL
8, not sure about RHEL 7.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Signed-off-by: Brian C. Lane <bcl@redhat.com>
mk-s390-cdboot has stopped working because the kernel outgrew the
hard-coded offset it used when creating cdboot.img. IBM now has a script
in s390utils that can do the same thing so use the upstream script
instead.
This drops mk-s390-cdboot script, switches the s390 templates to use
mk-s390image from s390utils.
It adds @ROOT@ to cdboot.prm, and sets inst.stage2 so that the installer
image will be found when booting the iso.
Resolves: rhbz#1903923
...turns out you can't just have a single template file, because lorax
just picks a single directory and expects all the data it needs to be
there. Sigh.
So this adds all the rest of the files, plus some Makefile machinery for
generating a tarball and updating the specfile after you've checked in
changes. See README for details.
