/systemd-251/src/shared/ |
D | condition.c | 213 OrderOperator order; in condition_test_kernel_version() local 238 order = parse_order(&s); in condition_test_kernel_version() 239 if (order >= 0) { in condition_test_kernel_version() 256 r = test_order(strverscmp_improved(u.release, s), order); in condition_test_kernel_version() 280 OrderOperator order; in condition_test_osrelease() local 301 order = parse_order(&word); in condition_test_osrelease() 302 if (order < 0 || isempty(word) || strchr(WHITESPACE, *word) != NULL) in condition_test_osrelease() 311 if (order == ORDER_EQUAL) in condition_test_osrelease() 313 else if (order == ORDER_UNEQUAL) in condition_test_osrelease() 316 matches = test_order(strverscmp_improved(actual_value, word), order); in condition_test_osrelease() [all …]
|
D | efi-api.h | 20 int efi_set_boot_order(const uint16_t *order, size_t n); 55 static inline int efi_set_boot_order(const uint16_t *order, size_t n) { in efi_set_boot_order() argument
|
D | efi-api.c | 454 int efi_set_boot_order(const uint16_t *order, size_t n) { in efi_set_boot_order() argument 459 return efi_set_variable(EFI_GLOBAL_VARIABLE(BootOrder), order, n * sizeof(uint16_t)); in efi_set_boot_order()
|
/systemd-251/src/boot/ |
D | bootctl.c | 524 _cleanup_free_ uint16_t *options = NULL, *order = NULL; in status_variables() local 535 n_order = efi_get_boot_order(&order); in status_variables() 544 print_efi_option(order[i], true); in status_variables() 549 if (options[i] == order[j]) in status_variables() 917 _cleanup_free_ uint16_t *order = NULL; in insert_into_order() local 921 n = efi_get_boot_order(&order); in insert_into_order() 927 if (n == 1 && order[0] == slot) in insert_into_order() 932 if (order[i] != slot) in insert_into_order() 940 memmove(order + 1, order, i * sizeof(uint16_t)); in insert_into_order() 941 order[0] = slot; in insert_into_order() [all …]
|
/systemd-251/shell-completion/bash/ |
D | systemd-cgtop | 37 [ARG]='--cpu --depth -M --machine --recursive -n --iterations -d --delay --order' 50 --order)
|
D | systemd-analyze | 57 [STANDALONE]='-h --help --version --system --user --global --order --require --no-pager 125 … comps='--help --version --system --user --global --from-pattern --to-pattern --order --require'
|
D | journalctl | 95 # escaped and unescaped names in order to be able to correctly
|
/systemd-251/docs/ |
D | BOOT_LOADER_INTERFACE.md | 37 timeout for a single following boot. It is set by the OS in order to request 49 order the entries are shown on screen during boot. See below regarding a 56 loader entry to use for a single following boot. It is set by the OS in order 64 the OS in order to identify which entry has been used for the current boot.
|
D | USER_GROUP_API.md | 70 Unlike with glibc NSS there's no order or programmatic expression language 72 queries are always enqueued in parallel to all defined services, in order to 103 order to look up or enumerate user/group records it's sufficient to talk to 240 record at all. (The `service` field is defined in order to allow implementation 242 `AF_UNIX` socket: in order to correctly determine which service a client wants 258 parameter needs to contain the name of the service being talked to, in order to
|
D | BLOCK_DEVICE_LOCKING.md | 78 If multiple devices are to be locked at the same time (for example in order to 79 format a RAID file system), the devices should be locked in the order of the 81 numbers (secondary ordering key, ditto), in order to avoid ABBA locking issues
|
D | BOOT_LOADER_SPECIFICATION.md | 29 * Distribution and Core OS developers, in order to create these snippets at 78 * The various EFI implementations implement the boot order/boot item logic to 80 all and instead unconditionally follow the EFI boot order, booting the first 200 In order to maximize compatibility with file system implementations and 253 order they are listed. Example: 260 specified parameters are used in the order they are listed. 267 applied in the same order as they are listed. This key is optional but 290 On EFI systems all Linux kernel images should be EFI images. In order to 295 Conversely, in order to increase compatibility it is recommended to install 314 not valid by this specification. In order to minimize confusion a boot loader
|
D | UIDS-GIDS.md | 112 65535), in order to provide compatibility with container environments that 150 `lckpwdf()` user database lock is taken, in order to make this logic race-free. 289 strongly recommended to stay away from this range in order to avoid 317 order to minimize synchronization points on systems that don't need it the unit 321 hack on some networked user database project, then make sure you order your 324 the user database to be up in full, then order your service
|
D | ENVIRONMENT.md | 43 debugging, in order to test generators and other code against specific kernel 161 shutdown in order to request the appropriate operation from the firmware in 172 file may be checked for by services run during system shutdown in order to 183 file may be checked for by services run during system shutdown in order to 208 to naming schemes of older udev versions, in order to provide more stable 410 debugging purposes in order to run a secondary `systemd-homed` instance that 416 debugging purposes, in order to run a secondary `systemd-homed` instance that
|
D | CODING_STYLE.md | 173 - The order in which header files are included doesn't matter too 174 much. systemd-internal headers must not rely on an include order, so it is 175 safe to include them in any order possible. However, to not clutter global 180 headers. Furthermore, in all three groups, order all includes alphabetically 635 the sorting order). 645 `uint16_t`. Also, "network byte order" is just a weird name for "big endian",
|
D | JOURNAL_FILE_FORMAT.md | 237 The format is supposed to be extensible in order to enable future additions of 320 in order to facilitate storage on the most basic of file systems (well, the 339 order to avoid annoyances with `mmap()` inconsistencies. 485 contents of the entry, being independent of the order of the DATA objects in 490 quickly compare the contents of two entries, and to define a well-defined order 684 problematic on rotating disks. In order to optimize these patterns the item
|
D | INITRD_INTERFACE.md | 16 from the initrd to systemd in order to avoid duplicate work and to provide
|
D | AUTOMATIC_BOOT_ASSESSMENT.md | 171 and order them before the generic `boot-complete.target` target unit, 179 wrap them in a unit and order them after `boot-complete.target`, pulling it
|
D | JOURNAL_NATIVE_PROTOCOL.md | 53 socket towards `journald` in order to delay blocking I/O as much as possible. 101 The order in which the fields are serialized within one datagram is undefined
|
/systemd-251/coccinelle/ |
D | run-coccinelle.sh | 44 parallel --halt now,fail=1 --keep-order --noswap --max-args=20 \
|
/systemd-251/shell-completion/zsh/ |
D | _systemd-analyze | 105 '--order[When generating graph for dot, show only order]' \
|
/systemd-251/test/fuzz/fuzz-udev-rules/ |
D | 78-sound-card.rules | 14 # however only maintains the order between father and child, but not between 18 # out of order by udev this fact is lost to applications.
|
/systemd-251/rules.d/ |
D | 78-sound-card.rules | 14 # however only maintains the order between father and child, but not between 18 # out of order by udev this fact is lost to applications.
|
/systemd-251/units/ |
D | systemd-machined.service.in | 36 # needs access to the host's mount namespace in order to implement the
|
D | systemd-logind.service.in | 63 # Increase the default a bit in order to allow many simultaneous logins since
|
/systemd-251/test/fuzz/fuzz-unit-file/ |
D | systemd-machined.service | 38 # needs access to the host's mount namespace in order to implement the
|