use/rescue need for alt-workstation. But sdab.cfg is not needed.
See also: https://bugzilla.altlinux.org/40704

The commit 99695713 used this variable
even though it didn't exist yet. A good reason to add this variable.

No problem with EFI support.

There are two different versions of the script with the same
name for different subprofiles, sharing some of the same bugs
over the years, *sigh*.

Shoving those into stage2 would yield online repositories enabled
there too which *might* be wanted but will likely need installer
support (at least some better error handling, the current culprit
with unavailable repositories being apt-pkg's size estimation).

Fixes: d2f892ab
Fixes: 0f4ee98f

Repositories are signed with different keys. In addition, they may
not have a signature.

The places of the terms *do* affect the sum in apt's case;
start with lowlevel items like SYSTEM_PACKAGES and end with
high-level ones like THE_LISTS to reduce the chance of getting
hit by premature virtual dependency expansion/fixation.

Adapt live and rescue features accordingly.

See-also: https://bugzilla.altlinux.org/show_bug.cgi?id=30806#c5Suggested-by: Leonid Krivoshein <klark@altlinux.org>

It's not a blocker if enabling online repos fails;
we should provide a better handling of warnings
with e.g. a summary of those after build.

It should be more clear what gets libX11 test triggered.

...instead of (often-crowded) ftp.altlinux.org for updates.

Should get into distributions' rescue image indeed.

Even base rescue images should get mount.nfs and rpcbind.

Apparently DH SHA1 key exchange algorithm is still in wide
use at least within Cisco products (there's a real world
case involving our user), and some still use DSA keys
which might be longer than "allowed" yet not trusted anymore.

See also:
http://www.openssh.com/legacy.html
http://bugzilla.altlinux.org/31716
http://altlinux.org/changes (Jan 2016; RU)

The added initscript used to be purged by 98-init-rescue
which has been somewhat overlooked during vain attempts
to build an image that would actually run it!

It's by no means substitution for proper l10n feature
but forcing users into POSIX locale for recovery ops
is no good at all.

This is basically a fork of live feature's 20-locale,
a font has been changed to save some face though.

It's required for NFS mounts but having a rescue image listening
to any non-localhost ports is too bad an idea, IMNSHO.

So let's fix this while spotted.

This has been spotted and solved manually several times already,
and that's just boring so let's add the ability to state that
X11-based software is not accepted into a particular rescue image.

Not that I would hate X but things like that belong to a carefully
crafted image which includes either X server or reasonable means
to ensure that GUI software can actually be used.

NB: this is a somewhat new entity: test/rescue/no-x11 knob
for an image-script intended to make it blow up the build
when libX11 is found within the chroot that makes up
the rescue image's filesystem.

The interface is not documented intentionally: it will take
some time to find out whether it sticks or is bad enough.
Please do remind/ask if interested in using that.

At least lspci was sorely missing in non-rescue images
(as well as in mini rescue part of server image);
thanks Dank Bagryantsev for pointing this out:
http://lists.altlinux.org/pipermail/community/2013-December/681223.html

In these tough times there are no extra resources to waste
for wars or some extra rescue; so it is imperative to provide
some lean and mean help, you know.

IOW a common base has been split out and a more tight rescue
image configuration has been added on top of that so as to
try and fit altlinux-p7-sysv-tde.iso for i586 into CD-R.

The changes in commits gb3e3234c and ga860b179 were actually useless
as rescue+fs list wasn't included into RESCUE_LISTS... and I need
pv(1) for convenient local disk cloning with time estimate.

Networking is *not* brought up by these rescue images
by default, one is expected to know enough to do that
by hand if needed; still there's no harm to have apt
preconfigured so that it would be operational then.

systemd would get pulled in via journal but both are really
irrelevant for these rescue images.

There are various bootloaders around there and some of them
are supported in ALT Linux; let's provide all the mainstream
ones so that knowledgeable root@ has every tool needed for
most situations needing bootloader repairs.

These might require particular knowledge or special boot mode
(like EFI ones).

Being able to handle [compressed] archives of all kinds
tends to be pretty instrumental in rescue operations,
and some backup system clients won't hurt either.

Some ancient Serial words like "minicom" still come handy
at times too.

Comments, constructive criticism and proposals are welcome.

Moved the packages which impeded pkglist reuse for live distros
so that these stay within dedicated rescue images but don't
neccessarily go into the more generic ones where things like
fdisk are still quite useful.

There's a need for a separate boot target since
persistent storage is way slower than tmpfs indeed;
usbflash has a tendency for huge performance drops
given simultaneous writes in addition to reads which
are the bottleneck already.

make-initrd-propagator 0.18 introduced ext4 rw slice,
so the corresponding kernel module needs to be included
into stage1; see also #28289.

NB: not available on x86_64-efi (or hybrid GPT to be strict)
due to fragility of the hack being made: parted(8) panics
upon seeing that, and good ol' fdisk is unable to treat it.

NB: use/live/rw use/rescue/rx use/syslinux/ui/gfxboot
are unlikely to play very nice together due to the latter's
magic l10n: "session" label is taken by live_rw config snippet
and *is* translated in design-bootloader-source;
OTOH "rescue_session" is *not*.

It's currently security+extra.

Things that weren't fit in the other rescue pkglists went here;
more are sure to follow.

It happens to hold a noticeable share of what might go into
rescue+misc, so why duplicate.

As the firmware feature got more involved, this one
has successfully dodged the change but is amended now.

Richard and Theo would probably roll their eyes at this point
but the unfortunate reality is that wireless hardware is very
much dependent on firmware being explicitly provided; so here
it is.

rtl8192 kernel module added since it's present in t6/branch
at least.

There's no use of a rescue image when it has no firmware
for the controller in the system being worked on...
so added some.

That sub/stage2/install2 was somewhat clumsy actually as it looked
like a hierarchical thing while being a substitution thing:
generic stage2 would get put in place renamed as install2.

This could only get worse with hierarchical features which have
already been both requested and considered for quite a time,
and "stage2 at install2" reads much more naturally.

There's no (convenient) "eject" at times, so it's better to provide
extra ways of booting right away.

Found myself pretty silly while sittin' at the rescue console
and bein' unable to leave the cool server room for a way
more comfortable armchair and a laptop's keyboard...

(yes, it was that disk array needing GPT tools)

The reason is that package lists and individual packages
are processed in different dependency resolution "transactions"
by mkimage; thus if packages (the more precise form of specifying
the contents) come first they can't override the lists appearing
later, and that's wrong: we should be able to specify the more
generic things and then pinpoint the specifics.

This became apparent while authoring [[Mkimage/Profiles/m-p/howto]]
asked for by drool@.