summaryrefslogtreecommitdiff
path: root/Specifications/DiscoverablePartitionsSpec.mdwn
diff options
context:
space:
mode:
authorLennartPoettering <LennartPoettering@web>2014-03-07 09:45:00 -0800
committerwww <iki-www@freedesktop.org>2014-03-07 09:45:00 -0800
commit1fd45ee3b27bf18e4c33bf9efad5847c3466826f (patch)
tree47562f06c9ec3a810da26a7dfef9930fc15e6e21 /Specifications/DiscoverablePartitionsSpec.mdwn
parentf03e49c9ecae590f12c5dc6511793d5e919023aa (diff)
Diffstat (limited to 'Specifications/DiscoverablePartitionsSpec.mdwn')
-rw-r--r--Specifications/DiscoverablePartitionsSpec.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/Specifications/DiscoverablePartitionsSpec.mdwn b/Specifications/DiscoverablePartitionsSpec.mdwn
index 342ffb59..edf613b6 100644
--- a/Specifications/DiscoverablePartitionsSpec.mdwn
+++ b/Specifications/DiscoverablePartitionsSpec.mdwn
@@ -111,3 +111,11 @@ Doing a similar automatic discovery of btrfs subvolumes and mounting them automa
### Why are you taking my /etc/fstab away?
We are not. /etc/fstab always overrides automatic discovery. We are just trying to make the boot and installation processes of Linux a bit more robust and self-descriptive.
+
+### Why did you only define the root partition for x86 and x86-64?
+
+Well, the automatic discovery of the root partition is defined to operate on the disk the EFI System Partition (ESP) that was used for booting is located on. Since EFI only exists on x86 and x86-64 so far we only defined root partition GUIDs for these two architectures. Should EFI be more common on other architectures too we can define additional GUIDs for them.
+
+### Why define distinct root partition GUIDs for the various architectures?
+
+In order to allow disk images that may be booted on multiple architectures we want to enable discovery of the appropriate root disk on each architecture.