This one relates to serial ports (including USB serial);
thanks dd@ for suggestion.

That space before ']' was missing indeed :-/

It's not neccessarily installation media.

Shift boot order so that rescue image can get mediacheck too
but still boot into rescue by default.

As proposed by Maxim Suhanov since there are only
7 loop devices available upon bootup which might be
not enough given ro,loop mounts by default.

This value is used to authenticate rescue rootfs image
by verifying the squashfs file's sha256sum before use
(propagator-20140419+).

Looks like this check might be useful for other stage2
images as well but let's get started with this one.

Thanks Maxim Suhanov <suhanov/group-ib.ru> for both
http://www.forensicswiki.org/wiki/Forensic_Live_CD_issues
and propagator patches.

Thanks Maxim Suhanov (suhanov <AT> group-ib.ru,
http://www.forensicswiki.org/wiki/User:.FUF)
for taking the time to review regular-rescue image.

Note that there are more than just filesystems:
arrays, logical volumes and swaps aren't activated either;
startup-rescue >= 0.18 should make that clear enough.

syslinux shortcut handling is case-insensitive,
let's find yet another letter...

A variant of rescue that marks the need to be careful
towards block devices and filesystems thus reducing
the amount of auto-activation done by startup-rescue
(0.17 or newer).

This is a refactored result of Zabbix-related experiments;
we can do a rough zabbix server sketch that still requires
its own setup to go.

NB: both the pkglist and the target are describing several
distinct things actually: zabbix server, zabbix agent,
and the underlying SQL/HTTP/SMTP servers which might get
their own smaller targets some day.

It appears that live feature has been buggy regarding user
groups: its 30-users script would create a predefined account
with fixed supplementry groups list, and even if deflogin feature
got used too it would fail to add any groups to already existing
account since its useradd(8) call would fail.

Let's drop this duplication which has been long overdue anyways.

Thanks dd@ for both reporting the problem and carrying out
initial investigation.

There have been several problems with this feature:
- a typo;
- non-existant GROUPS (even a single one) would block setting
  all of the supplementary groups but separately-set 'wheel';
- this feature isn't used much actually so sees no battle testing.

The typo has been just fixed; GROUPS are now applied by iteration
which is less effective but more reliable; an additional script
hook to write down login invitation for the first passwordless
account (if any) has been implemented; and several more group
managing targets have been added (based on live feature's script).

This relates to commit f2892ad3
as there's an obvious need to be able to set empty root password
for LiveCDs but previous implementation was very fragile (and is
going to stay that way) -- so clear and separate knob for making
an image defenseless looks better.

Whoops, the very first build of a real distro with gfxboot
has shown that the label isn't picked up there... and things
are actually worse: iso.needscheck gfxboot test seems to look
up "check=1" in sectors where it might have been landing back
then but it's just not there by now; some kludgery is due in
branding-altlinux-sisyphus unfortunately.

No use to hunt make or diff file-by-file.

Well this chroot should have been more lean
in the first place (or a few files in initrd)
but life is short so better use/baby/steps.

These aren't needed in this subprofile but can sneak in
via e.g. SYSTEM_PACKAGES.

This one is quite different already and utility-based name
was pretty clumsy; meet the new feature and retire the old
experimental one.

Please note that quite aggressive cleanups are implemented
within this stage2-based subprofile for the simple reason
that it has a single task to do; nothing else is expected
to be configured into it for that matter.

This functionality asks to be further moved into initrd of course;
adding it there will take a few more decisions to be made, mostly
regarding user interaction in failure scenarios, and it looks like
mkimage will have to be patched in case this doesn't just go into
full.cz under some sort of conditional check.

Just a humble config snippet for another squashfs;
note that @bootargs@ aren't expected at all this time.

It's not exactly obvious how install2_size, live_size or rescue_size
get defined since the variable names themselves get constructed;
help git grep these down.

acpid is not enough since power button handling configuration
has been split apart; and tracking this in zillion places is
utterly useless in face of a specially trained power feature.

Just use it.

At least Radeon drivers badly need those,
e.g. SUMO_uvd.bin + PALM_pfp.bin for C60 APU.

Helps live-flightgear.iso a lot indeed!

nodm needs fixing indeed but let's spell this clearly at least.

This one is really not needed, use/init/* instead.
Been declared obsolete for more than 9 months.

Installation finishes just fine if bzip2-compressed
hash files are removed *but* apt-cdrom add will fail.

It happens to hold couple of files nowadays
on an otherwise almost empty system!

This one has been missing for quite some time (infiniband modules
should have triggered a commit like this back then), finally there
in very crude and draft form for the starters.

This destructive target is like a "people's revolution":
almost nothing left.

Some need this to achieve jeos or chaos, respectively.

{lib,}bind shouldn't have to be removed twice, really.

By the time these hooks run the font packages' %post scriptlets
should have fired already; no need to carry the utilities on.

Yes these are bit-by-bit savings.  No it's too expensive still.

Both might be useful in some context but serve no real need
given the installer one, at least this year.

This rotten cherry-picking is ridiculous of course
but that's the price to pay for hard dependencies...

These aren't going to be really needed in that environment,
please refer to the more complete environments like rescue,
live, or an installed system.

xterm is pulled in by xinitrc (as xvt),
xdg-utils by alterator-browser-qt (for xdg-open).

...or are fine with fbdev like in case of installers,
especially minimalistic ones.

My gut feeling is that we're not going to see glib2's
messages a lot within installer environment anyways.

And there's a forgotten /usr/share/X11/locale/ too.

These are required by no package after the intermediate
cleanup has finished.  Argh.

Installer doesn't do systemd and needs no service files.

An installer needs video playback acceleration
when it has some content to show and some means to;
as long as these are not supported just drop this
unconditionally.

These are only needed for alterator-vm when making
LUKS encrypted partitions; ideally the extra libraries
would be omitted automatically when luks isn't included.

At least don't purge it with no questions answered.
Thanks naf@ for posting #29901.

Looks like today's xorg won't autoload radeon_drv but
insists on ati_drv falling back to fbdev if it's not there;
FlightGear runs definitely slow on C-60 APU with that.

I didn't specify ati since it pulls r128 and mach64 modules in
which are rather useless in this context (accelerated 3D graphics).