summaryrefslogtreecommitdiff
path: root/Specifications/DiscoverablePartitionsSpec.mdwn
diff options
context:
space:
mode:
authorLennartPoettering <LennartPoettering@web>2014-03-07 11:49:41 -0800
committerwww <iki-www@freedesktop.org>2014-03-07 11:49:41 -0800
commit4e99950bd0491eee82236d1fc7a2ed0bd54c1cd5 (patch)
tree7379077d4214917bf3544d1abf4e8cc5063b8005 /Specifications/DiscoverablePartitionsSpec.mdwn
parentea70292f60d0075ac24c846e5ff7fbe7982faa3a (diff)
Diffstat (limited to 'Specifications/DiscoverablePartitionsSpec.mdwn')
-rw-r--r--Specifications/DiscoverablePartitionsSpec.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/Specifications/DiscoverablePartitionsSpec.mdwn b/Specifications/DiscoverablePartitionsSpec.mdwn
index 821d9881..7dbfe9a5 100644
--- a/Specifications/DiscoverablePartitionsSpec.mdwn
+++ b/Specifications/DiscoverablePartitionsSpec.mdwn
@@ -86,7 +86,7 @@ Other GPT type IDs might be used on Linux, for example to mark software RAID or
An *installer* that repartitions the hard disk, should use the above GUID partition types for the partitions it creates. It is recommended to use expressive partition names in the GPT partition table, for example "Home Partition", "Server Data Partition" and similar, possibly localized.
-An *installer* which supports a "manual partitioning" UI is may choose to prepopulate the UI with existing swap, /home and /srv partitions identified with the GPT type GUIDS above. Note that it shall only prepopulate the UI with the Extended Boot Partition if its boot loader supports the <a href="http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/">Boot Loader Specification</a>. The installer should not prepopulate such an UI with any identified root partition unless the intention is too overwrite an existing operating system that might be installed.
+An *installer* which supports a "manual partitioning" UI is may choose to prepopulate the UI with swap, /home and /srv partitions of pre-existing Linux OS installations, identified with the GPT type GUIDS above. Note that it shall only prepopulate the UI with the Extended Boot Partition if its boot loader supports the <a href="http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/">Boot Loader Specification</a>. The installer should not prepopulate such an UI with any identified root partition unless the intention is too overwrite an existing operating system that might be installed.
An *installer* may omit creating entries in /etc/fstab for root, /home, /srv and for the swap partitions if they use these GUID partition types, and are the first partitions on the disk of each type. If the ESP shall be mounted to /boot it may omit creating entries in /etc/fstab for it, too. If an extended boot partition is used or if the EFI partition shall not be mounted to /boot it *must* create /etc/fstab entries for them. If other partitions are used (for example for /var or /usr), the installer *must* register these in /etc/fstab. The root= parameter passed to the kernel by the boot loader may be omitted too, if the root partition is the first one on the disk of its type. If the root partition is not the first one on the disk, the root= parameter *must* be passed to the kernel by the boot loader. An installer that mounts a root, /home or /srv file system with the partition types defined as above which contains a LUKS header *must* call the device mapper device "root", "home" and "srv". This is necessary to ensure that the automatic discovery will never result in different device mapper names than any static configuration by the installer, thus eliminating possibly naming conflicts and ambiguities.