Arch - revision history

Dank at 13:11, 6 February 2021

2021-02-06T13:11:33Z

← Older revision		Revision as of 13:11, 6 February 2021
Line 1:		Line 1:
	After fifteen years of exclusively running [[Debian\|Debian Linux]] in its [https://wiki.debian.org/DebianUnstable Unstable] ("sid") rolling configuration on [[Machines\|my machines]], I converted my day-to-day laptop to Arch in March 2019 (my workstation remains Debian Unstable). The [[Lenovo]] T580 started life as "[https://www.youtube.com/watch?v=hCuMWrfXG4E uptowngirl]"; she was renamed "uptowngrimes" for the first pass at running Arch, and finally "[https://www.youtube.com/watch?v=Tv9YoYCKNoE grimes]" once I was ready to give Arch a real go. My primary motivations were the increasingly European and ossified nature of Debian, and the fact that the Arch wiki provided ~~an increasing~~ portion of the best content I was reading each day.		After fifteen years of exclusively running [[Debian\|Debian Linux]] in its [https://wiki.debian.org/DebianUnstable Unstable] ("sid") rolling configuration on [[Machines\|my machines]], I converted my day-to-day laptop to Arch in March 2019 (my workstation remains Debian Unstable). The [[Lenovo]] T580 started life as "[https://www.youtube.com/watch?v=hCuMWrfXG4E uptowngirl]"; she was renamed "uptowngrimes" for the first pass at running Arch, and finally "[https://www.youtube.com/watch?v=Tv9YoYCKNoE grimes]" once I was ready to give Arch a real go. My primary motivations were the increasingly European and ossified nature of Debian, and the fact that the Arch wiki provided a significant portion of the best content I was reading each day.

	I dig it thus far!		I dig it thus far!

Dank: /* Building custom kernel packages */

2020-09-22T20:33:33Z

Building custom kernel packages

← Older revision		Revision as of 20:33, 22 September 2020
Line 26:		Line 26:
	</pre>		</pre>
	Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue.		Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue.

			If you wish to avoid the lengthy build of documentation (it will otherwise dominate your total build time), remove <tt>$pkgbase-docs</tt> from the <tt>pkgname</tt> array.
	===New kernel process===		===New kernel process===
	* Edit <tt>PKGBUILD</tt> and change <tt>_pkgver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH.arch1</tt>		* Edit <tt>PKGBUILD</tt> and change <tt>_pkgver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH.arch1</tt>

Dank: /* New kernel process */

2020-09-09T00:28:51Z

New kernel process

← Older revision		Revision as of 00:28, 9 September 2020
Line 27:		Line 27:
	Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue.		Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue.
	===New kernel process===		===New kernel process===
	* Edit <tt>PKGBUILD</tt> and change <tt>_pkgver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH-arch1</tt>		* Edit <tt>PKGBUILD</tt> and change <tt>_pkgver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH.arch1</tt>
	* Clear out any old packages and source: <tt>rm -rf *.xz src pkg</tt>		* Clear out any old packages and source: <tt>rm -rf *.xz src pkg</tt>
	* Make your packages, updating the kernel config along the way (see above):		* Make your packages, updating the kernel config along the way (see above):

Dank: /* New kernel process */

2020-09-09T00:28:36Z

New kernel process

← Older revision		Revision as of 00:28, 9 September 2020
Line 27:		Line 27:
	Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue.		Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue.
	===New kernel process===		===New kernel process===
	* Edit <tt>~~PKGCONFIG~~</tt> and change <tt>~~_srcver~~</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH-arch1</tt>		* Edit <tt>PKGBUILD</tt> and change <tt>_pkgver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH-arch1</tt>
	* Clear out any old packages and source: <tt>rm -rf *.xz src pkg</tt>		* Clear out any old packages and source: <tt>rm -rf *.xz src pkg</tt>
	* Make your packages, updating the kernel config along the way (see above):		* Make your packages, updating the kernel config along the way (see above):
Line 33:		Line 33:
	** Remember, <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config		** Remember, <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config
	* Install the new packages: <tt>pacman -U *.xz</tt>		* Install the new packages: <tt>pacman -U *.xz</tt>

	===GPG keys===		===GPG keys===
	If you're getting errors during verification of [[GPG]] signatures, you can use pacman's trusted keys. Add to your <tt>gpg.conf</tt>:		If you're getting errors during verification of [[GPG]] signatures, you can use pacman's trusted keys. Add to your <tt>gpg.conf</tt>:

Dank: /* GPG keys */

2020-01-07T06:17:01Z

GPG keys

← Older revision		Revision as of 06:17, 7 January 2020
Line 35:		Line 35:
	===GPG keys===		===GPG keys===
	If you're getting errors during verification of [[GPG]] signatures, you can use pacman's trusted keys. Add to your <tt>gpg.conf</tt>:		If you're getting errors during verification of [[GPG]] signatures, you can use pacman's trusted keys. Add to your <tt>gpg.conf</tt>:

	<tt>keyring /etc/pacman.d/gnupg/pubring.gpg</tt>		<tt>keyring /etc/pacman.d/gnupg/pubring.gpg</tt>

	and then run (as specified at [https://wiki.archlinux.org/index.php/Pacman/Package_signing Package Signing]):		and then run (as specified at [https://wiki.archlinux.org/index.php/Pacman/Package_signing Package Signing]):
	<pre>		<pre>
Line 44:		Line 46:
	If you then need a particular key, try e.g.:		If you then need a particular key, try e.g.:
	<pre>pacman-key -r A5E9288C4FA415FA</pre>		<pre>pacman-key -r A5E9288C4FA415FA</pre>
			and mark the key as trusted.

Dank: /* GPG keys */

2020-01-01T15:52:26Z

GPG keys

← Older revision		Revision as of 15:52, 1 January 2020
Line 41:		Line 41:
	pacman-key --populate archlinux		pacman-key --populate archlinux
	</pre>		</pre>

			If you then need a particular key, try e.g.:
			<pre>pacman-key -r A5E9288C4FA415FA</pre>

Dank: /* Building custom kernel packages */

2019-12-12T20:56:07Z

Building custom kernel packages

← Older revision		Revision as of 20:56, 12 December 2019
Line 33:		Line 33:
	** Remember, <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config		** Remember, <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config
	* Install the new packages: <tt>pacman -U *.xz</tt>		* Install the new packages: <tt>pacman -U *.xz</tt>
			===GPG keys===
			If you're getting errors during verification of [[GPG]] signatures, you can use pacman's trusted keys. Add to your <tt>gpg.conf</tt>:
			<tt>keyring /etc/pacman.d/gnupg/pubring.gpg</tt>
			and then run (as specified at [https://wiki.archlinux.org/index.php/Pacman/Package_signing Package Signing]):
			<pre>
			pacman-key --init
			pacman-key --populate archlinux
			</pre>

Dank: /* Building a kernel */

2019-10-21T02:34:47Z

Building a kernel

← Older revision		Revision as of 02:34, 21 October 2019
Line 6:		Line 6:
	The [https://aur.archlinux.org/ Arch User Repository] allows random people to upload Arch packaging. I maintain a [https://aur.archlinux.org/packages/?SeB=m&K=dankamongmen few packages in the AUR].		The [https://aur.archlinux.org/ Arch User Repository] allows random people to upload Arch packaging. I maintain a [https://aur.archlinux.org/packages/?SeB=m&K=dankamongmen few packages in the AUR].

	==Building a kernel==		==Building custom kernel packages==
	The [https://wiki.archlinux.org/index.php/Kernel/Arch_Build_System Arch Build System] page on the Arch Wiki purports to explain how to make custom kernel packages, but I've never found it very clear.		The [https://wiki.archlinux.org/index.php/Kernel/Arch_Build_System Arch Build System] page on the Arch Wiki purports to explain how to make custom kernel packages, but I've never found it very clear.
	===One-time setup===		===One-time setup===

Dank at 02:34, 21 October 2019

2019-10-21T02:34:20Z

← Older revision		Revision as of 02:34, 21 October 2019
Line 5:		Line 5:
	==AUR==		==AUR==
	The [https://aur.archlinux.org/ Arch User Repository] allows random people to upload Arch packaging. I maintain a [https://aur.archlinux.org/packages/?SeB=m&K=dankamongmen few packages in the AUR].		The [https://aur.archlinux.org/ Arch User Repository] allows random people to upload Arch packaging. I maintain a [https://aur.archlinux.org/packages/?SeB=m&K=dankamongmen few packages in the AUR].

			==Building a kernel==
			The [https://wiki.archlinux.org/index.php/Kernel/Arch_Build_System Arch Build System] page on the Arch Wiki purports to explain how to make custom kernel packages, but I've never found it very clear.
			===One-time setup===
			* Install the [https://www.archlinux.org/packages/extra/any/asp/ asp] package from the [https://www.archlinux.org/packages/?repo=Extra Extra] repository
			* Run <tt>asp update linux</tt> followed by <tt>asp checkout linux</tt>
			* You ought now have a directory <tt>linux</tt> with subdirectories <tt>repos</tt> and <tt>trunk</tt>
			** in the future, run <tt>asp update</tt> in this directory
			* Change the <tt>pkgbase</tt> field in <tt>PKGBUILD</tt>; I use <tt>linux-HOSTNAME</tt> where HOSTNAME is the name of that machine
			* We're going to keep our kernel config in the newly-created directory. If you don't have one ready, use the current config:
			** Insert the <tt>configs</tt> module if it's not loaded
			** Inflate and copy the current config: <tt>zcat /proc/config.gz > config</tt>
			* Add the following to <tt>PKGBUILD</tt>:
			<pre>
			msg2 "Setting config from ../../../config..."
			cp ../../../config .config
			make oldconfig
			make menuconfig
			diff -ur ../../../config .config is
			</pre>
			Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue.
			===New kernel process===
			* Edit <tt>PKGCONFIG</tt> and change <tt>_srcver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH-arch1</tt>
			* Clear out any old packages and source: <tt>rm -rf *.xz src pkg</tt>
			* Make your packages, updating the kernel config along the way (see above):
			** <tt>MAKEFLAGS=-jNN makepkg -s</tt>, where NN is the number of parallel processes
			** Remember, <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config
			* Install the new packages: <tt>pacman -U *.xz</tt>

Dank at 03:56, 24 August 2019

2019-08-24T03:56:54Z

← Older revision		Revision as of 03:56, 24 August 2019
Line 2:		Line 2:

	I dig it thus far!		I dig it thus far!

			==AUR==
			The [https://aur.archlinux.org/ Arch User Repository] allows random people to upload Arch packaging. I maintain a [https://aur.archlinux.org/packages/?SeB=m&K=dankamongmen few packages in the AUR].