| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
zpool needs the zfs module to be loaded early. by also loading
rootfstype module early we don't need specify zfs to both modules and
rootfstype
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
ref #6167
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch tries to add resume from hibernation (aka suspend to disk)
support to mkinitfs. The swap partition can be provided via the resume
option.
The default Alpine Linux kernel has no hibernation support compiled in,
so a custom kernel is needed in order to use this.
Some links on the topic:
* https://wiki.gentoo.org/wiki/Custom_Initramfs/Hibernation
* https://git.archlinux.org/mkinitcpio.git/tree/hooks/resume
|
| |
|
| |
|
|
|
|
|
|
|
| |
The kernel passes arguments from /proc/cmdline as a single string like
foo=bar baz="something with spaces". In the latter case, with the added
single quotes the actual value of ${KOPT_baz} would contain these quotes
as well, which is not the intention.
|
|
|
|
|
|
|
| |
This allows one to make a generic initramfs that doesn't require a running
kernel identical to the one used for booting, if said kernel already includes
everything it needs to function (such as compiling everything in instead of
using kernel modules).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|