Revert "docs: use collections to structure the data"

This reverts commit 5e8ff01. This broke all the URLs, we can't have that. (And actually, we probably don't _want_ to make the change either. It's nicer to have all the pages in one directory, so one doesn't have to figure out to which collection the page belongs.)
ufgkirk · Feb 23, 2024 · 8e3fee3 · 8e3fee3
1 parent c0b5b74
commit 8e3fee3
Show file tree

Hide file tree

Showing 83 changed files with 107 additions and 153 deletions.
diff --git a/README.md b/README.md
@@ -26,13 +26,13 @@ Information about build requirements is provided in the [README file](README).
 
 Consult our [NEWS file](NEWS) for information about what's new in the most recent systemd versions.
 
-Please see the [Code Map](docs/_contributing/ARCHITECTURE.md) for information about this repository's layout and content.
+Please see the [Code Map](docs/ARCHITECTURE.md) for information about this repository's layout and content.
 
-Please see the [Hacking guide](docs/_contributing/HACKING.md) for information on how to hack on systemd and test your modifications.
+Please see the [Hacking guide](docs/HACKING.md) for information on how to hack on systemd and test your modifications.
 
-Please see our [Contribution Guidelines](docs/_contributing/CONTRIBUTING.md) for more information about filing GitHub Issues and posting GitHub Pull Requests.
+Please see our [Contribution Guidelines](docs/CONTRIBUTING.md) for more information about filing GitHub Issues and posting GitHub Pull Requests.
 
