Change:
This is a tracking issue created only to track the different issues and pull requests related to the partitioning instructions in the manual. They may show more than one issue, the ordering of the partition may not match the expected ones for the following installation instructions, and the bootable flag might not be set properly. ; ; This issue is meant to track the problem and ask for help in finding a proper resolution. Not asking for others to write up, but asking to see if there would be issues in recommending things other than . I, myself, am extremely reluctant into fixing this using other incantations. They pretty much look like a self-selecting filter by obscurity. I would lean much more towards using commands, . (Though, not using ). Interfaces like are probably easier to reason about than single-letter commands which's meaning may change again in the future. They would also reduce the verbosity of the steps; it would be a set number of instructions, one per actual action, instead of a list of commands. (One for the disk format, one for setting the boot flag, and one per partition.)
# is twice in the list &ndash; that means you meant to link another fourth issue?
BTW, a couple weeks ago I successfully installed 18.09 (beta) on a machine for Hydra, and I followed our manual for partitioning via . It was a simple setup, though, so I most likely missed any corner cases. EDIT: to be clear, I do not at all oppose migrating the instructions to ...
is already in the closure so we should probably just switch to that anyway, then we don't need to have janky comments describing what the terse commands do.
I think people who have a preference among these tools need only a line «if you prefer fdisk, it is also available» and maybe an internal link to instructions for installing extra tools in case someone wants sfdisk. Parted probably has the lowest risk of instructions doing something but not the expected thing. (and partitioning — or tools with single-letter commands — is not something needed for NixOS use after installation, so the obscurity filter does not even select for people who would be happier NixOS users)

