this (reference) in projects: systemd-251

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:this (Results 1 – 25 of 262) sorted by relevance

12 3 4 5 6 7 8 9 10 11

/systemd-251/
D	LICENSE.LGPL2.1	7 of this license document, but changing it is not allowed. 24 this license or the ordinary General Public License is the better 30 for this service if you wish); that you receive source code or can get 49 library, and (2) we offer you this license, which gives you legal 64 consistent with the full freedom of use specified in this license. 70 this license for certain libraries in order to permit linking those 81 We call this license the "Lesser" General Public License because it 91 a de-facto standard. To achieve this, non-free programs must be 93 library does the same job as widely used non-free libraries. In this 121 this Lesser General Public License (also called "this License"). [all …]
D	LICENSE.GPL2	7 of this license document, but changing it is not allowed. 24 this service if you wish), that you receive source code or can get it 40 (2) offer you this license which gives you legal permission to copy, 44 that everyone understands that there is no warranty for this free 53 program proprietary. To prevent this, we have made it clear that any 64 under the terms of this General Public License. The "Program", below, 73 covered by this License; they are outside its scope. The act of 83 notices that refer to this License and to the absence of any warranty; 84 and give any other recipients of the Program a copy of this License 101 parties under the terms of this License. [all …]
D	README	47 are not recommended for use with this version of systemd. Taint flag 88 PrivateNetwork so this is effectively required. 144 sensible way to assign these budgets automatically this cannot really be 152 be a kernel compile-time option for this, but there currently isn't. The 153 next best thing is to make this change through a modprobe.d drop-in. 168 not use socketcall() and where seccomp is supported (this effectively 279 will only be introduced if there are significant reasons for this 298 group to exist. New journal files will be readable by this group (but 304 user and group to exist. During execution this network facing service 305 will drop privileges and assume this uid/gid for security reasons. [all …]
/systemd-251/LICENSES/
D	LGPL-2.0-or-later.txt	8 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing… 18 …ou have the freedom to distribute copies of free software (and charge for this service if you wish… 24 …g your rights has two steps: (1) copyright the library, and (2) offer you this license which gives… 26 …t to make certain that everyone understands that there is no warranty for this free library. If th… 28 … in effect transforming the program into proprietary software. To prevent this, we have made it cl… 34 Because of this blurred distinction, using the ordinary General Public License for libraries did no… 36 …ve this as regards changes in header files, but we have achieved it as regards changes in the actu… 40 …for a library to be covered by the ordinary General Public License rather than by this special one. 44 … saying it may be distributed under the terms of this Library General Public License (also called … 52 Activities other than copying, distribution and modification are not covered by this License; they … [all …]
/systemd-251/docs/
D	BOOT_LOADER_SPECIFICATION.md	13 setups. We'd like to improve this situation by getting everybody to commit to a 23 firmware includes a boot loader. The target audience for this specification is: 36 ## Why is there a need for this specification? 38 Of course, without this specification things already work mostly fine. But here's why we think this… 49 loader in their own partition headers. In this new scheme as all 61 code can parse the boot loader configuration, too, this allows for UIs that 67 * For boot loaders with configuration _scripts_ such as grub2, adopting this 90 * EFI is not universal yet (especially on non-x86 platforms), this 161 this specification. This specification only defines semantics of the `/loader/` 164 other software implementing this specification may choose to place other [all …]
D	USER_RECORD.md	42 for querying and enumerating records of this type, optionally acquiring them 68 2. Information about default IMAP, SMTP servers to use for this user 70 3. Parental control information to enforce on this user 91 Please note that this specification assumes that JSON numbers may cover the full 93 UINT64_MAX). Please read, write and process user records as defined by this 94 specification only with JSON implementations that provide this number range. 106 the user record). Fields contained in this object are security sensitive, 108 to see, but other users should not. In many ways this matches the data 127 machine ID of the host). Fields included in this section "bind" the object 131 record manager (such as `systemd-homed`). Data in this section is considered [all …]
D	ENVIRONMENT.md	18 the various tools. Note that this list only covers environment variables not 24 talking to PID 1; this has the same effect as the historical detection of 25 `chroot()`. Setting this variable to `0` instead has a similar effect as 28 set this to `1` if you maintain a package build system or similar and are 46 * `$SYSTEMD_OS_RELEASE` — if set, use this path instead of `/etc/os-release` or 51 * `$SYSTEMD_FSTAB` — if set, use this path instead of `/etc/fstab`. Only useful 54 * `$SYSTEMD_CRYPTTAB` — if set, use this path instead of `/etc/crypttab`. Only 58 * `$SYSTEMD_INTEGRITYTAB` — if set, use this path instead of 62 * `$SYSTEMD_VERITYTAB` — if set, use this path instead of 91 this only controls use of Unicode emoji glyphs, and has no effect on other [all …]
D	JOURNAL_NATIVE_PROTOCOL.md	18 The latter is what this document is about: if you are developing a program and 22 API that implements the client side of this protocol. This document explains 23 what this interface does behind the scenes, in case you'd like to implement a 32 `systemd-journald.service` listens. Each datagram sent to this socket 35 sent over this socket may come in one of two formats: 49 payload, but if this fails with an `EMSGSIZE` error it would immediately retry 72 byte. In this case, the key name is serialized as is, followed by a `\n` 75 `\n`. Example: a key `FOO` with a value `BAR` may be serialized using this 83 are easily recognized and understood by the human eye this way, without any 109 second serialization method described above must hence be used for this [all …]
D	PREDICTABLE_INTERFACE_NAMES.md	14 … As the driver probing is generally not predictable for modern technology this means that as soon … 16 …this problem multiple solutions have been proposed and implemented. For a longer time udev shipped… 18 …aces which incorporate their physical location on the mainboard. In a way this naming scheme is si… 40 ## Come again, what good does this do? 42 With this new scheme you now get: 45 …re is added or removed, i.e. no re-enumeration takes place (to the level the firmware permits this) 57 …this have any drawbacks? Yes, it does. Previously it was practically guaranteed that hosts equippe… 60 ## I don't like this, how do I disable this? 64 …f fixed names, so that the unpredictable kernel names are used again. For this, simply mask udev's… 70 …are/systemd/man/systemd.net-naming-scheme.html) man page. Please refer to this in case you are won…
D	TEMPORARY_DIRECTORIES.md	40 drop-ins. However this is not recommended, as it is fully safe only if these 56 (Linux; this doesn't bother with `/tmp/` or `/var/tmp/` at all, but uses the 68 recommended to turn this option on, it's highly recommended for applications 69 not to rely on this solely to avoid DoS vulnerabilities, because this option is 73 `/tmp/` and `/var/tmp/`. When this option is used, the per-service temporary 76 this option is not used. Also note that some applications use `/tmp/` and 77 `/var/tmp/` for sharing files and directories. If this option is turned on this 102 reading and writing. When operating this way it is recommended to delete the 107 suggestion above: files created this way are never linked under a filename 123 descriptors opened by a process are implicitly closed when it exits, this is [all …]
D	CGROUP_DELEGATION.md	16 concepts and interfaces involved with this. 21 comprehensive up-to-date information about all this, particular in light of the 39 wiki documentation into this very document, too.) 47 1. The no-processes-in-inner-nodes rule: this means that it's not permitted 52 exceptions to this rule, though. E.g. the root cgroup is special and allows 56 2. The single-writer rule: this means that each cgroup only has a single 63 These two rules have various effects. For example, one corollary of this is: if 70 violated. On cgroup v1 this rule didn't exist, and hence isn't enforced, even 72 either cgroup v1 nor cgroup v2 (this is UNIX after all, in the general case 80 kernel features in this area are only added to cgroup v2, and not cgroup v1 [all …]
D	PASSWORD_AGENTS.md	10 …nd of hardware or service. Right now this is used exclusively for encrypted hard-disk passphrases … 19 It is easy to write additional agents. The basic algorithm to follow looks like this: 27 …on use `kill(PID, 0)` and ignore the file if this returns `ESRCH`; there's no need to show the dat… 28 * `Echo=` specifies whether the input should be obscured. If this field is missing or is `Echo=0`, … 31 …password query dialog as soon as a) the `ask.xxxx` file is deleted, watch this with inotify. b) th… 39 …this all with manually invoking the "`systemd-ask-password`" tool on the command line. Pass `--no-… 41 …this. If systemd is used to maintain user sessions as well you can use a similar scheme to automat…
D	ROOT_STORAGE_DAEMONS.md	18 technology. Previously no clear path to make this work was available. This text 25 this needs to be set up by the initial RAM file system (initrd), i.e. on Fedora 63 ## What does this mean? 70 to do this in a tight loop as long as this results in any effect. From this 85 spree. To accomplish this the following logic is available starting with 91 of this logic needs to place the following at the top of its `main()` function: 99 And that's already it. Note that this functionality is only to be used by 101 root file system itself. Programs which use this functionality and are running 105 _Again: if your code is being run from the root file system, then this logic 113 otherwise doesn't. Something like this: [all …]
D	BUILDING_IMAGES.md	31 will be auto-generated on first boot and thus be truly unique. If this file 39 which is used to seed the kernel's random pool on boot. If this file is 61 for details. Note that by removing this file access to previously encrypted 62 credentials from this image is lost. The file is automatically generated if 74 without conflicts. However, this is problematic if the machine ID shall be 81 this the `kernel-install` logic knows the generalized entry token concept, 84 ID. The file `/etc/kernel/entry-token` may be used to configure this string 86 this file, for example the `IMAGE_ID=` or `ID=` field from 88 (also see below). It is recommended to do this before the `kernel-install` 97 i.e. the vendor OS resources) is empty (i.e. "unpopulated"). With this in mind [all …]
D	JOURNAL_EXPORT_FORMATS.md	12 _Note that this document describes the binary serialization format of journals only, as used for tr… 18 … to read without any special tools, but still binary safe where necessary. The format is like this: 21 …next field. Note that fields containing newlines cannot be formatted like this. Non-control UTF-8 … 23 …this way. Note that these meta-fields are only generated when actual journal files are serialized.… 125 _Note that this section describes the JSON serialization format of the journal only, as used for in… 136 …STAMP`, which contain the cursor string of this entry as string, and the realtime/monotonic timest… 138 Here's an example, illustrating all cases mentioned above. Consider this entry: 145 BINARY=this is a binary value \a 146 LARGE=this is a super large value (let's pretend at least, for the sake of this example)
D	CONTAINER_INTERFACE.md	37 in this context.) 40 mount some suitable TTY to `/dev/console`. If this is a pty, make sure to 75 (this only applies to cgroupv1, of course), to protect the controllers from 76 alteration from inside the containers. Or to turn this around: only the 99 implementation. With this in place the `ConditionVirtualization=` setting in 111 `/etc/machine-id` (if writable) when this option is used, hence you should 125 Note that this variable should not include the pty that `/dev/console` maps 131 running the container manager, if this is considered desirable, please parse 145 'ramfs'), and the absolute path to this directory exported in the 147 does this, the credentials passed to the service manager can be propagated [all …]
D	AUTOMATIC_BOOT_ASSESSMENT.md	65 encoding how many attempts to boot this entry shall still be made. The second 67 it have already been made. Each time a boot loader entry marked this way is 78 Here's an example walkthrough of how this all fits together. 90 indicating that at this point one attempt has started and thus only one less 93 4. Let's say this attempt to boot fails. On the following boot the boot loader 101 6. If this boot also fails, on the next boot the boot loader will see the 102 tag `+0-3`, i.e. the counter reached zero. At this point the entry will be 108 fails. Let's have a look at an alternative ending to this walkthrough. In this 139 system that this boot attempt shall be considered successful. 145 `4.14.11-300.fc27.x86_64.conf`. From this moment boot counting is turned [all …]
D	USERDB_AND_DESKTOPS.md	39 re-requesting it on resume this attack vector can be closed down effectively. 41 Supporting this mechanism requires support in the desktop environment, since 50 only revert back to the session after re-authentication via this system lock 51 screen (re-authentication in this case refers to passing the user's login 57 Note that this change in behavior is a good idea in any case, and does not 62 A display manager which supports this kind of out-of-context screen lock 63 operation needs to inform systemd-homed about this so that systemd-homed knows 68 to set this parameter to on. `systemd-homed` will not suspend home directories 70 suspending, as communicated via this parameter. 82 hook-up. On the command line this is exposed via the [all …]
D	GROUP_RECORD.md	33 `service` → A string, an identifier for the service managing this group record 34 (this field is typically in reverse domain name syntax.) 44 `members` → An array of strings, listing user names that are members of this 54 shall be considered "administrators" of this group. This field corresponds to 99 The fields in this section are defined identically to those in the matching 104 Currently no fields are defined in this section for group records. 122 At this time almost all Linux machines employ shadow passwords, thus the 132 A reasonable group record for a system group might look like this:
D	RANDOM_SEEDS.md	40 is not initialized. The provided random bytes will be of low quality in this 41 case however. Moreover the kernel will log about all programs using this 42 interface in this state, and which thus potentially rely on an uninitialized 60 includes random bytes generated this way in its entropy pool, but didn't use 61 to credit entropy for it (i.e. data from this source wasn't considered good 65 means systems with CPUs supporting this opcode will be able to very quickly 71 line to change that, but note that this is a global setting affect all 149 initialized, this is identical to `getrandom(0)`, returning cryptographically 176 this service typically runs relatively late during early boot: long after 179 not advised to rely exclusively on this functionality to seed the kernel's [all …]
/systemd-251/src/boot/efi/
D	shim.c	72 static EFIAPI EFI_STATUS security2_policy_authentication (const EFI_SECURITY2_PROTOCOL this, in security2_policy_authentication() argument 77 assert(this); in security2_policy_authentication() 81 status = es2fa(this, device_path, file_buffer, file_size, boot_policy); in security2_policy_authentication() 102 static EFIAPI EFI_STATUS security_policy_authentication (const EFI_SECURITY_PROTOCOL this, UINT32 … in security_policy_authentication() argument 111 assert(this); in security_policy_authentication() 141 return esfas(this, authentication_status, device_path_const); in security_policy_authentication()
/systemd-251/shell-completion/zsh/
D	_systemd	`8 {-h,--help}'[Show this help]' \ 17 {-h,--help}'[Show this help]' \ 26 {-h,--help}'[Show this help]' \ 35 {-h,--help}'[Show this help]' \ 49 {-h,--help}'[Show this help]' \ 57 {-h,--help}'[Show this help]' \ 62 {-h,--help}'[Show this help]' \`
/systemd-251/test/test-execute/
D	exec-standardinput-data.service	`6 ExecStart=/bin/sh -x -c 'd=$$(mktemp -d -p /tmp); echo -e "this is a test\nand this is more\nsometh… 9 StandardInputText=this is a test 10 StandardInputText=and this is more`
/systemd-251/units/
D	systemd-journald-dev-log.socket	`16 # Mount and swap units need this. If this socket unit is removed by an 18 # hence let's exclude this from isolate requests. 31 # block early. Note that journald internally uses the this socket both`
D	systemd-time-wait-sync.service.in	`14 # Note that this tool doesn't need CAP_SYS_TIME itself, but it's primary 16 # systemd-timesyncd.service, which is conditioned this way. There might be 17 # niche usecases where running this service independently is desired, but let's 18 # make this all "just work" for the general case, and leave it to local`

12 3 4 5 6 7 8 9 10 11

DADK
DragonBoot
DragonOS
DragonOS-0.1.0
DragonOS-0.1.1
DragonOS-0.1.10
DragonOS-0.1.2
DragonOS-0.1.3
DragonOS-0.1.4
DragonOS-0.1.5
DragonOS-0.1.6
DragonOS-0.1.7
DragonOS-0.1.8
DragonOS-0.1.9
DragonReach
DragonStub
Held
NovaShell
StarryEngine
busybox-1.35.0
dragonos-dsc
glibc-2.36
linux-2.4.37.9
linux-2.6.39
linux-3.4.99
linux-5.19.10
linux-6.1.9
linux-6.6.21
musl-1.2.4
smoltcp-0.9.1
systemd-251