/systemd-251/LICENSES/ |
D | CC0-1.0.txt | 17 exclusive Copyright and Related Rights (defined below) upon the creator 18 and subsequent owner(s) (each and all, an "owner") of an original work of 19 authorship and/or a database (each, a "Work"). 22 the purpose of contributing to a commons of creative, cultural and 23 scientific works ("Commons") that the public can reliably and without fear 25 works, reuse and redistribute as freely as possible in any form whatsoever 26 and for any purposes, including without limitation commercial purposes. 28 culture and the further production of creative, cultural and scientific 30 part through the use and efforts of others. 32 For these and/or other purposes and motivations, and without any [all …]
|
D | LGPL-2.0-or-later.txt | 8 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing… 14 …our freedom to share and change it. By contrast, the GNU General Public Licenses are intended to g… 16 …e, applies to some specially designated Free Software Foundation software, and to any other librar… 18 …and charge for this service if you wish), that you receive source code or can get it if you want i… 22 …they can relink them with the library, after making changes to the library and recompiling it. And… 24 …teps: (1) copyright the library, and (2) offer you this license which gives you legal permission t… 26 …warranty for this free library. If the library is modified by someone else and passed on, we want … 30 …ense is quite different from the ordinary one; be sure to read it in full, and don't assume that a… 32 …and simply using it. Linking a program with a library, without changing the library, is in some se… 38 …rms and conditions for copying, distribution and modification follow. Pay close attention to the d… [all …]
|
D | OFL-1.1.txt | 8 This license is copied below, and is also available with a FAQ at: 19 efforts of academic and linguistic communities, and to provide a free and 20 open framework in which fonts may be shared and improved in partnership 23 The OFL allows the licensed fonts to be used, studied, modified and 26 redistributed and/or sold with any software provided that any reserved 27 names are not used by derivative works. The fonts and derivatives, 34 Holder(s) under this license and clearly marked as such. This may 35 include source files, build scripts and documentation. 54 redistribute, and sell modified and unmodified copies of the Font 61 redistributed and/or sold with any software, provided that each copy [all …]
|
/systemd-251/docs/ |
D | ARCHITECTURE.md | 17 Directories in `src/` provide the implementation of all daemons, libraries and 18 command-line tools shipped by the project. There are many, and more are 24 You might wonder what kind of common code belongs in `src/shared/` and what 30 between multiple components and does not need to be in `src/basic/`, should be 45 `src/libsystemd/`, `src/nss-*`, `src/login/pam_systemd.*`, and files under 51 Code located in `src/core/` implements the main logic of the systemd system (and user) 54 BPF helpers written in C and used by PID 1 can be found under `src/core/bpf/`. 58 The system and session manager supports a large number of unit settings. These can generally 63 3. Via the `systemd-run` and `systemctl set-property` commands 68 1. *unit* *files* are parsed in `src/core/load-fragment.c`, with many simple and fixed-type [all …]
|
D | CGROUP_DELEGATION.md | 2 title: Control Group APIs and Delegation 8 # Control Group APIs and Delegation 11 cgroup access, such as container managers and similar.* 14 control groups (cgroups) a bit and are trying to integrate your software with 16 concepts and interfaces involved with this. 18 What's described here has been part of systemd and documented since v205 19 times. However, it has been updated and improved substantially, even 33 * [Writing VM and Container Managers](https://www.freedesktop.org/wiki/Software/systemd/writing-vm-… 37 with cgroups and systemd, in particular as they shine more light on the various 48 to have processes directly attached to a cgroup that also has child cgroups and [all …]
|
D | CODING_STYLE.md | 12 - 8ch indent, no tabs, except for files in `man/` which are 2ch indent, and 13 still no tabs, and shell scripts, which are 4ch indent, and no tabs either. 23 overdo it, ~109ch should be enough really. The `.editorconfig`, `.vimrc` and 94 expressions, and align them vertically. Define both an enum and a type for 112 "invalid" enum value, and set it to `-EINVAL`. That way the enum type can 122 ## Code Organization and Semantics 127 set of conservative and common extensions, such as fixed size integer types 131 have different size in memory and slightly different semantics, also see 132 below.) Both for internal and external code it's OK to use even newer 133 features and GCC extension than "gnu11", as long as there's reasonable [all …]
|
D | BOOT_LOADER_SPECIFICATION.md | 10 _TL;DR: Currently there's no common boot scheme across architectures and 14 single boot configuration format that is based on drop-in files, and thus is 15 robust, simple, works without rewriting configuration files and is free of 21 between various boot loader implementations, operating systems, and userspace 29 * Distribution and Core OS developers, in order to create these snippets at 33 * OS Installer developers, to prepare their installation media and for setting 46 MBR, and only that one installation can then update the boot loader 48 configured to never touch the MBR and instead install a chain-loaded boot 51 place, and all participants implicitly cooperate due to removal of name 52 collisions and can install/remove their own boot menu entries at free will, [all …]
|
D | TEMPORARY_DIRECTORIES.md | 2 title: Using /tmp/ and /var/tmp/ Safely 8 # Using `/tmp/` and `/var/tmp/` Safely 10 `/tmp/` and `/var/tmp/` are two world-writable directories Linux systems 11 provide for temporary files. The former is typically on `tmpfs` and thus 12 backed by RAM/swap, and flushed out on each reboot. The latter is typically a 13 proper, persistent file system, and thus backed by physical storage. This 21 If the `$TMPDIR` environment variable is set, use that path, and neither use 26 for details about these two (and most other) directories of a Linux system. 30 Note that `/tmp/` and `/var/tmp/` each define a common namespace shared by all 41 directories are pre-created during early boot, and thus problematic if package [all …]
|
D | USER_GROUP_API.md | 3 category: Users, Groups and Home Directories 11 and [JSON Group Records](GROUP_RECORD.md) documents) that are defined on the 14 [`getpwnam(3)`](http://man7.org/linux/man-pages/man3/getpwnam.3.html) and 19 user/group records from local services, and allows local subsystems to provide 28 This simple API only exposes only three method calls, and requires only a small 35 preferring Varlink over D-Bus and other IPCs in this context was made for three 38 1. User/Group record resolution should work during early boot and late shutdown 40 service for D-Bus generally runs as regular system daemon and is hence only 44 system that natively operates with JSON data is natural and clean. 46 3. IPC systems such as D-Bus do not provide flow control and are thus unusable [all …]
|
D | CONTAINER_INTERFACE.md | 20 running systemd it may just set it before invoking systemd, and systemd will 24 2. Make sure to pre-mount `/proc/`, `/sys/`, and `/sys/fs/selinux/` before 25 invoking systemd, and mount `/sys/`, `/sys/fs/selinux/` and `/proc/sys/` 30 uts and pid namespaces enabled, the entire `/proc/sys` can be left writable). 31 systemd and various other subsystems (such as the SELinux userspace) have 33 (It's OK to mount `/sys/` as `tmpfs` btw, and only mount a subset of its 34 sub-trees from the real `sysfs` to hide `/sys/firmware/`, `/sys/kernel/` and 36 condition is what systemd looks for, and is what is considered to be the API 39 3. Pre-mount `/dev/` as (container private) `tmpfs` for the container and bind 55 4. `systemd-udevd` is not available in containers (and refuses to start), and [all …]
|
D | USER_NAMES.md | 3 category: Users, Groups and Home Directories 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 15 processing users/group defined by other subsystems and when defining users/groups 18 will enforce the same rules everywhere and not make them configurable or 27 is defined as [lower and upper case ASCII letters, digits, period, 28 underscore, and 36 `^[a-z][-a-z0-9]*$`, i.e. only lower case ASCII letters, digits and 44 allows underscores and hyphens, but the latter not as first character. Also, 49 32 characters, with upper and lower case letters, digits, underscores, [all …]
|
D | INITRD_INTERFACE.md | 12 file system archive that is unpacked by the kernel and contains the first 13 userspace code that runs. It typically finds and transitions into the actual 14 root file system to use. systemd supports both initrd and initrd-less boots. If 16 from the initrd to systemd in order to avoid duplicate work and to provide 18 describe the interfaces that exist between the initrd and systemd. These 19 interfaces are currently used by dracut and the ArchLinux initrds. 21 * The initrd should mount `/run/` as a tmpfs and pass it pre-mounted when 26 appropriate and passes it pre-mounted to the main system, to avoid the 32 initrd environment to which systemd will pivot back and the `shutdown` 35 to set up this directory and executable in the right way so that this works [all …]
|
D | PORTABILITY_AND_STABILITY.md | 2 title: Interface Portability and Stability 8 # Interface Portability and Stability Promise 10 …pers and programs might rely on. Starting with version 26 (the first version released with Fedora … 16 …and all other command line utilities installed in `$PATH` and documented in a man page. We will ma… 20 …it names** and their semantics. To be precise the ones that are necessary for normal services, and… 22 …and other daemons**. We try to always preserve backwards compatibility, and intentional breakage i… 24 * For a more comprehensive and authoritative list, consult the chart below. 28 … e.g. the high-level unit states inactive, active, deactivating, and so on, as well (and in partic… 32 The following interfaces are considered private to systemd, and are not and will not be covered by … 34 * **Undocumented switches** to `systemd`, `systemctl` and otherwise. [all …]
|
D | UIDS-GIDS.md | 2 title: Users, Groups, UIDs and GIDs on systemd Systems 3 category: Users, Groups and Home Directories 8 # Users, Groups, UIDs and GIDs on systemd Systems 10 Here's a summary of the requirements `systemd` (and Linux) make on UID/GID 11 assignments and their ranges. 13 Note that while in theory UIDs and GIDs are orthogonal concepts they really 15 that whatever we say about UIDs applies to GIDs in mostly the same way, and all 16 the special assignments and ranges for UIDs always have mostly the same 31 bit confused the `nobody` user is called `nfsnobody` there (and they have a 37 `setresuid()`, `chown()` and friends treat -1 as a special request to not [all …]
|
D | JOURNAL_FILE_FORMAT.md | 24 making this available primarily to allow review and provide documentation. Note 28 and the code disagree, the code is right. That said we'll of course try hard to 29 keep this document up-to-date and accurate. 34 these files. It provides you with full access to the files, and will not 35 withhold any data. If you find a limitation, please ping us and we might add 42 format is much simpler to parse, but complete and accurate. Due to its 50 instead! This document is primarily for your entertainment and education. 54 the properties of a journal entry and so on. If not, please go and read up, 59 usually don't), and the same field might have multiple values assigned within 64 but received various compatible and incompatible additions since. [all …]
|
D | USER_RECORD.md | 3 category: Users, Groups and Home Directories 12 and consume records in a more extensible format of a dictionary of key/value 16 manages `human` user home directories and embeds these JSON records 21 processes these JSON records for users that log in, and applies various 23 levels and more. 26 processes these JSON records of users that log in, and applies various 33 both for look-up and enumeration. 42 for querying and enumerating records of this type, optionally acquiring them 46 passwd`, and are extensible for other applications. For example, the record may 55 3. Resource Management settings (such as CPU/IO weights, memory and tasks [all …]
|
D | CREDENTIALS.md | 8 # System and Service Credentials 11 acquiring and passing credential data to systems and services. The precise 13 intended to provide systems and services with potentially security sensitive 14 cryptographic keys, certificates, passwords, identity information and similar 16 parameterizing systems and services. 20 inherited down the process tree, have size limitations, and issues with binary 21 data) or simple, unencrypted files on disk. `systemd`'s system and service 25 1. Service credentials are acquired at the moment of service activation, and 44 5. Credentials may optionally be encrypted and authenticated, either with a key 46 encryption is supposed to *just* *work*, and requires no manual setup. (That [all …]
|
D | BUILDING_IMAGES.md | 12 disk and booting it up. When building such "golden" OS images for 16 [`mkosi`](https://github.com/systemd/mkosi) OS image builder developed and 18 builder it's recommended to keep the following concepts and recommendations in 23 Typically the same OS image shall be deployable in multiple instances, and each 31 will be auto-generated on first boot and thus be truly unique. If this file 32 is not reset, and carries a valid ID every instance of the system will come 33 up with the same ID and that will likely lead to problems sooner or later, 41 same random data that is included in the image, and thus possibly generate 52 and 59 and [all …]
|
D | BOOT_LOADER_INTERFACE.md | 10 systemd can interface with the boot loader to receive performance data and 11 other information, and pass control information. This is only supported on EFI 12 systems. Data is transferred between the boot loader and systemd in EFI 22 when the loader finished its work and is about to execute the kernel. The 23 time spent in the loader is the difference between `LoaderTimeExecUSec` and 32 currently in use. It may be modified both by the boot loader and by the 42 timeout is turned off, and the menu is shown indefinitely. 63 identifier that was booted. It is set by the boot loader and read by 67 number of flags bits that are set by the boot loader and passed to the OS and 82 the responsibility of the boot loader to ensure the quality and integrity of [all …]
|
/systemd-251/ |
D | LICENSE.GPL2 | 6 Everyone is permitted to copy and distribute verbatim copies 12 freedom to share and change it. By contrast, the GNU General Public 13 License is intended to guarantee your freedom to share and change free 16 Foundation's software and to any other program whose authors commit to 23 have the freedom to distribute copies of free software (and charge for 26 in new free programs; and that you know you can do these things. 39 We protect your rights with two steps: (1) copyright the software, and 41 distribute and/or modify the software. 43 Also, for each author's protection and ours, we want to make certain 45 software. If the software is modified by someone else and passed on, we [all …]
|
D | TODO | 23 * fedora: suggest auto-restart on failure, but not on success and not on coredump. also, ask people… 27 * fedora: update policy to declare access mode and ownership of unit files to root:root 0644, and a… 43 - how to make changes to sysctl and sysfs attributes 54 …mergency" mode, vs. "rescue" mode, vs. "multi-user" mode, vs. "graphical" mode, and the debug shell 56 - instantiated apache, dovecot and so on 71 * link up selected blog stories from man pages and unit files Documentation= fields 77 * rework mount.c and swap.c to follow proper state enumeration/deserialization 86 images that owned by arbitrary UIDs, and are owned/managed by the users, but 88 privileged dirs inside of unprivileged dirs, and thus containers really 93 file to move there, since it is managed by privileged code (i.e. homed) and [all …]
|
D | LICENSE.LGPL2.1 | 6 Everyone is permitted to copy and distribute verbatim copies 16 freedom to share and change it. By contrast, the GNU General Public 17 Licenses are intended to guarantee your freedom to share and change 22 Free Software Foundation and other authors who decide to use it. You 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 32 it in new free programs; and that you are informed that you can do 45 with the library after making changes to the library and recompiling 49 library, and (2) we offer you this license, which gives you legal 50 permission to copy, distribute and/or modify the library. [all …]
|
D | NEWS | 1 systemd System and Service Manager 8 and CLOCK_BOOTTIME is now assumed to always exist. 14 routes to addresses specified in AllowedIPs= was added and enabled by 24 * The org.freedesktop.portable1 methods GetMetadataWithExtensions() and 27 The current implementation was judged to be broken and unusable, and 29 and backward compatibility broken instead on the assumption that 50 reasonably, hence separate ourselves from that and use PCR 12 55 *and* the old-style PCR 8. It's strongly advised to migrate all users 65 supposed to be used, and we already had a rule that with the 74 * The tmpfiles entries that create the /run/systemd/netif directory and [all …]
|
D | README | 1 systemd System and Service Manager 27 ...and many others 38 ≥ 4.10 for cgroup-bpf egress and ingress hooks 39 ≥ 4.15 for cgroup-bpf device hook and cpu controller in cgroup v2 44 ≥ 5.7 for BPF links and the BPF LSM hook 46 Kernel versions below 4.15 have significant gaps in functionality and 49 upstream support and testing are limited. 61 CONFIG_FHANDLE (libudev, mount and bind mount handling) 71 Legacy hotplug slows down the system and confuses udev: 74 Userspace firmware loading is not supported and should be disabled in [all …]
|
/systemd-251/.lgtm/cpp-queries/ |
D | PotentiallyDangerousFunction.ql | 20 f.getQualifiedName() = "fgets" and 23 f.getQualifiedName() = "strtok" and 26 f.getQualifiedName() = "strsep" and 29 f.getQualifiedName() = "dup" and 32 f.getQualifiedName() = "htonl" and 35 f.getQualifiedName() = "htons" and 38 f.getQualifiedName() = "ntohl" and 41 f.getQualifiedName() = "ntohs" and 44 f.getQualifiedName() = "strerror" and 47 f.getQualifiedName() = "accept" and [all …]
|