Discussion:
.PHONY: debug debug: generated manual-combined.xml <del> manual-combined.xml: generated *.xml </del> <ins> manual-combined.xml: generated *.xml **/*.xml </ins> rm -f ./manual-combined.xml nix-shell --packages xmloscopy  --run "xmloscopy --docbook5 ./manual.xml ./manual-combined.xml"

For systems without CD drive, the NixOS live CD can be booted from a USB stick. You can use the <command>dd</command> utility to write the image: <command>dd if=<replaceable>path-to-image</replaceable> <del> of=<replaceable>/dev/sdb</replaceable></command>. Be careful about specifying </del> <ins> of=<replaceable>/dev/sdX</replaceable></command>. Be careful about specifying </ins> the correct drive; you can use the <command>lsblk</command> command to get a list of block devices. <del> </para> <para> On macOS: </del> <ins> <note> <title>On macOS</title> <para> </ins> <programlisting> $ diskutil list [..]

Unmount of all volumes on diskN was successful $ sudo dd bs=1m if=nix.iso of=/dev/rdiskN </programlisting> <del> Using the 'raw' <command>rdiskN</command> device instead of <command>diskN</command> completes in minutes instead of hours. After <command>dd</command> completes, a GUI dialog "The disk you inserted was not readable by this computer" will pop up, which can be ignored. </del> <ins> Using the 'raw' <command>rdiskN</command> device instead of <command>diskN</command> completes in minutes instead of hours. After <command>dd</command> completes, a GUI dialog "The disk you inserted was not readable by this computer" will pop up, which can be ignored. </para> </note> </ins> </para> <para> The <command>dd</command> utility will write the image verbatim to the drive, making it the recommended option for both UEFI and non-UEFI installations. <del> For non-UEFI installations, you can alternatively use <link xlink:href="http://unetbootin.sourceforge.net/">unetbootin</link>. If you cannot use <command>dd</command> for a UEFI installation, you can also mount the ISO, copy its contents verbatim to your drive, then either: <itemizedlist> <listitem> <para> Change the label of the disk partition to the label of the ISO (visible with the blkid command), or </para> </listitem> <listitem> <para> Edit <filename>loader/entries/nixos-livecd.conf</filename> on the drive and change the <literal>root=</literal> field in the <literal>options</literal> line to point to your drive (see the documentation on <literal>root=</literal> in <link xlink:href="https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt"> the kernel documentation</link> for more details). </para> </listitem> <listitem> <para> If you want to load the contents of the ISO to ram after bootin (So you can remove the stick after bootup) you can append the parameter <literal>copytoram</literal> to the <literal>options</literal> field. </para> </listitem> </itemizedlist> </del> </para> </section>

version="5.0" xml:id="sec-installation"> <title>Installing NixOS</title> <del> <para> NixOS can be installed on BIOS or UEFI systems. The procedure for a UEFI installation is by and large the same as a BIOS installation. The differences are mentioned in the steps that follow. </para> <orderedlist> <listitem> <para> Boot from the CD. </para> <variablelist> <varlistentry> <term> UEFI systems </term> <listitem> <para> You should boot the live CD in UEFI mode (consult your specific hardware's documentation for instructions). You may find the <link xlink:href="http://www.rodsbooks.com/refind">rEFInd boot manager</link> useful. </para> </listitem> </varlistentry> </variablelist> </listitem> <listitem> <para> The CD contains a basic NixOS installation. (It also contains Memtest86+, useful if you want to test new hardware). When it’s finished booting, it should have detected most of your hardware. </para> </listitem> <listitem> <para> The NixOS manual is available on virtual console 8 (press Alt+F8 to access) or by running <command>nixos-help</command>. </para> </listitem> <listitem> <para> You get logged in as <literal>root</literal> (with empty password). </para> </listitem> <listitem> <para> If you downloaded the graphical ISO image, you can run <command>systemctl start display-manager</command> to start KDE. If you want to continue on the terminal, you can use <command>loadkeys</command> to switch to your preferred keyboard layout. (We even provide neo2 via <command>loadkeys de neo</command>!) </para> </listitem> <listitem> </del> <ins> <section xml:id="sec-installation-booting"> <title>Booting the system</title> <para> NixOS can be installed on BIOS or UEFI systems. The procedure for a UEFI installation is by and large the same as a BIOS installation. The differences are mentioned in the steps that follow. </para> <para> The installation media can be burned to a CD, or now more commonly, "burned" to a USB drive (see <xref linkend="sec-booting-from-usb"/>). </para> <para> The installation media contains a basic NixOS installation. When it’s finished booting, it should have detected most of your hardware. </para> <para> The NixOS manual is available on virtual console 8 (press Alt+F8 to access) or by running <command>nixos-help</command>. </para> <para> You are logged-in automatically as <literal>root</literal>. (The <literal>root</literal> user account has an empty password.) </para> <para> If you downloaded the graphical ISO image, you can run <command>systemctl start display-manager</command> to start KDE. If you want to continue on the terminal, you can use <command>loadkeys</command> to switch to your preferred keyboard layout. (We even provide neo2 via <command>loadkeys de neo</command>!) </para> <section xml:id="sec-installation-booting-networking"> <title>Networking in the installer</title> </ins> <para> The boot process should have brought up networking (check <command>ip a</command>). Networking is necessary for the installer, since it will

binaries). It’s best if you have a DHCP server on your network. Otherwise configure networking manually using <command>ifconfig</command>. </para> <para> To manually configure the network on the graphical installer, first disable network-manager with <command>systemctl stop network-manager</command>. </para> <para> To manually configure the wifi on the minimal installer, run <command>wpa_supplicant -B -i interface -c &lt;(wpa_passphrase 'SSID' 'key')</command>. </para> <del> </listitem> <listitem> </del> <para> If you would like to continue the installation from a different machine you need to activate the SSH daemon via <literal>systemctl start sshd</literal>. In order to be able to login you also need to set a password for <literal>root</literal> using <literal>passwd</literal>. </para> <del> </listitem> <listitem> </del> <ins> </section> </section> <section xml:id="sec-installation-partitioning"> <title>Partitioning and formatting</title> <para> The NixOS installer doesn’t do any partitioning or formatting, so you need to do that yourself. </para> <para> The NixOS installer ships with multiple partitioning tools. The examples below use <command>parted</command>, but also provides <command>fdisk</command>, <command>gdisk</command>, <command>cfdisk</command>, and <command>cgdisk</command>. </para> <para> The recommended partition scheme differs depending if the computer uses <emphasis>Legacy Boot</emphasis> or <emphasis>UEFI</emphasis>. </para> <section xml:id="sec-installation-partitioning-UEFI"> <title>UEFI (GPT)</title> </ins> <para> <del> The NixOS installer doesn’t do any partitioning or formatting yet, so you need to do that yourself. Use the following commands: <itemizedlist> </del> <ins> Here's an example partition scheme for UEFI, using <filename>/dev/sda</filename> as the device. <note> <para> You can safely ignore <command>parted</command>'s informational message about needing to update /etc/fstab. </para> </note> </para> <para> <orderedlist> </ins> <listitem> <para> <del> For partitioning: <command>fdisk</command>. <screen> # fdisk /dev/sda # <lineannotation>(or whatever device you want to install on)</lineannotation> -- for UEFI systems only > n      # <lineannotation>(create a new partition for /boot)</lineannotation> > 3      # <lineannotation>(make it a partition number 3)</lineannotation> >        # <lineannotation>(press enter to accept the default)</lineannotation> > +512M  # <lineannotation>(the size of the UEFI boot partition)</lineannotation> > t      # <lineannotation>(change the partition type ...)</lineannotation> > 3      # <lineannotation>(... of the boot partition ...)</lineannotation> > 1      # <lineannotation>(... to 'UEFI System')</lineannotation> -- for BIOS or UEFI systems > n      # <lineannotation>(create a new partition for /swap)</lineannotation> > 2      # <lineannotation>(make it a partition number 2)</lineannotation> >        # <lineannotation>(press enter to accept the default)</lineannotation> > +8G    # <lineannotation>(the size of the swap partition, set to whatever you like)</lineannotation> > n      # <lineannotation>(create a new partition for /)</lineannotation> > 1      # <lineannotation>(make it a partition number 1)</lineannotation> >        # <lineannotation>(press enter to accept the default)</lineannotation> >        # <lineannotation>(press enter to accept the default and use the rest of the remaining space)</lineannotation> > a      # <lineannotation>(make the partition bootable)</lineannotation> > x      # <lineannotation>(enter expert mode)</lineannotation> > f      # <lineannotation>(fix up the partition ordering)</lineannotation> > r      # <lineannotation>(exit expert mode)</lineannotation> > w      # <lineannotation>(write the partition table to disk and exit)</lineannotation></screen> </del> <ins> Create a <emphasis>GPT</emphasis> partition table. <screen language="commands"># parted /dev/sda -- mklabel gpt</screen> </ins> </para> </listitem> <listitem> <para> <ins> Add a <emphasis>swap</emphasis> partition. The size required will vary according to needs, here a 8GiB one is created. The space left in front (512MiB) will be used by the boot partition. <screen language="commands"># parted /dev/sda -- mkpart primary linux-swap 512MiB 8.5GiB</screen> <note> <para> The swap partition size rules are no different than for other Linux distributions. </para> </note> </para> </listitem> <listitem> <para> Next, add the <emphasis>root</emphasis> partition. This will fill the remainder ending part of the disk. <screen language="commands"># parted /dev/sda -- mkpart primary 8.5GiB -1MiB</screen> </para> </listitem> <listitem> <para> Finally, the <emphasis>boot</emphasis> partition. NixOS by default uses the ESP (EFI system partition) as its <emphasis>/boot</emphasis> partition. It uses the initially reserved 512MiB at the start of the disk. <screen language="commands"># parted /dev/sda -- mkpart ESP fat32 1M 512MiB # parted /dev/sda -- set 3 boot on</screen> </para> </listitem> </orderedlist> </para> <para> Once complete, you can follow with <xref linkend="sec-installation-partitioning-formatting"/>. </para> </section> <section xml:id="sec-installation-partitioning-MBR"> <title>Legacy Boot (MBR)</title> <para> Here's an example partition scheme for Legacy Boot, using <filename>/dev/sda</filename> as the device. <note> <para> You can safely ignore <command>parted</command>'s informational message about needing to update /etc/fstab. </para> </note> </para> <para> <orderedlist> <listitem> <para> Create a <emphasis>MBR</emphasis> partition table. <screen language="commands"># parted /dev/sda -- mklabel msdos</screen> </para> </listitem> <listitem> <para> Add a <emphasis>swap</emphasis> partition. The size required will vary according to needs, here a 8GiB one is created. <screen language="commands"># parted /dev/sda -- mkpart primary linux-swap 1M 8GiB</screen> <note> <para> The swap partition size rules are no different than for other Linux distributions. </para> </note> </para> </listitem> <listitem> <para> Finally, add the <emphasis>root</emphasis> partition. This will fill the remainder of the disk. <screen language="commands"># parted /dev/sda -- mkpart primary 8GiB -1s</screen> </para> </listitem> </orderedlist> </para> <para> Once complete, you can follow with <xref linkend="sec-installation-partitioning-formatting"/>. </para> </section> <section xml:id="sec-installation-partitioning-formatting"> <title>Formatting</title> <para> Use the following commands: <itemizedlist> <listitem> <para> </ins> For initialising Ext4 partitions: <command>mkfs.ext4</command>. It is recommended that you assign a unique symbolic label to the file system using the option <option>-L <replaceable>label</replaceable></option>,

</listitem> </itemizedlist> </para> <del> </listitem> <listitem> <para> Mount the target file system on which NixOS should be installed on <filename>/mnt</filename>, e.g. </del> <ins> </section> </section> <section xml:id="sec-installation-installing"> <title>Installing</title> <orderedlist> <listitem> <para> Mount the target file system on which NixOS should be installed on <filename>/mnt</filename>, e.g. </ins> <screen> # mount /dev/disk/by-label/nixos /mnt </screen> <del> </para> </listitem> <listitem> <variablelist> <varlistentry> <term> UEFI systems </term> <listitem> <para> Mount the boot file system on <filename>/mnt/boot</filename>, e.g. </del> <ins> </para> </listitem> <listitem> <variablelist> <varlistentry> <term> UEFI systems </term> <listitem> <para> Mount the boot file system on <filename>/mnt/boot</filename>, e.g. </ins> <screen> # mkdir -p /mnt/boot # mount /dev/disk/by-label/boot /mnt/boot </screen> <del> </para> </listitem> </varlistentry> </variablelist> </listitem> <listitem> <para> If your machine has a limited amount of memory, you may want to activate swap devices now (<command>swapon <replaceable>device</replaceable></command>). The installer (or rather, the build actions that it may spawn) may need quite a bit of RAM, depending on your configuration. </del> <ins> </para> </listitem> </varlistentry> </variablelist> </listitem> <listitem> <para> If your machine has a limited amount of memory, you may want to activate swap devices now (<command>swapon <replaceable>device</replaceable></command>). The installer (or rather, the build actions that it may spawn) may need quite a bit of RAM, depending on your configuration. </ins> <screen> # swapon /dev/sda2</screen> <del> </para> </listitem> <listitem> <para> You now need to create a file <filename>/mnt/etc/nixos/configuration.nix</filename> that specifies the intended configuration of the system. This is because NixOS has a <emphasis>declarative</emphasis> configuration model: you create or edit a description of the desired configuration of your system, and then NixOS takes care of making it happen. The syntax of the NixOS configuration file is described in <xref linkend="sec-configuration-syntax"/>, while a list of available configuration options appears in <xref </del> <ins> </para> </listitem> <listitem> <para> You now need to create a file <filename>/mnt/etc/nixos/configuration.nix</filename> that specifies the intended configuration of the system. This is because NixOS has a <emphasis>declarative</emphasis> configuration model: you create or edit a description of the desired configuration of your system, and then NixOS takes care of making it happen. The syntax of the NixOS configuration file is described in <xref linkend="sec-configuration-syntax"/>, while a list of available configuration options appears in <xref </ins> linkend="ch-options"/>. A minimal example is shown in <del> <xref </del> <ins> <xref </ins> linkend="ex-config"/>. <del> </para> <para> The command <command>nixos-generate-config</command> can generate an initial configuration file for you: </del> <ins> </para> <para> The command <command>nixos-generate-config</command> can generate an initial configuration file for you: </ins> <screen> # nixos-generate-config --root /mnt</screen> <del> You should then edit <filename>/mnt/etc/nixos/configuration.nix</filename> to suit your needs: </del> <ins> You should then edit <filename>/mnt/etc/nixos/configuration.nix</filename> to suit your needs: </ins> <screen> # nano /mnt/etc/nixos/configuration.nix </screen> <del> If you’re using the graphical ISO image, other editors may be available (such as <command>vim</command>). If you have network access, you can also install other editors — for instance, you can install Emacs by running <literal>nix-env -i emacs</literal>. </para> <variablelist> <varlistentry> <term> BIOS systems </term> <listitem> <para> You <emphasis>must</emphasis> set the option <xref linkend="opt-boot.loader.grub.device"/> to specify on which disk the GRUB boot loader is to be installed. Without it, NixOS cannot boot. </para> </listitem> </varlistentry> <varlistentry> <term> UEFI systems </term> <listitem> <para> You <emphasis>must</emphasis> set the option <xref linkend="opt-boot.loader.systemd-boot.enable"/> to <literal>true</literal>. <command>nixos-generate-config</command> should do this automatically for new configurations when booted in UEFI mode. </para> <para> You may want to look at the options starting with <option><link linkend="opt-boot.loader.efi.canTouchEfiVariables">boot.loader.efi</link></option> and <option><link linkend="opt-boot.loader.systemd-boot.enable">boot.loader.systemd</link></option> as well. </para> </listitem> </varlistentry> </variablelist> <para> If there are other operating systems running on the machine before installing NixOS, the <xref linkend="opt-boot.loader.grub.useOSProber"/> option can be set to <literal>true</literal> to automatically add them to the grub menu. </para> <para> Another critical option is <option>fileSystems</option>, specifying the file systems that need to be mounted by NixOS. However, you typically don’t need to set it yourself, because <command>nixos-generate-config</command> sets it automatically in <filename>/mnt/etc/nixos/hardware-configuration.nix</filename> from your currently mounted file systems. (The configuration file <filename>hardware-configuration.nix</filename> is included from <filename>configuration.nix</filename> and will be overwritten by future invocations of <command>nixos-generate-config</command>; thus, you generally should not modify it.) </para> <note> </del> <ins> If you’re using the graphical ISO image, other editors may be available (such as <command>vim</command>). If you have network access, you can also install other editors — for instance, you can install Emacs by running <literal>nix-env -i emacs</literal>. </para> <variablelist> <varlistentry> <term> BIOS systems </term> <listitem> <para> You <emphasis>must</emphasis> set the option <xref linkend="opt-boot.loader.grub.device"/> to specify on which disk the GRUB boot loader is to be installed. Without it, NixOS cannot boot. </para> </listitem> </varlistentry> <varlistentry> <term> UEFI systems </term> <listitem> <para> You <emphasis>must</emphasis> set the option <xref linkend="opt-boot.loader.systemd-boot.enable"/> to <literal>true</literal>. <command>nixos-generate-config</command> should do this automatically for new configurations when booted in UEFI mode. </para> <para> You may want to look at the options starting with <option><link linkend="opt-boot.loader.efi.canTouchEfiVariables">boot.loader.efi</link></option> and <option><link linkend="opt-boot.loader.systemd-boot.enable">boot.loader.systemd</link></option> as well. </para> </listitem> </varlistentry> </variablelist> </ins> <para> <del> Depending on your hardware configuration or type of file system, you may need to set the option <option>boot.initrd.kernelModules</option> to include the kernel modules that are necessary for mounting the root file system, otherwise the installed system will not be able to boot. (If this happens, boot from the CD again, mount the target file system on <filename>/mnt</filename>, fix <filename>/mnt/etc/nixos/configuration.nix</filename> and rerun <filename>nixos-install</filename>.) In most cases, <command>nixos-generate-config</command> will figure out the required modules. </del> <ins> If there are other operating systems running on the machine before installing NixOS, the <xref linkend="opt-boot.loader.grub.useOSProber"/> option can be set to <literal>true</literal> to automatically add them to the grub menu. </ins> </para> <del> </note> </listitem> <listitem> <para> Do the installation: </del> <ins> <para> Another critical option is <option>fileSystems</option>, specifying the file systems that need to be mounted by NixOS. However, you typically don’t need to set it yourself, because <command>nixos-generate-config</command> sets it automatically in <filename>/mnt/etc/nixos/hardware-configuration.nix</filename> from your currently mounted file systems. (The configuration file <filename>hardware-configuration.nix</filename> is included from <filename>configuration.nix</filename> and will be overwritten by future invocations of <command>nixos-generate-config</command>; thus, you generally should not modify it.) </para> <note> <para> Depending on your hardware configuration or type of file system, you may need to set the option <option>boot.initrd.kernelModules</option> to include the kernel modules that are necessary for mounting the root file system, otherwise the installed system will not be able to boot. (If this happens, boot from the installation media again, mount the target file system on <filename>/mnt</filename>, fix <filename>/mnt/etc/nixos/configuration.nix</filename> and rerun <filename>nixos-install</filename>.) In most cases, <command>nixos-generate-config</command> will figure out the required modules. </para> </note> </listitem> <listitem> <para> Do the installation: </ins> <screen> # nixos-install</screen> <del> Cross fingers. If this fails due to a temporary problem (such as a network issue while downloading binaries from the NixOS binary cache), you can just re-run <command>nixos-install</command>. Otherwise, fix your <filename>configuration.nix</filename> and then re-run <command>nixos-install</command>. </para> <para> As the last step, <command>nixos-install</command> will ask you to set the password for the <literal>root</literal> user, e.g. </del> <ins> Cross fingers. If this fails due to a temporary problem (such as a network issue while downloading binaries from the NixOS binary cache), you can just re-run <command>nixos-install</command>. Otherwise, fix your <filename>configuration.nix</filename> and then re-run <command>nixos-install</command>. </para> <para> As the last step, <command>nixos-install</command> will ask you to set the password for the <literal>root</literal> user, e.g. </ins> <screen> setting root password... Enter new UNIX password: *** <del> Retype new UNIX password: *** </screen> <note> <para> For unattended installations, it is possible to use <command>nixos-install --no-root-passwd</command> in order to disable the password prompt entirely. </para> </note> </para> </listitem> <listitem> <para> If everything went well: </del> <ins> Retype new UNIX password: ***</screen> <note> <para> For unattended installations, it is possible to use <command>nixos-install --no-root-passwd</command> in order to disable the password prompt entirely. </para> </note> </para> </listitem> <listitem> <para> If everything went well: </ins> <screen> <del> # reboot</screen> </para> </listitem> <listitem> <para> You should now be able to boot into the installed NixOS. The GRUB boot menu shows a list of <emphasis>available configurations</emphasis> (initially just one). Every time you change the NixOS configuration (see <link </del> <ins> # reboot</screen> </para> </listitem> <listitem> <para> You should now be able to boot into the installed NixOS. The GRUB boot menu shows a list of <emphasis>available configurations</emphasis> (initially just one). Every time you change the NixOS configuration (see <link </ins> linkend="sec-changing-config">Changing Configuration</link> <del> ), a new item is added to the menu. This allows you to easily roll back to a previous configuration if something goes wrong. </para> <para> You should log in and change the <literal>root</literal> password with <command>passwd</command>. </para> <para> You’ll probably want to create some user accounts as well, which can be done with <command>useradd</command>: </del> <ins> ), a new item is added to the menu. This allows you to easily roll back to a previous configuration if something goes wrong. </para> <para> You should log in and change the <literal>root</literal> password with <command>passwd</command>. </para> <para> You’ll probably want to create some user accounts as well, which can be done with <command>useradd</command>: </ins> <screen> $ useradd -c 'Eelco Dolstra' -m eelco $ passwd eelco</screen> <del> </para> <para> You may also want to install some software. For instance, </del> <ins> </para> <para> You may also want to install some software. For instance, </ins> <screen> $ nix-env -qa *</screen> <del> shows what packages are available, and </del> <ins> shows what packages are available, and </ins> <screen> $ nix-env -i w3m</screen> <del> install the <literal>w3m</literal> browser. </para> </listitem> </orderedlist> <para> To summarise, <xref linkend="ex-install-sequence" /> shows a typical sequence of commands for installing NixOS on an empty hard drive (here <filename>/dev/sda</filename>). <xref linkend="ex-config" </del> <ins> install the <literal>w3m</literal> browser. </para> </listitem> </orderedlist> </section> <section xml:id="sec-installation-summary"> <title>Installation summary</title> <para> To summarise, <xref linkend="ex-install-sequence" /> shows a typical sequence of commands for installing NixOS on an empty hard drive (here <filename>/dev/sda</filename>). <xref linkend="ex-config" </ins> /> shows a <del> corresponding configuration Nix expression. </para> <example xml:id='ex-install-sequence'> <title>Commands for Installing NixOS on <filename>/dev/sda</filename></title> <screen> # fdisk /dev/sda # <lineannotation>(or whatever device you want to install on)</lineannotation> -- for UEFI systems only > n      # <lineannotation>(create a new partition for /boot)</lineannotation> > 3      # <lineannotation>(make it a partition number 3)</lineannotation> >        # <lineannotation>(press enter to accept the default)</lineannotation> > +512M  # <lineannotation>(the size of the UEFI boot partition)</lineannotation> > t      # <lineannotation>(change the partition type ...)</lineannotation> > 3      # <lineannotation>(... of the boot partition ...)</lineannotation> > 1      # <lineannotation>(... to 'UEFI System')</lineannotation> -- for BIOS or UEFI systems > n      # <lineannotation>(create a new partition for /swap)</lineannotation> > 2      # <lineannotation>(make it a partition number 2)</lineannotation> >        # <lineannotation>(press enter to accept the default)</lineannotation> > +8G    # <lineannotation>(the size of the swap partition)</lineannotation> > n      # <lineannotation>(create a new partition for /)</lineannotation> > 1      # <lineannotation>(make it a partition number 1)</lineannotation> >        # <lineannotation>(press enter to accept the default)</lineannotation> >        # <lineannotation>(press enter to accept the default and use the rest of the remaining space)</lineannotation> > a      # <lineannotation>(make the partition bootable)</lineannotation> > x      # <lineannotation>(enter expert mode)</lineannotation> > f      # <lineannotation>(fix up the partition ordering)</lineannotation> > r      # <lineannotation>(exit expert mode)</lineannotation> > w      # <lineannotation>(write the partition table to disk and exit)</lineannotation> </del> <ins> corresponding configuration Nix expression. </para> <example xml:id="ex-partition-scheme-MBR"> <title>Example partition schemes for NixOS on <filename>/dev/sda</filename> (MBR)</title> <screen language="commands"> # parted /dev/sda -- mklabel msdos # parted /dev/sda -- mkpart primary linux-swap 1M 8GiB # parted /dev/sda -- mkpart primary 8GiB -1s</screen> </example> <example xml:id="ex-partition-scheme-UEFI"> <title>Example partition schemes for NixOS on <filename>/dev/sda</filename> (UEFI)</title> <screen language="commands"> # parted /dev/sda -- mklabel gpt # parted /dev/sda -- mkpart primary linux-swap 512MiB 8.5GiB # parted /dev/sda -- mkpart primary 8.5GiB -1MiB # parted /dev/sda -- mkpart ESP fat32 1M 512MiB # parted /dev/sda -- set 3 boot on</screen> </example> <example xml:id="ex-install-sequence"> <title>Commands for Installing NixOS on <filename>/dev/sda</filename></title> <para> With a partitioned disk. <screen language="commands"> </ins> # mkfs.ext4 -L nixos /dev/sda1 # mkswap -L swap /dev/sda2 # swapon /dev/sda2

# nano /mnt/etc/nixos/configuration.nix # nixos-install # reboot</screen> <del> </example> <example xml:id='ex-config'> <title>NixOS Configuration</title> </del> <ins> </para> </example> <example xml:id='ex-config'> <title>NixOS Configuration</title> </ins> <screen> { config, pkgs, ... }: { imports = [

services.sshd.enable = true; } </screen> <del> </example> <xi:include href="installing-usb.xml" /> <xi:include href="installing-pxe.xml" /> <xi:include href="installing-virtualbox-guest.xml" /> <xi:include href="installing-from-other-distro.xml" /> <xi:include href="installing-behind-a-proxy.xml" /> </del> <ins> </example> </section> <section xml:id="sec-installation-additional-notes"> <title>Additional installation notes</title> <xi:include href="installing-usb.xml" /> <xi:include href="installing-pxe.xml" /> <xi:include href="installing-virtualbox-guest.xml" /> <xi:include href="installing-from-other-distro.xml" /> <xi:include href="installing-behind-a-proxy.xml" /> </section> </ins> </chapter>