zfs module can not build for ppc64le sinse kernel 5.10.

Use a more reliable way to identify the theme grub.

1. Package repository on a disk with Live is not necessary.
2. Online repositories need to be connected always, and not when
there is a network. The network can be configured after bootloading.

- added notes about mkimage network options.

- Add gitlab-runner feature.

By default, GRUB_TERMINAL_OUTPUT='gfxterm' is configured.
This creates problems for virtual machines and single-board computers,
since they need output to console.

grub.iso is available for more platforms.

etcnet will be useful in any case, even if we switch to NetworkManager.

NetworkManager support automatic connection of connection and also
wireless connections. Configuring wired connections will be through

This will solve the problems with the update (p9 -> p10).

Rename to default.

/usr/sbin/install2-init-functions is provided by several packages.
Because of this, extra packages are installed. It is necessary to
simplify the task for the packages manager.

/usr/sbin/install2-init-functions is provided by several packages.
Because of this, extra packages are installed. It is necessary to
simplify the task for the packages manager.

/usr/sbin/install2-init-functions is provided by several packages.
Because of this, extra packages are installed. It is necessary to
simplify the task for the packages manager.

Not available for all kernels in p10, sisyphus.
Available for std-def only i p9.

...just to have it handy when it's in need next time.

"-a arch" is not requisite either; and having bunches
of empty lines in the resulting pkglists that are user
visible at least within the conventional installer's
alterator-pkg (groups selection) module wouldn't be nice.

I chose to sacrifice empty-line separators for clarity;
the really good cleanup would save *single* empty lines
between chunks of non-empty ones (not at the pkglist's
start or end); feel free to implement that as well.

This has been clearly lacking while making the previous commit
but the implementation isn't that clear so let it be a separate
step.

The problem requiring the change in subsequent processors
is that these relied upon "@arch" as a flag to be inspected,
and "pkg@!arch1,arch2" on arch2 needs to take out *all* of that
fragment *including* arch1 mention as well.

Part of the cause is difference in handling: "positive" multi-match
would explode its "client" line into multiple lines to filter down
the pipeline, while "negative" multi-match *has* to keep that line
on a similarly single line (otherwise we'd end up with N-1 of those
slipping past the filter for particular architecture thus defeating
the whole purpose of "negative" matching semantics):

$ echo 'pkg@!E2K,mipsel,riscv64' |
  sed -r  ':loop; s/^((([^@]+@!)[^,]+)+),([a-zA-Z0-9_]+)/\1@!\4/; t loop'
pkg@!E2K@!mipsel@!riscv64

I've tried my best to test this specific change but it still might
introduce a regression in some corner case; feel free to report;
looks like there's a space for improvement in m-p's automated
tests department as well.

So now we can do:

  pkg@!ARCHES1,ARCHES2,arch3,arch4

and have pkg excluded on arches mentioned; the previous approach
could only offer explicit whitelists (not that it was entirely
wrong but then again, we have both ExclusiveArch and ExcludeArch
rpmtags in our spec files).

This has been inspired by a few commits that cared
for package availability reasons on a particular
architecture; the problem at hand is that pkglists
might need to include groups of packages that are
(un)available on groups of arches, and tackling that
with plain pkg@arch just results in combinatorial
explosion of that matrix.

Arches are handled one-by-one with a few hardcoded
macro substitutions.

Exploding a "pkg@arch1,arch2" string into a set of:

pkg@arch1
pkg@arch2

with subsequent archdep pruning would do the trick;
so here's another sed oneliner that does just that:

$ echo 'pkg@X86,ARM,ppc64le' |
  sed -r ':loop; s/^((([^@]+@)[^,]+)+),([^,]+)/\1\n\3\4/; t loop'
pkg@X86
pkg@ARM
pkg@ppc64le

See-also: 9601a9e7
See-also: 5581dc91
See-also: http://stackoverflow.com/a/55781741/561921

needed update rdma-core.

ttyS0 is needed qemu. ttySIF0 needs to be set separately.

It was encumbered, it's only java11 part that should be
archdep as e2k-alt-linux lacks that one so far.

See-also: 8f0f5f7d

The parameter determines use of QEMU or not, if the target architecture
does not correspond to the host architecture.
By default, the parameter is on (Value 1).
For architectures that do not support QEMU (e2k), the option is turned off.

The network can be controlled via NetworkManager without ETCnet
configs. DHCP support needs to be added to other targets.

Needed alterator-setup 0.3.13.
Now alterator-setup to prepare self to work via VNC.
Also VNC mode is now optional and requires inclusion
in/etc/alterator-setup/config option ALTERATOR_SETUP_VNC=1

android-tools -- need disable build documentat
bacula11 -- need  php7
fio -- require ceph
fuse-lftpfs -- in process
kexec-tools -- need to port package
ltrace  -- need to port code
perftest -- need to port code
scsitarget-utils -- require ceph

UBOOT_NOFDTDIR does not need more, так как bootload in QEMU uses
U-Boot/EFI.

This space is reserved for installation U-Boot.

At the moment it seems useless on other architectures.