man/repart.d.xml

   1 <?xml version='1.0'?>
   2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   3   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
   4 <refentry id="repart.d" conditional='ENABLE_REPART'
   5           xmlns:xi="http://www.w3.org/2001/XInclude">
   6
   7   <refentryinfo>
   8     <title>repart.d</title>
   9     <productname>systemd</productname>
  10   </refentryinfo>
  11
  12   <refmeta>
  13     <refentrytitle>repart.d</refentrytitle>
  14     <manvolnum>5</manvolnum>
  15   </refmeta>
  16
  17   <refnamediv>
  18     <refname>repart.d</refname>
  19     <refpurpose>Partition Definition Files for Automatic Boot-Time Repartitioning</refpurpose>
  20   </refnamediv>
  21
  22   <refsynopsisdiv>
  23     <para><literallayout><filename>/etc/repart.d/*.conf</filename>
  24 <filename>/run/repart.d/*.conf</filename>
  25 <filename>/usr/lib/repart.d/*.conf</filename>
  26     </literallayout></para>
  27   </refsynopsisdiv>
  28
  29   <refsect1>
  30     <title>Description</title>
  31
  32     <para><filename>repart.d/*.conf</filename> files describe basic properties of partitions of block
  33     devices of the local system. They may be used to declare types, names and sizes of partitions that shall
  34     exist. The
  35     <citerefentry><refentrytitle>systemd-repart</refentrytitle><manvolnum>8</manvolnum></citerefentry>
  36     service reads these files and attempts to add new partitions currently missing and enlarge existing
  37     partitions according to these definitions. Operation is generally incremental, i.e. when applied, what
  38     exists already is left intact, and partitions are never shrunk, moved or deleted.</para>
  39
  40     <para>These definition files are useful for implementing operating system images that are prepared and
  41     delivered with minimally sized images (for example lacking any state or swap partitions), and which on
  42     first boot automatically take possession of any remaining disk space following a few basic rules.</para>
  43
  44     <para>Currently, support for partition definition files is only implemented for GPT partitition
  45     tables.</para>
  46
  47     <para>Partition files are generally matched against any partitions already existing on disk in a simple
  48     algorithm: the partition files are sorted by their filename (ignoring the directory prefix), and then
  49     compared in order against existing partitions matching the same partition type UUID. Specifically, the
  50     first existing partition with a specific partition type UUID is assigned the first definition file with
  51     the same partition type UUID, and the second existing partition with a specific type UUID the second
  52     partition file with the same type UUID, and so on. Any left-over partition files that have no matching
  53     existing partition are assumed to define new partition that shall be created. Such partitions are
  54     appended to the end of the partition table, in the order defined by their names utilizing the first
  55     partition slot greater than the highest slot number currently in use. Any existing partitions that have
  56     no matching partition file are left as they are.</para>
  57
  58     <para>Note that these definitions may only be used to created and initialize new partitions or grow
  59     existing ones. In the latter case it will not grow the contained files systems however; separate
  60     mechanisms, such as
  61     <citerefentry><refentrytitle>systemd-growfs</refentrytitle><manvolnum>8</manvolnum></citerefentry> may be
  62     used to grow the file systems inside of these partitions.</para>
  63   </refsect1>
  64
  65   <refsect1>
  66     <title>[Partition] Section Options</title>
  67
  68     <variablelist>
  69       <varlistentry>
  70         <term><varname>Type=</varname></term>
  71
  72         <listitem><para>The GPT partition type UUID to match. This may be a GPT partition type UUID such as
  73         <constant>4f68bce3-e8cd-4db1-96e7-fbcaf984b709</constant>, or one of the following special
  74         identifiers:</para>
  75
  76         <table>
  77           <title>GPT partition type identifiers</title>
  78
  79           <tgroup cols='2' align='left' colsep='1' rowsep='1'>
  80             <colspec colname="name" />
  81             <colspec colname="explanation" />
  82
  83             <thead>
  84               <row>
  85                 <entry>Identifier</entry>
  86                 <entry>Explanation</entry>
  87               </row>
  88             </thead>
  89
  90             <tbody>
  91               <row>
  92                 <entry><constant>esp</constant></entry>
  93                 <entry>EFI System Partition</entry>
  94               </row>
  95
  96               <row>
  97                 <entry><constant>xbootldr</constant></entry>
  98                 <entry>Extended Boot Loader Partition</entry>
  99               </row>
 100
 101               <row>
 102                 <entry><constant>swap</constant></entry>
 103                 <entry>Swap partition</entry>
 104               </row>
 105
 106               <row>
 107                 <entry><constant>home</constant></entry>
 108                 <entry>Home (<filename>/home/</filename>) partition</entry>
 109               </row>
 110
 111               <row>
 112                 <entry><constant>srv</constant></entry>
 113                 <entry>Server data (<filename>/srv/</filename>) partition</entry>
 114               </row>
 115
 116               <row>
 117                 <entry><constant>var</constant></entry>
 118                 <entry>Variable data (<filename>/var/</filename>) partition</entry>
 119               </row>
 120
 121               <row>
 122                 <entry><constant>tmp</constant></entry>
 123                 <entry>Temporary data (<filename>/var/tmp/</filename>) partition</entry>
 124               </row>
 125
 126               <row>
 127                 <entry><constant>linux-generic</constant></entry>
 128                 <entry>Generic Linux file system partition</entry>
 129               </row>
 130
 131               <row>
 132                 <entry><constant>root</constant></entry>
 133                 <entry>Root file system partition type appropriate for the local architecture (an alias for an architecture root file system partition type listed below, e.g. <constant>root-x86-64</constant>)</entry>
 134               </row>
 135
 136               <row>
 137                 <entry><constant>root-verity</constant></entry>
 138                 <entry>Verity data for the root file system partition for the local architecture</entry>
 139               </row>
 140
 141               <row>
 142                 <entry><constant>root-secondary</constant></entry>
 143                 <entry>Root file system partition of the secondary architecture of the local architecture (usually the matching 32bit architecture for the local 64bit architecture)</entry>
 144               </row>
 145
 146               <row>
 147                 <entry><constant>root-secondary-verity</constant></entry>
 148                 <entry>Verity data for the root file system partition of the secondary architecture</entry>
 149               </row>
 150
 151               <row>
 152                 <entry><constant>root-x86</constant></entry>
 153                 <entry>Root file system partition for the x86 (32bit, aka i386) architecture</entry>
 154               </row>
 155
 156               <row>
 157                 <entry><constant>root-x86-verity</constant></entry>
 158                 <entry>Verity data for the x86 (32bit) root file system partition</entry>
 159               </row>
 160
 161               <row>
 162                 <entry><constant>root-x86-64</constant></entry>
 163                 <entry>Root file system partition for the x86_64 (64bit, aka amd64) architecture</entry>
 164               </row>
 165
 166               <row>
 167                 <entry><constant>root-x86-64-verity</constant></entry>
 168                 <entry>Verity data for the x86_64 (64bit) root file system partition</entry>
 169               </row>
 170
 171               <row>
 172                 <entry><constant>root-arm</constant></entry>
 173                 <entry>Root file system partition for the ARM (32bit) architecture</entry>
 174               </row>
 175
 176               <row>
 177                 <entry><constant>root-arm-verity</constant></entry>
 178                 <entry>Verity data for the ARM (32bit) root file system partition</entry>
 179               </row>
 180
 181               <row>
 182                 <entry><constant>root-arm64</constant></entry>
 183                 <entry>Root file system partition for the ARM (64bit, aka aarch64) architecture</entry>
 184               </row>
 185
 186               <row>
 187                 <entry><constant>root-arm64-verity</constant></entry>
 188                 <entry>Verity data for the ARM (64bit, aka aarch64) root file system partition</entry>
 189               </row>
 190
 191               <row>
 192                 <entry><constant>root-ia64</constant></entry>
 193                 <entry>Root file system partition for the ia64 architecture</entry>
 194               </row>
 195
 196               <row>
 197                 <entry><constant>root-ia64-verity</constant></entry>
 198                 <entry>Verity data for the ia64 root file system partition</entry>
 199               </row>
 200
 201               <row>
 202                 <entry><constant>usr</constant></entry>
 203                 <entry><filename>/usr/</filename> file system partition type appropriate for the local architecture (an alias for an architecture <filename>/usr/</filename> file system partition type listed below, e.g. <constant>usr-x86-64</constant>)</entry>
 204               </row>
 205
 206               <row>
 207                 <entry><constant>usr-verity</constant></entry>
 208                 <entry>Verity data for the <filename>/usr/</filename> file system partition for the local architecture</entry>
 209               </row>
 210
 211               <row>
 212                 <entry><constant>usr-secondary</constant></entry>
 213                 <entry><filename>/usr/</filename> file system partition of the secondary architecture of the local architecture (usually the matching 32bit architecture for the local 64bit architecture)</entry>
 214               </row>
 215
 216               <row>
 217                 <entry><constant>usr-secondary-verity</constant></entry>
 218                 <entry>Verity data for the <filename>/usr/</filename> file system partition of the secondary architecture</entry>
 219               </row>
 220
 221               <row>
 222                 <entry><constant>usr-x86</constant></entry>
 223                 <entry><filename>/usr/</filename> file system partition for the x86 (32bit, aka i386) architecture</entry>
 224               </row>
 225
 226               <row>
 227                 <entry><constant>usr-x86-verity</constant></entry>
 228                 <entry>Verity data for the x86 (32bit) <filename>/usr/</filename> file system partition</entry>
 229               </row>
 230
 231               <row>
 232                 <entry><constant>usr-x86-64</constant></entry>
 233                 <entry><filename>/usr/</filename> file system partition for the x86_64 (64bit, aka amd64) architecture</entry>
 234               </row>
 235
 236               <row>
 237                 <entry><constant>usr-x86-64-verity</constant></entry>
 238                 <entry>Verity data for the x86_64 (64bit) <filename>/usr/</filename> file system partition</entry>
 239               </row>
 240
 241               <row>
 242                 <entry><constant>usr-arm</constant></entry>
 243                 <entry><filename>/usr/</filename> file system partition for the ARM (32bit) architecture</entry>
 244               </row>
 245
 246               <row>
 247                 <entry><constant>usr-arm-verity</constant></entry>
 248                 <entry>Verity data for the ARM (32bit) <filename>/usr/</filename> file system partition</entry>
 249               </row>
 250
 251               <row>
 252                 <entry><constant>usr-arm64</constant></entry>
 253                 <entry><filename>/usr/</filename> file system partition for the ARM (64bit, aka aarch64) architecture</entry>
 254               </row>
 255
 256               <row>
 257                 <entry><constant>usr-arm64-verity</constant></entry>
 258                 <entry>Verity data for the ARM (64bit, aka aarch64) <filename>/usr/</filename> file system partition</entry>
 259               </row>
 260
 261               <row>
 262                 <entry><constant>usr-ia64</constant></entry>
 263                 <entry><filename>/usr/</filename> file system partition for the ia64 architecture</entry>
 264               </row>
 265
 266               <row>
 267                 <entry><constant>usr-ia64-verity</constant></entry>
 268                 <entry>Verity data for the ia64 <filename>/usr/</filename> file system partition</entry>
 269               </row>
 270             </tbody>
 271           </tgroup>
 272         </table>
 273
 274         <para>This setting defaults to <constant>linux-generic</constant>.</para>
 275
 276         <para>Most of the partition type UUIDs listed above are defined in the <ulink
 277         url="https://systemd.io/DISCOVERABLE_PARTITIONS">Discoverable Partitions
 278         Specification</ulink>.</para></listitem>
 279       </varlistentry>
 280
 281       <varlistentry>
 282         <term><varname>Label=</varname></term>
 283
 284         <listitem><para>The textual label to assign to the partition if none is assigned yet. Note that this
 285         setting is not used for matching. It is also not used when a label is already set for an existing
 286         partition. It is thus only used when a partition is newly created or when an existing one had a no
 287         label set (that is: an empty label). If not specified a label derived from the partition type is
 288         automatically used. Simple specifier expansion is supported, see below.</para></listitem>
 289       </varlistentry>
 290
 291       <varlistentry>
 292         <term><varname>UUID=</varname></term>
 293
 294         <listitem><para>The UUID to assign to the partition if none is assigned yet. Note that this
 295         setting is not used for matching. It is also not used when a UUID is already set for an existing
 296         partition. It is thus only used when a partition is newly created or when an existing one had a
 297         all-zero UUID set. If not specified a UUID derived from the partition type is automatically
 298         used.</para></listitem>
 299       </varlistentry>
 300
 301       <varlistentry>
 302         <term><varname>Priority=</varname></term>
 303
 304         <listitem><para>A numeric priority to assign to this partition, in the range -2147483648…2147483647,
 305         with smaller values indicating higher priority, and higher values indicating smaller priority. This
 306         priority is used in case the configured size constraints on the defined partitions do not permit
 307         fitting all partitions onto the available disk space. If the partitions do not fit, the highest
 308         numeric partition priority of all defined partitions is determined, and all defined partitions with
 309         this priority are removed from the list of new partitions to create (which may be multiple, if the
 310         same priority is used for multiple partitions). The fitting algorithm is then tried again. If the
 311         partitions still do not fit, the now highest numeric partition priority is determined, and the
 312         matching partitions removed too, and so on. Partitions of a priority of 0 or lower are never
 313         removed. If all partitions with a priority above 0 are removed and the partitions still do not fit on
 314         the device the operation fails. Note that this priority has no effect on ordering partitions, for
 315         that use the alphabetical order of the filenames of the partition definition files. Defaults to
 316         0.</para></listitem>
 317       </varlistentry>
 318
 319       <varlistentry>
 320         <term><varname>Weight=</varname></term>
 321
 322         <listitem><para>A numeric weight to assign to this partition in the range 0…1000000. Available disk
 323         space is assigned the defined partitions according to their relative weights (subject to the size
 324         constraints configured with <varname>SizeMinBytes=</varname>, <varname>SizeMaxBytes=</varname>), so
 325         that a partition with weight 2000 gets double the space as one with weight 1000, and a partition with
 326         weight 333 a third of that. Defaults to 1000.</para>
 327
 328         <para>The <varname>Weight=</varname> setting is used to distribute available disk space in an
 329         "elastic" fashion, based on the disk size and existing partitions. If a partition shall have a fixed
 330         size use both <varname>SizeMinBytes=</varname> and <varname>SizeMaxBytes=</varname> with the same
 331         value in order to fixate the size to one value, in which case the weight has no
 332         effect.</para></listitem>
 333       </varlistentry>
 334
 335       <varlistentry>
 336         <term><varname>PaddingWeight=</varname></term>
 337
 338         <listitem><para>Similar to <varname>Weight=</varname> but sets a weight for the free space after the
 339         partition (the "padding"). When distributing available space the weights of all partitions and all
 340         defined padding is summed, and then each partition and padding gets the fraction defined by its
 341         weight. Defaults to 0, i.e. by default no padding is applied.</para>
 342
 343         <para>Padding is useful if empty space shall be left for later additions or a safety margin at the
 344         end of the device or between partitions.</para></listitem>
 345       </varlistentry>
 346
 347       <varlistentry>
 348         <term><varname>SizeMinBytes=</varname></term>
 349         <term><varname>SizeMaxBytes=</varname></term>
 350
 351         <listitem><para>Specifies minimum and maximum size constraints in bytes. Takes the usual K, M, G, T,
 352         …  suffixes (to the base of 1024). If <varname>SizeMinBytes=</varname> is specified the partition is
 353         created at or grown to at least the specified size. If <varname>SizeMaxBytes=</varname> is specified
 354         the partition is created at or grown to at most the specified size. The precise size is determined
 355         through the weight value value configured with <varname>Weight=</varname>, see above. When
 356         <varname>SizeMinBytes=</varname> is set equal to <varname>SizeMaxBytes=</varname> the configured
 357         weight has no effect as the partition is explicitly sized to the specified fixed value. Note that
 358         partitions are never created smaller than 4096 bytes, and since partitions are never shrunk the
 359         previous size of the partition (in case the partition already exists) is also enforced as lower bound
 360         for the new size. The values should be specified as multiples of 4096 bytes, and are rounded upwards
 361         (in case of <varname>SizeMinBytes=</varname>) or downwards (in case of
 362         <varname>SizeMaxBytes=</varname>) otherwise. If the backing device does not provide enough space to
 363         fulfill the constraints placing the partition will fail. For partitions that shall be created,
 364         depending on the setting of <varname>Priority=</varname> (see above) the partition might be dropped
 365         and the placing algorithm restarted. By default a minimum size constraint of 10M and no maximum size
 366         constraint is set.</para></listitem>
 367       </varlistentry>
 368
 369       <varlistentry>
 370         <term><varname>PaddingMinBytes=</varname></term>
 371         <term><varname>PaddingMaxBytes=</varname></term>
 372
 373         <listitem><para>Specifies minimum and maximum size constraints in bytes for the free space after the
 374         partition (the "padding"). Semantics are similar to <varname>SizeMinBytes=</varname> and
 375         <varname>SizeMaxBytes=</varname>, except that unlike partition sizes free space can be shrunk and can
 376         be as small as zero. By default no size constraints on padding are set, so that only
 377         <varname>PaddingWeight=</varname> determines the size of the padding applied.</para></listitem>
 378       </varlistentry>
 379
 380       <varlistentry>
 381         <term><varname>CopyBlocks=</varname></term>
 382
 383         <listitem><para>Takes a path to a regular file, block device node or directory. If specified and the
 384         partition is newly created the data from the specified path is written to the newly created
 385         partition, on the block level. If a directory is specified the backing block device of the file
 386         system the directory is on is determined and the data read directly from that. This option is useful
 387         to efficiently replicate existing file systems on the block level on a new partition, for example to
 388         build a simple OS installer or OS image builder.</para>
 389
 390         <para>The file specified here must have a size that is a multiple of the basic block size 512 and not
 391         be empty. If this option is used, the size allocation algorithm is slightly altered: the partition is
 392         created as least as big as required to fit the data in, i.e. the data size is an additional minimum
 393         size value taken into consideration for the allocation algorithm, similar to and in addition to the
 394         <varname>SizeMin=</varname> value configured above.</para>
 395
 396         <para>This option has no effect if the partition it is declared for already exists, i.e. existing
 397         data is never overwritten. Note that the data is copied in before the partition table is updated,
 398         i.e. before the partition actually is persistently created. This provides robustness: it is
 399         guaranteed that the partition either doesn't exist or exists fully populated; it is not possible that
 400         the partition exists but is not or only partially populated.</para>
 401
 402         <para>This option cannot be combined with <varname>Format=</varname> or
 403         <varname>CopyFiles=</varname>.</para></listitem>
 404       </varlistentry>
 405
 406       <varlistentry>
 407         <term><varname>Format=</varname></term>
 408
 409         <listitem><para>Takes a file system name, such as <literal>ext4</literal>, <literal>btrfs</literal>,
 410         <literal>xfs</literal> or <literal>vfat</literal>, or the special value <literal>swap</literal>. If
 411         specified and the partition is newly created it is formatted with the specified file system (or as
 412         swap device). The file system UUID and label are automatically derived from the partition UUID and
 413         label. If this option is used, the size allocation algorithm is slightly altered: the partition is
 414         created as least as big as required for the minimal file system of the specified type (or 4KiB if the
 415         minimal size is not known).</para>
 416
 417         <para>This option has no effect if the partition already exists.</para>
 418
 419         <para>Similar to the behaviour of <varname>CopyBlocks=</varname> the file system is formatted before
 420         the partition is created, ensuring that the partition only ever exists with a fully initialized
 421         file system.</para>
 422
 423         <para>This option cannot be combined with <varname>CopyBlocks=</varname>.</para></listitem>
 424       </varlistentry>
 425
 426       <varlistentry>
 427         <term><varname>CopyFiles=</varname></term>
 428
 429         <listitem><para>Takes a pair of colon separated absolute file system paths. The first path refers to
 430         a source file or directory on the host, the second path refers to a target in the file system of the
 431         newly created partition and formatted file system. This setting may be used to copy files or
 432         directories from the host into the file system that is created due to the <varname>Format=</varname>
 433         option. If <varname>CopyFiles=</varname> is used without <varname>Format=</varname> specified
 434         explicitly, <literal>Format=</literal> with a suitable default is implied (currently
 435         <literal>ext4</literal>, but this may change in the future). This option may be used multiple times
 436         to copy multiple files or directories from host into the newly formatted file system. The colon and
 437         second path may be omitted in which case the source path is also used as the target path (relative to
 438         the root of the newly created file system). If the source path refers to a directory it is copied
 439         recursively.</para>
 440
 441         <para>This option has no effect if the partition already exists: it cannot be used to copy additional
 442         files into an existing partition, it may only be used to populate a file system created anew.</para>
 443
 444         <para>The copy operation is executed before the file system is registered in the partition table,
 445         thus ensuring that a file system populated this way only ever exists fully initialized.</para>
 446
 447         <para>This option cannot be combined with <varname>CopyBlocks=</varname>.</para></listitem>
 448       </varlistentry>
 449
 450       <varlistentry>
 451         <term><varname>Encrypt=</varname></term>
 452
 453         <listitem><para>Takes a boolean parameter, defaulting to false. If true the partition will be
 454         formatted with a LUKS2 superblock, before the blocks configured with <varname>CopyBlocks=</varname>
 455         are copied in or the file system configured with <varname>Format=</varname> is created.</para>
 456
 457         <para>The LUKS2 UUID is automatically derived from the partition UUID in a stable fashion. A single
 458         key is added to the LUKS2 superblock, configurable with the <option>--key-file=</option> switch to
 459         <command>systemd-repart</command>.</para>
 460
 461         <para>When used this slightly alters the size allocation logic as the implicit, minimal size limits
 462         of <varname>Format=</varname> and <varname>CopyBlocks=</varname> are increased by the space necessary
 463         for the LUKS2 superblock (see above).</para>
 464
 465         <para>This option has no effect if the partition already exists.</para></listitem>
 466       </varlistentry>
 467
 468       <varlistentry>
 469         <term><varname>FactoryReset=</varname></term>
 470
 471         <listitem><para>Takes a boolean argument. If specified the partition is marked for removal during a
 472         factory reset operation. This functionality is useful to implement schemes where images can be reset
 473         into their original state by removing partitions and creating them anew. Defaults to off.</para></listitem>
 474       </varlistentry>
 475     </variablelist>
 476   </refsect1>
 477
 478   <refsect1>
 479     <title>Specifiers</title>
 480
 481     <para>Specifiers may be used in the <varname>Label=</varname> setting. The following expansions are understood:</para>
 482       <table class='specifiers'>
 483         <title>Specifiers available</title>
 484         <tgroup cols='3' align='left' colsep='1' rowsep='1'>
 485           <colspec colname="spec" />
 486           <colspec colname="mean" />
 487           <colspec colname="detail" />
 488           <thead>
 489             <row>
 490               <entry>Specifier</entry>
 491               <entry>Meaning</entry>
 492               <entry>Details</entry>
 493             </row>
 494           </thead>
 495           <tbody>
 496             <xi:include href="standard-specifiers.xml" xpointer="a"/>
 497             <xi:include href="standard-specifiers.xml" xpointer="b"/>
 498             <xi:include href="standard-specifiers.xml" xpointer="B"/>
 499             <xi:include href="standard-specifiers.xml" xpointer="H"/>
 500             <xi:include href="standard-specifiers.xml" xpointer="l"/>
 501             <xi:include href="standard-specifiers.xml" xpointer="m"/>
 502             <xi:include href="standard-specifiers.xml" xpointer="o"/>
 503             <xi:include href="standard-specifiers.xml" xpointer="v"/>
 504             <xi:include href="standard-specifiers.xml" xpointer="w"/>
 505             <xi:include href="standard-specifiers.xml" xpointer="W"/>
 506             <xi:include href="standard-specifiers.xml" xpointer="percent"/>
 507           </tbody>
 508         </tgroup>
 509       </table>
 510   </refsect1>
 511
 512   <refsect1>
 513     <title>Examples</title>
 514
 515     <example>
 516       <title>Grow the root partition to the full disk size at first boot</title>
 517
 518       <para>With the following file the root partition is automatically grown to the full disk if possible during boot.</para>
 519
 520       <para><programlisting># /usr/lib/repart.d/50-root.conf
 521 [Partition]
 522 Type=root
 523 </programlisting></para>
 524     </example>
 525
 526     <example>
 527       <title>Create a swap and home partition automatically on boot, if missing</title>
 528
 529       <para>The home partition gets all available disk space while the swap partition gets 1G at most and 64M
 530       at least. We set a priority > 0 on the swap partition to ensure the swap partition is not used if not
 531       enough space is available. For every three bytes assigned to the home partition the swap partition gets
 532       assigned one.</para>
 533
 534       <para><programlisting># /usr/lib/repart.d/60-home.conf
 535 [Partition]
 536 Type=home
 537 </programlisting></para>
 538
 539       <para><programlisting># /usr/lib/repart.d/70-swap.conf
 540 [Partition]
 541 Type=swap
 542 SizeMinBytes=64M
 543 SizeMaxBytes=1G
 544 Priority=1
 545 Weight=333
 546 </programlisting></para>
 547     </example>
 548
 549     <example>
 550       <title>Create B partitions in an A/B Verity setup, if missing</title>
 551
 552       <para>Let's say the vendor intends to update OS images in an A/B setup, i.e. with two root partitions
 553       (and two matching Verity partitions) that shall be used alternatingly during upgrades. To minimize
 554       image sizes the original image is shipped only with one root and one Verity partition (the "A" set),
 555       and the second root and Verity partitions (the "B" set) shall be created on first boot on the free
 556       space on the medium.</para>
 557
 558       <para><programlisting># /usr/lib/repart.d/50-root.conf
 559 [Partition]
 560 Type=root
 561 SizeMinBytes=512M
 562 SizeMaxBytes=512M
 563 </programlisting></para>
 564
 565       <para><programlisting># /usr/lib/repart.d/60-root-verity.conf
 566 [Partition]
 567 Type=root-verity
 568 SizeMinBytes=64M
 569 SizeMaxBytes=64M
 570 </programlisting></para>
 571
 572       <para>The definitions above cover the "A" set of root partition (of a fixed 512M size) and Verity
 573       partition for the root partition (of a fixed 64M size). Let's use symlinks to create the "B" set of
 574       partitions, since after all they shall have the same properties and sizes as the "A" set.</para>
 575
 576 <para><programlisting># ln -s 50-root.conf /usr/lib/repart.d/70-root-b.conf
 577 # ln -s 60-root-verity.conf /usr/lib/repart.d/80-root-verity-b.conf
 578 </programlisting></para>
 579     </example>
 580
 581   </refsect1>
 582
 583   <refsect1>
 584     <title>See Also</title>
 585     <para>
 586       <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 587       <citerefentry><refentrytitle>systemd-repart</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
 588       <citerefentry project='man-pages'><refentrytitle>sfdisk</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 589     </para>
 590   </refsect1>
 591
 592 </refentry>