Closes: #869668

In kernel 4.8 the vsyscall emulation framework was removed, and the new
interface is only supported in dietlibc 0.33 or higher. To make sure
the code is never built against older versions, bump the Build-Depends.

Closes: #845937

Intel microcode has special alignment requirements that cannot be
fulfilled with the current cpio logic. Instead of trying to do this
manually, rely on iucode_tool to generate an early-initramfs CPIO
image. For a detailed explanation, please read Debian bug #840255.

An arbitrary number of early-initramfs CPIO images can be prepended to
the initramfs itself, so this logic won't interfere with other
early-initramfs image logic.

Closes: #840255

dietlibc is now available on all release architectures and most ports.
There is currently no architecture where dietlibc is not available but
musl isn't.

Git-Dch: ignore

Git-Dch: Ignore

It conflicts with the default initramfs-tools (Priority: optional) and
should hence be Priority: extra as per policy, section 2.5.

Thanks: Jakub Wilk

Upstream version 0.1

Add support for loading modules in tiny-initramfs. The support is
extremely simple, it just looks for a file /modules in the initramfs
image, where each line should be the absolute path (within the
initramfs image) to the module file name, followed optionally by a
space and the options.

No dependency resolution is performed, the modules are loaded in the
order they are specified in the /modules file. The construction of the
initramfs image should take care of the proper order of the modules and
adding all required dependencies.

If a module cannot be loaded, an error message will be shown, but
tiny-initramfs will still try to mount the root file system.

Install the binary as init (in pkglibexecdir) instead of tiny_initramfs
and add support for variants (init-$VARIANT) that may be passed to
configure. That way, builds of tiny-initramfs with different compile
time options may be installed simultaneously on a given system.

Documentation/filesystems/ramfs-rootfs-initramfs.txt says we should do
that. Note that this was not a huge problem before, as our initramfs is
really small anyway.

Switch to an automake-based build system, and allow certain features to
be optional, so that the initrd.img size may be reduced further.

Update the documentation.

Do some changes that reduce the code size a bit.

Add basic NFSv4 mounting support. This increases code size a bit (will
thus be made optional later), but it now supports mounting NFSv4 shares
directly - as long as sec=sys is used and no idmapper is required.

The kernel must have compiled-in support for NFSv4 for this to work.

To help with debugging of the initramfs, add #ifdef'd debug statements.
When compiled with CPPFLAGS="-DDEBUG_INITRAMFS" the initramfs will now
be verbose - and sleep for 5s at the end before executing init.