SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

man: fix typo

Browse Source 
Follow-up for eb581ff6d9.
This commit is contained in:
Yu Watanabe
2026-02-20 01:18:54 +09:00
parent fcf5f1db94
commit e94c410e51
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/systemd-mstack.xml
+1 -1
View File
@@ -176,7 +176,7 @@
<!-- In case you are wondering why this is spelled out with the /sbin/ prefix, rather than /usr/bin/ or
so, or omitting the prefix entirely: it's simply because util-linux mount always uses precisely this
spelling in their API docs. For example open mount(8), and grep for '/sbin/mount', and you see a ton
of occurences. We just inherit this spelling here, to make clear this is just an instantiation of
of occurrences. We just inherit this spelling here, to make clear this is just an instantiation of
their plugin mechanism. -->
<para>The <command>systemd-mstack</command> executable may be symlinked to
man/systemd.mstack.xml
+2 -2
View File
@@ -27,7 +27,7 @@
mount hierarchies based on bind and overlay mounts, for use in
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
<option>--mstack=</option> switch or the service manager's <option>RootMStack=</option> setting for
services. <literal>.mstack/</literal> directroies may contain various files and subdirectories, where
services. <literal>.mstack/</literal> directories may contain various files and subdirectories, where
each will effect one layer of an <literal>overlayfs</literal> mount, or a bind mount. The name of the
file or subdirectory indicates how it shall used in the mount hierarchy. Specifically, the following
names are defined:</para>
@@ -51,7 +51,7 @@
<listitem><para>A <filename>bind@<replaceable>location</replaceable>/</filename> directory will be bind
mounted to the mount point indicated by the <variable>location</variable> identifier, in read-write
fashion. The loction is encoded via the same escaping logic used for naming <literal>.mount</literal>
fashion. The location is encoded via the same escaping logic used for naming <literal>.mount</literal>
units, i.e. slashes become dashes.</para></listitem>
<listitem><para>Similar, a