-
Notifications
You must be signed in to change notification settings - Fork 0
volume
XADE edited this page Dec 10, 2023
·
1 revision
Partition Table
- must be finalized by user, prior to executing the script according to requirements
- is completely under the responsibility of user and is Not altered by the script
NAME FSTYPE
sda
├─sda1 vfat
├─sda2
├─sda3 ntfs
├─sda4 vfat
├─sda5 btrfs
├─sda6 crypto_LUKS
│ └─cryptroot btrfs
├─sda7 crypto_LUKS
│ └─cryptlvm LVM2_member
│ └─vg1-a btrfs
├─sda8 LVM2_member
│ ├─vg2-a btrfs
│ └─vg2-b
├─sda9 LVM2_member
│ ├─vg3-a crypto_LUKS
│ │ └─cryptlvm2 LVM2_member
│ │ └─vg4-d btrfs
│ └─vg3-b
┌┈▶ └─sda10 LVM2_member
└┬▶ sdb LVM2_member
└┈┈cryptraid crypto_LUKS
└─raidA btrfs
┌┈▶ sdw LVM2_member
├─▶ sdx LVM2_member
├─▶ sdy LVM2_member
└┬▶ sdz LVM2_member
└┈─raidB btrfs
Supported devices will be listed by the script during installation. So, only choose from one of those.
- it's recommended to choose the same FAT device for all installations.
/dev/sda1
/dev/sda4
> FAT device : /dev/sda4
/dev/sda5
/dev/mapper/cryptroot
/dev/mapper/vg1-a
/dev/mapper/vg2-a
/dev/mapper/vg4-d
/dev/mapper/raidA
/dev/mapper/raidB
BTRFS partition
> ROOT device : /dev/sda5
LVM
> ROOT device : /dev/mapper/vg2-a
> ROOT device : /dev/mapper/raidB
> ROOT device : /dev/mapper/cryptroot
> ROOT device : /dev/mapper/vg1-a
> ROOT device : /dev/mapper/vg4-d
LUKS on LVM-RAID
> ROOT device : /dev/mapper/raidA
AFTER installation completes, One can REBOOT.
on successful boot up, login as root with empty password.
Enable necessary services like dhcp to access network.
Don't wanna install but bootstrap ?
- try leaving the above prompts empty
- root file system will be inside
/tmp/name_of_installation
- definitely won't for GUIX