curtin already supports extended partitions, as the filer suggests, the missing bit is the size of the extended partition in that dictionary:
I don't have the actual disk sizes, but, something like this will work.
- device: sda flag: extended id: sda-part4 number: 4 type: partition size: 9999220736B - device: sda flag: logical id: sda-part5 name: sda-part5 number: 5 size: 9999220736B
curtin already exercises extended/logical partition paths, for example, this 10G disk defines a 3G primary, and 5G extended, and then 2G logical and 3G logical.
config: - id: sda type: disk ptable: msdos model: QEMU HARDDISK path: /dev/vdb name: main_disk - id: sda1 type: partition size: 3GB device: sda flag: boot - id: sda_extended type: partition size: 5G flag: extended device: sda - id: sda2 type: partition size: 2G flag: logical device: sda - id: sda3 type: partition size: 3G flag: logical device: sda
curtin already supports extended partitions, as the filer suggests, the missing bit is the size of the extended partition in that dictionary:
I don't have the actual disk sizes, but, something like this will work.
- device: sda
flag: extended
id: sda-part4
number: 4
type: partition
size: 9999220736B
- device: sda
flag: logical
id: sda-part5
name: sda-part5
number: 5
size: 9999220736B
curtin already exercises extended/logical partition paths, for example, this 10G disk
defines a 3G primary, and 5G extended, and then 2G logical and 3G logical.
config:
- id: sda
type: disk
ptable: msdos
model: QEMU HARDDISK
path: /dev/vdb
name: main_disk
- id: sda1
type: partition
size: 3GB
device: sda
flag: boot
- id: sda_extended
type: partition
size: 5G
flag: extended
device: sda
- id: sda2
type: partition
size: 2G
flag: logical
device: sda
- id: sda3
type: partition
size: 3G
flag: logical
device: sda