mirror of
https://github.com/systemd/systemd
synced 2026-03-10 15:14:58 +01:00
Compare commits
No commits in common. "a1f782e44c363ee1c2e8fd0cdd54ea523d72807c" and "a9f2f1c13a8583e249cd454c701ef09637ea76ed" have entirely different histories.
a1f782e44c
...
a9f2f1c13a
@ -225,12 +225,10 @@ appliance-like installations.
|
|||||||
|
|
||||||
### What partitioning tools will create a DPS-compliant partition table?
|
### What partitioning tools will create a DPS-compliant partition table?
|
||||||
|
|
||||||
As of util-linux 2.25.2, the `fdisk` tool provides type codes to create the
|
As of util-linux 2.25.2, the fdisk tool provides type codes to create the root,
|
||||||
root, home, and swap partitions that the DPS expects, By default, `fdisk` will
|
home, and swap partitions that the DPS expects, but the gdisk tool (version
|
||||||
create an old-style MBR, not a GPT, so typing `l` to list partition types will
|
0.8.10) and its variants do not support creation of a root file system with a
|
||||||
not show the choices to let you set the correct UUID. Make sure to first create
|
matching type code. By default, fdisk will create an old-style MBR, not a GPT,
|
||||||
an empty GPT, then type `l` in order for the DPS-compliant type codes to be
|
so typing 'l' to list partition types will not show the choices that the root
|
||||||
available.
|
partition with the correct UUID. You must first create an empty GPT and then
|
||||||
|
type 'l' in order for the DPS-compliant type codes to be available.
|
||||||
The `gdisk` tool (from version 1.0.5 onward) and its variants (`sgdisk`,
|
|
||||||
`cgdisk`) also support creation of partitions with a matching type code.
|
|
||||||
|
|||||||
@ -84,8 +84,8 @@
|
|||||||
be invoked to write out any queued message data to the transport.</para>
|
be invoked to write out any queued message data to the transport.</para>
|
||||||
|
|
||||||
<para><function>sd_bus_message_send()</function> is the same as <function>sd_bus_send()</function> but
|
<para><function>sd_bus_message_send()</function> is the same as <function>sd_bus_send()</function> but
|
||||||
without the first and last argument. <function>sd_bus_message_send(m)</function> is equivalent to
|
without the first and last argument. It's equivalent to
|
||||||
<function>sd_bus_send(sd_bus_message_get_bus(m), m, NULL)</function>.</para>
|
<function>sd_bus_message_send(sd_bus_message_get_bus(m), m, NULL)</function>.</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
|
|||||||
@ -98,7 +98,7 @@
|
|||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><constant>-EPERM</constant></term>
|
<term><constant>-EPERM</constant></term>
|
||||||
|
|
||||||
<listitem><para>The bus connection has already been started.</para></listitem>
|
<listitem><para>The bus connection has aleady been started.</para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
</variablelist>
|
</variablelist>
|
||||||
</refsect2>
|
</refsect2>
|
||||||
|
|||||||
@ -45,9 +45,9 @@
|
|||||||
<filename>/run/systemd/transient/*</filename>
|
<filename>/run/systemd/transient/*</filename>
|
||||||
<filename>/run/systemd/generator.early/*</filename>
|
<filename>/run/systemd/generator.early/*</filename>
|
||||||
<filename>/etc/systemd/system/*</filename>
|
<filename>/etc/systemd/system/*</filename>
|
||||||
<filename>/etc/systemd/system.attached/*</filename>
|
<filename>/etc/systemd/systemd.attached/*</filename>
|
||||||
<filename>/run/systemd/system/*</filename>
|
<filename>/run/systemd/system/*</filename>
|
||||||
<filename>/run/systemd/system.attached/*</filename>
|
<filename>/run/systemd/systemd.attached/*</filename>
|
||||||
<filename>/run/systemd/generator/*</filename>
|
<filename>/run/systemd/generator/*</filename>
|
||||||
<filename index='false'>…</filename>
|
<filename index='false'>…</filename>
|
||||||
<filename>/usr/lib/systemd/system/*</filename>
|
<filename>/usr/lib/systemd/system/*</filename>
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user