|
40 | 40 | <citerefentry><refentrytitle>repart.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>. |
41 | 41 | </para> |
42 | 42 |
|
43 | | - <para>If invoked with no arguments, it operates on the block device backing the root file system partition |
44 | | - of the OS, thus growing and adding partitions of the booted OS image itself. When called in the initial |
45 | | - RAM disk it operates on the block device backing <filename>/sysroot/</filename> instead, i.e. on the |
46 | | - block device the system will soon transition into. The <filename>systemd-repart.service</filename> |
47 | | - service is generally run at boot in the initial RAM disk, in order to augment the partition table of the |
48 | | - OS before its partitions are mounted. <command>systemd-repart</command> (mostly) operates in a purely |
49 | | - incremental mode: it only grows existing and adds new partitions; it does not shrink, delete or move |
50 | | - existing partitions. The service is intended to be run on every boot, but when it detects that the |
51 | | - partition table already matches the installed <filename>repart.d/*.conf</filename> configuration |
52 | | - files, it executes no operation.</para> |
| 43 | + <para>If invoked with no arguments, it operates on the block device backing the root file system |
| 44 | + partition of the running OS, thus growing and adding partitions of the booted OS image itself. If |
| 45 | + <varname>--image=</varname> is used it will operate on the specified image file. When called in the |
| 46 | + <literal>initrd</literal> it operates on the block device backing <filename>/sysroot/</filename> instead, |
| 47 | + i.e. on the block device the system will soon transition into. The |
| 48 | + <filename>systemd-repart.service</filename> service is generally run at boot in the initial RAM disk, in |
| 49 | + order to augment the partition table of the OS before its partitions are |
| 50 | + mounted. <command>systemd-repart</command> (mostly) operates in a purely incremental mode: it only grows |
| 51 | + existing and adds new partitions; it does not shrink, delete or move existing partitions. The service is |
| 52 | + intended to be run on every boot, but when it detects that the partition table already matches the |
| 53 | + installed <filename>repart.d/*.conf</filename> configuration files, it executes no operation.</para> |
53 | 54 |
|
54 | 55 | <para><command>systemd-repart</command> is intended to be used when deploying OS images, to automatically |
55 | 56 | adjust them to the system they are running on, during first boot. This way the deployed image can be |
|
251 | 252 | <term><option>--root=</option></term> |
252 | 253 |
|
253 | 254 | <listitem><para>Takes a path to a directory to use as root file system when searching for |
254 | | - <filename>repart.d/*.conf</filename> files and for the machine ID file to use as seed. By default |
255 | | - when invoked on the regular system this defaults to the host's root file system |
| 255 | + <filename>repart.d/*.conf</filename> files, for the machine ID file to use as seed and for the |
| 256 | + <varname>CopyFiles=</varname> and <varname>CopyBlocks=</varname> source files and directories. By |
| 257 | + default when invoked on the regular system this defaults to the host's root file system |
256 | 258 | <filename>/</filename>. If invoked from the initial RAM disk this defaults to |
257 | 259 | <filename>/sysroot/</filename>, so that the tool operates on the configuration and machine ID stored |
258 | 260 | in the root file system later transitioned into itself.</para></listitem> |
259 | 261 | </varlistentry> |
260 | 262 |
|
| 263 | + <varlistentry> |
| 264 | + <term><option>--image=</option></term> |
| 265 | + |
| 266 | + <listitem><para>Takes a path to a disk image file or device to mount and use in a similar fashion to |
| 267 | + <option>--root=</option>, see above.</para></listitem> |
| 268 | + </varlistentry> |
| 269 | + |
261 | 270 | <varlistentry> |
262 | 271 | <term><option>--seed=</option></term> |
263 | 272 |
|
|
0 commit comments