nixo
/
guix-devel
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: Use a consistent partitioning scheme. 

* doc/guix.texi (Preparing for Installation): Consistently refer to the ESP as
/dev/sda1; root file system as /dev/sda2; and swap as /dev/sda3.
This commit is contained in:
Marius Bakke 2018-06-26 11:59:51 +02:00
parent a1fa2691cd
commit 671dd8d6e6
No known key found for this signature in database
GPG Key ID: A2A06DF2A33A54FA
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/guix.texi
View File

@ -8641,21 +8641,21 @@ create a file system on the relevant partition(s)@footnote{Currently
GuixSD only supports ext4 and btrfs file systems. In particular, code GuixSD only supports ext4 and btrfs file systems. In particular, code
that reads file system UUIDs and labels only works for these file system that reads file system UUIDs and labels only works for these file system
types.}. For the ESP, if you have one and assuming it is types.}. For the ESP, if you have one and assuming it is
@file{/dev/sda2}, run: @file{/dev/sda1}, run:
@example @example
mkfs.fat -F32 /dev/sda2 mkfs.fat -F32 /dev/sda1
@end example @end example
Preferably, assign file systems a label so that you can easily and Preferably, assign file systems a label so that you can easily and
reliably refer to them in @code{file-system} declarations (@pxref{File reliably refer to them in @code{file-system} declarations (@pxref{File
Systems}). This is typically done using the @code{-L} option of Systems}). This is typically done using the @code{-L} option of
@command{mkfs.ext4} and related commands. So, assuming the target root @command{mkfs.ext4} and related commands. So, assuming the target root
partition lives at @file{/dev/sda1}, a file system with the label partition lives at @file{/dev/sda2}, a file system with the label
@code{my-root} can be created with: @code{my-root} can be created with:
@example @example
mkfs.ext4 -L my-root /dev/sda1 mkfs.ext4 -L my-root /dev/sda2
@end example @end example
@cindex encrypted disk @cindex encrypted disk
@ -8663,12 +8663,12 @@ If you are instead planning to encrypt the root partition, you can use
the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html, the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html,
@uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}}, @uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}},
@code{man cryptsetup}} for more information.) Assuming you want to @code{man cryptsetup}} for more information.) Assuming you want to
store the root partition on @file{/dev/sda1}, the command sequence would store the root partition on @file{/dev/sda2}, the command sequence would
be along these lines: be along these lines:
@example @example
cryptsetup luksFormat /dev/sda1 cryptsetup luksFormat /dev/sda2
cryptsetup open --type luks /dev/sda1 my-partition cryptsetup open --type luks /dev/sda2 my-partition
mkfs.ext4 -L my-root /dev/mapper/my-partition mkfs.ext4 -L my-root /dev/mapper/my-partition
@end example @end example
@ -8688,11 +8688,11 @@ by @code{guix system init} afterwards.
Finally, if you plan to use one or more swap partitions (@pxref{Memory Finally, if you plan to use one or more swap partitions (@pxref{Memory
Concepts, swap space,, libc, The GNU C Library Reference Manual}), make Concepts, swap space,, libc, The GNU C Library Reference Manual}), make
sure to initialize them with @command{mkswap}. Assuming you have one sure to initialize them with @command{mkswap}. Assuming you have one
swap partition on @file{/dev/sda2}, you would run: swap partition on @file{/dev/sda3}, you would run:
@example @example
mkswap /dev/sda2 mkswap /dev/sda3
swapon /dev/sda2 swapon /dev/sda3
@end example @end example
Alternatively, you may use a swap file. For example, assuming that in Alternatively, you may use a swap file. For example, assuming that in