Alpine Linux - User contributions [en]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T23:31:36Z

Anthumchris:

''This draft was removed'' and is published at https://wiki.alpinelinux.org/wiki/How_to_build_the_Alpine_Linux_kernel

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T23:30:52Z

Anthumchris: removed

''This draft was removed''

User:Anthumchris

2024-12-11T14:28:48Z

Anthumchris:

👨‍💻 [https://gitlab.alpinelinux.org/anthumchris/ gitlab.alpinelinux.org/anthumchris]

== To do ==
* Kernel build tutorial

Custom Kernel

2024-12-11T03:37:55Z

Anthumchris: add How to build the Alpine Linux kernel

{{Draft}}

This process of building a '''custom configured kernel''' assumes you are running on Alpine Linux utilizing abuild & aports.

== But why? ==

You want to build a custom kernel to enable experimental hardware or features or outdated hardware, to reduce bloat further, to tune the kernel to the hardware.

The lts kernel for most Alpine ARCHs uses defaults to balance throughput at the expense of some responsiveness, and support for many devices. You can tweak the kernel for desktop use and low latency and responsiveness.

You should disable modules to increase security. By default, Alpine will install modules but not disable most of them. Disabling modules will reduce an DMA attack but not eliminate it completely. If you have a newer processor with VT-d, you can mitigate as long as you:

Leave <code>CONFIG_INTEL_IOMMU_DEFAULT_ON=y</code> or pass <code>intel_iommu=on</code> as a kernel parameter and disable kernel logging so the attacker doesn't gain DMAR address information through dmesg.[https://blog.frizk.net/2016/11/disable-virtualization-based-security.html] Also remove references to the kernel version to calculate the IOMMU addresses.[https://link.springer.com/content/pdf/10.1186/s13173-017-0066-7.pdf]

To increase the security of the boot process, if you have a TPM, you could set <code>CONFIG_INTEL_TXT=y</code> (Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)) (which is not enabled in the hardened kernel by default), then you would need the SINIT module (provided only by Intel)[https://software.intel.com/en-us/articles/intel-trusted-execution-technology], a possibly compiled TrustedGrub2[https://github.com/Rohde-Schwarz-Cybersecurity/TrustedGRUB2], trousers[https://sourceforge.net/projects/trousers/?source=navbar], tboot[https://sourceforge.net/projects/tboot/]. These packages are not in aports and it is unknown if these tools work on musl. It's not recommended for Edge. Also, there would be trigger packages to generate hashes for the kernel and the mkinitfs updates.

== Setting up the Alpine Build System ==

First, you need to follow the steps in [[Creating_an_Alpine_package#Setup_your_system_and_account|Setup your system and account for building packages]]. You also need to configure your {{path|/etc/apk/repositories}} so that they search locally for your apks. See [[Creating_an_Alpine_package#Testing_the_package_locally|Testing the package locally]] for details.

After setting up accounts and repos, change your shell's current working directory to '''aports''' that you just cloned.

{{cmd|$ cd aports}}

== Working with aports ==

We will try using an existing lts kernel just tweaking the {{path|lts.ARCH.config}} file.

=== Switching to the proper release version ===

You need to switch to the proper branch that matches the release so that the kernel compiles against the dependencies properly.

{| cellpadding="5" border="1" class="wikitable"
|-
! Alpine version
! Remote branch
|-
| Edge
| master
|-
| 3.17.0
| 3.17-stable
|-
|}

The following is required to get access to the {{path|APKBUILD}} released for that version of Alpine and which you will create a commit for.

If you are on 3.17 do:

{{cmd|$ git checkout -b 3.17-stable origin/3.17-stable}}

If you are on Edge do:

{{cmd|$ git checkout master}}

=== Creating your config ===

You can use {{pkg|linux-lts}} but what you should do is create a local branch by doing:

For Alpine Edge:

{{cmd|$ git checkout -b my-custom-kernel}}

For Alpine 3.17:

{{cmd|$ git checkout -b my-custom-kernel origin/3.17-stable}}

Doing it this way, you do less work in maintaining. All you need to do is keep ''master'' or ''3.17-stable'' in sync[https://help.github.com/articles/syncing-a-fork/][https://help.github.com/articles/configuring-a-remote-for-a-fork/] and merge any conflicts.

First switch to the branch by doing <code>git checkout my-custom-kernel</code>. Then, you need to navigate to the {{path|main/linux-lts}} folder where you should see a APKBUILD and some config- files. When you are done with your edits either by editing directly the APKBUILD and copying the {{path|lts.ARCH.config}} as {{path|.config}} in the {{path|linux-4.15}} folder. You will then move the {{path|.config}} back overriding the {{path|lts.ARCH.config}} generated by <code>make menuconfig</code> (discussed below in the ''Configuring kernel'' section). After generating your config, you need to <code>abuild checksum</code>. Then, do <code>git add APKBUILD lts.ARCH.config</code> where ARCH is whatever architecture (x86, x86_64, ...) you use. Then, you need to do <code>git commit APKBUILD config-NAME.ARCH -m "Enabled these options ...."</code> for your customization the ARCHitecture of your system. You do this so that git can keep your code separate from Alpine's and so your changes float forward between kernel updates.

== Adding custom patches ==

Custom patches should be added to ''sources=''.

After you added the URL, you need to produce a checksum by doing <code>abuild checksum</code>.

The custom patches may not be autopatched, due to being distributed as an archive or different patch level, so you need to define what to do with it in the prepare().

== Configuring kernel ==

Attempt to build the kernel first. To do that, you do <code>abuild -rK</code> to install most of the dependencies. If it complains about a dependency like {{pkg|elfutils-dev}} use <code>-rKd</code>. Then, when it prompts for values for new found config options just hold enter till it starts compiling the kernel. There should be two sets one for -lts and the other for the -virt. Just {{Key|Ctrl}}+{{Key|C}} out of the compilation process after the second set so you can further customize the config. Then you go into the {{path|src/linux-VER}} and edit the config file. Copy the {{path|.config}} file overriding the {{path|lts.ARCH.config}} in the srcdir.

The alternative is to use the kernel configuration menu in the build-NAME folder, but before yo do that you need to <code>sudo apk add {{pkg|ncurses-dev}}</code>

After you are done using the menu in the build-NAME folder by doing <code>make menuconfig</code>, you want to remove <code>ncurses-dev</code>. When you are done, it will be stored in ''.config'' which you need to again override the {{path|lts.ARCH.config}} file. When you are done updating the {{path|config-NAME.ARCH}}, you need to do <code>abuild checksum</code>.

The options in the kernel config are typically defaults. If your device is old, it may be set to n by default.

=== Vanilla targets and tuning ===

{|cellpadding="5" border="1" class="wikitable"
!ARCH
!Processor Type / CPU Selection / System Type
!Code Generation / Instruction Extensions
!Timer Frequency
!Preemption Model
!Bitness
|-
|s390x
|IBM zEnterprise 114 and 196
|IBM zBC12 and zEC12 (<code>-march=zEC12 -mtune=zEC12</code>)
|100 Hz
|No Forced Preemption (Server)
|64
|-
|ppc64le
|Server processors
|POWER8 (<code>-mcpu=power8</code>), AltiVec (<code>-Wa,-maltivec</code> to assembler or <code>-maltivec -mabi=altivec</code>), VSX
|100 HZ
|No Forced Preemption (Server)
|64
|-
|ppc
|
512x/52xx/6xx/7xx/74xx/82xx/83xx/86xx
* Apple PowerMac based machines
|AltiVec (<code>-Wa,-maltivec</code> to assembler or <code>-maltivec -mabi=altivec</code>) on >=74xx
|250 HZ
|No Forced Preemption (Server)
|32
|-
|x86_64
|Generic-x86-64
|(-mtune=generic ; SIMD assembly modules enabled based on simple compile test and/or presence of CPU flag)
|300 HZ
|Voluntary Kernel Preemption (Desktop)
|64
|-
|x86
|586/K5/5x86/6x86/6x86MX
|(-mtune=generic ; SIMD assembly modules enabled based on simple compile test and/or presence of CPU flag)
|300 HZ
|Voluntary Kernel Preemption (Desktop)
|32
|-
|armhf
|
* ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait)
* Freescale i.MX family -- Cortex A (i.MX51, i.MX53, i.MX6 Quad/DualLite, i.MX6 SoloLite, i.MX6 SoloX, i.MX6 UltraLite, i.MX7 Dual)
* Qualcomm -- (MSM8X60, MSM8960, MSM8974)
* Allwinner SoCs -- (A10 (sun4i), A10s / A13 (sun5i), A31 (sun6i), A20 (sun7i), sun8i Family, (sun9i))
* ARM Ldt Versatile Express family --
|Either <code>-march=armv7-a</code> or <code>-march=armv5t -Wa,-march=armv7-a</code> based on a compile test. <code>-mfpu=vfp</code>
|100 Hz
|Voluntary Kernel Preemption (Desktop)
|32
|-
|aarch64
|
* Allwinner sunxi 64-bit SoC Family
* Broadcom BCM2835 family
* Marvell Berlin SoC Family
* ARMv8 based Samsung Exynos SoC family
* ARMv8 based Freescale Layerscape SoC family
* Hisilicon SoC Family
* Mediatek MT65xx & MT81xx ARMv8 SoC
* Marvell EBU SoC Family
* Qualcomm Platforms
* Rockchip Platforms
* AMD Seattle SoC Family
* Altera's Stratix 10 SoCFPGA Family
* NVIDIA Tegra SoC Family
* Spreadtrum SoC platform
* Cavium Inc. Thunder SoC Family
* ARMv8 software model (Versatile Express)
* AppliedMicro X-Gene SOC Family
* Xilinx ZynqMP Family
|
|300 HZ
|Voluntary Kernel Preemption (Desktop)
|64
|-
|}
If you do desktop multitasking, you may want to switch to Voluntary Kernel Preemption (Desktop) or Preemptible Kernel (Low-Latency Desktop) and up the Timer Frequency. If you run a dedicated render farm node or a dedicated bitcoin miner use No Forced Preemption (Server) and decrease the Timer Frequency.

Optimized modules (most are already compiled as modules):
* raid6 -- altivec, avx512, ssse3, avx2, mmx, sse, sse2, neon
* some operations of raid5 -- mmx (32 bit), sse (64 bit), avx
For Kernel API:
* 32-bit memcpy -- 3dnow
* 32-bit memory page clearing and copying -- sse (Athlon/K7 only), mmx
From x86/crypto, arm/crypto, powerpc/crypto:
* CAMELLIA -- avx2, avx, aes-ni
* CHACHA20 -- avx2, neon
* CAST5 -- avx
* CAST6 -- avx
* TWOFISH -- avx
* SERPENT -- avx2, avx, sse2
* SHA1 -- avx2, ssse3, neon, spe
* SHA2 -- avx2
* SHA256 -- ssse3, neon, spe
* SHA512 -- avx2, ssse3, neon
* POLY1305 -- avx2
* GHASH -- pclmulqdq (part of aes-ni), vmx (power8)
* AES -- aes-ni, neon, vmx (power8), spe
* CRC32 -- pclmulqdq, sse, neon, vmx (power8)
* CRCT10DIF -- pclmulqdq, sse, neon, vmx (power8)

=== Fast reboots with kexec ===
{{main|kexec}}

If you want to reboot the kernel fast avoiding the POST test, you need {{ic|doas apk add {{pkg|kexec-tools}}}} and enable kexec in the kernel:

Processor type and features
[*] kexec system call

=== Hibernation to prevent data loss ===

Power management and ACPI options
[*] Hibernation (aka 'suspend to disk')

Hibernation should be used if you have a laptop. You don't want the laptop to suddenly shut off resulting in data loss, you want it to save your work based on a percentage of battery life (this requires special script). When hibernation resumes, should lock and ask for credentials. Depending on your needs, the hibernated image can be encrypted/decrypted which again requires additional customization to scripts.

Hibernation with an unsanitized swap file is generally insecure because data and unlocked memory pages are swapped out in plaintext. To increase the security either disable swap or use an encrypted swap. The swap file/partition is typically used as the hibernation resume image.

== Building ==

Before building, you may want to remove as many modules as possible. This will reduce the time to compile greatly. Also, you may want to use [https://github.com/ccache/ccache/ ccache] for faster recompiles especially if you are searching for the minimal set of options or modules to use or include.

You should then do an <code>abuild -r</code> to attempt to build it.

== Installing ==

To install it you do a {{ic|doas apk add linux-NAME}} where NAME is your custom kernel name.

== Testing ==

Before you test, you should install the lts kernel too, using <code>apk add {{pkg|linux-lts}}</code>. You may be missing a module and can't boot, so you use the other kernel as the fallback boot kernel. Don't forget to update your bootloader configuration.

To test, first you should make a bootable Alpine USB image. Then, when you have your rescue USB done, you <code>reboot</code> the computer.

To test it, you basically do trial and error. Sometimes your config is missing something if you want to have a bare minimum setting.

If you are curious about correctness testing, some kernel modules or components do preform self tests at the beginning of the boot process. The tools may have test suites that you run with the make command.

== See Also ==
* [https://wiki.archlinux.org/title/Kernel Archwiki Kernels]
* [https://wiki.gentoo.org/wiki/Kernel Gentoo Wiki Kernel]
* [https://wiki.gentoo.org/wiki/Kernel/Configuration Gentoo Wiki Kernel Configuration]
* [[How to build the Alpine Linux kernel]]

[[Category:Kernel]]

Kernels

2024-12-11T03:36:53Z

Anthumchris:

Alpine Linux has several kernels (see {{Pkg|linux-*}}) designed to suit different situations.

* {{Pkg|linux-lts}} is the stock modular kernel and is configured for a generous selection of hardware.
* {{Pkg|linux-virt}} ({{Pkg|linux-lts}}, see the -virt configs) is recommended for Alpine Linux guests, and disables most hardware in favor of a commonly-virtualized subset of drivers.
* {{pkg|linux-rpi|arch=}} is optimized for the Raspberry Pi. For alpine 3.18 and older there is also {{pkg|linux-rpi2|branch=v3.18|arch=}} and {{pkg|linux-rpi4|branch=v3.18|arch=}} optimized for the raspberry pi 2 and 4 respectively. See {{issue|15324}} for future plans.

For installing a custom kernel, see [[Custom Kernel]]. To select a specific kernel or firmware packages during installation from the Alpine ISO, simply install the desired kernel flavor and firmware packages with {{ic|apk add}} before running {{ic|setup-alpine}}.

== Firmware ==

The {{Pkg|linux-firmware}} meta-package is included in the [[Installation|default installation]], and depends on all firmware. It is a large download. You may be better served by installing only the firmware you need (see {{Pkg|linux-firmware-*}}), or {{Pkg|linux-firmware-none}} if you do not require any firmware. If you're unsure which firmware you need, boot with no firmware installed and run {{ic|dmesg | grep firmware}} to get an idea. Be aware that most firmware is non-free.

== Experimental Kernels ==

Some kernels are not well tested and are therefor only available in the testing repository. Use at own risk.

* {{pkg|linux-asahi|arch=aarch64}} for Apple silicon
* {{pkg|linux-elm|arch=aarch64}} for elm chromebooks
* {{pkg|linux-gru|arch=aarch64}} for gru chromebooks

== See also ==
* [[How to build the Alpine Linux kernel]]
* [https://wiki.archlinux.org/title/Kernel Kernel - Archwiki]

[[category:Kernel]]

Tutorials and Howtos

2024-12-11T03:14:32Z

Anthumchris: add Kernels howto

{{Todo|This material has been re-organized..., but grouping should be checked: '''Howtos are smaller articles''' and '''tutorials are more detailed document'''}}

[[Image:package_edutainment.svg|right|link=]]
{{TOC left}}
'''Welcome to Tutorials and Howtos, a place of basic and advanced configuration tasks for your Alpine Linux.'''

'''The tutorials are hands-on''' and the reader is expected to try and achieve the goals described in each step, possibly with the help of a good example. The output in one step is the starting point for the following step.

'''Howtos are smaller articles''' explaining how to perform a particular task with Alpine Linux, that expects a minimal knowledge from reader to perform actions.

'''IMPORTANT:''' contributions on those pages must be complete articles as well as requesting topics to be covered, don't override already made contributions. If you want to request a topic, please add your request in this page's [[Talk:Tutorials_and_Howtos|Discussion]].

{{Clear}}

= Howtos =

== Applications ==

=== Miscellaneous ===

* [[Ansible]] ''(Configuration management)''

=== Monitoring ===

* [[Awstats]] ''(Free log file analyzer)''
* [[Cacti: traffic analysis and monitoring network]] ''(Front-end for rrdtool networking monitor)''
* [[Cvechecker]] ''(Compare installed packages for Common Vulnerabilities Exposure)'' 
* [[Linfo]]
* [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[PhpSysInfo]] ''(A simple application that displays information about the host it's running on)''
* [[Matomo]] ''(A real time web analytics software program)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
** [[Setting up NRPE daemon]] ''(Performs remote Nagios checks)'' 
* [[Setting Up Fprobe And Ntop|Ntop]] ''(NetFlow collection and analysis using a remote fprobe instance; for alpine 3.10-3.12 only)'' 
* [[Setting up lm_sensors]]
* [[SqStat]] ''(Script to look at active squid users connections)''
* [[Traffic monitoring]] 
** [[Setting up monitoring using rrdtool (and rrdcollect)]]
** [[Setting up traffic monitoring using rrdtool (and snmp)]] 
* [[Zabbix|Zabbix - the professional complete manager]] ''(Monitor and track the status of network services and hardware)''
* [[ZoneMinder video camera security and surveillance]]

=== Networking ===

* Alpine Wall ''(a new firewall management framework)''
** [[Alpine Wall]]
** [https://git.alpinelinux.org/awall/about/ Alpine Wall User's Guide]
** [[How-To Alpine Wall]]
* [[Freeradius Active Directory Integration]]
* [[GNUnet]]
* [[Setting up a OpenVPN server|OpenVPN server]] ''(Allowing single users or devices to remotely connect to your network)''
* [[OpenVSwitch]]
* [[Using Alpine on Windows domain with IPSEC isolation]]
* [[Configure a Wireguard interface (wg)|Wireguard]]

=== Telephony ===

* [[FreePBX|FreePBX on Alpine Linux]]
* [[Setting up Zaptel/Asterisk on Alpine]]
* [[Kamailio]] ''(SIP Server, formerly OpenSER)''

== Backup and data migration ==

* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)''
** [[Back Up a Flash Memory Installation]]
** [[Manually editing a existing apkovl]]
* [[Migrating data]]
* [[Rsnapshot]] - setting up periodic backups

== Desktop ==
* [[Daily driver guide]]
* [[Alpine and UEFI]]
* [[Default applications]]
* Desktop cloud
** [[Nextcloud]] ''(Self hostable cloud suite - Dropbox Alternative)''
* [[Desktop environments and Window managers]] (overall information only)
* [[Gaming on Alpine]]
* [[Printer Setup]]
* [[Remote Desktop Server]]
* Sound Systems
** [[ALSA]]
** [[PipeWire]]
** [[PulseAudio]]

== Power management ==

* [[Configure action when power-button is pressed]]
* [[Suspend on LID close]]
* [[Configure Wake-on-LAN]]

== Kernel ==

* [[How to build the Alpine Linux kernel]]

== Networking ==

* [[Bluetooth]] - Instructions for installing and configuring Bluetooth
* [[Bonding]] - Bond (or aggregate) multiple ethernet interfaces
* [[Bridge]] - Configuring a network bridge
** [[Bridge wlan0 to eth0]]
* [[Configure Networking]]
* [[How to configure static routes]]
* Modem
** [[Using HSDPA modem]]
** [[Using serial modem]]
* [[mDNS]] - Howto implement multicast DNS resolution in Alpine.
* [[Multi ISP]] ''(Dual-ISP setup with load-balancing and automatic failover)''
* [[PXE boot]]
* Wi-Fi
** [[Wi-Fi|Connecting to a wireless access point]]
** [[How to setup a wireless access point]] ''(Setting up Secure Wireless AP w/ WPA encryption with bridge to wired network)''
* [[VLAN]]

== Other Architectures ==

=== ARM ===

* [[Alpine on ARM]]

==== Raspberry Pi ====

* [[Raspberry Pi Bluetooth Speaker|Raspberry Pi - Bluetooth Speaker]]
* [[Raspberry Pi|Raspberry Pi - Installation]]
* [[Linux Router with VPN on a Raspberry Pi|Raspberry Pi - Router with VPN]]
* [[Linux Router with VPN on a Raspberry Pi (IPv6)|Raspberry Pi - Router with VPN (IPv6)]]
* [[Classic install or sys mode on Raspberry Pi|Raspberry Pi - Sys mode install]]
* [[Raspberry Pi LVM on LUKS|Raspberry Pi - Sys mode install - LVM on LUKS]]
* [[RPI Video Receiver|Raspberry Pi - Video Receiver]] ''(network video decoder using Rasperry Pi and omxplayer)''
* [[Raspberry Pi 3 - Browser Client]] - kiosk or digital sign
* [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]
* [[Raspberry Pi 3 - Setting Up Bluetooth]]
* [[Raspberry Pi 4 - Persistent system acting as a NAS and Time Machine]]
* [[How to set up Alpine as a wireless router|Raspberry Pi Zero W - Wireless router]] ''(Setting up a firewalled, Wireless AP with wired network on a Pi Zero W)''
* [[RPI Video Receiver]]

=== IBM Z (IBM z Systems) ===

* [[s390x|s390x - Installation]]

=== PowerPC ===

* [[Ppc64le|Powerpc64le - Installation]]

== Post-Install ==

* [[CPU frequency scaling]]
* [[Repositories#Enabling_the_community_repository|Enable Community repository]] ''(Providing additional packages)''
* [[Enable Serial Console on Boot]]
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(Configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services|Init System - Multiple Instances of Services]]
** [[Writing Init Scripts|Init System - Writing Init Scripts]]
* [[Installing Oracle Java|Oracle Java (installation)]]
* [[IGMPproxy]]
* [[Alpine Package Keeper|Package Management (apk)]] ''(How to add/remove packages on your Alpine)''
** [[Comparison with other distros|Package Management - Comparison with other distros]]
* [[Running glibc programs]]
* [[Setting up a new user]]
* [[Upgrading Alpine]]

== Remote Administration ==

* ACF
** [[Changing passwords for ACF|ACF - changing passwords]]
** [[Generating SSL certs with ACF]] 
** [[setup-acf| ACF - setup]] ''(Configures ACF (webconfiguration/webmin) so you can manage your box through https)''
* [[Setting up a SSH server]] ''(Using ssh is a good way to administer your box remotely)''
** [[HOWTO OpenSSH 2FA with password and Google Authenticator |OpenSSH 2FA]] ''(A simple two factor setup for OpenSSH)''
* [[OpenVCP]] ''(VServer Control Panel)''
* [[PhpMyAdmin]] ''(Web-based administration tool for MYSQL)''
* [[PhpPgAdmin]] ''(Web-based administration tool for PostgreSQL)''
* [[Webmin]] ''(A web-based interface for Linux system)''

== Server ==

* [[Hosting services on Alpine]] ''(Hosting mail, webservices and other services)''
* [[Hosting Web/Email services on Alpine]]

=== DNS ===

* [[DNSCrypt-Proxy]] ''Encrypt and authenticate DNS calls from your system''
* [[Setting up nsd DNS server]]
* [[Setting up unbound DNS server]]
* [[TinyDNS Format]]

=== HTTP ===

* [[Apache]]
** [[Apache with php-fpm]]
** [[Setting Up Apache with PHP]]
** [[Apache authentication: NTLM Single Signon]]
* [[Darkhttpd]]
* [[Lighttpd]]
** [[Lighttpd Advanced security]]
** [[Setting Up Lighttpd With FastCGI]]
* [[Nginx]]
** [[Nginx as reverse proxy with acme (letsencrypt)]]
** [[Nginx with PHP]]
* Squid Proxy
** [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
** [[Setting up Explicit Squid Proxy]]
** [[Setting up Transparent Squid Proxy]] ''(Covers Squid proxy and URL Filtering system)''
** [[SqStat]] ''(Script to look at active squid users connections)''
* [[Tomcat]]

==== Hostable Content ====

* [[DokuWiki]]
* [[Drupal]] ''(Content Management System (CMS) written in PHP)''
* [[Kopano]] ''(Microsoft Outlook compatible Groupware)''
* [[Mahara]] ''(E-portfolio and social networking system)''
* [[MediaWiki]] ''(Free web-based wiki software application)''
* [[Pastebin]] ''(Pastebin software application)''
* [[WordPress]] ''(Web software to create website or blog)''

=== IRC ===

* [[NgIRCd]] ''(Server for Internet Relay Chat/IRC)''

=== Mail ===

* Exim/Dovecot
** [[Small-Time Email with Exim and Dovecot]] ''(A simple configuration for your home network.)
** [[Setting up dovecot with imap and tls]]
* [[relay email to gmail (msmtp, mailx, sendmail]]
* [[Roundcube]] ''(Webmail system)''
* [[Setting up postfix with virtual domains]]
* Server protection
** [[Setting up clamsmtp]]

=== Other Servers ===

* [[apcupsd]] ''(UPS Monitoring with apcupsd)''
* [[Chrony and GPSD | Chrony, gpsd, and a garmin LVC 18 as a Stratum 1 NTP source ]]
* [[Glpi]] ''(Manage inventory of technical resources)''
* [[How to setup a Alpine Linux mirror]]
* [[Setting up an NFS server|nfs-server]]
* [[nut-ups|NUT UPS]] ''(UPS Monitoring with Network UPS Tools)''
* [[Odoo]]
* [[Configure OpenLDAP | OpenLDAP]] ''(Installing and configuring the Alpine package for OpenLDAP)''
* [[Setting up a LLDAP server|lldap-server]] ''(Directory Server)''
* [[Setting up a samba-ad-dc|samba-ad-dc]] ''(Active Directory compatible domain controller)''
* [[Setting up a Samba server|samba-server]] ''(standard file sharing)''
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]

=== Software development ===

* [[Cgit]]
* [[OsTicket]] ''(Ticket system)''
* [[Patchwork]] ''(Patch review management system)''
* [[Redmine]] ''(Project management system)''
* [[Request Tracker]] ''(Ticket system)''
* [[Setting up trac wiki|Trac]] ''(Enhanced wiki and issue tracking system for software development projects)''

== Storage ==

* [[Setting up disks manually|Manual partitioning]]
* [[Disk Replication with DRBD|DRBD: Disk Replication]]
* [[Filesystems]]
** [[Burning ISOs]]
* [[Setting up iSCSI|iSCSI Setup]]
** [[iSCSI Raid and Clustered File Systems]]
** [[Linux iSCSI Target (TCM)|iSCSI Target (TCM)/LinuxIO (LIO)]]
** [[Linux iSCSI Target (tgt)|User space iSCSI Target (tgt)]]
* [[Setting up Logical Volumes with LVM|LVM Setup]]
** [[Setting up LVM on GPT-labeled disks|LVM on GPT-labeled disks]]
** [[Installing on GPT LVM|LVM on GPT-labeled disks (updated)]]
** [[LVM on LUKS]]
* RAID
** [[Raid Administration]]
** [[Setting up a software RAID array]]
* ZFS
** [[Root on ZFS with native encryption]]
** [[Setting up ZFS on LUKS]]
** [[Setting up ZFS with native encryption]]
** [[ZFS scrub and trim]]
* [[CEPH|CEPH]]

== Virtualization ==

* [[Docker]]
* [[Installing Alpine in a virtual machine]]
** [[Install Alpine on VMware ESXi]]
* [[KVM]] ''(Setting up Alpine as a KVM hypervisor)''
* [[LXC]] ''(Setting up a Linux container in Alpine Linux)''
* [[QEMU]]
* Xen
** [[Xen Dom0]] ''(Setting up Alpine as a dom0 for Xen hypervisor)''
** [[Xen Dom0 on USB or SD]]
** [[Create Alpine Linux PV DomU|Xen DomU (paravirtualized)]]
** [[Xen LiveCD]]
** [[Xen PCI Passthrough]]

= Tutorials =

== Miscellaneous ==

* [[TTY_Autologin|TTY Autologin]]
* [[Kexec|Faster rebooting with kexec]]
* [[Dynamic Multipoint VPN (DMVPN)]] combined with [[Small Office Services]]
* [[DIY Fully working Alpine Linux for Allwinner and Other ARM SOCs]]
* [[Fault Tolerant Routing with Alpine Linux]]
* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)''
* [[Linux iSCSI Target (TCM)]]
* [[ISP Mail Server 3.x HowTo]] ''(Postfix+PostfixAdmin+DoveCot+Roundcube+ClamAV+Spamd - A full-service ISP mail server)''
* [[Grommunio Mail Server]] ''(Mariadb+Postfix+Rspamd+Grommunio - Full-service mail server as MS exchange replacement)''
* [[Replacing non-Alpine Linux with Alpine remotely]]
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
* [[Streaming Security Camera Video with VLC]]
* [[Install Alpine on a btrfs filesystem with refind as boot manager]]
* [[Compile software from source|How to Compile a software from source in Alpine Linux]]

== Newbie corner ==

* [[How to get regular stuff working]] ''some notes on need-to-know topics''

== Servers ==

* [[Alpine production deploy]]
** [[Production Web server: Lighttpd|Production web server: Lighttpd‎‎]]
** [[MySQL|Production database: MySQL]]
** [[Production LAMP system: Lighttpd + PHP + MySQL‎‎]]
* Alpine production monitoring
** [[Cacti: traffic analysis and monitoring network]]
** [[Zabbix|Zabbix - the professional complete manager]]
* Kubernetes
** [[K8s]] Building a K8s Cluster on Alpine Linux

== Security ==

* [[Securing Alpine Linux]] How to Secure Alpine Linux using Security Technical Implementation Guides (STIGs)

How to build the Alpine Linux kernel

2024-12-11T03:11:57Z

Anthumchris: initial page

== How to build the Alpine Linux kernel ==

This [[Tutorials and Howtos|Howto]] quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]] "LTS" and "virt". Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. Alpine releases multiple [https://alpinelinux.org/downloads/ downloads] which contain kernels that vary in features and file sizes.

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T03:00:45Z

Anthumchris:

== How to build the Alpine Linux kernel ==

This [[Tutorials and Howtos|Howto]] quickly demonstrates how to build and compile the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] (e.g. LTS, virt) that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T03:00:01Z

Anthumchris:

== How to build the Alpine Linux kernel ==

This [[Tutorials and Howtos|Howto]] quickly demonstrates how to build and compile the default Alpine Linux [[Kernels|kernels]] (currently "lts" and "virt"). Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T02:59:28Z

Anthumchris:

== How to build the Alpine Linux kernel ==

This [[Tutorials and Howtos|Howto]] quickly demonstrates how to build and compile the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

How to write a HOWTO

2024-12-11T02:56:27Z

Anthumchris: remove bold from how to template

If you are reading this, it probably means you are interested in contributing a Howto or Tutorial to Alpine Linux Wiki. This is great! Just follow those simple steps and you will end up with a great howto in no time.

== Writing the HOWTO ==
Know your readers and what you are trying to tell them to do and pay proper attention to name your page. Changing the name of pages in Wiki is not trivial.
#Login to Alpine Linux Wiki.{{tip|If you have never logged in, click the Log in / create account on the top-right, and then click the Create an account link.}}
#Read the basics of wiki editing with specific reference to Alpine Wiki at [[Help:Editing]].
# If you are new to Wiki editing, use a subpage of your User namespace or use [[Sandbox]] to create a Temporary page first.
#Paste the [[#Basic_HOWTO_Template|Basic HOWTO Template]] into your new Temporary page.
#Follow the instructions in the template.
#Try as much as possible to refer existing wiki content for standard tasks like [[installation]], [[Setting_up_disks_manually#Manual partitioning|partitioning]], [[Setting_up_disks_manually#Formatting_partitions|formatting]], [[Setting_up_a_new_user#Creating_a_new_user|user management]], [[Repositories#Managing_repositories|managing repositories]] etc.. instead of repeating the same in your page. This avoids confusing users and prevents content fragmentation.
# Finally create the properly named HOWTO page as explained in [[Help:Editing]] and paste your content from the temporary page.

== Learn to format Wiki text ==
*Refer [[Help:Editing]] to understand the Text Formatting Rules
*By clicking the Edit page button on Alpine Linux Wiki articles to read the source. Do not accidentally modify them.
*By experimenting in [[Sandbox]]

== Basic HOWTO Template ==

A WikiText skeleton of a basic HOWTO:
== How To Do Something ==

Summarize your article here so readers can decide
quickly whether to read it.

== Before You Start Title ==
Your readers might need to get ready before they can do the work.
If so explain those prerequisites first. This section might alternatively
contain background information readers need to know before they can make
sense of your example or carry out your instructions.

== Doing Something Title ==
Write the steps of how to do something in this section.
If possible, show an example first, then tell your readers the steps.
Break this procedure into separate procedures to avoid more than
about 7-9 steps per procedure.

INSERT GREAT EXAMPLE HERE

#Answer the following three questions, at least in your head.
##What do I explain how to do?
##How do I do that?
##What do HOWTO readers already know about doing that?
#Write up a good example. This ensures you can do it.
#Write up the steps to do it.
#Write the background info/prerequisites readers need.
#Write the summary.
#Clean up your work.
# Add relevant [[Special:Categories|category]] to your page, as every page should be assigned at least one Category.
#Revise, revise, revise.

== See Also ==
If you ought to point your readers to related information
they no doubt need but that does not fit in your HOWTO, add links here.

== See Also ==
*[[Help:Editing]]
*[[Project:Wiki etiquette|Wiki etiquette]]

[[Category:Wiki]]

How to write a HOWTO

2024-12-11T02:55:58Z

Anthumchris: add link to howto template

If you are reading this, it probably means you are interested in contributing a Howto or Tutorial to Alpine Linux Wiki. This is great! Just follow those simple steps and you will end up with a great howto in no time.

== Writing the HOWTO ==
Know your readers and what you are trying to tell them to do and pay proper attention to name your page. Changing the name of pages in Wiki is not trivial.
#Login to Alpine Linux Wiki.{{tip|If you have never logged in, click the Log in / create account on the top-right, and then click the Create an account link.}}
#Read the basics of wiki editing with specific reference to Alpine Wiki at [[Help:Editing]].
# If you are new to Wiki editing, use a subpage of your User namespace or use [[Sandbox]] to create a Temporary page first.
#Paste the [[#Basic_HOWTO_Template|'''Basic HOWTO Template''']] into your new Temporary page.
#Follow the instructions in the template.
#Try as much as possible to refer existing wiki content for standard tasks like [[installation]], [[Setting_up_disks_manually#Manual partitioning|partitioning]], [[Setting_up_disks_manually#Formatting_partitions|formatting]], [[Setting_up_a_new_user#Creating_a_new_user|user management]], [[Repositories#Managing_repositories|managing repositories]] etc.. instead of repeating the same in your page. This avoids confusing users and prevents content fragmentation.
# Finally create the properly named HOWTO page as explained in [[Help:Editing]] and paste your content from the temporary page.

== Learn to format Wiki text ==
*Refer [[Help:Editing]] to understand the Text Formatting Rules
*By clicking the Edit page button on Alpine Linux Wiki articles to read the source. Do not accidentally modify them.
*By experimenting in [[Sandbox]]

== Basic HOWTO Template ==

A WikiText skeleton of a basic HOWTO:
== How To Do Something ==

Summarize your article here so readers can decide
quickly whether to read it.

== Before You Start Title ==
Your readers might need to get ready before they can do the work.
If so explain those prerequisites first. This section might alternatively
contain background information readers need to know before they can make
sense of your example or carry out your instructions.

== Doing Something Title ==
Write the steps of how to do something in this section.
If possible, show an example first, then tell your readers the steps.
Break this procedure into separate procedures to avoid more than
about 7-9 steps per procedure.

INSERT GREAT EXAMPLE HERE

#Answer the following three questions, at least in your head.
##What do I explain how to do?
##How do I do that?
##What do HOWTO readers already know about doing that?
#Write up a good example. This ensures you can do it.
#Write up the steps to do it.
#Write the background info/prerequisites readers need.
#Write the summary.
#Clean up your work.
# Add relevant [[Special:Categories|category]] to your page, as every page should be assigned at least one Category.
#Revise, revise, revise.

== See Also ==
If you ought to point your readers to related information
they no doubt need but that does not fit in your HOWTO, add links here.

== See Also ==
*[[Help:Editing]]
*[[Project:Wiki etiquette|Wiki etiquette]]

[[Category:Wiki]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T02:50:39Z

Anthumchris:

== How to build the Alpine Linux kernel ==

This [[Tutorials and Howtos|Howto]] quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T02:48:53Z

Anthumchris:

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T02:47:59Z

Anthumchris:

[[User:Anthumchris|anthumchris]] ([[User talk:Anthumchris|talk]]) 02:47, 11 December 2024 (UTC)

== How to build the Alpine Linux kernel ==
This [[Tutorials and Howtos|Howto]] quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-11T02:45:36Z

Anthumchris: add tilde signature

== How to build the Alpine Linux kernel ==
This [[Tutorials and Howtos|Howto]] quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

[[User:Anthumchris|anthumchris]] ([[User talk:Anthumchris|talk]]) 02:45, 11 December 2024 (UTC)

User talk:Anthumchris

2024-12-11T02:41:25Z

Anthumchris: Created page with "Please add your thoughts or questions below, starting new topics with wikimarkup: <code>== Heading ==</code> == Example =="

Please add your thoughts or questions below, starting new topics with wikimarkup: <code>== Heading ==</code>

== Example ==

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:57:12Z

Anthumchris:

== How to build the Alpine Linux kernel ==
This [[Tutorials and Howtos|Howto]] quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:50:13Z

Anthumchris:

== How to build the Alpine Linux kernel ==
This [[Tutorials and Howtos|Howto]] quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] privileges (i.e. sudo, wheel group) are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:44:31Z

Anthumchris:

== How to build the Alpine Linux kernel ==
This [[Tutorials and Howtos|Howto]] quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (i.e. sudo, wheel group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:43:20Z

Anthumchris:

== How to build the Alpine Linux kernel ==
This HOWTO quickly demonstrates building/compiling the default Alpine Linux [[Kernels|kernels]]. Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (i.e. sudo, wheel group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:36:47Z

Anthumchris:

== How to build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (i.e. sudo, wheel group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:24:24Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (i.e. sudo, wheel group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
doas apk add FILENAME
doas reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:19:37Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (i.e. sudo, wheel group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:13:45Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (i.e. sudo, wheel group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example how to revert to the previous "alpine-lts" package after removing the newly-installed package "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:06:23Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example how to revert to the previous "alpine-lts" package after removing the newly-installed package "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel|Custom Kernel (2018-present)]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:05:11Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example how to revert to the previous "alpine-lts" package after removing the newly-installed package "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:04:17Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example how to revert to the previous '''alpine-lts''' package after removing the newly-installed package (both are named "alpine-lts" yet refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:03:50Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example how to revert to the previous '''alpine-lts''' package after removing the newly-installed package (both have the same name alpine-lts but refer to different versions/locations):
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T22:00:04Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous '''alpine-lts''' kernel we identified earlier:
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T21:59:10Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-build kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous '''alpine-lts''' kernel we identified earlier:
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T21:52:42Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel modules/features. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Identify backup ===

Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that '''linux-lts''' is the current package that we would revert to as a backup.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package2.png|600px]]

=== Install ===
Find the newly-build kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:

<pre>
apk add FILENAME
reboot
</pre>

[[File:Alpine-kernel-install.png|600px]]

After rebooting, verify the newly-installed kernel version:
<pre>
echo "kernel: $(uname -r)"
</pre>

[[File:Alpine-kernel-new.png|320px]]

=== Revert ===
If needed, revert to the previous '''alpine-lts''' kernel we identified earlier:
<pre>
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
reboot
</pre>

[[File:Alpine-kernel-revert.png|465px]]

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

File:Alpine-kernel-revert.png

2024-12-03T21:49:59Z

Anthumchris:

revert to previous kernel

File:Alpine-kernel-new.png

2024-12-03T20:58:50Z

Anthumchris:

new kernel version

File:Alpine-kernel-install.png

2024-12-03T20:53:12Z

Anthumchris:

install new kernel

File:Alpine-kernel-package2.png

2024-12-03T20:22:52Z

Anthumchris:

kernel package name

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T19:51:58Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure keys are readable

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===

Identify the package name of your current kernel. This example shows that <code>linux-lts</code> is the current package that we will later revert to.

<pre>
echo "kernel: $(uname -r)"
apk list --installed linux-*
</pre>

[[File:Alpine-kernel-package.png|600px]]

==== Install new kernel ====
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

File:Alpine-kernel-package.png

2024-12-03T19:44:43Z

Anthumchris:

output showing kernel package name

File:Alpine-kernel-lts.png

2024-12-03T19:36:16Z

Anthumchris:

Command output of linux kernel package name

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T19:13:39Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T19:12:35Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. For example, Alpine releases multiple [[Kernels|kernels]] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T19:12:02Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. For example, Alpine releases multiple [[Kernels]kernels] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T19:11:10Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux may be needed if you are experimenting with adding/removing kernel features and modules. For example, Alpine releases multiple [[Kernels]kernels] that vary in features and file sizes. Alpine kernels extend the standard [https://www.kernel.org/linux.html Linux kernel] and build within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with [https://pkgs.alpinelinux.org/package/edge/main/x86_64/doas doas] (<code>wheel</code> group) privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T18:32:26Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. The Alpine kernel extends the standard [https://www.kernel.org/linux.html Linux kernel] and builds within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user with wheel/doas privileges are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
## Run as root

apk add alpine-sdk
addgroup USERNAME abuild # your non-root user
</pre>

<pre>
## Run as non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T18:29:10Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. The Alpine kernel extends the standard [https://www.kernel.org/linux.html Linux kernel] and builds within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
## Run as root

apk add alpine-sdk
addgroup USERNAME abuild # your non-root user
</pre>

<pre>
## Run as non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T18:26:20Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. The Alpine kernel extends the standard [https://www.kernel.org/linux.html Linux kernel] and builds within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code>, [https://gitlab.alpinelinux.org/alpine/aports aports], and [https://pkgs.alpinelinux.org/package/edge/main/x86_64/alpine-sdk alpine-sdk].

== Before you start ==
A running instance of Alpine Linux and a non-root user are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
<pre>
## Run as root

apk add alpine-sdk # install required packages
addgroup USERNAME abuild # your non-root user
</pre>

<pre>
## Run as non-root user

git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T18:22:20Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. The Alpine kernel extends the standard [https://www.kernel.org/linux.html Linux kernel] and builds within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code> and [https://gitlab.alpinelinux.org/alpine/aports aports].

== Before you start ==
A running instance of Alpine Linux and a non-root user are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
Run as root:
<pre>
apk add alpine-sdk # install required packages
addgroup USERNAME abuild # your non-root user
</pre>

Run as non-root user:
<pre>
git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append

cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T18:21:49Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. The Alpine kernel extends the standard [https://www.kernel.org/linux.html Linux kernel] and builds within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code> and [https://gitlab.alpinelinux.org/alpine/aports aports].

== Before you start ==
A running instance of Alpine Linux and a non-root user are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
Run as root:
<pre>
apk add alpine-sdk # install required packages
addgroup USERNAME abuild # your non-root user
</pre>

Run as non-root user:
<pre>
git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append
</pre>

<pre>
cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T18:19:59Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. The Alpine kernel extends the standard [https://www.kernel.org/linux.html Linux kernel] and builds within a few minutes to a few hours (depending on the speed of your system) using <code>[[abuild]]</code> and [https://gitlab.alpinelinux.org/alpine/aports aports].

== Before you start ==
A running instance of Alpine Linux and a non-root user are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
Run as root:
<pre>
apk add alpine-sdk # install required packages
addgroup USERNAME abuild # your non-root user
</pre>

Run as non-root user:
<pre>
git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append

# build/install the kernel
cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]

User:Anthumchris:How to build the Alpine Linux kernel

2024-12-03T18:12:31Z

Anthumchris:

== How build the Alpine Linux kernel ==
A customized build of the Alpine Linux kernel may be needed if you are experimenting with adding/removing kernel features and modules. The Alpine kernel extends the standard [https://www.kernel.org/linux.html Linux kernel] and builds within a few minutes to a few hours (depending on the speed of your system). The kernel is built using <code>[[abuild]]</code> and [https://gitlab.alpinelinux.org/alpine/aports aports].

== Before you start ==
A running instance of Alpine Linux and a non-root user are required to use <code>[[abuild]]</code>.

== Build & install the kernel ==

=== Build ===
Run as root:
<pre>
apk add alpine-sdk # install required packages
addgroup USERNAME abuild # your non-root user
</pre>

Run as non-root user:
<pre>
git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append

# build/install the kernel
cd aports/main/linux-lts/
time abuild -crK
</pre>

=== Install ===
<pre>
apk add /home/USERNAME/packages/.....................................
</pre>

== See Also ==

* [[Kernels]]
* [[Custom Kernel]]