GitLab

Fix typo in prepare_zfs_root().

See merge request !72

features: add phy drivers to network

Closes aports#11715

See merge request !74

Add zstd compression support

See merge request !75

Now that 5.10 is out and supports zstd compression for the kernel and
initramfs, add support for zstd to mkinitfs. The benefits have been
discussed at length on lkml[1][2].

In my personal experience, the compression (mkinitfs) seems to be
slower, but decompression (booting) seems to be faster. I think most
people boot more than they mkinitfs.

The default is still gzip, so no change should be noticed unless
someone goes looking for trouble.

To test this functionality, just add the following to mkinitfs.conf:

```text
initfscomp=zstd
```

[1] https://lkml.org/lkml/2020/7/23/1010
[2] https://lkml.org/lkml/2020/7/1/722

Some ethernet drivers (e.g. Realtek r8169) require a corresponding
phy driver to function.

Fixes aports#11715

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

pigz(1) is a parallel gzip implementation. As such, it significantly
faster than gzip(1). This patch uses pigz(1) instead of gzip(1),
if it is installed, otherwise it just falls back to gzip(1). This is
similar to the current pigz support in abuild.

Without this patch:

	$ time mkinitfs
	==> initramfs: creating /boot/initramfs-lts
	real	0m 38.19s
	user	0m 35.47s
	sys	0m 0.49s

With this patch applied and pigz installed:

	==> initramfs: creating /boot/initramfs-lts
	real	0m 13.24s
	user	0m 38.30s
	sys	0m 0.56s

This change was discussed on IRC with _ikke_ and mps.

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.

ref aports#11044

Henrik Riomar authored Oct 15, 2019 and Natanael Copa committed Nov 25, 2019

Add new feature rpi rtc allowing a hw rtc to be used.

The init script in Alpine Linux since v3.9 looks for /dev/rtc, if
not found it will switch to swclock.

To make this check work on a Rasberry PI with a mounted rtc and
the following in usercfg.txt
 dtoverlay=i2c-rtc,ds3231
we must have rtc drivers available already initramfs.

udhcpc needs af_packet to work.

ref aports#10750

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.

Handle case when the crypt header is a normal file which is included in
initramfs and not a blockdevice.

Add ssl_client so busybox wget has https support.

This provides basic dhcp client support without including all the
network drivers/modules like the network feature does.

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

if search device is prefixed with ZFS= then we search for a label with
the zpool name in the zfs path. For example, if search device is
"ZFS=tank/alpine/root" then we search for device that is type
"zfs_member" and label "tank".

This makes it work better with grub which creates a boot cmdline with
ZFS=

https://bugs.alpinelinux.org/issues/9889