Workaround is not needed for etcnet> = 0.9.19.1-alt1
See also commit 8a299b4a

Otherwise, the automatic loading of the iso starts without the ability to set
the loading of another.

See also commit: 61f66b08

- If the BRANCH variable is not empty, and the BRANDING variable on
  the contrary is empty, then BRANDING is assigned to alt-starterkit.
- Revert commit "base+rescue: add eepm"
- Fixed conditions with variable BRANCH
- Drop STARTERKIT variable
- grub: add submenu "Network installation"
- Do not use udev-rule-generator-net in regulars/starterkits
- initrd-bootchain: Initial feature
- stage1: allow creating stage1 without stage2
- ntp: fix add fallbck THE_NTPD_SERVICE
- Makefile: check *_PACKAGES* variables as lists
- vmguest: fix build with use/vmguest/kvm/x11 for BRANCH=p9
- grub, syslinux: replace 'splash=0' to 'nosplash' in rescue
- drop features: aarch64-dbm, armh-cubox, armh-dovefb, nexus7,
  armh-tegra, armh
- build-vm: add FEATURES and MODULES_TRY_ADD from /etc/initrd.mk
- syslinux: Generate isolinux.cfg for any BOOTLOADER
- build-vm, stage2: set GLOBAL_HSH_PROC=1
- vm.mk: Add sr_mod to initrd modules for vm/cloud-system
  (thanks obirvalger@)

isolinux.cfg required for alterator-netinst.

make-initrd-bootchain >= 0.1.4-alt1 uses tmpfs if ramdisk_size is not set.

Variables in cmdline override variables from /etc/initrd.mk
See also: https://lists.altlinux.org/pipermail/make-initrd/2021-September/000533.html

Allows you to enable graphical output at the initrd stage.

Many cloud providers pass metadata via cdrom. Generator used by the
cloud-init to determine a datasource works before loading modules. So cdrom
modules must be loaded in the initrd.
Other linux distributions enable cdrom modules in the kernel.

Enable /proc for build vm/<target> and distro/<target> with use/stage2.
/proc needed for make-initrd >= 2.23.0.
See also https://bugzilla.altlinux.org/40900

This reverts commit 1ca16022.

wmpomme not available in Sisyphus and p10.

This feature has long lost its relevance, as intended for the first
samples of boards Baikal M with very raw UEFI firmware.

Writing zeros to a USB flash drive is not a very useful activity.

The 'splash=0' parameter not only disables splash, but also switches
to tty5 on which plymouth is supposed to run. This looks like a bug
in propagator. 'nosplash' is also a general parameter for propagator
and make-initrd.

This parameter needed for bootloading with initrd-bootchain.
there are currently no network configuration dialogs when booting
with initrd-bootchain.

Request by Speccyfighter.

This is no longer necessary, since the dependencies of
livecd-net-eth.service are fixed, and for sysvinit the
udev-rule-generator is added already.

For install2, this is needed to work around error 99-cdrom.sh with method:cdrom.
The error shows up with make-initrd-bootchain, but not propagator, as lowmem is
enabled for propagator in this mode.
For rescue, the point is that the latter has become quite large, so by default
it would be better that way.

This targets required udev-rule-generator-net.

Need to support initrd-bootchain in e2k feature.

In the future, will need to modify generate.mk so that can set all
the variables in this config.