docs(os): Typo (#3)
This commit is contained in:
parent
0cd149f8cb
commit
412eb93c60
@ -78,7 +78,8 @@ export ARCHZBM_ZFSPROPS_NO_ENCRYPTION=yup
|
||||
The script takes the following installation steps.
|
||||
|
||||
1. Install ZFS tools and kernel module with [github.com/eoli3n/archiso-zfs](https://github.com/eoli3n/archiso-zfs)
|
||||
1. Create one encrypted ZFS zpool on top of `BF00` partition, password `password`
|
||||
1. Create one ZFS zpool on top of `BF00` partition, encrypted and compressed datasets, password `password`
|
||||
1. _See paragraphs [Compression](#compression)/[Encryption](#encryption) to optionally disable properties_
|
||||
1. Create dataset for Arch Linux and `/home`
|
||||
1. Install Arch Linux into pool
|
||||
1. Add ZFSBootMenu to `EF00` partition if it doesn't exist already
|
||||
@ -216,7 +217,7 @@ In order to generate a new master key after you've changed your user key as ment
|
||||
- With `-v` we get verbose progress output
|
||||
- Argument `-u` makes sure the dataset does not get mounted after transfer. ZFS would mount it into `/` which wouldn't be helpful since we're currently using that filesystem ourselves.
|
||||
- We set encryption properties `keyformat`, `keylocation` and most importantly `encryption`. The latter will turn our transferred dataset into its own `encryptionroot` which in turn generates a new master key. The auto-generated new master key gets wrapped with our updated passphrase in `keylocation`. This basically reencrypts all data in this dataset during transfer.
|
||||
- We set `mountpoint` and `canmount` as well as a `org.zfsbootmenu:commandline` as we would for any new system dataset.
|
||||
- We set `mountpoint` and `canmount` as well as an `org.zfsbootmenu:commandline` as we would for any new system dataset.
|
||||
1. Change zpool's `bootfs` property to new system dataset
|
||||
```
|
||||
zpool set bootfs=zpool/root/archlinux-frn zpool
|
||||
|
Loading…
x
Reference in New Issue
Block a user