Architecture: Difference between revisions
WhyNotHugo (talk | contribs) m (→Init: Formatting and slight wording improvements) |
WhyNotHugo (talk | contribs) (→Boot Loader: some minor bootloader references) |
||
Line 40: | Line 40: | ||
=== Boot Loader === | === Boot Loader === | ||
==== EFI ==== | ==== EFI ==== | ||
- The default setup uses GRUB2. | |||
- See also [[UEFI Secure Boot]] | |||
==== BIOS ==== | ==== BIOS ==== | ||
- The default setup uses GRUB2. | |||
==== Other ==== | ==== Other ==== | ||
Revision as of 15:34, 12 January 2023
This material is work-in-progress ... Do not follow instructions here until this notice is removed. |
Alpine Hardware Architecture ("arch") Support
x86 Based
ARM Based
PowerPC Based
- ppc64le - 64 bit PowerPC (little-endian)
IBM System Z Based
Alpine Packaging
Package Building
Alpine Package Building Ports
Package Building Tools
Package Format
Alpine uses packages in the .apk file format.
Package Management Tools
- apk - Alpine Package Keeper (see apk internals for more detail)
Boot Process
Boot Loader
EFI
- The default setup uses GRUB2. - See also UEFI Secure Boot
BIOS
- The default setup uses GRUB2.
Other
Kernel
Versioning
Flavors
- vanilla
- hardened
- virthardened
- rpi
Signing
Command line options
- modules="<modules>" - specify list of modules to be loaded by initramfs /init needed to mount real root filesystem.
Initfs
The kernel will decompress the stream of compressed cpio archives passed to it by the 'append' bootloader option to the root of 'rootfs', a tmpfs automatically mounted at '/' by the kernel at boot.
'/init' Script
Not to be confused with '/sbin/init', the '/init' script in the root of the 'rootfs' is called by the kernel upon completion of its boot process, and is responsible for doing whatever steps are necessary to mount the real root file system to '/' and transfer control to '/sbin/init'.
- Parses kernel command line options.
- Uses nlplug-findfs to discover devices.
Initfs Module Handling
Modules required to mount the root filesystem and boot must either built into the kernel or available from with the initramfs filesystem through use of appended initrd cpio.gz files provided by the bootloader.
The /init script will first modprobe the modules specified by the modules= kernel command line option and by the name of the specified rootfs type. It will then load the contents of /etc/modules, which may include module options. Modules may be blacklisted from autoprobing (but NOT explicit insertion!) using the blacklist= kernel command line option which appends blacklist entries to '/etc/modprobe.d/boot-opt-blacklist.conf'.
Minimal Required Set
Directory Structure
- / /bin /boot /dev /etc /lib /lib/modules /media /media/cdrom /media/usb /mnt /proc /sbin /sys /usr /usr/bin /usr/sbin
Devices
- /dev/null
- /dev/console
- /dev/kmsg
Mounts
- /proc
- /sys
- /dev (can be disabled?)
Configuration
- /etc/passwd
- /etc/group
- /etc/fstab
Binaries
Feature Sets
Feature sets consist of lists for the set of modules and files that need to be included in a final initramfs to support the indicated feature.
Init
/sbin/init
is the first process to be started in the live system after the initramfs completes its work. It is part of the Busybox package and should not be confused with the /init
script mentioned above.
Module Loading
/etc/init.d/modules
loads all modules specified in /etc/modules
and /(etc|run|usr/lib|lib)/modules-load.d/*.conf