Lines Matching refs:of

14 A number of complex storage technologies on Linux (e.g. RAID, volume
17 root file system of the Linux operating system is stored on such storage
22 ## A Bit of Background
26 by Dracut. In newer systemd versions tear-down of the root file system backing
34 first time arbitrary complex stacks of storage technology.
38 the root storage itself, thus creating a number of dependency loops. Safely
56 from the perspective of the init system (i.e. systemd) these services have been
65 Near the end of system shutdown, systemd executes a small tool called
68 mounted file systems and running processes (as well as a couple of other
71 killing spree a couple of processes are automatically excluded: PID 1 itself of
88 Processes (run by the root user) whose first character of the zeroth command
91 of this logic needs to place the following at the top of its `main()` function:
103 clean unmounting/detaching of the root file system and its backing storage.
126 Why `@`? Why `argv[0][0]`? First of all, a technique like this is not without
132 character of `argv[0]` with `@` also visually invalidates the path normally
140 (i.e. `/proc/self/comm`) of your process untouched.
167   inherits a multitude of process attributes (ranging from the obvious to the
170   process context of the spawning process. In particular, systemd tracks which
173   it part of its service/login. Effectively this means that whenever udev is
183   socket of your storage daemon will result in the storage to be started. For
185   to listen on on behalf of your daemon and minimally modify the daemon to
186   receive the listening socket for its services from systemd instead of
189   systems. For more information on making use of socket activation in your
193 * Consider having a look at the [initrd Interface of systemd](INITRD_INTERFACE.md).