User:Halscode/Atomic Alpine - Revision history

Halscode at 18:35, 18 March 2025

2025-03-18T18:35:26Z

← Older revision		Revision as of 18:35, 18 March 2025
Line 2:		Line 2:
	<br/>Specifically, this is a draft I (Halscode) am working on as I build my own system based on the linked guide. See [[Talk:Immutable root with atomic upgrades]] to see the changes I made to get the guide to work.}}		<br/>Specifically, this is a draft I (Halscode) am working on as I build my own system based on the linked guide. See [[Talk:Immutable root with atomic upgrades]] to see the changes I made to get the guide to work.}}
	{{Todo\|Add the/an everywhere, use [[Template:Cat]] and [[Template:Cmd]] instead of pre tags where appropriate}}		{{Todo\|Add the/an everywhere, use [[Template:Cat]] and [[Template:Cmd]] instead of pre tags where appropriate}}
			{{Todo\|To install Nix on this system, you'll need to use the installation script, then create a dedicated user with its own home somewhere, and set a custom nix-daemon service to use that (also TODO: provide my script)}}

	=== What? ===		=== What? ===

Halscode at 07:14, 2 October 2024

2024-10-02T07:14:26Z

← Older revision		Revision as of 07:14, 2 October 2024
Line 420:		Line 420:
	# vi /usr/sbin/sysmut</pre>		# vi /usr/sbin/sysmut</pre>

	Example script to mutate ~~the~~ the system:		Example script to mutate the system:

	<pre>#!/bin/execlineb -W		<pre>#!/bin/execlineb -W
Line 441:		Line 441:
	if { mkdir -p ${mnt}/snapshots/${newsnap} }		if { mkdir -p ${mnt}/snapshots/${newsnap} }
	if { btrfs subvolume snapshot ${mnt}/current/${source}/@ ${mnt}/snapshots/${newsnap}/@ }		if { btrfs subvolume snapshot ${mnt}/current/${source}/@ ${mnt}/snapshots/${newsnap}/@ }
			if { btrfs subvolume snapshot ${mnt}/current/${source}/@etc ${mnt}/snapshots/${newsnap}/@etc }
	if {		if {
	redirfd -w 1 ${mnt}/snapshots/${newsnap}/@/etc/fstab		redirfd -w 1 ${mnt}/snapshots/${newsnap}/@etc/fstab
	sed s#CURRENT_SNAPSHOTS_PATH#/snapshots/${newsnap}#g ${mnt}/fstab		sed s#CURRENT_SNAPSHOTS_PATH#/snapshots/${newsnap}#g ${mnt}/fstab
	}		}
Line 449:		Line 450:
	if { mount -o bind,ro /dev ${mnt}/snapshots/${newsnap}/@/dev }		if { mount -o bind,ro /dev ${mnt}/snapshots/${newsnap}/@/dev }
	foreground {		foreground {
	foreground { mount -o bind,ro /etc/resolv.conf ${mnt}/snapshots/${newsnap}/@/etc/resolv.conf }		foreground { mount -o bind,ro /etc/resolv.conf ${mnt}/snapshots/${newsnap}/@etc/resolv.conf }
	foreground {		foreground {
	chroot ${mnt}/snapshots/${newsnap}/@		chroot ${mnt}/snapshots/${newsnap}/@
	foreground { mount -a }		foreground { mount -a }
			foreground { echo "=== Entering sysmut (make your changes now)" }
	foreground { sh }		foreground { sh }
	importas apply ?		importas apply ?
Line 459:		Line 461:
	}		}
	importas apply ?		importas apply ?
	foreground { redirfd -w 2 /dev/null umount ${mnt}/snapshots/${newsnap}/@/etc/resolv.conf }		foreground { redirfd -w 2 /dev/null umount ${mnt}/snapshots/${newsnap}/@etc/resolv.conf }
	ifelse { exit ${apply} } {		ifelse { exit ${apply} } {
	if { btrfs property set -ts ${mnt}/snapshots/${newsnap}/@ ro true }		if { btrfs property set -ts ${mnt}/snapshots/${newsnap}/@ ro true }
Line 471:		Line 473:
	if { ln -sfn ./links/${newlink} ${mnt}/next/current }		if { ln -sfn ./links/${newlink} ${mnt}/next/current }
	if { mv ${mnt}/next/current ${mnt}/ }		if { mv ${mnt}/next/current ${mnt}/ }
	echo "Changes applied"		echo "=== Changes applied"
	}		}
	echo "Changes discarded"		# Remove failed snapshot
			btrfs subvolume delete ${mnt}/snapshots/${newsnap}/@
			btrfs subvolume delete ${mnt}/snapshots/${newsnap}/@etc
			rm -r ${mnt}/snapshots/${newsnap}
			echo "=== Changes discarded"
	}		}
	foreground { redirfd -w 2 /dev/null umount ${mnt}/snapshots/${newsnap}/@/proc }		foreground { redirfd -w 2 /dev/null umount ${mnt}/snapshots/${newsnap}/@/proc }

Halscode at 06:57, 2 October 2024

2024-10-02T06:57:48Z

← Older revision		Revision as of 06:57, 2 October 2024
Line 297:		Line 297:

	All you have to do now is reboot, remove your media, and you should be done:		All you have to do now is reboot, remove your media, and you should be done:
	{{Cmd\|# umount /mnt		{{Cmd\|# umount /mnt<br># reboot}}
	# reboot}}

	==== Using the <code>overlaytmpfs</code> option ====		==== Using the <code>overlaytmpfs</code> option ====

Halscode at 06:56, 2 October 2024

2024-10-02T06:56:46Z

Show changes

Halscode at 05:40, 2 October 2024

2024-10-02T05:40:46Z

← Older revision		Revision as of 05:40, 2 October 2024
Line 79:		Line 79:
	<pre># btrfs subvolume create /mnt/commons/@var		<pre># btrfs subvolume create /mnt/commons/@var
	# btrfs subvolume create /mnt/commons/@home</pre><br><br>		# btrfs subvolume create /mnt/commons/@home</pre><br><br>

			Let's go ahead and add a couple needed folders for <code>/var</code> before they become an issue:
			<pre># mkdir /mnt/commons/@var/empty
			# mkdir /mnt/commons/@var/tmp # this will be mounted over</pre><br><br>

	Next, the most important directories:		Next, the most important directories:
Line 153:		Line 157:
	Considering that installation is done from Alpine system, we only need following parts of [[Alpine_Linux_in_a_chroot\|the process]]:		Considering that installation is done from Alpine system, we only need following parts of [[Alpine_Linux_in_a_chroot\|the process]]:
	<pre># apk -X https://dl-cdn.alpinelinux.org/alpine/latest-stable/main -U --allow-untrusted -p /mnt/snapshots/20210411212549sdBXyLxg/@ --initdb add alpine-base</pre>		<pre># apk -X https://dl-cdn.alpinelinux.org/alpine/latest-stable/main -U --allow-untrusted -p /mnt/snapshots/20210411212549sdBXyLxg/@ --initdb add alpine-base</pre>

			Copy the contents of <code>/etc</code> to the etc subvolume:
			<pre># cp -r /mnt/snapshots/20210411212549sdBXyLxg/@/etc/* /mnt/snapshots/20210411212549sdBXyLxg/@etc</pre>

	Now we can setup basic chroot to complete the installation process:		Now we can setup basic chroot to complete the installation process:
	<pre># export SNP="/mnt/snapshots/20210411212549sdBXyLxg/@"		<pre># export SNP="/mnt/snapshots/20210411212549sdBXyLxg/@"
Line 162:		Line 170:

	# sed "s#CURRENT_SNAPSHOTS_PATH#/snapshots/20210411212549sdBXyLxg#g" /mnt/fstab > "$SNP/etc/fstab"		# sed "s#CURRENT_SNAPSHOTS_PATH#/snapshots/20210411212549sdBXyLxg#g" /mnt/fstab > "$SNP/etc/fstab"
	~~# # tip: use tab to fill in the correct snapshot; this one is just an example~~

	# cp -L /etc/resolv.conf "$SNP/etc/" # so DNS still works		# cp -L /etc/resolv.conf "$SNP/etc/" # so DNS still works
Line 175:		Line 182:

	Now it's time for the firmware, kernel, and btrfs packages:		Now it's time for the firmware, kernel, and btrfs packages:
	<pre># apk add -U linux-firmware linux-lts btrfs-progs</pre>		<pre># setup-apkrepos
	You may want to change <code>linux-firmware</code> to a custom set of firmware packages suitable for your system, for example, <code>linux-firmware-amd linux-firmware-amd-ucode linux-firmware-amdgpu linux-firmware-ath10k linux-firmware-qca</code> for a typical AMD laptop.~~<br>~~		# apk add -U linux-firmware linux-lts btrfs-progs</pre>
			{{tip\|You may want to change <code>linux-firmware</code> to a custom set of firmware packages suitable for your system, for example, <code>linux-firmware-amd linux-firmware-amd-ucode linux-firmware-amdgpu linux-firmware-ath10k linux-firmware-qca</code> for a typical AMD laptop.}}

	It's also important to add the <code>btrfs</code> feature to <code>mkinitfs.conf</code> and run <code>mkinitfs</code> manually:		It's also important to add the <code>btrfs</code> feature to <code>mkinitfs.conf</code> and run <code>mkinitfs</code> manually:
	<pre># vi /etc/mkinitfs/mkinitfs.conf		<pre># vi /etc/mkinitfs/mkinitfs.conf
	# mkinitfs</pre>		# mkinitfs "$(ls /lib/modules)"</pre>
	These steps prepare the kernel and generate the <code>initramfs</code>, which will be used later to boot from our first snapshot.		These steps prepare the kernel and generate the <code>initramfs</code>, which will be used later to boot from our first snapshot.

Line 186:		Line 195:
	* run [[setup-desktop]]		* run [[setup-desktop]]
	* install NetworkManager if you installed GNOME with setup-desktop (and if you need WiFi, {{pkg\|networkmanager-wifi}} as well)		* install NetworkManager if you installed GNOME with setup-desktop (and if you need WiFi, {{pkg\|networkmanager-wifi}} as well)
	* ~~Add~~ [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> the tools you'll use to upgrade the system, add new software if you need, and clean up old snapshots.		* add [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> the tools you'll use to upgrade the system, add new software if you need, and clean up old snapshots.
	* '''Make sure you install {{pkg\|execline}}''' so you can run sysmut and syscln!		* '''Make sure you install {{pkg\|execline}}''' so you can run sysmut and syscln!
			* install {{pkg\|wpa_supplicant}} or {{pkg\|iwd}} to use WiFi

			{{Warning\|In case your PC only has wireless connection, '''make sure you install wireless software''', like <code>iwd</code> or <code>wpa_supplicant</code>, so you will not end up severed from network on your first boot. '''The network connection from the installer does not carry over onto the installed system!''' So if you need WiFi and you don't do this, you may not be able to get it back!}}

			You should add the [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> scripts, which you'll use to upgrade the system, add new software if you need, and clean up old snapshots.

	{{Warning\|~~In case your PC only has wireless connection~~ you ~~should also install any suitable networking software, like <code>iwd</code> or <code>wpa_supplicant</code>~~, so you ~~will not end up severed from network on your first boot.~~ '~~''The network connection from~~ the ~~installer does not carry over onto the installed~~ system.~~'''~~}}		{{Warning\|If you do not add sysmut, you'll have to do its steps manually in the future to update your system. Please add it, or find or create a suitable alternative that is tailored to this configuration.}}

	<!--{{Note\|Due to root being immutable during operation, it's recommended to install the <code>openresolv</code> package to support changing the network connection. In this case, <code>/etc/resolvconf.conf</code> should have <code>resolv_conf{{=}}/tmp/resolv.conf</code>, <code>/etc/resolv.conf</code> should be moved to <code>/tmp/resolv.conf</code>, and a link to the new resolv.conf location should be created: <code>ln -sfn /tmp/resolv.conf /etc/resolv.conf</code>.		<!--{{Note\|Due to root being immutable during operation, it's recommended to install the <code>openresolv</code> package to support changing the network connection. In this case, <code>/etc/resolvconf.conf</code> should have <code>resolv_conf{{=}}/tmp/resolv.conf</code>, <code>/etc/resolv.conf</code> should be moved to <code>/tmp/resolv.conf</code>, and a link to the new resolv.conf location should be created: <code>ln -sfn /tmp/resolv.conf /etc/resolv.conf</code>.
Line 219:		Line 233:
	<pre># umount -a		<pre># umount -a
	# exit</pre>		# exit</pre>

	~~Copy the contents of <code>/etc</code> to the etc subvolume:~~
	~~<pre># cp -r /mnt/snapshots/20210411212549sdBXyLxg/@/etc/* /mnt/snapshots/20210411212549sdBXyLxg/@etc</pre>~~

	Finish editing the snapshot by setting the <code>ro</code> flag and unmounting the root volume:		Finish editing the snapshot by setting the <code>ro</code> flag and unmounting the root volume:

Halscode at 05:05, 2 October 2024

2024-10-02T05:05:43Z

← Older revision		Revision as of 05:05, 2 October 2024
Line 90:		Line 90:
	<pre># NEWSNAPSHOTS="$(date -u +"%Y%m%d%H%M%S")$(cat /dev/urandom \| tr -dc 'a-zA-Z' \| fold -w 8 \| head -n 1)"		<pre># NEWSNAPSHOTS="$(date -u +"%Y%m%d%H%M%S")$(cat /dev/urandom \| tr -dc 'a-zA-Z' \| fold -w 8 \| head -n 1)"
	# mkdir "/mnt/snapshots/$NEWSNAPSHOTS"		# mkdir "/mnt/snapshots/$NEWSNAPSHOTS"
	# btrfs subvolume create /mnt/snapshots/$NEWSNAPSHOTS/@</pre>		# btrfs subvolume create /mnt/snapshots/$NEWSNAPSHOTS/@
			# btrfs subvolume create /mnt/snapshots/$NEWSNAPSHOTS/@etc</pre>

	Populate <code>links</code>:		Populate <code>links</code>:
Line 108:		Line 109:
	The answer is common <code>fstab</code> in the [[BTRFS\|btrfs]] root.		The answer is common <code>fstab</code> in the [[BTRFS\|btrfs]] root.

	Get UUIDs of the partitions first:		Get UUIDs of the partitions first (this puts them in the file for easy access):
	<pre># blkid > /mnt/fstab</pre>		<pre># blkid > /mnt/fstab</pre>

			{{tip\|You may want to install {{pkg\|vim}} or {{pkg\|nano}} here to make editing files easier.}}

	Now edit fstab accordingly:		Now edit fstab accordingly:
	<pre># vi /mnt/fstab</pre>		<pre># vi /mnt/fstab</pre>
	~~Example~~:		Replace the UUIDs below, but it should look like:
	<pre>UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 / btrfs subvol=CURRENT_SNAPSHOTS_PATH/@,ro,noatime 0 0		<pre>UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 / btrfs subvol=CURRENT_SNAPSHOTS_PATH/@,ro,noatime 0 0
	UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 /etc btrfs subvol=CURRENT_SNAPSHOTS_PATH/@etc,rw,noatime 0 0		UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 /etc btrfs subvol=CURRENT_SNAPSHOTS_PATH/@etc,rw,noatime 0 0
Line 123:		Line 126:
	UUID=f0239163-9d46-47c1-67a4-3ee1d63d0676 swap swap rw,noatime,discard 0 0</pre>		UUID=f0239163-9d46-47c1-67a4-3ee1d63d0676 swap swap rw,noatime,discard 0 0</pre>

	<code>CURRENT_SNAPSHOTS_PATH</code> will be replaced by ~~scripts~~ with, for example, <code>/snapshots/20210411212549sdBXyLxg</code>, and the result will be piped into <code>/etc/fstab</code> of a created ~~<code>@</code>~~ snapshot ~~during new generation preparations~~.		<code>CURRENT_SNAPSHOTS_PATH</code> will be replaced by sysmut with, for example, <code>/snapshots/20210411212549sdBXyLxg</code>, and the result will be piped into <code>/etc/fstab</code> of a created snapshot while applying it.

	~~Root~~ [[BTRFS\|btrfs]] volume structure mounted on <code>/mnt</code>:		{{tip\|If you want to persistently edit fstab later, remount the full root partition (i.e. <code>mount -t btrfs /dev/sda2 /mnt</code>) and edit <code>/mnt/fstab</code>. You do not have to do this within sysmut, but it is recommended to do it that way, since your changes will then be applied for the next boot when you exit.}}

			Here's what the root [[BTRFS\|btrfs]] volume structure mounted on <code>/mnt</code> should look like now:
	<pre>\|--mnt		<pre>\|--mnt
	\| \|--commons		\| \|--commons
Line 141:		Line 146:
	\| \|--snapshots		\| \|--snapshots
	\| \| \|--20210411212549sdBXyLxg		\| \| \|--20210411212549sdBXyLxg
	\| \| \| \|--@</pre>		\| \| \| \|--@
			\| \| \| \|--@etc</pre>

	= Base system install =		= Base system install =
Line 164:		Line 170:

	As soon as you're in chroot, define repositories:		As soon as you're in chroot, define repositories:
	<pre># echo "https://dl-cdn.alpinelinux.org/alpine/latest-stable/main" > /etc/apk/repositories</pre>		<pre># echo "https://dl-cdn.alpinelinux.org/alpine/latest-stable/main" >> /etc/apk/repositories</pre>

	This example shows only <code>main</code>, but you should also add <code>testing</code> and <code>community</code> if you need any packages in those.		This example shows only <code>main</code>, but you should also add <code>testing</code> and <code>community</code> if you need any packages in those. You can do this by repeating that command, but with <code>testing</code> or <code>community</code> instead of <code>main</code> accordingly.

	Now it's time for the firmware, kernel, and btrfs packages:		Now it's time for the firmware, kernel, and btrfs packages:
Line 177:		Line 183:

	This would be a good time to:		This would be a good time to:
			* install and set up [[doas]]
	* run [[setup-desktop]]		* run [[setup-desktop]]
	* install NetworkManager if you installed GNOME with setup-desktop (and if you need WiFi, {{pkg\|networkmanager-wifi}} as well)		* install NetworkManager if you installed GNOME with setup-desktop (and if you need WiFi, {{pkg\|networkmanager-wifi}} as well)
	* Add [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> the tools you'll use to upgrade the system, add new software if you need, and clean up old snapshots.		* Add [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> the tools you'll use to upgrade the system, add new software if you need, and clean up old snapshots.
	* Make sure you install {{pkg\|execline}} so you can run sysmut and syscln!		* '''Make sure you install {{pkg\|execline}}''' so you can run sysmut and syscln!

	{{Warning\|In case your PC only has wireless connection you should also install any suitable networking software, like <code>iwd</code> ~~in this example~~, so you will not end up severed from network on your first boot. The network connection from the installer does not carry over onto the installed system.}}		{{Warning\|In case your PC only has wireless connection you should also install any suitable networking software, like <code>iwd</code> or <code>wpa_supplicant</code>, so you will not end up severed from network on your first boot. '''The network connection from the installer does not carry over onto the installed system.'''}}

	<!--{{Note\|Due to root being immutable during operation, it's recommended to install the <code>openresolv</code> package to support changing the network connection. In this case, <code>/etc/resolvconf.conf</code> should have <code>resolv_conf{{=}}/tmp/resolv.conf</code>, <code>/etc/resolv.conf</code> should be moved to <code>/tmp/resolv.conf</code>, and a link to the new resolv.conf location should be created: <code>ln -sfn /tmp/resolv.conf /etc/resolv.conf</code>.		<!--{{Note\|Due to root being immutable during operation, it's recommended to install the <code>openresolv</code> package to support changing the network connection. In this case, <code>/etc/resolvconf.conf</code> should have <code>resolv_conf{{=}}/tmp/resolv.conf</code>, <code>/etc/resolv.conf</code> should be moved to <code>/tmp/resolv.conf</code>, and a link to the new resolv.conf location should be created: <code>ln -sfn /tmp/resolv.conf /etc/resolv.conf</code>.
Line 188:		Line 195:
	}}-->		}}-->

	~~Now, configure~~ the system~~, start~~ with setting a password for the root:		= Configure the system =
			Start with setting a password for the root:
	<pre># passwd root</pre>		<pre># passwd root</pre>

Line 211:		Line 219:
	<pre># umount -a		<pre># umount -a
	# exit</pre>		# exit</pre>

			Copy the contents of <code>/etc</code> to the etc subvolume:
			<pre># cp -r /mnt/snapshots/20210411212549sdBXyLxg/@/etc/* /mnt/snapshots/20210411212549sdBXyLxg/@etc</pre>

	Finish editing the snapshot by setting the <code>ro</code> flag and unmounting the root volume:		Finish editing the snapshot by setting the <code>ro</code> flag and unmounting the root volume:

Halscode at 04:32, 2 October 2024

2024-10-02T04:32:54Z

← Older revision		Revision as of 04:32, 2 October 2024
Line 16:		Line 16:

	If you cannot connect to the Internet via Ethernet, you will need to install and set up [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] to connect to the Internet. Follow the linked instructions until the header "Automatic Configuration on System Boot"; since the installer system is not permanent, that step is not necessary. The standard image does not include iwd, so you must use wpa_supplicant for the setup process.		If you cannot connect to the Internet via Ethernet, you will need to install and set up [[Wi-Fi#wpa_supplicant\|wpa_supplicant]] to connect to the Internet. Follow the linked instructions until the header "Automatic Configuration on System Boot"; since the installer system is not permanent, that step is not necessary. The standard image does not include iwd, so you must use wpa_supplicant for the setup process.

			The installer will need several packages that are not available on the base images. Set up your network and repository:
			<pre># setup-interfaces # if you've already set up wifi, you can skip this
			# setup-apkrepos</pre>

	= Partitioning disks =		= Partitioning disks =
Line 25:		Line 29:
	<pre># apk add gptfdisk		<pre># apk add gptfdisk
	# gdisk /dev/sda		# gdisk /dev/sda
	> o ↵		> o ↵ # creates a new GPT partition table
	> y ↵		> y ↵ # confirm
	> w ↵		> w ↵ # commits this new table to disk
	> y ↵		> y ↵ # confirm
	</pre>		</pre>
	~~<!-- TODO: explain what these commands mean -->~~

	Now we can define the partitions:		Now we can define the partitions:
Line 50:		Line 53:
	{{tip\|If you want to put the swap partition at the end, set its start sector to, for example, <code>-16G</code>. This gives it 16 GiB of space to work with, so the size should remain default (which will be 16GiB). The swap size should be between as much RAM as you have and double that.		{{tip\|If you want to put the swap partition at the end, set its start sector to, for example, <code>-16G</code>. This gives it 16 GiB of space to work with, so the size should remain default (which will be 16GiB). The swap size should be between as much RAM as you have and double that.
	<br/>If you don't use swap, you may encounter performance issues and you will not be able to suspend to disk.}}		<br/>If you don't use swap, you may encounter performance issues and you will not be able to suspend to disk.}}

			You will likely need to manually re-read the partition table to get the block devices needed for the next step. To do this:
			<pre># partprobe /dev/sda
			# mdev -s</pre>

	Next step is creating filesystems:		Next step is creating filesystems:
	<pre># mkfs.vfat -F32 /dev/sda1 # EFI		<pre># apk add btrfs-progs # includes mkfs.btrfs
			# mkfs.vfat -F32 /dev/sda1 # EFI
	# mkfs.btrfs /dev/sda2 # ROOT		# mkfs.btrfs /dev/sda2 # ROOT
	# mkswap /dev/sda3 # SWAP</pre>		# mkswap /dev/sda3 # SWAP</pre>

Halscode at 03:53, 2 October 2024

2024-10-02T03:53:55Z

← Older revision		Revision as of 03:53, 2 October 2024
Line 45:		Line 45:
	3 32.0 GiB Linux swap SWAP</pre>		3 32.0 GiB Linux swap SWAP</pre>
	<code>ROOT</code> partition name will later be used in rEFInd configuration to identify boot volume.		<code>ROOT</code> partition name will later be used in rEFInd configuration to identify boot volume.

			{{note\|We recommend giving your root partition at least 20 GiB of space.}}

	{{tip\|If you want to put the swap partition at the end, set its start sector to, for example, <code>-16G</code>. This gives it 16 GiB of space to work with, so the size should remain default (which will be 16GiB). The swap size should be between as much RAM as you have and double that.		{{tip\|If you want to put the swap partition at the end, set its start sector to, for example, <code>-16G</code>. This gives it 16 GiB of space to work with, so the size should remain default (which will be 16GiB). The swap size should be between as much RAM as you have and double that.
Line 171:		Line 173:
	* Add [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> the tools you'll use to upgrade the system, add new software if you need, and clean up old snapshots.		* Add [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> the tools you'll use to upgrade the system, add new software if you need, and clean up old snapshots.
	* Make sure you install {{pkg\|execline}} so you can run sysmut and syscln!		* Make sure you install {{pkg\|execline}} so you can run sysmut and syscln!

	~~This would also be a good time to install~~

	{{Warning\|In case your PC only has wireless connection you should also install any suitable networking software, like <code>iwd</code> in this example, so you will not end up severed from network on your first boot. The network connection from the installer does not carry over onto the installed system.}}		{{Warning\|In case your PC only has wireless connection you should also install any suitable networking software, like <code>iwd</code> in this example, so you will not end up severed from network on your first boot. The network connection from the installer does not carry over onto the installed system.}}

Halscode at 03:51, 2 October 2024

2024-10-02T03:51:33Z

← Older revision		Revision as of 03:51, 2 October 2024
Line 100:		Line 100:
	Get UUIDs of the partitions first:		Get UUIDs of the partitions first:
	<pre># blkid > /mnt/fstab</pre>		<pre># blkid > /mnt/fstab</pre>

	Now edit fstab accordingly:		Now edit fstab accordingly:
	<pre># vi /mnt/fstab</pre>		<pre># vi /mnt/fstab</pre>
	Example:		Example:
	<pre>UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 / btrfs subvol=CURRENT_SNAPSHOTS_PATH/@,ro,noatime 0 0		<pre>UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 / btrfs subvol=CURRENT_SNAPSHOTS_PATH/@,ro,noatime 0 0
			UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 /etc btrfs subvol=CURRENT_SNAPSHOTS_PATH/@etc,rw,noatime 0 0
	UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 /var btrfs subvol=/commons/@var,rw,noatime 0 0		UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 /var btrfs subvol=/commons/@var,rw,noatime 0 0
	UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 /home btrfs subvol=/commons/@home,rw,noatime 0 0		UUID=b9ff5e7b-e128-4e64-861a-2fdd794a9828 /home btrfs subvol=/commons/@home,rw,noatime 0 0
	# UUID=2FE6-837A /boot/efi vfat rw,noatime,discard 0 2		# UUID=2FE6-837A /boot/efi vfat rw,noatime,discard 0 2
	tmpfs /tmp tmpfs mode=1777,noatime,nosuid,nodev,size=2G 0 0		tmpfs /tmp tmpfs mode=1777,noatime,nosuid,nodev,size=2G 0 0
			tmpfs /var/tmp tmpfs mode=1777,noatime,nosuid,nodev,size=2G 0 0
	UUID=f0239163-9d46-47c1-67a4-3ee1d63d0676 swap swap rw,noatime,discard 0 0</pre>		UUID=f0239163-9d46-47c1-67a4-3ee1d63d0676 swap swap rw,noatime,discard 0 0</pre>

Line 136:		Line 139:
	Now we can setup basic chroot to complete the installation process:		Now we can setup basic chroot to complete the installation process:
	<pre># export SNP="/mnt/snapshots/20210411212549sdBXyLxg/@"		<pre># export SNP="/mnt/snapshots/20210411212549sdBXyLxg/@"
			# # tip: use tab to fill in the correct snapshot; this one is just an example

	# mount -o bind /dev $SNP/dev		# mount -o bind /dev $SNP/dev
Line 142:		Line 146:

	# sed "s#CURRENT_SNAPSHOTS_PATH#/snapshots/20210411212549sdBXyLxg#g" /mnt/fstab > "$SNP/etc/fstab"		# sed "s#CURRENT_SNAPSHOTS_PATH#/snapshots/20210411212549sdBXyLxg#g" /mnt/fstab > "$SNP/etc/fstab"
			# # tip: use tab to fill in the correct snapshot; this one is just an example

	# cp -L /etc/resolv.conf "$SNP/etc/"		# cp -L /etc/resolv.conf "$SNP/etc/" # so DNS still works
	# chroot "$SNP" /bin/sh		# chroot "$SNP" /bin/sh

	# mount -a		# mount -a</pre>

	~~# mv /etc/resolv.conf /tmp/~~
	~~# ln -s /tmp/resolv.conf /etc/resolv.conf~~</pre>

	As soon as you're in chroot, define repositories:		As soon as you're in chroot, define repositories:
	<pre># echo "https://dl-cdn.alpinelinux.org/alpine/latest-stable/main" > /etc/apk/repositories</pre>		<pre># echo "https://dl-cdn.alpinelinux.org/alpine/latest-stable/main" > /etc/apk/repositories</pre>
	This example shows only <code>main</code>, but you should also add <code>testing</code> and <code>community</code> if you need any packages in those.~~<br>~~
			This example shows only <code>main</code>, but you should also add <code>testing</code> and <code>community</code> if you need any packages in those.

	Now it's time for the firmware, kernel, and btrfs packages:		Now it's time for the firmware, kernel, and btrfs packages:
	<pre># apk add -U linux-firmware linux-lts btrfs-progs</pre>		<pre># apk add -U linux-firmware linux-lts btrfs-progs</pre>
Line 160:		Line 164:
	<pre># vi /etc/mkinitfs/mkinitfs.conf		<pre># vi /etc/mkinitfs/mkinitfs.conf
	# mkinitfs</pre>		# mkinitfs</pre>
	These steps prepare the kernel and generate the <code>initramfs</code>, which will be used later to boot from our first snapshot.<br>		These steps prepare the kernel and generate the <code>initramfs</code>, which will be used later to boot from our first snapshot.
	~~After that,~~ you ~~should~~ install ~~any package~~ you ~~may need on first boot.~~
			This would be a good time to:
			* run [[setup-desktop]]
			* install NetworkManager if you installed GNOME with setup-desktop (and if you need WiFi, {{pkg\|networkmanager-wifi}} as well)
			* Add [[#Updating_or_altering_the_system\|sysmut]] and [[#Deleting_unused_snapshots\|syscln]], <!-- TODO: give a downloadable file for both here. or a package? --> the tools you'll use to upgrade the system, add new software if you need, and clean up old snapshots.
			* Make sure you install {{pkg\|execline}} so you can run sysmut and syscln!

			This would also be a good time to install

	{{Warning\|In case your PC only has wireless connection you should also install any suitable networking software, like <code>iwd</code> in this example, so you will not end up severed from network on your first boot.}}		{{Warning\|In case your PC only has wireless connection you should also install any suitable networking software, like <code>iwd</code> in this example, so you will not end up severed from network on your first boot. The network connection from the installer does not carry over onto the installed system.}}

	{{Note\|Due to root being immutable during operation, it's recommended to install the <code>openresolv</code> package to support changing the network connection. In this case, <code>/etc/resolvconf.conf</code> should have <code>resolv_conf{{=}}/tmp/resolv.conf</code>, <code>/etc/resolv.conf</code> should be moved to <code>/tmp/resolv.conf</code>, and a link to the new resolv.conf location should be created: <code>ln -sfn /tmp/resolv.conf /etc/resolv.conf</code>.		<!--{{Note\|Due to root being immutable during operation, it's recommended to install the <code>openresolv</code> package to support changing the network connection. In this case, <code>/etc/resolvconf.conf</code> should have <code>resolv_conf{{=}}/tmp/resolv.conf</code>, <code>/etc/resolv.conf</code> should be moved to <code>/tmp/resolv.conf</code>, and a link to the new resolv.conf location should be created: <code>ln -sfn /tmp/resolv.conf /etc/resolv.conf</code>.
	You may also use static DNS, but this would make your network activity directly identifiable to the DNS server provider, therefore it's not recommended.		You may also use static DNS, but this would make your network activity directly identifiable to the DNS server provider, therefore it's not recommended.
	}}		}}-->

	Now, configure the system, start with setting a password for the root:		Now, configure the system, start with setting a password for the root:

Halscode at 03:38, 2 October 2024

2024-10-02T03:38:39Z

← Older revision		Revision as of 03:38, 2 October 2024
Line 50:		Line 50:

	Next step is creating filesystems:		Next step is creating filesystems:
	<pre># mkfs.vfat -F32 /dev/sda1		<pre># mkfs.vfat -F32 /dev/sda1 # EFI
	# mkfs.btrfs /dev/sda2		# mkfs.btrfs /dev/sda2 # ROOT
	# mkswap /dev/sda3</pre>		# mkswap /dev/sda3 # SWAP</pre>

	Now we can mount our root volume:		Now we can mount our root volume:
	<pre># mount -t btrfs /dev/sda2 /mnt</pre>		<pre># mount -t btrfs /dev/sda2 /mnt</pre>

	= File system structure =		= File system structure =
	Now we should create the file structure that would provide reliable atomic system upgrades.<br>		Now we should create the file structure that would provide reliable atomic system upgrades.<br>
	Start with following directories:~~<br>~~		Start with the following directories:

	<pre># mkdir /mnt/next</pre>		<pre># mkdir /mnt/next</pre>
	Stores next <code>current</code> link, is necessary due to how busybox <code>mv</code> does atomic link replacement.<br>		Stores next <code>current</code> link, is necessary due to how busybox <code>mv</code> does atomic link replacement.<br><br>

	<pre># mkdir /mnt/commons</pre>		<pre># mkdir /mnt/commons</pre>
	Stores common non-snapshotting subvolumes.<br>		Stores common non-snapshotting subvolumes.<br>
	We may populate it right away:		We may populate it right away:
	<pre># btrfs subvolume create /mnt/commons/@var		<pre># btrfs subvolume create /mnt/commons/@var
	# btrfs subvolume create /mnt/commons/@home</pre>		# btrfs subvolume create /mnt/commons/@home</pre><br><br>
	Next, most important directories:
			Next, the most important directories:
	<pre># mkdir /mnt/snapshots</pre>		<pre># mkdir /mnt/snapshots</pre>
	Stores directories containing snapshots belonging to one generation.<br>		Stores directories containing snapshots belonging to one generation.<br><br>

	<pre># mkdir /mnt/links</pre>		<pre># mkdir /mnt/links</pre>
	Stores generations of directories containing links to snapshot generations.<br>		Stores generations of directories containing links to snapshot generations.<br><br>
	Let's create first generation and populate it with one OS root snapshot <code>@</code>:
			Let's create the first generation and populate it with one OS root snapshot <code>@</code>:
	<pre># NEWSNAPSHOTS="$(date -u +"%Y%m%d%H%M%S")$(cat /dev/urandom \| tr -dc 'a-zA-Z' \| fold -w 8 \| head -n 1)"		<pre># NEWSNAPSHOTS="$(date -u +"%Y%m%d%H%M%S")$(cat /dev/urandom \| tr -dc 'a-zA-Z' \| fold -w 8 \| head -n 1)"
	# mkdir "/mnt/snapshots/$NEWSNAPSHOTS"		# mkdir "/mnt/snapshots/$NEWSNAPSHOTS"
	# btrfs subvolume create /mnt/snapshots/$NEWSNAPSHOTS/@</pre>		# btrfs subvolume create /mnt/snapshots/$NEWSNAPSHOTS/@</pre>

	Populate <code>links</code>:		Populate <code>links</code>:
	<pre># NEWLINKS="$(date -u +"%Y%m%d%H%M%S")$(cat /dev/urandom \| tr -dc 'a-zA-Z' \| fold -w 8 \| head -n 1)"		<pre># NEWLINKS="$(date -u +"%Y%m%d%H%M%S")$(cat /dev/urandom \| tr -dc 'a-zA-Z' \| fold -w 8 \| head -n 1)"
Line 81:		Line 89:
	# ln -s "../../snapshots/$NEWSNAPSHOTS" "/mnt/links/$NEWLINKS/2"		# ln -s "../../snapshots/$NEWSNAPSHOTS" "/mnt/links/$NEWLINKS/2"
	# ln -s "../../snapshots/$NEWSNAPSHOTS" "/mnt/links/$NEWLINKS/3"</pre>		# ln -s "../../snapshots/$NEWSNAPSHOTS" "/mnt/links/$NEWLINKS/3"</pre>
	You can have as many links as you like, just apply changes to rEFInd config and upgrade scripts described below accordingly.~~<br>~~		You can have as many links as you like, just apply changes to rEFInd config and upgrade scripts described below accordingly.

	Link that will point to latest links generation:		Link that will point to latest links generation:
	<pre># ln -s "./links/$NEWLINKS" /mnt/current</pre>		<pre># ln -s "./links/$NEWLINKS" /mnt/current</pre>
	This setup allows us to just have static rEFInd config that points to to <code>/current/0/@</code>, <code>/current/1/@</code>, etc. while the actual underlying boot environment will change with each upgrade.~~<br>~~		This setup allows us to just have static rEFInd config that points to to <code>/current/0/@</code>, <code>/current/1/@</code>, etc. while the actual underlying boot environment will change with each upgrade.

	But how will fs mounting services know which snapshot generation is currently loaded?<br>		But how will fs mounting services know which snapshot generation is currently loaded?<br>
	The answer is common <code>fstab</code> in the [[BTRFS\|btrfs]] root.~~<br>~~		The answer is common <code>fstab</code> in the [[BTRFS\|btrfs]] root.

	Get UUIDs of the partitions first:		Get UUIDs of the partitions first:
	<pre># blkid > /mnt/fstab</pre>		<pre># blkid > /mnt/fstab</pre>
Line 98:		Line 109:
	tmpfs /tmp tmpfs mode=1777,noatime,nosuid,nodev,size=2G 0 0		tmpfs /tmp tmpfs mode=1777,noatime,nosuid,nodev,size=2G 0 0
	UUID=f0239163-9d46-47c1-67a4-3ee1d63d0676 swap swap rw,noatime,discard 0 0</pre>		UUID=f0239163-9d46-47c1-67a4-3ee1d63d0676 swap swap rw,noatime,discard 0 0</pre>
	<code>CURRENT_SNAPSHOTS_PATH</code> will be replaced by scripts with, for example, <code>/snapshots/20210411212549sdBXyLxg</code>, and the result will be piped into <code>/etc/fstab</code> of a created <code>@</code> snapshot during new generation preparations.~~<br>~~
			<code>CURRENT_SNAPSHOTS_PATH</code> will be replaced by scripts with, for example, <code>/snapshots/20210411212549sdBXyLxg</code>, and the result will be piped into <code>/etc/fstab</code> of a created <code>@</code> snapshot during new generation preparations.

	Root [[BTRFS\|btrfs]] volume structure mounted on <code>/mnt</code>:		Root [[BTRFS\|btrfs]] volume structure mounted on <code>/mnt</code>:
	<pre>\|--mnt		<pre>\|--mnt