| /systemd-251/src/udev/ata_id/ |
| D | ata_id.c | 45 uint8_t sense[32] = {}; in disk_scsi_inquiry_command() local
52 .max_response_len = sizeof(sense), in disk_scsi_inquiry_command()
53 .response = (uintptr_t) sense, in disk_scsi_inquiry_command()
70 .sbp = sense, in disk_scsi_inquiry_command()
71 .mx_sb_len = sizeof(sense), in disk_scsi_inquiry_command()
126 uint8_t sense[32] = {}; in disk_identify_command() local
127 uint8_t *desc = sense + 8; in disk_identify_command()
134 .max_response_len = sizeof(sense), in disk_identify_command()
135 .response = (uintptr_t) sense, in disk_identify_command()
152 .sbp = sense, in disk_identify_command()
[all …]
|
| /systemd-251/src/udev/scsi_id/ |
| D | scsi_serial.c | 274 unsigned char sense[SENSE_BUFF_LEN]; in scsi_inquiry() local
293 io_v4.max_response_len = sizeof(sense); in scsi_inquiry()
294 io_v4.response = (uintptr_t)sense; in scsi_inquiry()
302 io_hdr.mx_sb_len = sizeof(sense); in scsi_inquiry()
307 io_hdr.sbp = sense; in scsi_inquiry()
|
| /systemd-251/docs/ |
| D | DESKTOP_ENVIRONMENTS.md | 83 TODO: Does it really make sense to insert the `<launcher>`? In GNOME I am
86 policy makes sense, but it may make much more sense to just define a
|
| D | BUILDING_IMAGES.md | 50 4. It might also make sense to remove
163 1. Additional partitions should be created, that make no sense to ship
170 makes sense to ship the original A file system in the deployed image, but
259 Depending on how the images are put together it might make sense to leave the
|
| D | RESOLVED-VPNS.md | 137 and nothing else. Finally, it might make sense to also configure a routing
169 have IP subnet information for the VPN, it might make sense to insert
241 about search domains to use. In some cases it might make sense to install those
|
| D | INITRD_INTERFACE.md | 48 in this sense as a term that is unrelated to the actual backing technologies
|
| D | USERDB_AND_DESKTOPS.md | 77 supports is directly available in these JSON records. Hence it makes sense for
141 In the short term, it might make sense to also expose the `userdb` provided
|
| D | GVARIANT-SERIALIZATION.md | 66 made sense of just by looking at the first 32bit.
|
| D | TRANSIENT-SETTINGS.md | 501 …ion is currently not available at all for transient units, and it probably doesn't even make sense.
|
| D | CODING_STYLE.md | 189 said, there are many cases where they explicitly make a lot of sense, and are
208 - Allocate local variables where it makes sense: at the top of the block, or at
296 sense, by all means check its state with `if (b) …` — but if `b` can actually
522 types based on `short`. They *never* make sense. Use `int`, `long`, `long
|
| D | PORTABLE_SERVICES.md | 221 but they generally don't have to, and it might make sense to avoid any, to keep
313 Sometimes it makes sense to instantiate the same set of services multiple
|
| D | DISCOVERABLE_PARTITIONS.md | 20 * OS installers can automatically discover and make sense of partitions of
176 For the Root/Verity/Verity signature partitions it might make sense to use a
256 case it makes sense to include the root hash on the kernel command line that is
|
| D | USER_RECORD.md | 116 management-related fields, as those tend to make sense on a specific system
117 only, e.g. limiting a user's memory use to 1G only makes sense on a specific
749 sense in a local context but not necessarily in a global one. For example, a
754 All fields in the `binding` section only make sense in a local context and are
|
| D | USER_GROUP_API.md | 133 would make sense for LDAP/ActiveDirectory projects to implement these
|
| D | CREDENTIALS.md | 242 via `systemd` credentials. In particular, it might make sense to boot a
|
| D | UIDS-GIDS.md | 117 if you write them in hexadecimal, they might make more sense: 0xEF00 and
|
| /systemd-251/coccinelle/ |
| D | flags-set.cocci | 3 /* Disable this transformation in cases where it doesn't make sense or
|
| /systemd-251/.github/workflows/ |
| D | codeql-analysis.yml | 17 # so it doesn't seem to make much sense to trigger it on every PR or commit.
|
| /systemd-251/po/ |
| D | ca.po | 358 msgstr "Permet a l'usuari sense inici de sessió executar programes"
364 "sense inici de sessió."
368 msgstr "Permet als usuaris sense inici de sessió executar programes"
374 "sense inici de sessió."
|
| /systemd-251/src/udev/cdrom_id/ |
| D | cdrom_id.c | 173 cmd->cgc.sense = &cmd->_sense.s; in scsi_cmd_init()
|
| /systemd-251/src/boot/efi/ |
| D | meson.build | 383 # BCD parser only makes sense on arches that Windows supports.
|
| /systemd-251/LICENSES/ |
| D | LGPL-2.0-or-later.txt | 32 …n some sense simply using the library, and is analogous to running a utility program or applicatio…
|
| /systemd-251/ |
| D | NEWS | 1980 distribution does not install it yet, it might make sense to change
2676 sense there, as the event loop is already exiting when they are
3485 This is not standard-conformant, but may make sense in setups where
3946 with its sense inverted.
4365 the calling thread. This behaviour never made much sense, since
8769 resolved, but hardly made any sense, since the user instance
9443 configuration dynamically to the link sense of other
11079 with networkd, but will also make a best effort to make sense
11992 never made much sense in the intrinsically hierarchical
|