| /systemd-251/ |
| D | LICENSE.LGPL2.1 | 7 of this license document, but changing it is not allowed.
9 [This is the first released version of the Lesser GPL. It also counts
10 as the successor of the GNU Library Public License, version 2, hence
21 specially designated software packages--typically libraries--of the
27 When we speak of free software, we are referring to freedom of use,
29 you have the freedom to distribute copies of free software (and charge
31 it if you want it; that you can change the software and use pieces of
38 you if you distribute copies of the library or if you modify it.
40 For example, if you distribute copies of the library, whether gratis
59 Finally, software patents pose a constant threat to the existence of
[all …]
|
| D | LICENSE.GPL2 | 7 of this license document, but changing it is not allowed.
15 General Public License applies to most of the Free Software
21 When we speak of free software, we are referring to freedom, not
23 have the freedom to distribute copies of free software (and charge for
25 if you want it, that you can change the software or use pieces of it
31 distribute copies of the software, or if you modify it.
33 For example, if you distribute copies of such a program, whether
51 patents. We wish to avoid the danger that redistributors of a free
64 under the terms of this General Public License. The "Program", below,
67 that is to say, a work containing the Program or a portion of it,
[all …]
|
| D | NEWS | 28 thus the usual procedure of adding a new set of methods was skipped,
30 nobody can be affected given the current state of this interface.
37 historically been a source of bugs. Furthermore, kernels ≥5.6 provide
41 of RDRAND has been removed. x86 systems ≥Broadwell that are running
47 rather than PCR 8. This improves usefulness of the measurements on
60 of pcap.
99 make the OS images independent of any machine ID, and ensure that the
101 but on the other hand means that multiple parallel installations of
107 value of the IMAGE_ID= or ID= field of /etc/os-release or another
112 that disambiguates the format of the entries in the /loader/entries/
[all …]
|
| /systemd-251/LICENSES/ |
| D | CC0-1.0.txt | 14 Statement of Purpose
16 The laws of most jurisdictions throughout the world automatically confer
18 and subsequent owner(s) (each and all, an "owner") of an original work of
22 the purpose of contributing to a commons of creative, cultural and
24 of later claims of infringement build upon, modify, incorporate in other
27 These owners may contribute to the Commons to promote the ideal of a free
28 culture and the further production of creative, cultural and scientific
30 part through the use and efforts of others.
33 expectation of additional consideration or compensation, the person
35 is an owner of Copyright and Related Rights in the Work, voluntarily
[all …]
|
| D | LGPL-2.0-or-later.txt | 8 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing…
10 [This is the first released version of the library GPL. It is numbered 2 because it goes with vers…
18 …of free software, we are referring to freedom, not price. Our General Public Licenses are designed…
20 …ons translate to certain responsibilities for you if you distribute copies of the library, or if y…
22 For example, if you distribute copies of the library, whether gratis or for a fee, you must give th…
24 Our method of protecting your rights has two steps: (1) copyright the library, and (2) offer you th…
32 …al and legal sense, the linked executable is a combined work, a derivative of the original library…
34 Because of this blurred distinction, using the ordinary General Public License for libraries did no…
36 …of non-free programs would deprive the users of those programs of all benefit from the free status…
44 …der or other authorized party saying it may be distributed under the terms of this Library General…
[all …]
|
| D | OFL-1.1.txt | 17 The goals of the Open Font License (OFL) are to stimulate worldwide
18 development of collaborative font projects, to support the font creation
19 efforts of academic and linguistic communities, and to provide a free and
28 however, cannot be released under any other type of license. The
33 "Font Software" refers to the set of files released by the Copyright
40 "Original Version" refers to the collection of Font Software components as
44 or substituting -- in part or in whole -- any of the components of the
52 Permission is hereby granted, free of charge, to any person obtaining
53 a copy of the Font Software, to use, study, copy, merge, embed, modify,
54 redistribute, and sell modified and unmodified copies of the Font
[all …]
|
| /systemd-251/docs/ |
| D | JOURNAL_FILE_FORMAT.md | 10 _Note that this document describes the binary on-disk format of journals only.
12 For transfer of journal data across the network there's the [Journal Export Format](JOURNAL_EXPORT_…
23 This document explains the basic structure of the file format on disk. We are
27 only ultimately authoritative description of the format, so if this document
28 and the code disagree, the code is right. That said we'll of course try hard to
31 Instead of implementing your own reader or writer for journal files we ask you
39 API our recommendation is to make use of the [Journal Export
46 you want to use as base of your project. You want our [C
53 This document assumes you have a basic understanding of the journal concepts,
54 the properties of a journal entry and so on. If not, please go and read up,
[all …]
|
| D | GVARIANT-SERIALIZATION.md | 14 1. A fixed header of "yyyyuu"
15 2. Additional header fields of "a(yv)"
23 The header consists of the following:
29 u Length of the body, i.e. the length of part 4 above
53 structure of (yyyyuta{tv}v).
59 Regarding the framing of dbus2, also see:
63 The first four bytes of the header are defined the same way for dbus1
65 protocol version, so that the remainder of the message can be safely
66 made sense of just by looking at the first 32bit.
68 Note that the length of the body is no longer included in the header
[all …]
|
| D | GROUP_RECORD.md | 13 Conceptually, much of what applies to JSON user records also applies to JSON
14 group records. They also consist of seven sections, with similar properties and
19 `groupName` → A string with the UNIX group name. Matches the `gr_name` field of
24 field of user records. A string in DNS domain name syntax.
27 `realName` field of user records, and accepts arbitrary strings, as long as
30 `disposition` → The disposition of the group, conceptually identical to the
31 same field of user records. A string.
37 epoch 1970) of the last time the group record has been modified. (Covers only
41 ID (GID) to use for the group. This corresponds to the `gr_gid` field of
44 `members` → An array of strings, listing user names that are members of this
[all …]
|
| D | USER_RECORD.md | 11 glibc NSS) `struct passwd`. Various components of systemd are able to provide
12 and consume records in a more extensible format of a dictionary of key/value
26 processes these JSON records of users that log in, and applies various
36 effect of `DynamicUser=` in service unit files) as these advanced JSON
37 records, making them discoverable to the rest of the system.
42 for querying and enumerating records of this type, optionally acquiring them
80 also be dropped in number of drop-in directories as files. See
92 integer range of -2^63 … 2^64-1 without loss of precision (i.e. INT64_MIN …
99 structure, consisting of seven distinct "sections". Specifically:
101 1. Various fields are placed at the top-level of user record (the `regular`
[all …]
|
| D | CGROUP_DELEGATION.md | 15 what systemd has to offer there. Here's a bit of documentation about the
18 What's described here has been part of systemd and documented since v205
21 comprehensive up-to-date information about all this, particular in light of the
22 poor implementations of the components interfacing with systemd of current
43 Much of the philosophy behind these concepts is based on a couple of basic
44 design ideas of cgroup v2 (which we however try to adapt as far as we can to
49 vice versa. A cgroup is either an inner node or a leaf node of the tree, and if
60 should manipulate it at the same time. This rule ensures that various pieces of
63 These two rules have various effects. For example, one corollary of this is: if
74 be in constant pain as various pieces of software will fight over cgroup
[all …]
|
| D | USER_GROUP_API.md | 13 API takes both the role of what
23 records may be dropped in number of drop-in directories as files where they are
29 subset of the Varlink functionality.
33 The API described in this document is based on a simple subset of the
34 mechanisms described by [Varlink](https://varlink.org/). The choice of
49 D-Bus is not suitable, as any such streaming of messages would be considered
50 flooding in D-Bus' logic, and thus possibly result in termination of
52 enumerating potentially large numbers of users and groups, D-Bus is simply
66 queries on behalf of the client, drastically simplifying client
73 make look-ups efficient, and the simple rule of "first successful lookup wins"
[all …]
|
| D | USER_NAMES.md | 10 The precise set of allowed user and group names on Linux systems is weakly
11 defined. Depending on the distribution a different set of requirements and
12 restrictions on the syntax of user/group names are enforced — on some
14 the interest of interoperability systemd enforces different rules when
16 itself, following the principle of "Be conservative in what you send, be
17 liberal in what you accept". Also in the interest of interoperability systemd
25 * On POSIX the set of [valid user
30 with the restriction that hyphen is not allowed as first character of the
33 string is a valid user name as well as a string of gigabytes in length.
39 though. This rule enforces a minimum length of one character but no maximum
[all …]
|
| D | ARCHITECTURE.md | 12 This section will attempt to provide a high-level overview of the various
13 components of the systemd repository.
17 Directories in `src/` provide the implementation of all daemons, libraries and
24 You might wonder what kind of common code belongs in `src/shared/` and what
37 - may not use any code outside of `src/basic/`
41 - may not use any code outside of `src/basic/`, `src/libsystemd/`
47 - may not use any code outside of `src/basic/`, `src/libsystemd/`, `src/shared/`
51 Code located in `src/core/` implements the main logic of the systemd system (and user)
58 The system and session manager supports a large number of unit settings. These can generally
88 corresponding module. While most of the tests can be run by any user, some
[all …]
|
| D | PORTABILITY_AND_STABILITY.md | 10 …26 (the first version released with Fedora 15) we promise to keep a number of them stable and comp…
14 …format**. Unit files written now will stay compatible with future versions of systemd. Extensions …
16 …of `systemd`, `systemctl`, `loginctl`, `journalctl`, and all other command line utilities installe…
20 * Some of the **"special" unit names** and their semantics. To be precise the ones that are necessa…
22 * **The D-Bus interfaces of the main service daemon and other daemons**. We try to always preserve …
26 …these interfaces too. In the meantime we will however try to keep breakage of these interfaces at …
28 * **The set of states of the various state machines used in systemd**, e.g. the high-level unit sta…
38 One of the main goals of systemd is to unify basic Linux configurations and service behaviors acros…
40 …of the latter interfaces, or we will tell your mom, and she won't love you anymore. You are welcom…
42 …ons, but if in the future there are very good reasons to change or get rid of an interface we have…
[all …]
|
| D | BOOT_LOADER_SPECIFICATION.md | 15 robust, simple, works without rewriting configuration files and is free of
40 * To make the boot more robust, as no explicit rewriting of configuration files
42 * To allow an out of the box boot experience on any platform without the need
43 of traditional firmware mechanisms (e.g. BIOS calls, UEFI Boot Services)
45 to fight over which boot loader becomes the primary one in possession of the
47 configuration of it freely. Other Linux installs have to be manually
51 place, and all participants implicitly cooperate due to removal of name
53 without interfering with the entries of other installed operating systems.
56 configuration files. For the sake of uniformity, we should do the same for
64 * To unify and thus simplify configuration of the various boot loaders around,
[all …]
|
| D | CONTAINER_INTERFACE.md | 13 systemd has a number of interfaces for interacting with container managers,
14 when systemd is used inside of an OS container. If you work on a container
33 (It's OK to mount `/sys/` as `tmpfs` btw, and only mount a subset of its
59 container (see above). Various clients of `systemd-udevd` also check the
60 read-only state of `/sys/`, including PID 1 itself and `systemd-networkd`.
72 "upper" parts read-only of the hierarchies, and only allow write-access to
74 all controller hierarchies with exception of `name=systemd` fully read-only
75 (this only applies to cgroupv1, of course), to protect the controllers from
77 cgroup sub-tree of the container itself (on cgroupv2 in the unified
81 7. Create the control group root of your container by either running your
[all …]
|
| D | HOME_DIRECTORY.md | 11 manages home directories of regular ("human") users. Each directory it manages
12 encapsulates both the data store and the user record of the user, so that it
15 the format used by these home directories, in the context of the storage
20 Inside of the home directory a file `~/.identity` contains the JSON formatted
21 user record of the user. It follows the format defined in
34 If the plain directory or `btrfs` subvolume storage mechanism of
58 pair of Base64 encoded data fields. The first field contains a salt value, the
71 the `homectl` command line.) The local password of the user is used to log into
82 This is the most advanced and most secure storage mechanism and consists of a
92 name. The LUKS2 volume must contain a LUKS2 token field of type
[all …]
|
| D | CONTRIBUTING.md | 14 … **exclusively** for tracking **bugs** and **feature** **requests** (RFEs) of systemd. If you are …
15 …of systemd in the GitHub Issue tracker. If you are using an older version of systemd, please conta…
16 …uest issue (RFE), please always check first if the newest upstream version of systemd already impl…
30 See [reporting of security vulnerabilities](SECURITY.md).
39 … easy to miss the update without an explicit comment). If you are a member of the systemd project …
44 …ot able to process and reply to your issue or PR right-away. We have a lot of work to do, but we a…
51 …se-by-case exceptions might be applied at the discretion of the maintainers. The current set of bu…
59 In case a new feature is added to both `systemd` and one of its dependencies, we expect the corresp…
60 be merged upstream in the dependency before accepting our side of the implementation.
61 Making use of new kernel syscalls can be achieved through compat wrappers in our tree (see: `src/ba…
[all …]
|
| D | JOURNAL_NATIVE_PROTOCOL.md | 13 * STDOUT/STDERR of programs via `StandardOutput=journal` + `StandardError=journal` in service files…
22 API that implements the client side of this protocol. This document explains
30 The native protocol of `journald` is spoken on the
35 sent over this socket may come in one of two formats:
52 A client probably should bump up the `SO_SNDBUF` socket option of its `AF_UNIX`
57 Each datagram should consist of a number of environment-like key/value
64 key/value pair is serialized via one of two methods:
71 * The second method should be used if the value of a field contains a `\n`
74 encoding the size of the value, followed by the literal value data, followed by
79 If the value of a key/value pair contains a newline character (`\n`), it *must*
[all …]
|
| D | CODE_OF_CONDUCT.md | 12 - Participants will be tolerant of opposing views.
13 - Participants must ensure that their language and actions are free of personal attacks and dispara…
14 - When interpreting the words and actions of others, participants should always assume good intenti…
19 …of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the projec…
21 …e project team is obligated to maintain confidentiality with regard to the reporter of an incident.
|
| D | PORTABLE_SERVICES.md | 10 systemd (since version 239) supports a concept of "Portable Services".
12 two specific features of container management:
17 2. Stricter default security policies, i.e. sand-boxing of applications.
23 is put together known concepts to cover a specific set of use-cases in a
28 A portable service is ultimately just an OS tree, either inside of a directory,
36 The OS tree/image can be created with any tool of your choice. For example, you
62 root directory than the rest of the system. Hence, the intent is not to run
67 One point of differentiation: since programs running as "portable services" are
69 under Docker), but as normal processes. A corollary of that is that they aren't
71 the execution environment is mostly shared with the rest of the system.
[all …]
|
| D | ROOT_STORAGE_DAEMONS.md | 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
[all …]
|
| /systemd-251/shell-completion/zsh/ |
| D | _udevadm | 7 …'--query=[Query the database for specified type of device data. It needs the --path or --name to i…
8 '--path=[The devpath of the device to query.]:sys files:_files -P /sys/ -W /sys' \
9 …'--name=[The name of the device node or a symlink to query]:device files:_files -P /dev/ -W /dev' \
11 …'--attribute-walk[Print all sysfs properties of the specified device that can be used in udev rule…
13 '--export-prefix=[Add a prefix to the key name of exported values.]:prefix' \
14 …'--device-id-of-file=[Print major/minor numbers of the underlying device, where the file lives on.…
15 '--export-db[Export the content of the udev database.]' \
24 '--verbose[Print the list of devices which will be triggered.]' \
27 '--type=[Trigger a specific type of devices.]:types:(all devices subsystems failed)' \
28 …'--action=[Type of event to be triggered.]:actions:(add change remove move online offline bind unb…
[all …]
|
| /systemd-251/sysctl.d/ |
| D | 50-coredump.conf.in | 1 # This file is part of systemd.
4 # under the terms of the GNU Lesser General Public License as published by
5 # the Free Software Foundation; either version 2.1 of the License, or
8 # See sysctl.d(5) for the description of the files in this directory.
11 # by the kernel will start a second copy of itself as the
12 # systemd-coredump@.service, which will do the actual processing and storing of
24 # the specified number of crashes in parallel. The value of 16 is chosen to
29 # owned by a user/group other than the real user/group ID of the process, or
33 # of the running process (and not the filesystem-user-ID which the kernel uses
|