Specialisation - Revision history

Noewaeda at 23:50, 22 September 2026

2026-09-22T23:50:53Z

← Older revision		Revision as of 23:50, 22 September 2026
Line 70:		Line 70:
	== Further reading ==		== Further reading ==

	* https://discourse.nixos.org/t/nixos-specialisations-how-do-you-use-them/~~10367/4~~		* https://discourse.nixos.org/t/nixos-specialisations-how-do-you-use-them/

	{{references}}		{{references}}

Noewaeda: Update example to use plasma6, remove usage of the "services.xserver" option

2026-09-22T23:34:49Z

Update example to use plasma6, remove usage of the "services.xserver" option

← Older revision		Revision as of 23:34, 22 September 2026
Line 11:		Line 11:
	specialisation = {		specialisation = {
	chani.configuration = {		chani.configuration = {
	services~~.xserver~~.desktopManager.~~plasma5~~.enable = true;		services.desktopManager.plasma6.enable = true;
	};		};

Line 18:		Line 18:
	configuration = {		configuration = {
	system.nixos.tags = [ "paul" ];		system.nixos.tags = [ "paul" ];
	services~~.xserver~~.desktopManager.gnome.enable = true;		services.desktopManager.gnome.enable = true;
	users.users.paul = {		users.users.paul = {
	isNormalUser = true;		isNormalUser = true;
Line 24:		Line 24:
	extraGroups = [ "networkmanager" "video" ];		extraGroups = [ "networkmanager" "video" ];
	};		};
	services~~.xserver~~.displayManager.autoLogin = {		services.displayManager.autoLogin = {
	enable = true;		enable = true;
	user = "paul";		user = "paul";
Line 35:		Line 35:
	};</syntaxHighlight>		};</syntaxHighlight>

	In this example, the <code>chani</code> specialisation inherits the parent configuration (which contains the <code>specialisation</code> directive), but additionally activates the <code>~~plasma5~~</code> desktop. The <code>paul</code> specialisation does not inherit the parent configuration, and defines its own configuration from scratch instead.		In this example, the <code>chani</code> specialisation inherits the parent configuration (which contains the <code>specialisation</code> directive), but additionally activates the <code>plasma6</code> desktop. The <code>paul</code> specialisation does not inherit the parent configuration, and defines its own configuration from scratch instead.

	{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services~~.xserver~~.desktopManager.~~plasma5~~.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar<ref>https://discourse.nixos.org/t/what-does-mkdefault-do-exactly/9028</ref>: <code>services~~.xserver~~.desktopManager.~~plasma5~~.enable = lib.mkDefault false;</code>}}		{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services.desktopManager.plasma6.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar<ref>https://discourse.nixos.org/t/what-does-mkdefault-do-exactly/9028</ref>: <code>services.desktopManager.plasma6.enable = lib.mkDefault false;</code>}}

	== Special case: the default non-specialised entry ==		== Special case: the default non-specialised entry ==

Noewaeda: Copyedit the entire article

2026-09-22T23:28:45Z

Copyedit the entire article

← Older revision		Revision as of 23:28, 22 September 2026
Line 2:		Line 2:
	{{low quality\|References need to use <nowiki><cite></nowiki> instead of just being numbers in brackets.}}		{{low quality\|References need to use <nowiki><cite></nowiki> instead of just being numbers in brackets.}}

	Specialisations allow you to define variations of your system configuration. For instance, if you don't usually use GPU, you might create a base system with your GPU disabled and create a dedicated specialisation with Nvidia/AMD drivers installed ~~- later~~, during boot, you can choose which configuration you want to boot into this time.		Specialisations allow you to define variations of your system configuration. For instance, if you don't usually use GPU, you might create a base system with your GPU disabled and create a dedicated specialisation with Nvidia/AMD drivers installed. Then, during boot, you can choose which configuration you want to boot into this time.

	== Config ==		== Config ==
Line 35:		Line 35:
	};</syntaxHighlight>		};</syntaxHighlight>

	In this example, the <code>chani</code> specialisation inherits the parent ~~config~~ (~~that~~ contains the <code>specialisation</code> directive), but additionally activates the plasma5 desktop. The <code>paul</code> specialisation ~~on the other hand~~ does not ~~<code>inheritParentConfig</code>~~ and defines its own ~~one~~ from scratch instead.		In this example, the <code>chani</code> specialisation inherits the parent configuration (which contains the <code>specialisation</code> directive), but additionally activates the <code>plasma5</code> desktop. The <code>paul</code> specialisation does not inherit the parent configuration, and defines its own configuration from scratch instead.

	{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services.xserver.desktopManager.plasma5.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar<ref>https://discourse.nixos.org/t/what-does-mkdefault-do-exactly/9028</ref>: <code>services.xserver.desktopManager.plasma5.enable = lib.mkDefault false;</code>}}		{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services.xserver.desktopManager.plasma5.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar<ref>https://discourse.nixos.org/t/what-does-mkdefault-do-exactly/9028</ref>: <code>services.xserver.desktopManager.plasma5.enable = lib.mkDefault false;</code>}}

	== Special case: the default non-~~specialized~~ entry ==		== Special case: the default non-specialised entry ==

	Specialisations ~~are receiving~~ options in addition to your default configuration~~, but what if~~ you want to have options in your default configuration that shouldn't be pulled by the specialisations?		Specialisations will receive options in addition to your default configuration. If you want to have options in your default configuration that shouldn't be pulled by the specialisations, use the conditional <code>config.specialisation != {}</code> to declare values for the non-specialised case.

	~~Use the conditional <code>config.specialisation != {}</code> to declare values for the non-specialized case.~~ For example, you could write a module (as variable, or separate file), imported from <code>configuration.nix</code> via <code>imports = [...]</code> like this:		For example, you could write a module (as a variable, or a separate file), imported from <code>configuration.nix</code> via <code>imports = [...]</code> like this:

	<syntaxHighlight lang=nix>		<syntaxHighlight lang=nix>
Line 56:		Line 56:
	</syntaxHighlight>		</syntaxHighlight>

	However, if there are no specialisations defined, then <code>config.specialisation != {}</code> always ~~evaluate~~ to <code>false</code>.		However, if there are no specialisations defined, then <code>config.specialisation != {}</code> always evaluates to <code>false</code>.

	== Activating a specialisation ==		== Activating a specialisation ==

	After rebuilding your system, you can choose a specialisation during boot~~; it~~'s also possible to switch into a specialisation at runtime - following the example above, you would run:		After rebuilding your system, you can choose a specialisation during boot. It's also possible to switch into a specialisation at runtime - following the example above, you would run:

	<syntaxHighlight lang=console>		<syntaxHighlight lang=console>
Line 66:		Line 66:
	</syntaxHighlight>		</syntaxHighlight>

	~~Note that not~~ all configurations can be fully switched into at runtime ~~- e.g~~. if your specialisation uses a different kernel, switching into it will not actually reload the kernel (but if you were to restart your computer and pick the specialisation from the boot menu, the alternative kernel would ~~get~~ loaded).		Not all configurations can be fully switched into at runtime. For example, if your specialisation uses a different kernel, switching into it will not actually reload the kernel, but if you were to restart your computer and pick the specialisation from the boot menu, the alternative kernel would be loaded.

	== Further reading ==		== Further reading ==

Noewaeda: Use consistent spelling of the word "specialisation"

2026-09-08T03:53:39Z

Use consistent spelling of the word "specialisation"

← Older revision		Revision as of 03:53, 8 September 2026
Line 2:		Line 2:
	{{low quality\|References need to use <nowiki><cite></nowiki> instead of just being numbers in brackets.}}		{{low quality\|References need to use <nowiki><cite></nowiki> instead of just being numbers in brackets.}}

	Specialisations allow you to define variations of your system configuration. For instance, if you don't usually use GPU, you might create a base system with your GPU disabled and create a dedicated ~~specialization~~ with Nvidia/AMD drivers installed - later, during boot, you can choose which configuration you want to boot into this time.		Specialisations allow you to define variations of your system configuration. For instance, if you don't usually use GPU, you might create a base system with your GPU disabled and create a dedicated specialisation with Nvidia/AMD drivers installed - later, during boot, you can choose which configuration you want to boot into this time.

	== Config ==		== Config ==
Line 41:		Line 41:
	== Special case: the default non-specialized entry ==		== Special case: the default non-specialized entry ==

	~~Specializations~~ are receiving options in addition to your default configuration, but what if you want to have options in your default configuration that shouldn't be pulled by the ~~specializations~~?		Specialisations are receiving options in addition to your default configuration, but what if you want to have options in your default configuration that shouldn't be pulled by the specialisations?

	Use the conditional <code>config.specialisation != {}</code> to declare values for the non-specialized case. For example, you could write a module (as variable, or separate file), imported from <code>configuration.nix</code> via <code>imports = [...]</code> like this:		Use the conditional <code>config.specialisation != {}</code> to declare values for the non-specialized case. For example, you could write a module (as variable, or separate file), imported from <code>configuration.nix</code> via <code>imports = [...]</code> like this:
Line 58:		Line 58:
	However, if there are no specialisations defined, then <code>config.specialisation != {}</code> always evaluate to <code>false</code>.		However, if there are no specialisations defined, then <code>config.specialisation != {}</code> always evaluate to <code>false</code>.

	== Activating a ~~specialization~~ ==		== Activating a specialisation ==

	After rebuilding your system, you can choose a specialisation during boot; it's also possible to switch into a specialisation at runtime - following the example above, you would run:		After rebuilding your system, you can choose a specialisation during boot; it's also possible to switch into a specialisation at runtime - following the example above, you would run:
Line 66:		Line 66:
	</syntaxHighlight>		</syntaxHighlight>

	Note that not all configurations can be fully switched into at runtime - e.g. if your ~~specialization~~ uses a different kernel, switching into it will not actually reload the kernel (but if you were to restart your computer and pick the specialisation from the boot menu, the alternative kernel would get loaded).		Note that not all configurations can be fully switched into at runtime - e.g. if your specialisation uses a different kernel, switching into it will not actually reload the kernel (but if you were to restart your computer and pick the specialisation from the boot menu, the alternative kernel would get loaded).

	== Further reading ==		== Further reading ==

Noewaeda: /* Activating a specialization */ "we'd" -> "you would"

2026-08-17T00:41:41Z

Activating a specialization: "we'd" -> "you would"

← Older revision		Revision as of 00:41, 17 August 2026
Line 60:		Line 60:
	== Activating a specialization ==		== Activating a specialization ==

	After rebuilding your system, you can choose a specialisation during boot; it's also possible to switch into a specialisation at runtime - following the example above, ~~we'd~~ run:		After rebuilding your system, you can choose a specialisation during boot; it's also possible to switch into a specialisation at runtime - following the example above, you would run:

	<syntaxHighlight lang=console>		<syntaxHighlight lang=console>

Noewaeda: Fix references to use ref tag

2026-08-17T00:11:25Z

Fix references to use ref tag

← Older revision		Revision as of 00:11, 17 August 2026
Line 6:		Line 6:
	== Config ==		== Config ==

	Specialisations are defined with the following options ~~[1]~~: https://search.nixos.org/options?from=0&size=50&sort=relevance&query=specialisation		Specialisations are defined with the following options<ref>https://www.tweag.io/blog/2022-08-18-nixos-specialisations/</ref>: https://search.nixos.org/options?from=0&size=50&sort=relevance&query=specialisation

	<syntaxHighlight lang=nix>		<syntaxHighlight lang=nix>
Line 37:		Line 37:
	In this example, the <code>chani</code> specialisation inherits the parent config (that contains the <code>specialisation</code> directive), but additionally activates the plasma5 desktop. The <code>paul</code> specialisation on the other hand does not <code>inheritParentConfig</code> and defines its own one from scratch instead.		In this example, the <code>chani</code> specialisation inherits the parent config (that contains the <code>specialisation</code> directive), but additionally activates the plasma5 desktop. The <code>paul</code> specialisation on the other hand does not <code>inheritParentConfig</code> and defines its own one from scratch instead.

	{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services.xserver.desktopManager.plasma5.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar ~~[3]~~: <code>services.xserver.desktopManager.plasma5.enable = lib.mkDefault false;</code>}}		{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services.xserver.desktopManager.plasma5.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar<ref>https://discourse.nixos.org/t/what-does-mkdefault-do-exactly/9028</ref>: <code>services.xserver.desktopManager.plasma5.enable = lib.mkDefault false;</code>}}

	== Special case: the default non-specialized entry ==		== Special case: the default non-specialized entry ==
Line 70:		Line 70:
	== Further reading ==		== Further reading ==

	~~[1]~~ https://~~www~~.~~tweag~~.io/~~blog~~/~~2022~~-08-18-~~nixos~~-~~specialisations~~/		* https://discourse.nixos.org/t/nixos-specialisations-how-do-you-use-them/10367/4

	~~[2] https://discourse.nixos.org/t/nixos-specialisations-how-do-you-use-them/10367/4~~		{{references}}

	~~[3] https://discourse.nixos.org/t/what-does-mkdefault-do-exactly/9028~~

Zeal: It might be more intuitive to add `lib.` to the `mkDefault`-value for users copying this code.

2025-10-19T02:33:32Z

It might be more intuitive to add `lib.` to the `mkDefault`-value for users copying this code.

← Older revision		Revision as of 02:33, 19 October 2025
Line 37:		Line 37:
	In this example, the <code>chani</code> specialisation inherits the parent config (that contains the <code>specialisation</code> directive), but additionally activates the plasma5 desktop. The <code>paul</code> specialisation on the other hand does not <code>inheritParentConfig</code> and defines its own one from scratch instead.		In this example, the <code>chani</code> specialisation inherits the parent config (that contains the <code>specialisation</code> directive), but additionally activates the plasma5 desktop. The <code>paul</code> specialisation on the other hand does not <code>inheritParentConfig</code> and defines its own one from scratch instead.

	{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services.xserver.desktopManager.plasma5.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar [3]: <code>services.xserver.desktopManager.plasma5.enable = mkDefault false;</code>}}		{{Note\|At times, you may want to overwrite values in specialisations which you have already defined in your parent configuration. To solve this problem in <code>chani</code> example, the parent configuration could define <code>services.xserver.desktopManager.plasma5.enable = false;</code> in an overwritable manner using <code>mkDefault</code> and similar [3]: <code>services.xserver.desktopManager.plasma5.enable = lib.mkDefault false;</code>}}

	== Special case: the default non-specialized entry ==		== Special case: the default non-specialized entry ==

SigmaSquadron: lowquality

2025-04-17T17:49:22Z

lowquality

← Older revision		Revision as of 17:49, 17 April 2025
Line 1:		Line 1:
	{{Expansion\|Configuration with and for GRUB could use explaining here}}		{{Expansion\|Configuration with and for GRUB could use explaining here}}
			{{low quality\|References need to use <nowiki><cite></nowiki> instead of just being numbers in brackets.}}

	Specialisations allow you to define variations of your system configuration. For instance, if you don't usually use GPU, you might create a base system with your GPU disabled and create a dedicated specialization with Nvidia/AMD drivers installed - later, during boot, you can choose which configuration you want to boot into this time.		Specialisations allow you to define variations of your system configuration. For instance, if you don't usually use GPU, you might create a base system with your GPU disabled and create a dedicated specialization with Nvidia/AMD drivers installed - later, during boot, you can choose which configuration you want to boot into this time.

Fin444 at 01:26, 7 November 2024

2024-11-07T01:26:26Z

← Older revision		Revision as of 01:26, 7 November 2024
Line 54:		Line 54:
	})		})
	</syntaxHighlight>		</syntaxHighlight>

			However, if there are no specialisations defined, then <code>config.specialisation != {}</code> always evaluate to <code>false</code>.

	== Activating a specialization ==		== Activating a specialization ==

Patryk27 at 09:48, 20 October 2024

2024-10-20T09:48:07Z

← Older revision		Revision as of 09:48, 20 October 2024
Line 57:		Line 57:
	== Activating a specialization ==		== Activating a specialization ==

	After rebuilding your system, you can choose a specialisation during boot; ~~but~~ it's also possible to switch into a specialisation at runtime - following the example above, we'd run:		After rebuilding your system, you can choose a specialisation during boot; it's also possible to switch into a specialisation at runtime - following the example above, we'd run:

	<syntaxHighlight lang=console>		<syntaxHighlight lang=console>
Line 63:		Line 63:
	</syntaxHighlight>		</syntaxHighlight>

	Note that not all configurations can be switched into at runtime - e.g. if your specialization uses a different kernel, switching into it will not actually reload the kernel (but if you were to restart your computer and pick the specialisation from the boot menu, the alternative kernel would get loaded).		Note that not all configurations can be fully switched into at runtime - e.g. if your specialization uses a different kernel, switching into it will not actually reload the kernel (but if you were to restart your computer and pick the specialisation from the boot menu, the alternative kernel would get loaded).

	== Further reading ==		== Further reading ==