Lines Matching refs:relevant
190 Typically, a better approach to user namespacing in relevant
670 when the relevant keys are pressed for more than 5s. This is useful
957 whether to use the relevant fields from the IPv6 Router Advertisement
2528 where the device starts being relevant, and those where it stops
2529 being relevant (the latter now regularly happening due to the new
2563 uevents actions (i.e. considering devices only relevant after "add"
2566 devices relevant after all event types, except for "remove", which
2568 should be considered relevant on "unbind", even though conceptually
2571 considered relevant even after "unbind", however I/O errors
2575 relevant or not most likely needs to be updated to use the new
2603 it would suddenly lose the relevant properties. This always has been
2604 problematic, but as soon as all udev devices are triggered on relevant
2640 relevant operations will fail gracefully, or a suitable fallback
2792 of all relevant types which may be used by the container payload as
3093 relevant during upstream development, e.g. verification that
3755 * Only relevant for developers: the mkosi.default symlink has been
4512 that any relevant loggable events happening during late shutdown are
5043 skip the relevant operation completely (when set to false), or to
5670 incompatible kernel change. The relevant kernel developers have been
5795 any relevant symlinks both in /run and /etc.
6237 not relevant to the unit, while still allowing some paths lower in
7234 relevant due to the high amount of recently discovered namespacing
7454 "API VFS") will be mounted for the service. This is only relevant if
8881 the systemd manager when exiting. This is only relevant when
10219 rotational disk drives and was becoming less relevant in the
10489 NamePolicy= in the relevant .link file.