Age | Commit message (Collapse) | Author |
|
|
|
verify that LABEL= is added to fstab
|
|
|
|
ref: https://gitlab.alpinelinux.org/alpine/aports/-/issues/14064
ref: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10531
This reverts commit 5427c716f6bee896942219cc7cee76eb07288e16.
|
|
This works around issue where /root might get world rx permissions.
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10532
|
|
|
|
|
|
|
|
|
|
Some brcm firmwares uses a glob. Fix this and add tests to verify that
it works as expected.
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10533
|
|
|
|
Needed to test that we get the proper firmware included in modloop with
update-kernel
|
|
We need this to test what we get into modloop in update-kernel
|
|
This was broken.
ref https://gitlab.alpinelinux.org/alpine/alpine-conf/-/merge_requests/124#note_274593
This reverts commit 1e1ac71fc0e6efe8c6bacc5ff3ba6429a97330cd.
|
|
allow pass options for mksquashfs via MKSQUASHFS_OPTS. this will allow
us to pass -info as option to test what gets included in the modloop.
|
|
we use ROOT for testsuite
|
|
Previously, setup-disk could fail when installing over an existing
identical partition table. The additions ensure that a clean disklabel
is created and existing partitions are wiped.
Signed-off-by: Edin Taric <unicorn@regrow.earth>
|
|
also fix so we can join networks without PSK
filter out hidden (\x00) SSIDs
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10518
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10475
|
|
Ref: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/merge_requests/106
Fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10476
|
|
|
|
Use an option to setup-disk to write the selected diskmode instead of
using an undocumented /tmp/alpine-install-diskmode.out
Adjust setup-alpine to use this, and make sure that we write the
diskmode when installing to a mounted root.
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10444
|
|
Only give warning about MBR on x86 and x86_64 and when in legacy bios
mode. (syslinux or grub).
Make sure grub is installed if needed, by using select_bootloader_pkg.
|
|
Some modules wants non-existing firmware like b43 and b43legacy
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10530
|
|
|
|
|
|
|
|
Consider my laptop with linux-lts on UEFI with Secure Boot:
System.map-lts.....4 MiB
initramfs-lts.....36 MiB
vmlinuz-lts........8 MiB
linux-lts.efi.....44 MiB (signed Unified Kernel Image)
linux-lts.efi.bak 44 MiB (backup of the previous)
Total............136 MiB
256 MiB might be enough, but what if the user wants to experiment with
more kernel variants? It would be still too tight. On the other side,
if the user has only 1 GiB disk (e.g. ncopa uses 1GiB images for testing),
then even 256 MiB would be too much.
Originally, I just increased the default to 512 MiB, but ncopa pointed
out that it's too much for small disks and he personally uses 1GiB
disks (images) for testing. For this reason, I chose a more
sophisticated approach that takes into account the size of the disk.
* 512 MiB if disk > 8 GiB
* 264 MiB if disk > 2 GiB
* 160 MiB otherwise
And the size is never lower than the approximate minimal allowed size of
the FAT32 filesystem for the disk's block size (32 MiB for 512 bytes
blocks, 260 MiB for 4096 bytes blocks).
Issue reported by Andrey Maslyuk <andrey@maslyuk.net> (via email).
|
|
0 is not a safe fallback for a block size.
|
|
VMD is Intel's Volume Management Device. Some Intel-based machines
have a BIOS/UEFI option to present a NVME SSD via either VMD or as
a "native" NVME device.
If Alpine is installed on a NVME device when it is presented via
VMD then once the Alpine ISO/USB boots the 'vmd' kernel module will
be loaded by /etc/init.d/hwdrivers and Alpine will see a
/dev/nvme0n1 device to which setup-alpine can install successfully.
However, once the newly installed system is then booted from the
NVME device the initramfs' init will fail to find the rootfs to
mount/boot from as, without the 'vmd' module being loaded, no NVME
device will be visible.
This MR ensures that the 'vmd' kernel module is added to the cmdline
modules list whenever the 'vmd' has been automatically loaded by
hwdrivers init.d when booting Alpine prior to running
setup-alpine/setup-disk.
This MR works together with
https://gitlab.alpinelinux.org/alpine/mkinitfs/-/merge_requests/112
(which ensures that 'vmd' present in the initramfs).
|
|
soem disk operations takes more time apparently
|
|
some of the tests uses those
|
|
|
|
|
|
fixes use with yash.
|
|
and add test from missing block device
|
|
we dont dont that for real when testing
|
|
|
|
Use an env var SETUP_DISK_TESTFUNC to run individual functions for unit
testing purposes.
|
|
not used since commit 427a14cb8d80 (setup-disk: remove grsec traces)
|
|
prefix /sys/... with $ROOT so we can test it
|
|
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10538
|
|
openrc 0.45 replaced the /etc/init.d/urandom script with
/etc/init.d/seedrng. Change setup-alpine to enable this
script.
|
|
"mesa" does not contain anything except two text files, and all the
graphics drivers are in gallium instead
|
|
Skip user creation if username is 'none' and no other options are set.
fixes https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10528
|
|
some module refer to wildcarded firmware name: ensure proper handling
|
|
Signed-off-by: Laurent Bercot <ska@appnovation.com>
|
|
|
|
The mdev init script isn't guaranteed to be there anymore;
we explicitly add the busybox-mdev-openrc package when choosing
mdev as our device manager.
Signed-off-by: Laurent Bercot <ska@appnovation.com>
|
|
setup-xorg-base didn't correctly handle the case where
/etc/apk/repositories contains several main sources, and that
caused test failures. We fix this by throwing out the big sed command
(which fails on multiline /etc/apk/repositories) and processing the
repositories file in a pedestrian way, line by line in shell. Since
we entirely cut grep and sed and make sure we never fork in the loop,
the performance is acceptable.
Signed-off-by: Laurent Bercot <ska@appnovation.com>
|
|
The hwdriver service is currently activated for mdev and deactivated
when mdev is disabled. Since mdevd and mdev use (more or less) the
same mechanism, we also enable hwdrivers with mdevd.
The service is only started when a coldplug is required, because
if no coldplug is required, the appropriate kernel modules are
already loaded.
Note that with the MODALIAS line in /etc/mdev.conf, it is possible
that the hwdrivers service is entirely redundant. This would need
some additional testing.
Signed-off-by: Laurent Bercot <ska@appnovation.com>
|