mirror of
https://github.com/TECHNOFAB11/disko.git
synced 2025-12-11 23:50:05 +01:00
upgrade-guide: fix markdown syntax
This commit is contained in:
parent
859e7c5be2
commit
8cb5b9656a
1 changed files with 14 additions and 11 deletions
|
|
@ -1,4 +1,4 @@
|
||||||
2023-04-07 7d70009
|
# 2023-04-07 7d70009
|
||||||
|
|
||||||
Changes:
|
Changes:
|
||||||
|
|
||||||
|
|
@ -9,6 +9,7 @@ Changes:
|
||||||
Updated example/zfs.nix file:
|
Updated example/zfs.nix file:
|
||||||
|
|
||||||
```nix
|
```nix
|
||||||
|
{
|
||||||
datasets = {
|
datasets = {
|
||||||
zfs_fs = {
|
zfs_fs = {
|
||||||
type = "zfs_fs";
|
type = "zfs_fs";
|
||||||
|
|
@ -29,17 +30,18 @@ datasets = {
|
||||||
size = "10M";
|
size = "10M";
|
||||||
content = {
|
content = {
|
||||||
type = "filesystem";
|
type = "filesystem";
|
||||||
...
|
# ...
|
||||||
|
}
|
||||||
Note: The `zfs_type` attribute has been replaced with a type attribute for each dataset, and the `size` attribute is only available for `zfs_volume`.
|
|
||||||
These changes have been reflected in the example/zfs.nix file.
|
|
||||||
```
|
```
|
||||||
|
|
||||||
2023-04-07 654ecb3
|
Note: The `zfs_type` attribute has been replaced with a type attribute for each dataset, and the `size` attribute is only available for `zfs_volume`.
|
||||||
|
These changes have been reflected in the `example/zfs.nix` file.
|
||||||
|
|
||||||
|
# 2023-04-07 654ecb3
|
||||||
|
|
||||||
The `lvm_lv` type is always part of an `lvm_vg` and it is no longer necessary to specify the type.
|
The `lvm_lv` type is always part of an `lvm_vg` and it is no longer necessary to specify the type.
|
||||||
|
|
||||||
This means that if you were using the `lvm_lv` type in your code, you should remove it and make sure to only use the `lvm_vg` type.
|
This means that if you were using the `lvm_lv` type in your code, you should remove it.
|
||||||
For example, if you were defining an `lvm_lv` type like this:
|
For example, if you were defining an `lvm_lv` type like this:
|
||||||
|
|
||||||
```nix
|
```nix
|
||||||
|
|
@ -48,6 +50,7 @@ For example, if you were defining an `lvm_lv` type like this:
|
||||||
size = "10G";
|
size = "10G";
|
||||||
# ...
|
# ...
|
||||||
}
|
}
|
||||||
|
```
|
||||||
|
|
||||||
You should now define it like this:
|
You should now define it like this:
|
||||||
|
|
||||||
|
|
@ -92,14 +95,14 @@ After:
|
||||||
|
|
||||||
Note that the `type` field is no longer necessary and should be removed from your code.
|
Note that the `type` field is no longer necessary and should be removed from your code.
|
||||||
|
|
||||||
2023-03-22 2624af6
|
# 2023-03-22 2624af6
|
||||||
|
|
||||||
disk config now needs to be inside a disko.devices attrset always
|
disk config now needs to be inside a disko.devices attrset always
|
||||||
|
|
||||||
2023-03-22 0577409
|
# 2023-03-22 0577409
|
||||||
|
|
||||||
the extraArgs option in the luks type was renamed to extraFormatArgs
|
the extraArgs option in the luks type was renamed to extraFormatArgs
|
||||||
|
|
||||||
2023-02-14 6d630b8
|
# 2023-02-14 6d630b8
|
||||||
|
|
||||||
btrfs, btrfs_subvol filesystem and lvm_lv extraArgs are now lists
|
btrfs, `btrfs_subvol` filesystem and `lvm_lv` extraArgs are now lists
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue