This typo causes $_root_pool to be an empty string, which causes the
subsequent `zpool list` to output encryption status for every pool
rather than just one, breaking the comparison.

On systems with a zfs root and more than one pool present, this
manifests as an error message on boot just before openrc is invoked:

    sh: enabled: unknown operand

Similar to DASD and QETH devices.

Example of kernel argument for 2 device paths:
zfcp=0.0.1905:0x50050763070845e3:0x4082400400000000,0.0.1945:0x50050763071845e3:0x4082400400000000

Each device path is separated by a comma (,). Adapter bus ID and WWPNs and
LUNs are separated by a colon (:).

Since Alpine has the advantage of using root=UUID= for root disk, device
order and device naming don't matter.

Sometimes a console is specified on the kernel command line but doesn't
get initialized by the kernel because for example the driver is built as
a module. The init should still spawn getty on it.

We accidentally used $_root_vol instead of $_root_pol for force importing.
Also import (but without -f) if we don't force import as this is required
on some setups. Add -d /dev as this is required for zpool to find the
pool if you have defined some subvolume as partition (e.g. for VMs)

This enables debug of early-init problems via the use of the earlyprintk kernel parameter.

The LUKS2 cryptsetup format uses a locking mechanism, see the "LUKS2
header locking" section in cryptsetup(8) for further information on this
mechanism. The mechanism requires a locking directory, if it is not
present it will be created automatically. Unfortunately, cryptsetup
emits a warning when creating it.

To silence this warning message make init create the directory.

Without this change this may result in a warning message to be printed
during boot if the rootfstype kernel parameter is not set.

Harm Berntsen authored Apr 27, 2019 and Natanael Copa committed Jun 07, 2019

Right now, when $KOPT_BOOTIF is specified, it can echo a device related
to that option and still continue with the loop that checks the
operstate. Due to this, it can echo two network interfaces. This commit
fixes that so it will only return a single network interface.

The configuration option was renamed when parts of our patch
were upstreamed to busybox.

grub will set root=ZFS=... when root is zfs but will not add rootfstype,
so make a special case for zfs

Ain authored Sep 02, 2018 and Natanael Copa committed Nov 08, 2018

BOOTIF can be set by the SYSAPPEND option of PXELINUX. Its primary
usecase is telling the OS which interface it was booted from. This
fixes netbooting from eth1 or upwards if eth0 is connected to an
different network.

Ain authored Sep 09, 2018 and Natanael Copa committed Nov 08, 2018

This flag does not exist on most non-x86 platforms.

Ain authored Aug 23, 2018 and Natanael Copa committed Nov 08, 2018

The kernel offers the same functionality through libata.dma=0.

Ain authored Aug 13, 2018 and Natanael Copa committed Aug 21, 2018

Instead of parsing the console= options in the initramfs, we ask the
kernel of its interpretation of the console= parameters. The kernel
does the console setup as part of its early startup, including the
configuration of the baud rate, control bits and flow control.

The options and format of the console= parameter are documented here:
https://www.kernel.org/doc/html/v4.15/admin-guide/serial-console.html

By keeping the settings from the kernel, we avoid baud rate switching
between printk and getty output on edge cases.

This adds support for additional tty types, like hvc, while removing
string parsing code from the initramfs.

Ain authored Aug 09, 2018 and Natanael Copa committed Aug 21, 2018

Previously, configure_ip was only called from code paths of other
boot options that require network.

This fixes the passing of -n to nlplug-findfs and --no-network to
the apk memory bootstrap.

lemmarathon authored Apr 30, 2018 and Natanael Copa committed Jun 12, 2018

The "cryptkey" boot parameter enables keyfile decryption. By default,
init will look for a keyfile named "/crypto_keyfile.bin". Another file
may be specified like so: "cryptkey=/path/to/keyfile.bin". If keyfile
decryption fails, init will fall back to passphrase mode.

Mick Tarsel authored Jun 08, 2018 and Natanael Copa committed Jun 12, 2018

Previous code would return eth0 every time and pay no attention
if interface was up. This patch gets the state from operstate file
in sysfs to use the interface that is actually up in case there
are multiple interfaces present. If no interface is up, just use
last interface.

ssl_client provides the https support for busybox wget

ssh_pass is not recommended and causes some issues in firstboot. We
remove support for it to keep things simple.

also make sure that sshd is started if ssh_key is set

Tuan M. Hoang authored May 21, 2018 and Carlo Landmeter committed May 24, 2018

This commit allows starting 'firstboot' service (see aports/openrc),
which will setup installation through SSH if specified in kernel
parameters.

Real wget is used instead since busybox's wget is broken without
openssl binary #8917. Credits to clandmeter.

- Allow adding DNS server in configure_ip()
- Prefix kernel parameters with KOPT_

- Allow including dasd and qeth modules when building initramfs
- Add detection for dasd and qeth devices from cmdline in init

mountpoint cannot be located when repo is external.

Sören Tempel authored Feb 18, 2018 and Jakub Jirutka committed Feb 18, 2018

None of the other commands emit any output if everything works as
expected and I just like consistency.

example:
```sh
❯ docker run --rm -ti alpine
/ # KOPT_blacklist=igb,ixgbe,tg3
/ # for i in ${KOPT_blacklist/,/ }; do echo "blacklist $i"; done
blacklist igb
blacklist ixgbe,tg3
/ # for i in ${KOPT_blacklist//,/ }; do echo "blacklist $i"; done
blacklist igb
blacklist ixgbe
blacklist tg3
```

Henrik Riomar authored Jan 08, 2018 and Timo Teräs committed Jan 09, 2018

We can not run hooks before musl and busybox is installed.

Use the new flag --initramfs-diskless-boot in order to skip hooks.
This flag also implies --initdb and the relevant --force flags for
initramfs diskless boot.

https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices:
> btrfs device scan is used to scan all of the block devices under /dev
> and probe for Btrfs volumes. This is required after loading the btrfs
> module if you're running with more than one device in a filesystem.

See http://bugs.alpinelinux.org/issues/6903

When enabled allows the use of discard (TRIM) requests for the device.
See cryptsetup(1) for more information.