-When preparing patches for systemd, please follow our [Coding Style Guidelines](docs/_contributing/CODING_STYLE.md).
+When preparing patches for systemd, please follow our [Coding Style Guidelines](docs/CODING_STYLE.md).
 
 If you are looking for support, please contact our [mailing list](https://lists.freedesktop.org/mailman/listinfo/systemd-devel), join our [IRC channel #systemd on libera.chat](https://web.libera.chat/#systemd) or [Matrix channel](https://matrix.to/#/#systemd-project:matrix.org)
 

diff --git a/docs/_userdocs/API_FILE_SYSTEMS.md → docs/API_FILE_SYSTEMS.md b/docs/_userdocs/API_FILE_SYSTEMS.md → docs/API_FILE_SYSTEMS.md
@@ -50,4 +50,3 @@ You have three options:
 1. Disable any mounting on `/tmp` so that it resides on the same physical file system as the root directory. For that, execute `systemctl mask tmp.mount`
 2. Mount a different, physical file system to `/tmp`. For that, simply create an entry for it in `/etc/fstab` as you would do for any other file system.
 3. Keep `/tmp` but increase/decrease the size of it. For that, also just create an entry for it in `/etc/fstab` as you would do for any other `tmpfs` file system, and use the right `size=` option.
-
diff --git a/docs/_contributing/ARCHITECTURE.md → docs/ARCHITECTURE.md b/docs/_contributing/ARCHITECTURE.md → docs/ARCHITECTURE.md
@@ -145,7 +145,7 @@ as a normal executable and executed for each of the input samples under
 with sanitizers and invoked as part of the test suite (if `-Dfuzz-tests=true`
 is configured). Thirdly, fuzzers are executed through fuzzing engines that try
 to find new "interesting" inputs through coverage feedback and massive
-parallelization; see the links for oss-fuzz in [Code quality](CODE_QUALITY).
+parallelization; see the links for oss-fuzz in [Code quality](CODE_QUALITY.md).
 For testing and debugging, fuzzers can be executed as any other program,
 including under `valgrind` or `gdb`.
 

diff --git a/docs/_booting/AUTOMATIC_BOOT_ASSESSMENT.md → docs/AUTOMATIC_BOOT_ASSESSMENT.md b/docs/_booting/AUTOMATIC_BOOT_ASSESSMENT.md → docs/AUTOMATIC_BOOT_ASSESSMENT.md
diff --git a/docs/_devdocs/AUTOPKGTEST.md → docs/AUTOPKGTEST.md b/docs/_devdocs/AUTOPKGTEST.md → docs/AUTOPKGTEST.md
diff --git a/docs/_devdocs/BACKPORTS.md → docs/BACKPORTS.md b/docs/_devdocs/BACKPORTS.md → docs/BACKPORTS.md
diff --git a/docs/_interfaces/BLOCK_DEVICE_LOCKING.md → docs/BLOCK_DEVICE_LOCKING.md b/docs/_interfaces/BLOCK_DEVICE_LOCKING.md → docs/BLOCK_DEVICE_LOCKING.md
diff --git a/docs/_devdocs/BOOT.md → docs/BOOT.md b/docs/_devdocs/BOOT.md → docs/BOOT.md
@@ -109,4 +109,3 @@ Links:
 [https://github.com/systemd/systemd](https://github.com/systemd/systemd)
 
 [http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/](http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/)
-
diff --git a/docs/_booting/BOOT_LOADER_INTERFACE.md → docs/BOOT_LOADER_INTERFACE.md b/docs/_booting/BOOT_LOADER_INTERFACE.md → docs/BOOT_LOADER_INTERFACE.md
@@ -78,7 +78,7 @@ variables. All EFI variables use the vendor UUID
   * `1 << 1` → The boot loader honours `LoaderConfigTimeoutOneShot` when set.
   * `1 << 2` → The boot loader honours `LoaderEntryDefault` when set.
   * `1 << 3` → The boot loader honours `LoaderEntryOneShot` when set.
-  * `1 << 4` → The boot loader supports boot counting as described in [Automatic Boot Assessment](AUTOMATIC_BOOT_ASSESSMENT).
+  * `1 << 4` → The boot loader supports boot counting as described in [Automatic Boot Assessment](AUTOMATIC_BOOT_ASSESSMENT.md).
   * `1 << 5` → The boot loader supports looking for boot menu entries in the Extended Boot Loader Partition.
   * `1 << 6` → The boot loader supports passing a random seed to the OS.
   * `1 << 13` → The boot loader honours `menu-disabled` option when set.

diff --git a/docs/_booting/BOOT_LOADER_SPECIFICATION.md → docs/BOOT_LOADER_SPECIFICATION.md b/docs/_booting/BOOT_LOADER_SPECIFICATION.md → docs/BOOT_LOADER_SPECIFICATION.md
diff --git a/docs/_concepts/BUILDING_IMAGES.md → docs/BUILDING_IMAGES.md b/docs/_concepts/BUILDING_IMAGES.md → docs/BUILDING_IMAGES.md
diff --git a/docs/_devdocs/CATALOG.md → docs/CATALOG.md b/docs/_devdocs/CATALOG.md → docs/CATALOG.md
@@ -65,4 +65,3 @@ To add message catalog entries for log messages your application generates, plea
 * Use the [native Journal logging APIs](http://0pointer.de/blog/projects/journal-submit.html) to generate your messages, and define message IDs for all messages you want to add catalog entries for. You may use `journalctl --new-id128` to allocate new message IDs.
 * Write a catalog entry file for your messages and ship them in your package and install them to `/usr/lib/systemd/catalog/` (if you package your software with RPM use `%_journalcatalogdir`)
 * Ensure that after installation of your application's RPM/DEB "`journalctl --update-catalog`" is executed, in order to update the binary catalog index. (if you package your software with RPM use the `%journal_catalog_update` macro to achieve that.)
-
diff --git a/docs/_interfaces/CGROUP_DELEGATION.md → docs/CGROUP_DELEGATION.md b/docs/_interfaces/CGROUP_DELEGATION.md → docs/CGROUP_DELEGATION.md
diff --git a/docs/_contributing/CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md b/docs/_contributing/CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md
diff --git a/docs/_contributing/CODE_QUALITY.md → docs/CODE_QUALITY.md b/docs/_contributing/CODE_QUALITY.md → docs/CODE_QUALITY.md
@@ -75,7 +75,7 @@ available functionality:
 
 15. Each PR is automatically tested with [Address Sanitizer](https://clang.llvm.org/docs/AddressSanitizer.html)
     and [Undefined Behavior Sanitizer](https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html).
-    See [Testing systemd using sanitizers](TESTING_WITH_SANITIZERS)
+    See [Testing systemd using sanitizers](TESTING_WITH_SANITIZERS.md)
     for more information.
 
 16. Fossies provides [source code misspelling reports](https://fossies.org/features.html#codespell).

diff --git a/docs/_contributing/CODING_STYLE.md → docs/CODING_STYLE.md b/docs/_contributing/CODING_STYLE.md → docs/CODING_STYLE.md
diff --git a/docs/_interfaces/CONTAINER_INTERFACE.md → docs/CONTAINER_INTERFACE.md b/docs/_interfaces/CONTAINER_INTERFACE.md → docs/CONTAINER_INTERFACE.md
diff --git a/docs/_contributing/CONTRIBUTING.md → docs/CONTRIBUTING.md b/docs/_contributing/CONTRIBUTING.md → docs/CONTRIBUTING.md
@@ -29,13 +29,13 @@ For older versions that are still supported by your distribution please use resp
 
 ## Security vulnerability reports
 
-See [reporting of security vulnerabilities](SECURITY).
+See [reporting of security vulnerabilities](SECURITY.md).
 
 ## Posting Pull Requests
 
 * Make sure to post PRs only relative to a recent tip of the `main` branch.
-* Follow our [Coding Style](CODING_STYLE) when contributing code. This is a requirement for all code we merge.
-* Please make sure to test your change before submitting the PR. See the [Hacking guide](HACKING) for details on how to do this.
+* Follow our [Coding Style](CODING_STYLE.md) when contributing code. This is a requirement for all code we merge.
+* Please make sure to test your change before submitting the PR. See the [Hacking guide](HACKING.md) for details on how to do this.
 * Make sure to run the test suite locally, before posting your PR. We use a CI system, meaning we don't even look at your PR if the build and tests don't pass.
 * If you need to update the code in an existing PR, force-push into the same branch, overriding old commits with new versions.
 * After you have pushed a new version, add a comment explaining the latest changes. If you are a member of the systemd project on GitHub, remove the `reviewed/needs-rework`/`ci-fails/needs-rework`/`needs-rebase` labels.

diff --git a/docs/_devdocs/CONTROL_GROUP_INTERFACE.md → docs/CONTROL_GROUP_INTERFACE.md b/docs/_devdocs/CONTROL_GROUP_INTERFACE.md → docs/CONTROL_GROUP_INTERFACE.md
diff --git a/docs/_groups/CONVERTING_TO_HOMED.md → docs/CONVERTING_TO_HOMED.md b/docs/_groups/CONVERTING_TO_HOMED.md → docs/CONVERTING_TO_HOMED.md
@@ -16,10 +16,10 @@ it might be desirable to convert an existing, traditional user account to a
 
 Before continuing, please read up on these basic concepts:
 
-* [Home Directories](HOME_DIRECTORY)
-* [JSON User Records](USER_RECORD)
-* [JSON Group Records](GROUP_RECORD)
-* [User/Group Record Lookup API via Varlink](USER_GROUP_API)
+* [Home Directories](HOME_DIRECTORY.md)
+* [JSON User Records](USER_RECORD.md)
+* [JSON Group Records](GROUP_RECORD.md)
+* [User/Group Record Lookup API via Varlink](USER_GROUP_API.md)
 
 ## Caveat
 

diff --git a/docs/_concepts/COREDUMP.md → docs/COREDUMP.md b/docs/_concepts/COREDUMP.md → docs/COREDUMP.md
diff --git a/docs/_concepts/CREDENTIALS.md → docs/CREDENTIALS.md b/docs/_concepts/CREDENTIALS.md → docs/CREDENTIALS.md
@@ -59,7 +59,7 @@ purpose. Specifically, the following features are provided:
 8. Credentials are an effective way to pass parameters into services that run
    with `RootImage=` or `RootDirectory=` and thus cannot read these resources
    directly from the host directory tree.
-   Specifically, [Portable Services](PORTABLE_SERVICES) may be
+   Specifically, [Portable Services](PORTABLE_SERVICES.md) may be
    parameterized this way securely and robustly.
 
 9. Credentials can be binary and relatively large (though currently an overall
@@ -288,7 +288,7 @@ services where they are ultimately consumed.
    invokes. [`systemd-nspawn(1)`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#Credentials)'s
    `--set-credential=` and `--load-credential=` switches implement this, in
    order to pass arbitrary credentials from host to container payload. Also see
-   the [Container Interface](CONTAINER_INTERFACE) documentation.
+   the [Container Interface](CONTAINER_INTERFACE.md) documentation.
 
 2. Quite similar, VMs can be passed credentials via SMBIOS OEM strings (example
    qemu command line switch `-smbios

diff --git a/docs/_userdocs/DAEMON_SOCKET_ACTIVATION.md → docs/DAEMON_SOCKET_ACTIVATION.md b/docs/_userdocs/DAEMON_SOCKET_ACTIVATION.md → docs/DAEMON_SOCKET_ACTIVATION.md
@@ -120,4 +120,3 @@ It's possible to shut down the service and re-activate it using the web browser,
 sudo systemctl stop my-php-fpm-pool.socket my-php-fpm-pool.service
 sudo systemctl start my-php-fpm-pool.socket
 ```
-
diff --git a/docs/_userdocs/DEBUGGING.md → docs/DEBUGGING.md b/docs/_userdocs/DEBUGGING.md → docs/DEBUGGING.md
@@ -209,4 +209,3 @@ Whenever possible, the following should be mentioned and attached to your bug re
   * ideally after booting with `systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on`
 * The output of a systemd dump: `systemd-analyze dump > systemd-dump.txt`
 * The output of `/usr/lib/systemd/systemd --test --system --log-level=debug > systemd-test.txt 2>&1`
-
diff --git a/docs/_concepts/DESKTOP_ENVIRONMENTS.md → docs/DESKTOP_ENVIRONMENTS.md b/docs/_concepts/DESKTOP_ENVIRONMENTS.md → docs/DESKTOP_ENVIRONMENTS.md
diff --git a/docs/_concepts/DISTRO_PORTING.md → docs/DISTRO_PORTING.md b/docs/_concepts/DISTRO_PORTING.md → docs/DISTRO_PORTING.md
diff --git a/docs/_interfaces/ELF_PACKAGE_METADATA.md → docs/ELF_PACKAGE_METADATA.md b/docs/_interfaces/ELF_PACKAGE_METADATA.md → docs/ELF_PACKAGE_METADATA.md
diff --git a/docs/_interfaces/ENVIRONMENT.md → docs/ENVIRONMENT.md b/docs/_interfaces/ENVIRONMENT.md → docs/ENVIRONMENT.md
diff --git a/docs/_userdocs/FAQ.md → docs/FAQ.md b/docs/_userdocs/FAQ.md → docs/FAQ.md
@@ -112,4 +112,3 @@ A: That's a long story, and that's why we have a wiki page of its own about this
 **Q: My systemd system always comes up with `/tmp` as a tiny `tmpfs`. How do I get rid of this?**
 
 A: That's also a long story, please have a look on [API File Systems](../API_FILE_SYSTEMS)
-
diff --git a/docs/_interfaces/FILE_DESCRIPTOR_STORE.md → docs/FILE_DESCRIPTOR_STORE.md b/docs/_interfaces/FILE_DESCRIPTOR_STORE.md → docs/FILE_DESCRIPTOR_STORE.md
diff --git a/docs/_groups/GROUP_RECORD.md → docs/GROUP_RECORD.md b/docs/_groups/GROUP_RECORD.md → docs/GROUP_RECORD.md
@@ -8,7 +8,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
 # JSON Group Records
 
 Long story short: JSON Group Records are to `struct group` what
-[JSON User Records](USER_RECORD) are to `struct passwd`.
+[JSON User Records](USER_RECORD.md) are to `struct passwd`.
 
 Conceptually, much of what applies to JSON user records also applies to JSON
 group records. They also consist of seven sections, with similar properties and

diff --git a/docs/_contributing/HACKING.md → docs/HACKING.md b/docs/_contributing/HACKING.md → docs/HACKING.md
@@ -11,8 +11,8 @@ We welcome all contributions to systemd. If you notice a bug or a missing
 feature, please feel invited to fix it, and submit your work as a
 [GitHub Pull Request (PR)](https://github.com/systemd/systemd/pull/new).
 
-Please make sure to follow our [Coding Style](CODING_STYLE) when submitting
-patches. Also have a look at our [Contribution Guidelines](CONTRIBUTING).
+Please make sure to follow our [Coding Style](CODING_STYLE.md) when submitting
+patches. Also have a look at our [Contribution Guidelines](CONTRIBUTING.md).
 
 When adding new functionality, tests should be added. For shared functionality
 (in `src/basic/` and `src/shared/`) unit tests should be sufficient. The general
@@ -23,7 +23,7 @@ test executable. For features at a higher level, tests in `src/test/` are very
 strongly recommended. If that is not possible, integration tests in `test/` are
 encouraged.
 
-Please also have a look at our list of [code quality tools](CODE_QUALITY) we
+Please also have a look at our list of [code quality tools](CODE_QUALITY.md) we
 have setup for systemd, to ensure our codebase stays in good shape.
 
 Please always test your work before submitting a PR. For many of the components
@@ -148,7 +148,7 @@ distribution and can be disabled by setting `-Dmode=release`.
 
 ## Sanitizers in mkosi
 
-See [Testing systemd using sanitizers](TESTING_WITH_SANITIZERS) for more information
+See [Testing systemd using sanitizers](TESTING_WITH_SANITIZERS.md) for more information
 on how to build with sanitizers enabled in mkosi.
 
 ## Fuzzers
@@ -211,7 +211,7 @@ done
 ```
 
 If you find a bug that impacts the security of systemd, please follow the
-guidance in [CONTRIBUTING.md](CONTRIBUTING) on how to report a security vulnerability.
+guidance in [CONTRIBUTING.md](CONTRIBUTING.md) on how to report a security vulnerability.
 
 For more details on building fuzzers and integrating with OSS-Fuzz, visit:
 

diff --git a/docs/_groups/HOME_DIRECTORY.md → docs/HOME_DIRECTORY.md b/docs/_groups/HOME_DIRECTORY.md → docs/HOME_DIRECTORY.md
@@ -19,7 +19,7 @@ mechanism used.
 
 Inside of the home directory a file `~/.identity` contains the JSON formatted
 user record of the user. It follows the format defined in
-[`JSON User Records`](USER_RECORD). It is recommended to bring the
+[`JSON User Records`](USER_RECORD.md). It is recommended to bring the
 record into 'normalized' form (i.e. all objects should contain their fields
 sorted alphabetically by their key) before storing it there, though this is not
 required nor enforced. Since the user record is cryptographically signed, the

diff --git a/docs/_userdocs/INCOMPATIBILITIES.md → docs/INCOMPATIBILITIES.md b/docs/_userdocs/INCOMPATIBILITIES.md → docs/INCOMPATIBILITIES.md
@@ -13,7 +13,7 @@ systemd provides a fair degree of compatibility with the behavior exposed by the
 * LSB header dependency information matters. The SysV implementations on many distributions did not use the dependency information encoded in LSB init script headers, or used them only in very limited ways. Due to that they are often incorrect or incomplete. systemd however fully interprets these headers and follows them closely at runtime (and not at installation time like some implementations).
 * Timeouts apply to all init script operations in systemd. While on SysV systems a hanging init script could freeze the system on systemd all init script operations are subject to a timeout of 5min.
 * Services are executed in completely clean execution contexts, no context of the invoking user session is inherited. Not even $HOME or similar are set. Init scripts depending on these will not work correctly.
-* Services cannot read from stdin, as this will be connected to /dev/null. That means interactive init scripts are not supported (i.e. Debian's X-Interactive in the LSB header is not supported either.) Thankfully most distributions do not support interaction in init scripts anyway. If you need interaction to ask disk or SSL passphrases please consider using the minimal password querying framework systemd supports. ([details](PASSWORD_AGENTS), [manual page](http://0pointer.de/public/systemd-man/systemd-ask-password.html))
+* Services cannot read from stdin, as this will be connected to /dev/null. That means interactive init scripts are not supported (i.e. Debian's X-Interactive in the LSB header is not supported either.) Thankfully most distributions do not support interaction in init scripts anyway. If you need interaction to ask disk or SSL passphrases please consider using the minimal password querying framework systemd supports. ([details](../PASSWORD_AGENTS), [manual page](http://0pointer.de/public/systemd-man/systemd-ask-password.html))
 * Additional verbs for init scripts are not supported. If your init script traditionally supported additional verbs for your init script simply move them to an auxiliary script.
 * Additional parameters to the standard verbs (i.e. to "start", "stop" and "status") are not supported. This was an extension of SysV that never was standardized officially, and is not supported in systemd.
 * Overriding the "restart" verb is not supported. This verb is always implemented by systemd itself, and consists of a "stop" followed by a "start".

diff --git a/docs/_devdocs/INHIBITOR_LOCKS.md → docs/INHIBITOR_LOCKS.md b/docs/_devdocs/INHIBITOR_LOCKS.md → docs/INHIBITOR_LOCKS.md
diff --git a/docs/_interfaces/INITRD_INTERFACE.md → docs/INITRD_INTERFACE.md b/docs/_interfaces/INITRD_INTERFACE.md → docs/INITRD_INTERFACE.md
@@ -40,7 +40,7 @@ Arch Linux initrds.
   line options, for example `--log-level=` and similar.
 
 * Storage daemons run from the initrd should follow the guide on
-  [systemd and Storage Daemons for the Root File System](ROOT_STORAGE_DAEMONS)
+  [systemd and Storage Daemons for the Root File System](ROOT_STORAGE_DAEMONS.md)
   to survive properly from the boot initrd all the way to the point where
   systemd jumps back into the initrd for shutdown.
 
@@ -67,4 +67,4 @@ systemd. Here are a few terse notes:
 
 * The switch-root operation will result in a killing spree of all running
   processes. Some processes might need to be excluded from that, see the guide
-  on [systemd and Storage Daemons for the Root File System](ROOT_STORAGE_DAEMONS).
+  on [systemd and Storage Daemons for the Root File System](ROOT_STORAGE_DAEMONS.md).
diff --git a/docs/_interfaces/JOURNAL_EXPORT_FORMATS.md → docs/JOURNAL_EXPORT_FORMATS.md b/docs/_interfaces/JOURNAL_EXPORT_FORMATS.md → docs/JOURNAL_EXPORT_FORMATS.md
@@ -11,7 +11,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
 
 _Note that this document describes the binary serialization format of journals only, as used for transfer across the network.
 For interfacing with web technologies there's the Journal JSON Format, described below.
-The binary format on disk is documented as the [Journal File Format](JOURNAL_FILE_FORMAT)._
+The binary format on disk is documented as the [Journal File Format](JOURNAL_FILE_FORMAT.md)._
 
 _Before reading on, please make sure you are aware of the [basic properties of journal entries](https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html), in particular realize that they may include binary non-text data (though usually don't), and the same field might have multiple values assigned within the same entry (though usually hasn't)._
 
@@ -124,7 +124,7 @@ _SOURCE_REALTIME_TIMESTAMP=1423944916372858
 
 _Note that this section describes the JSON serialization format of the journal only, as used for interfacing with web technologies.
 For binary transfer of journal data across the network there's the Journal Export Format described above.
-The binary format on disk is documented as [Journal File Format](JOURNAL_FILE_FORMAT)._
+The binary format on disk is documented as [Journal File Format](JOURNAL_FILE_FORMAT.md)._
 
 _Before reading on, please make sure you are aware of the [basic properties of journal entries](https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html), in particular realize that they may include binary non-text data (though usually don't), and the same field might have multiple values assigned within the same entry (though usually hasn't)._
 

diff --git a/docs/_interfaces/JOURNAL_FILE_FORMAT.md → docs/JOURNAL_FILE_FORMAT.md b/docs/_interfaces/JOURNAL_FILE_FORMAT.md → docs/JOURNAL_FILE_FORMAT.md
@@ -46,7 +46,7 @@ _Or, to put this in other words: this low-level document is probably not what
 you want to use as base of your project. You want our [C
 API](https://www.freedesktop.org/software/systemd/man/sd-journal.html) instead!
 And if you really don't want the C API, then you want the
-[Journal Export Format or Journal JSON Format](JOURNAL_EXPORT_FORMATS)
+[Journal Export Format or Journal JSON Format](JOURNAL_EXPORT_FORMATS.md)
 instead! This document is primarily for your entertainment and education.
 Thank you!_
 

diff --git a/docs/_interfaces/JOURNAL_NATIVE_PROTOCOL.md → docs/JOURNAL_NATIVE_PROTOCOL.md b/docs/_interfaces/JOURNAL_NATIVE_PROTOCOL.md → docs/JOURNAL_NATIVE_PROTOCOL.md
diff --git a/docs/_interfaces/MEMORY_PRESSURE.md → docs/MEMORY_PRESSURE.md b/docs/_interfaces/MEMORY_PRESSURE.md → docs/MEMORY_PRESSURE.md
diff --git a/docs/_devdocs/MINIMAL_BUILDS.md → docs/MINIMAL_BUILDS.md b/docs/_devdocs/MINIMAL_BUILDS.md → docs/MINIMAL_BUILDS.md
diff --git a/docs/_booting/MOUNT_REQUIREMENTS.md → docs/MOUNT_REQUIREMENTS.md b/docs/_booting/MOUNT_REQUIREMENTS.md → docs/MOUNT_REQUIREMENTS.md
diff --git a/..._userdocs/MY_SERVICE_CANT_GET_REATLIME.md → docs/MY_SERVICE_CANT_GET_REATLIME.md b/..._userdocs/MY_SERVICE_CANT_GET_REATLIME.md → docs/MY_SERVICE_CANT_GET_REATLIME.md
@@ -26,4 +26,3 @@ Of course, that's quite a limitation, so here's how you work around this:
 Note that this all only applies to services. By default, user applications run in the root cgroup of the "cpu" hierarchy, which avoids these problems for normal user applications.
 
 In the long run we hope that the kernel is fixed to not require an RT budget to be assigned for any cgroup created before a process can acquire RT (i.e. a process' RT budget should be derived from the nearest ancestor cgroup which has a budget assigned, rather than unconditionally its own uninitialized budget.) Ideally, we'd also like to create a per-user cgroup by default, so that users with many processes get roughly the same amount of CPU as users with very few.
-
diff --git a/docs/_networking/NETWORK_ONLINE.md → docs/NETWORK_ONLINE.md b/docs/_networking/NETWORK_ONLINE.md → docs/NETWORK_ONLINE.md
diff --git a/docs/_devdocs/OPTIMIZATIONS.md → docs/OPTIMIZATIONS.md b/docs/_devdocs/OPTIMIZATIONS.md → docs/OPTIMIZATIONS.md
diff --git a/docs/_interfaces/PASSWORD_AGENTS.md → docs/PASSWORD_AGENTS.md b/docs/_interfaces/PASSWORD_AGENTS.md → docs/PASSWORD_AGENTS.md
Original file line number	Diff line number	Diff line change
Expand Up		@@ -50,4 +50,3 @@ You have three options:
		1. Disable any mounting on `/tmp` so that it resides on the same physical file system as the root directory. For that, execute `systemctl mask tmp.mount`
		2. Mount a different, physical file system to `/tmp`. For that, simply create an entry for it in `/etc/fstab` as you would do for any other file system.
		3. Keep `/tmp` but increase/decrease the size of it. For that, also just create an entry for it in `/etc/fstab` as you would do for any other `tmpfs` file system, and use the right `size=` option.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -109,4 +109,3 @@ Links:
		[https://github.com/systemd/systemd](https://github.com/systemd/systemd)

		[http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/](http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -65,4 +65,3 @@ To add message catalog entries for log messages your application generates, plea
		* Use the [native Journal logging APIs](http://0pointer.de/blog/projects/journal-submit.html) to generate your messages, and define message IDs for all messages you want to add catalog entries for. You may use `journalctl --new-id128` to allocate new message IDs.
		* Write a catalog entry file for your messages and ship them in your package and install them to `/usr/lib/systemd/catalog/` (if you package your software with RPM use `%_journalcatalogdir`)
		* Ensure that after installation of your application's RPM/DEB "`journalctl --update-catalog`" is executed, in order to update the binary catalog index. (if you package your software with RPM use the `%journal_catalog_update` macro to achieve that.)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -120,4 +120,3 @@ It's possible to shut down the service and re-activate it using the web browser,
		sudo systemctl stop my-php-fpm-pool.socket my-php-fpm-pool.service
		sudo systemctl start my-php-fpm-pool.socket
		```
Original file line number	Diff line number	Diff line change
Expand Up		@@ -209,4 +209,3 @@ Whenever possible, the following should be mentioned and attached to your bug re
		* ideally after booting with `systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on`
		* The output of a systemd dump: `systemd-analyze dump > systemd-dump.txt`
		* The output of `/usr/lib/systemd/systemd --test --system --log-level=debug > systemd-test.txt 2>&1`
Original file line number	Diff line number	Diff line change
Expand Up		@@ -112,4 +112,3 @@ A: That's a long story, and that's why we have a wiki page of its own about this
		Q: My systemd system always comes up with `/tmp` as a tiny `tmpfs`. How do I get rid of this?

		A: That's also a long story, please have a look on [API File Systems](../API_FILE_SYSTEMS)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -26,4 +26,3 @@ Of course, that's quite a limitation, so here's how you work around this:
		Note that this all only applies to services. By default, user applications run in the root cgroup of the "cpu" hierarchy, which avoids these problems for normal user applications.

		In the long run we hope that the kernel is fixed to not require an RT budget to be assigned for any cgroup created before a process can acquire RT (i.e. a process' RT budget should be derived from the nearest ancestor cgroup which has a budget assigned, rather than unconditionally its own uninitialized budget.) Ideally, we'd also like to create a per-user cgroup by default, so that users with many processes get roughly the same amount of CPU as users with very few.