Actually a copy of 10localboot.cfg with a different name
and sorting order so as to address #26608: there's no possibility
to make a LiveCD image that would boot itself by default if localboot
has been configured in.

It's only a partial solution as it doesn't override 10localboot
in case it's there already but a step in that direction...

A hint regarding livecd-net-eth is due -- as well as
review and cleanup of live, net, net-eth features
involved in configuring that ethernet for a LiveCD.

This is not strictly required but is basically requisite for some
operations with both packages (did you know about rpm2cpio.sh?)
and initramfs images (which are gzipped cpio archives).

So let's put it in.

It's just reasonable given that new hardware tends to have that.

It's hardwired at 1/10 of the default /etc/net value
since 3 seconds are enough for properly functioning
DHCP servers in properly maintained networks (those
improper ones tend to have problems with 30 seconds
anyways), and waiting for too long makes users feel
bad for a reason.

Thanks msp@ for bringing attention to this.

This one is intended for WD Green drives so as to bring
their spindown timeout into some kind of sanity;
see also http://bugs.etersoft.ru/9438

This package has replaced installer-feature-setup-network-stage3
without declaring that; it appears that installer-distro-altlinux-*
don't require it even if most of the others do.

This is to ensure it's included, at least at the moment.

mixin/regular-tde is used in sysv-tde flavour which has hit 700M
limit for CD-R as Speccyfighter has noted; we can do without games
probably, or at least let's try to.

http://lists.altlinux.org/pipermail/community/2014-January/681534.html

It lacked base desktop packages indeed; thanks Speccyfighter
for naming rsync and wget (as well as mc).

The initial revision was brilliantly buggy: it is *so* apparent
that cdrom will never be actually used for rw slice that this
has evaded my attention rather completely.

- ahci kludge (see #29705) :(

This change tries to force loading the storage driver
for cases when SecureBoot is "helping" the chainloader
to fail, see #29705 for details collected so far.

Of course ahci.ko only does AHCI but that's every storage
controller I've seen on UEFI/SecureBoot systems so far.

This reverts commit d160d610:
GNUstep reportedly works on x86_64 now.

Conflicts:
	conf.d/regular.mk

- rescue tweaks

Let's put osec tools into installable packages at least
(aiming to shift these into default install probably);
these are worthwile addition to sysadmin's toolbox.

Thanks dobr@ for bringing this up.

It turns out that regular-rescue.iso lacks sshfs,
which is unfortunate (even if it could be installed
with apt in this particular case); three more FUSE
based filesystems have been added just in case.

Thanks mithraen@ for suggesting davfs2.

I'm fed up with graphical software occasionally making it
into regular-rescue.iso and bloating it for no good reason
given that window managers or xinitrc aren't included.

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.

It's a pretty hefty addition which isn't strictly required
in a basic rescue image even if it's welcome as an extra.

Seeing tagged/base+rescue~ in build.log isn't particularly
heart-warming; while other editors but the one leaving tilda
marked backups and .sw* swap files might exist let's do this
step at this time.

Wonder what changed though, this used not to happen before.

Rescue images definitely don't need alterator pulled in.

- support for CIFS installation method (sin@)
- glibc-locales for regular images (closes: #29693)

At least regular images should include locale support,
various software and users might malfunction otherwise;
thanks manowar@ for spotting and reporting this (#29693):

http://lists.altlinux.org/pipermail/sisyphus/2014-January/361929.html

It's a tad pointless to be able to create a filesystem
but not to be able to fsck it at boot.

- regular fixes

Dank Bagryantsev asked if it could be added to available packages
at least; well it is there now but not in default install
as aptitude is currently unsupported.

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

Thanks ksa at Russia-2 forum:
http://forum.russ2.com/index.php?showtopic=3784&st=0&p=37927&#entry37927

This is pretty valuable addition and doesn't take that much space
(roughly +100M).

I don't think we're gonna like plymouth over rescue image
anytime soon, especially when it hides the moment when shell
pops up somewhere under it without startup-rescue caring to
remove the splash.

So let's put that $(INSTALL2_BRANDING) into proper stage2
flavours only and avoid choking on missing plymouth as well.

led@ has different kernel-modules-* package set,
some of those "standard" names are provided but
vbox* is not the case.

As our macros and helpers will grok this just fine,
let's add both variants so what's present gets in.

Another fork place: live branch used to depend on +vmguest,
installable one omitted that for some reason.

Suddenly got lots of extra space to wa^H^Hfill due to led-ws
thus a few more FRs by Speccyfighter can go in ;-)

This kernel can help save almost 50 megabytes of image size
and shave off several megs of RAM consumption as well which
is important after the installation has been through.

Adding rescue image was requested by Speccyfighter (in Russian):

http://lists.altlinux.org/pipermail/community/2013-December/681045.html

...and it seems hard but doable if one doesn't mind barebone rescue;
still efi-shell shouldn't spoil x86_64 build as that one won't fit CD-R
and doesn't have to anyways.