| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
we may want have conditional default config depending on architecture
|
| |
|
|
|
|
|
| |
Having xfs_repair in the initramfs can help if your root filesystem
is messed up.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
mountpoint cannot be located when repo is external.
|
|
|
|
|
| |
None of the other commands emit any output if everything works as
expected and I just like consistency.
|
|
|
|
|
|
|
|
|
| |
Since we previously specified an explicit request_type for the
crypt_load() function nlplug-findfs couldn't open LUKS2 containers. By
using CRYPT_LUKS crypt_load accepts any known LUKUS container format.
We could add an additional command line flag to nlplug-finds for
specifying the request_type but I guess this is good enough for now.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
```
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
release 3.2.0
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
ref #7611
fix a duplicate in xfs while at it
|
| |
|
| |
|
|
|
|
| |
For reference: http://git.r-36.net/nldev/tree/arg.h
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to https://www.kernel.org/doc/Documentation/admin-guide/serial-console.rst
the serial port options is specified as:
"... BBBBPNF, where BBBB is the speed, P is parity (n/o/e), N is number of bits,
and F is flow control ('r' for RTS)." Parity and Number of bits are ignored
since getty does not have any options for them.
I tested the paramater substitution using the following script/snippet:
```sh
/ # cat /etc/alpine-release; cat kernel2getty.sh; sh kernel2getty.sh
3.5.2
consoles="ttyS0 ttyS0,115200 ttyS0,115200n8 ttyS0,115200n8r ttyS0,115200r"
for console in $consoles; do
line=-L
term=vt100
tty=${console%,*}
speed=${console#*,}
flow=${speed##*[^r]}
speed=${speed%%[^0-9]*}
echo "console=$console"
echo " speed=$speed"
echo " flow=$flow"
echo " getty=getty ${flow:+-h }$line ${speed:-15200} $tty $term"
echo "----------"
done
console=ttyS0
speed=
flow=
getty=getty -L 15200 ttyS0 vt100
----------
console=ttyS0,115200
speed=115200
flow=
getty=getty -L 115200 ttyS0 vt100
----------
console=ttyS0,115200n8
speed=115200
flow=
getty=getty -L 115200 ttyS0 vt100
----------
console=ttyS0,115200n8r
speed=115200
flow=r
getty=getty -h -L 115200 ttyS0 vt100
----------
console=ttyS0,115200r
speed=115200
flow=r
getty=getty -h -L 115200 ttyS0 vt100
----------
```
closes #7037
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Without a call to crypt_set_data_device(), the cryptsetup system does
not know where to find the data device. It works whether the header is
deported or not, according to
https://github.com/mbroz/cryptsetup/blob/8f84fb49faa69b0ddde3d534ee9c72119256f4c9/src/cryptsetup.c#L782
so it is fine to call it in all cases.
|
| |
|
| |
|
| |
|
|
|
|
| |
move the logic to separate function
|
|
|
|
|
| |
put all data related cryptsetup in a struct. No changes in
functionality.
|
| |
|
| |
|
|
|
|
| |
ref #6689
|
|
|
|
|
|
|
| |
instead of having only one features.d directory, make it a search
path to which paths can be prepended with -P option. This allows
custom boot media creation scripts to contain features.d overlays,
and additional features.
|
| |
|
| |
|
|
|
|
|
| |
We could sucessfully read the password but fail to reset the tty. If
that happens, then just warn, but return success.
|
| |
|
| |
|
|
|
|
|
| |
we dont need mount and scan the tree if not explicitly told to look for
apkovls or bootrepos.
|
|
|
|
|
|
|
|
|
| |
- specify what device nlplugfindfs is looking for
- make sure we run mdev, otherwise we have no control over when the
/dev/mapper/test-device node is created and may end up in a race
condition with udev
- clean up even if we have error
- add -k option to keep the loop device
|
| |
|
| |
|
| |
|