diff --git a/doc/devel/3. Use Cases b/doc/devel/3. Use Cases index 1437c96..e6e17f0 100644 --- a/doc/devel/3. Use Cases +++ b/doc/devel/3. Use Cases @@ -137,7 +137,20 @@ Phases: 3.2.3 Bootable information -------------------------- -[TODO] + - Addition of a boot image to a volume. + - In most cases, the catalog and the boot image itself is added to the + iso tree. + - Alternatively, user can select to add a hidden images, i.e., images + that don't appear in the iso tree. + - Modification of boot image attributes: + - bootable flag + - load segment + - load size + - Automatic patching of isolinux images. User needs to set whether to apply + this. + - Reading of El-Torito info from multisession images. Modification of its + attributes. + - Removing of El-Torito images 3.2.4 Other operations diff --git a/doc/devel/UML/eltorito.violet b/doc/devel/UML/eltorito.violet new file mode 100644 index 0000000..4a5df24 --- /dev/null +++ b/doc/devel/UML/eltorito.violet @@ -0,0 +1,399 @@ + + + + + + + + Volume + + + + + + 731.0 + 193.0 + + + + + + + + ElToritoCatalog + + + + + + 474.0 + 192.0 + + + + + + + + bootable : bool +type : enum +partition_type : enum +load_seg : uint16 +load_size : uint16 +patch_isolinux : bool + + + + + BootImage + + + + + + 469.0 + 329.0 + + + + + + + + In a future we can support several boot +images + + + + + + 666.0 + 301.0 + + + + + + + + img : boolean + + + + + BootNode + + + + + + 186.0 + 186.0 + + + + + + + + + + TreeNode + + + + + + iso_tree + + + + + 180.0 + 40.0 + + + + + + + + 193.0 + 69.0 + + + + + + + + The img field is an implementation detail, used +to distinguish between the catalog node and the image +node. This is needed when the image is written. + + + + + + 347.0 + 82.0 + + + + + + + + block : uint32_t + + + + + PreviousSessionImage + + + + + + 539.0 + 509.0 + + + + + + + + «interface» +DataSource + + + + + + 746.5857864376269 + 511.3380951166248 + + + + + + + + block : uint32_t + + + + + PreviousSessionCatalog + + + + + + 287.0 + 292.0 + + + + + + + + The support for growing or modify El-Torito images +is really hard to implement. The reason: when the +image is hidden, we don't know its size, so the best we +can do is just refer to the old image. When modify, all +we can do may be wrong. + + + + + + 644.3271028254218 + 382.5643050695048 + + + + + + + + path : char * + + + + + LocalImage + + + + + + 424.0 + 511.0 + + + + + + + + Once we have support for all El-Torito features, namelly +multiple boot images, this type is not needed, the info +can be read and cached in a new catalog. + + + + + + 52.325113060119634 + 434.0605969759931 + + + + + + + + + + + + + 1 image + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0..1 boot_cat + + + + + + + + + + + + + + + 0..1 node + + + + + + + + + + + + + + + + + + + + 0..1 node + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/doc/devel/UML/eltorito.violet.png b/doc/devel/UML/eltorito.violet.png new file mode 100644 index 0000000..07fd2b9 Binary files /dev/null and b/doc/devel/UML/eltorito.violet.png differ