morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-15 00:47:10 +09:00
Code Issues Packages Projects Releases Wiki Activity

docs/MOUNT_REQUIREMENTS: fix typo

Browse Source 
Follow-ups for 3e94ae6f1e.
This commit is contained in:
Yu Watanabe
2025-11-25 22:51:25 +09:00
parent 05afbcc377
commit f01daa30f1
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/MOUNT_REQUIREMENTS.md
View File

@@ -44,12 +44,12 @@ if a mount point is *not* split out,
but a given subtree is part of the parent mount, but a given subtree is part of the parent mount,
the requirements for that subtree are trivially satisfied by the parent. the requirements for that subtree are trivially satisfied by the parent.
A "mount point" in this document means the whole subtree of the hierachy, A "mount point" in this document means the whole subtree of the hierarchy,
until a mountpoint lower in the hierarchy which is conceptually separate. until a mountpoint lower in the hierarchy which is conceptually separate.
For example, on a system with a custom mount point located below `/var/spool/`, For example, on a system with a custom mount point located below `/var/spool/`,
most of `/var/` would be in category 2/early, most of `/var/` would be in category 2/early,
but the additional mount would be in category 3/regular. but the additional mount would be in category 3/regular.
Conversly, if some part of `/usr/` that is normally part of that subtree Conversely, if some part of `/usr/` that is normally part of that subtree
was split out to a separate mount, was split out to a separate mount,
this mount point would fall into category 1/initrd this mount point would fall into category 1/initrd
and configuration would need to be provided for it to be mounted in the initrd. and configuration would need to be provided for it to be mounted in the initrd.