Skip to content

Commit

Permalink
chroot: Fix formatting/style issues.
Browse files Browse the repository at this point in the history
  • Loading branch information
flexibeast committed Jun 19, 2020
1 parent 55bc576 commit 943dbdf
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 9 deletions.
3 changes: 1 addition & 2 deletions src/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,7 @@
- [Partitioning Notes](./installation/live-images/partitions.md)
- [Installation Guide](./installation/live-images/guide.md)
- [Advanced Installation](./installation/guides/index.md)
- [Installation via chroot (x86 or
x86_64)](./installation/guides/chroot.md)
- [Installation via chroot (x86/x86_64)](./installation/guides/chroot.md)
- [Full Disk Encryption](./installation/guides/fde.md)
- [musl](./installation/musl.md)
- [Configuration](./config/index.md)
Expand Down
14 changes: 7 additions & 7 deletions src/installation/guides/chroot.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Installation via chroot (x86 or x86_64)
# Installation via chroot (x86/x86_64)

This guide details the process of manually installing Void via a chroot on an
x86 or x86_64 PC architecture. It is assumed that you have a familiarity with
Expand All @@ -14,11 +14,11 @@ base system by unpacking a ROOTFS tarball.

The **XBPS method** requires that the host operating system have XBPS installed.
This may be an existing installation of Void, an official [live
image](../live-images/prep.md) or any Linux installation running a [statically
image](../live-images/prep.md), or any Linux installation running a [statically
linked XBPS](../../xbps/troubleshooting/static.md).

The **ROOTFS method** requires only a host operating system that can enter a
Linux chroot and that has [tar(1)](https://man.voidlinux.org/tar.1) and
Linux chroot and that has both [tar(1)](https://man.voidlinux.org/tar.1) and
[xz(1)](https://man.voidlinux.org/xz.1) installed. This method may be preferable
if you wish to install Void using a different Linux distribution.

Expand All @@ -45,11 +45,11 @@ For a UEFI booting system, make sure to create an EFI System Partition (ESP).
The ESP should have the partition type "EFI System" (code `EF00`) and be
formatted as FAT32 using [mkfs.vfat(8)](https://man.voidlinux.org/mkfs.vfat.8).

If you're unsure what partitions to create, create a 1GB partition of type `EFI
System` (code `EF00`), then create a second partition of type `Linux Filesystem`
If you're unsure what partitions to create, create a 1GB partition of type "EFI
System" (code `EF00`), then create a second partition of type "Linux Filesystem"
(code `8300`) using the remainder of the drive.

Format these partitions as FAT32 and ext4, respectively.
Format these partitions as FAT32 and ext4, respectively:

```
# mkfs.vfat /dev/sda1
Expand Down Expand Up @@ -107,7 +107,7 @@ does not need to be the same. If your host is running an x86_64 operating
system, any of the three architectures can be installed (whether the host is
musl or glibc), but an i686 host can only install i686 distributions.

Use [xbps-install](https://man.voidlinux.org/xbps-install.1) to bootstrap the
Use [xbps-install(1)](https://man.voidlinux.org/xbps-install.1) to bootstrap the
installation by installing the `base-system` metapackage:

```
Expand Down

0 comments on commit 943dbdf

Please sign in to comment.