summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* journal: log filtering options support in PID1Quentin Deslandes2022-12-151-0/+1
| | | | | | | | | Define new unit parameter (LogFilterPatterns) to filter logs processed by journald. This option is used to store a regular expression which is carried from PID1 to systemd-journald through a cgroup xattrs: `user.journald_log_filter_patterns`.
* Merge pull request #25723 from keszybz/generators-tmpYu Watanabe2022-12-151-1/+1
|\ | | | | Run generators with / ro and /tmp mounted
| * tree-wide: use mode=0nnn for mount optionZbigniew Jędrzejewski-Szmek2022-12-141-1/+1
| | | | | | | | | | | | This is an octal number. We used the 0 prefix in some places inconsistently. The kernel always interprets in base-8, so this has no effect, but I think it's nicer to use the 0 to remind the reader that this is not a decimal number.
* | doc: add language decorator on the code blockJiayi Chen2022-12-141-1/+1
| | | | | | Add `c` decorator on the code block for applying syntax highlighting.
* | doc: add an example code to lock the whole diskJanuary2022-12-131-0/+143
|/ | | | add an example to leverage `libsystemd` infrastructure to get the whole disk of a block device and take BSD lock on it #25046
* repart: support erofsLennart Poettering2022-12-101-2/+2
| | | | | | | | | | | | | | | So, i think "erofs" is probably the better, more modern alternative to "squashfs". Many of the benefits don't matter too much to us I guess, but there's one thing that stands out: erofs has a UUID in the superblock, squashfs has not. Having an UUID in the superblock matters if the file systems are used in an overlayfs stack, as overlayfs uses the UUIDs to robustly and persistently reference inodes on layers in case of metadata copy-up. Since we probably want to allow such uses in overlayfs as emplyoed by sysext (and the future syscfg) we probably should ramp up our erofs game early on. Hence let's natively support erofs, test it, and in fact mention it in the docs before squashfs even.
* ci: Labeler improvementsDaan De Meyer2022-12-091-0/+3
| | | | | | | | - Mention "/please-review" in the contributing guide - Remove "needs-rebase" on push - Don't add "please-review" if a green label is set - Don't add please-review label to draft PRs - Add please-review when a PR moves out of draft
* Implement --luks-pbkdf-force-iterations for homedAidan Dang2022-12-061-2/+5
|
* Merge pull request #25638 from bluca/rate_limit_configLuca Boccassi2022-12-061-0/+7
|\ | | | | pid1: add env var to override default mount rate limit burst
| * pid1: add env var to override default mount rate limit burstLuca Boccassi2022-12-051-0/+7
| | | | | | | | | | I am hitting the rate limit on a busy system with low resources, and it stalls the boot process which is Very Bad (TM).
* | doc: CentOS is EOL use CentOS streamJan Macku2022-12-051-1/+1
| |
* | doc: fix markdown-lint issues in `CONTRIBUTING.md`Jan Macku2022-12-051-6/+8
| |
* | doc: update link to systemd-rhel GitHub repoJan Macku2022-12-051-1/+1
|/ | | | | | systemd-rhel GitHub repository has been moved to new location: - https://github.com/redhat-plumbers
* core: add possibility to not track certain unit typesMichal Sekletar2022-11-241-0/+9
|
* boot: remove random-seed-modeJason A. Donenfeld2022-11-221-8/+0
| | | | | | | | Now that the random seed is used on virtualized systems, there's no point in having a random-seed-mode toggle switch. Let's just always require it now, with the existing logic already being there to allow not having it if EFI itself has an RNG. In other words, the logic for this can now be automatic.
* Merge pull request #25379 from keszybz/update-doc-linksLuca Boccassi2022-11-226-32/+34
|\ | | | | Update doc links
| * docs/BOOT_LOADER_INTERFACE: reword sentence to apply to both entry typesZbigniew Jędrzejewski-Szmek2022-11-211-3/+3
| |
| * tree-wide: BLS and DPS are now on uapi-group websiteZbigniew Jędrzejewski-Szmek2022-11-216-31/+33
| |
* | bootctl: install system token on virtualized systemsJason A. Donenfeld2022-11-211-11/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removing the virtualization check might not be the worst thing in the world, and would potentially get many, many more systems properly seeded rather than not seeded. There are a few reasons to consider this: - In most QEMU setups and most guides on how to setup QEMU, a separate pflash file is used for nvram variables, and this generally isn't copied around. - We're now hashing in a timestamp, which should provide some level of differentiation, given that EFI_TIME has a nanoseconds field. - The kernel itself will additionally hash in: a high resolution time stamp, a cycle counter, RDRAND output, the VMGENID uniquely identifying the virtual machine, any other seeds from the hypervisor (like from FDT or setup_data). - During early boot, the RNG is reseeded quite frequently to account for the importance of early differentiation. So maybe the mitigating factors make the actual feared problem significantly less likely and therefore the pros of having file-based seeding might outweigh the cons of weird misconfigured setups having a hypothetical problem on first boot.
* | pcrphase: add $SYSTEMD_PCRPHASE_STUB_VERIFY env var for overriding stub checkLennart Poettering2022-11-171-1/+6
| |
* | boot: implement kernel EFI RNG seed protocol with proper hashingJason A. Donenfeld2022-11-142-28/+32
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rather than passing seeds up to userspace via EFI variables, pass seeds directly to the kernel's EFI stub loader, via LINUX_EFI_RANDOM_SEED_TABLE_GUID. EFI variables can potentially leak and suffer from forward secrecy issues, and processing these with userspace means that they are initialized much too late in boot to be useful. In contrast, LINUX_EFI_RANDOM_SEED_TABLE_GUID uses EFI configuration tables, and so is hidden from userspace entirely, and is parsed extremely early on by the kernel, so that every single call to get_random_bytes() by the kernel is seeded. In order to do this properly, we use a bit more robust hashing scheme, and make sure that each input is properly memzeroed out after use. The scheme is: key = HASH(LABEL || sizeof(input1) || input1 || ... || sizeof(inputN) || inputN) new_disk_seed = HASH(key || 0) seed_for_linux = HASH(key || 1) The various inputs are: - LINUX_EFI_RANDOM_SEED_TABLE_GUID from prior bootloaders - 256 bits of seed from EFI's RNG - The (immutable) system token, from its EFI variable - The prior on-disk seed - The UEFI monotonic counter - A timestamp This also adjusts the secure boot semantics, so that the operation is only aborted if it's not possible to get random bytes from EFI's RNG or a prior boot stage. With the proper hashing scheme, this should make boot seeds safe even on secure boot. There is currently a bug in Linux's EFI stub in which if the EFI stub manages to generate random bytes on its own using EFI's RNG, it will ignore what the bootloader passes. That's annoying, but it means that either way, via systemd-boot or via EFI stub's mechanism, the RNG *does* get initialized in a good safe way. And this bug is now fixed in the efi.git tree, and will hopefully be backported to older kernels. As the kernel recommends, the resultant seeds are 256 bits and are allocated using pool memory of type EfiACPIReclaimMemory, so that it gets freed at the right moment in boot.
* locale: honour new env var $SYSTEMD_UTF8=Lennart Poettering2022-11-101-0/+6
| | | | | | | | | This is useful to force off fancy unicode glyph use (i.e. use "->" instead of "→"), which is useful in tests where locales might be missing, and thus control via $LC_CTYPE is not reliable. Use this in TEST-58, to ensure the output checks we do aren't confused by missing these glyphs being unicode or not.
* Revert "initrd: extend SYSTEMD_IN_INITRD to accept non-ramfs rootfs"Zbigniew Jędrzejewski-Szmek2022-11-091-7/+3
| | | | | | | | | | | | | | | | This reverts commit 1f22621ba33f8089d2ae5fbcaf8b3970dd68aaf0. As described in the reverted commit, we don't want to get rid of the check completely. But the check requires opting-in by setting SYSTEMD_IN_INITRD=lenient, which is cumbersome and doesn't seem to actually happen. https://bugzilla.redhat.com/show_bug.cgi?id=2137631 is caused by systemd refusing to treat the system as an initrd because overlayfs is used. Let's revert this approach and do something that doesn't require opt-in instead. I don't think it makes sense to keep support for "SYSTEMD_IN_INITRD=lenient" or "SYSTEMD_IN_INITRD=auto". To get "auto" behaviour, just unset the option. And "lenient" will be reimplemented as a better check. Thus the changes to the option interface are completely reverted.
* docs: DPS and BLS have moved to uapi-group.orgLuca Boccassi2022-11-022-1167/+2
|
* docs/HACKING.md: clarify some portionsWilliam Roberts2022-10-311-4/+6
| | | | | | | Clarify portions of HACKING.md so folks don't spend as much time as I did on it. Signed-off-by: William Roberts <william.c.roberts@intel.com>
* docs: update translation strings before new releaseFrantisek Sumsal2022-10-201-9/+10
|
* tree-wide: replace "plural(s)" by "plurals"Zbigniew Jędrzejewski-Szmek2022-10-171-5/+5
| | | | | | | | (s) is just ugly with a vibe of DOS. In most cases just using the normal plural form is more natural and gramatically correct. There are some log_debug() statements left, and texts in foreign licenses or headers. Those are not touched on purpose.
* Merge pull request #24629 from DaanDeMeyer/mkosi-kernelDaan De Meyer2022-10-111-0/+20
|\ | | | | mkosi: Optionally build a kernel image from mkosi.kernel/
| * mkosi: Optionally build a kernel image from mkosi.kernel/Daan De Meyer2022-09-291-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If mkosi.kernel/ exists, the mkosi script will try to build a kernel image from it. We use the architecture defconfig as a base and add our own extra configuration on top. We also add some extra tooling to the build image required to build the kernel and include some documentation in HACKING.md on how to use this new feature. To avoid the kernel sources from being copied into the build or final image (which we don't want because it takes a while), we put the mkosi.kernel/ directory in .gitignore and use "SourceFileTransfer=mount" so that the sources are still accessible in the build image.
* | Implement --luks-sector-size for homedAidan Dang2022-10-071-1/+5
| |
* | journal: Store offsets to tail entry array objects in chainDaan De Meyer2022-10-071-1/+18
| | | | | | | | | | | | | | | | | | Previously, we'd iterate an entry array from start to end every time we added an entry offset to it. To speed up this operation, we cache the last entry array in the chain and how many items it contains. This allows the addition of an entry to the chain to be done in constant time instead of linear time as we don't have to iterate the entire chain anymore every time we add an entry.
* | journal: Use 32-bit entry item object offsets in compact modeDaan De Meyer2022-10-071-6/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To do this, we move EntryItem out of journal-def.h and turn it into a host only struct in native endian mode so we can still use it to ship the necessary info around. Aside from that, the changes are pretty simple, we introduce some extra functions to access the right field depending on the mode and convert all the other code to use those functions instead of accessing the raw fields. We also drop the unused entry item hash field in compact mode. We already stopped doing anything with this field a while ago, now we actually drop it from the format in compact mode.
* | journal: Use 32-bit entry array offsets in compact modeDaan De Meyer2022-10-071-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before: OBJECT TYPE ENTRIES SIZE Unused 0 0B Data 3610336 595.7M Field 5310 285.2K Entry 3498326 1.2G Data Hash Table 29 103.1M Field Hash Table 29 151.3K Entry Array 605991 1011.6M Tag 0 0B Total 7720021 2.9G After: OBJECT TYPE ENTRIES SIZE Unused 0 0B Data 3562667 591.0M Field 3971 213.6K Entry 3498566 1.2G Data Hash Table 20 71.1M Field Hash Table 20 104.3K Entry Array 582647 505.0M Tag 0 0B Total 7647891 2.4G
* | journal: Enable compact modeDaan De Meyer2022-10-071-0/+7
| | | | | | | | | | | | We also add an environment variable $SYSTEMD_JOURNAL_COMPACT that can be used to disable compact mode if needed (similar to $SYSTEMD_JOURNAL_KEYED_HASH).
* | journal: Add compact modeDaan De Meyer2022-10-071-0/+4
| | | | | | | | | | | | This adds a new flag in preparation for incompatible journal changes which will be gated behind this flag. The max file size of journal files in compact mode is limited to 4 GiB.
* | docs/CONTRIBUTING: strenghten language about ABI stability, fix links, other ↵Zbigniew Jędrzejewski-Szmek2022-10-011-13/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | tweaks The text made it sound like breaking ABI in libsystemd is allowed with good reasons. In fact, we plan never to do this, so make the language stronger. Also remind people about distro forums for reporting bugs. Those are probably a better place than systemd-devel for new users. Also, add some missing articles and apostrophes, fix URLs, remove repeated phrases, etc.
* | docs/CONTRIBUTING: explain various labels and add link to "reviewable" PRsZbigniew Jędrzejewski-Szmek2022-09-301-1/+17
| | | | | | | | | | | | | | | | | | | | The linked filter gives an up-to-date list of pull requests that need review. (Yes, there's too many.) We used to set 'needs-review' label, but that is not available to non-members, and also every pull requests which is not labeled 'reviewed/needs-rework'/'ci-fails/needs-rework'/'needs-rebase' can and should be reviewed. If this is merged, I'll drop the 'needs-review' label.
* | docs/NETWORK_ONLINE: systemd.network hyperlink fixSarah Brofeldt2022-09-281-1/+1
|/
* Merge pull request #24799 from poettering/initrd-ftwLuca Boccassi2022-09-235-32/+33
|\ | | | | use "initrd" rather than "initial RAM disk" or "initramfs" to refernce the concept
| * tree-wide: also settle on "initrd" instead of "initial RAM disk"Lennart Poettering2022-09-235-32/+33
| | | | | | | | | | With this the concept is now called the same way everywhere except where historical info is relevant or where the other names are API.
* | Merge pull request #24635 from DaanDeMeyer/repart-verity-sigDaan De Meyer2022-09-231-2/+2
|\ \ | | | | | | repart: Add support for generating verity sig partitions
| * | docs: Mention that "certificateFingerprint" source should be in DERDaan De Meyer2022-09-231-2/+2
| |/
* | doc: drop remaining references to LGTM.comYu Watanabe2022-09-232-4/+4
|/
* Merge pull request #24709 from keszybz/partition-table-constantsLennart Poettering2022-09-211-146/+146
|\ | | | | Expose various GPT UUIDs as public contants and link them up in docs
| * docs/DPS: use the SD_GPT_* constants here tooZbigniew Jędrzejewski-Szmek2022-09-211-146/+146
| |
| * sd-gpt, docs: define s390 before s390xZbigniew Jędrzejewski-Szmek2022-09-201-5/+5
| | | | | | | | | | | | | | In all other cases we have the older variant before the newer. And since we generate some documentation tables from the header, this order is also visible for users. Let's restore the order. This commit does 4565246911adbdd1b20d8944c0754772788a768c in a slightly different fashion.
* | boot-loader-spec: undo redefinition of $BOOTLennart Poettering2022-09-201-134/+185
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In 53c26db4dac0f5b79ca2a57364ee7df78a14bbfd the meaning of $BOOT was redefined. I think that's quite problematic, since the concept is implemented in code and interface of bootctl. Thus, I think we should stick to the original definition, which is: "where to *place* boot menu entries" (as opposed to "where to *read* boot menu entries from"). The aforementioned change was done to address two things afaiu: 1. it focussed on a $BOOT as the single place to put boot entries in, instead of mentioning that both ESP and $BOOT are expected to be the source 2. it mentioned the /loader/ dir (as location for boot loader resources) itself as part of the spec, which however only really makes sense in the ESP. /loader/entries/ otoh makes sense in either the ESP or $BOOT. With this rework I try to address these two issues differently: 1. I intend to make clear the $BOOT is the "primary" place to put stuff in, and is what should be mounted to /boot/. 2. The ESP (if different from $BOOT) is listed as "secondary" source to read from, and is what should be mounted to /efi/. NB we now make the distinction between "where to put" (which is single partition) and "where to read from". 3. This drops any reference of the /loader/ dir witout the /entries/ suffix. Only the full /loader/entries/ dir (and its companion file /loader/entries.srel) are now mentioned. Thus isolated /loader/ directory hence becomes irrelevant in the spec, and the fact that sd-boot maintains some files there (and only in the ESP) is kept out of the spec, because it is irrelevant to other boot loaders. 4. It puts back the suggestion to mount $BOOT to /boot/ and the ESP to /efi/ (and suggests adding a symlink or bind mount if both are the same partition). Why? Because the dirs are semantically unrelated: it's OK and common to have and ESP but no $BOOT, hence putting ESP inside of a useless, non-existing "ghost" dir /boot/ makes little sense. More importantly though, because these partitions are typically backed by VFAT we want to maintain them as an autofs, with a short idle delay, so that the file systems are unmounted (and thus fully clean) at almost all times. This doesn't work if they are nested within each other, as the establishment of the inner autofs would pin the outer one, making the excercise useless. Now I don't think the spec should mention autofs (since that is an implementation detail), but it should arrange things so that this specific, very efficient, safe and robust implementation can be implemented. The net result should be easy from an OS perspective: 1. *Put* boot loader entries in /boot/, always. 2. *Read* boot loader entries from both /boot/ and /efi/ -- if these are distinct. 3. The only things we define in the spec are /loader/entries/*.conf and /EFI/Linux/*.efi in these two partitions (well, and the companion file /loader/entries.srel 4. /efi/ and /boot/ because not nested can be autofs. 5. bootctl code and interface (in particular --esp-path= and --boot-path=) match the spec again. `bootctl -x` and `bootctl -p` will now print the path to $BOOT and ESP again, matching the concepts in the spec again. From the sd-boot perspective things are equally easy: 1. Read boot enrties from ESP and XBOOTLDR. 2. Maintain boot loader config/other resources in ESP only. And that's it. Fixes: #24247
* | boot-loader-spec: fix typoLennart Poettering2022-09-201-1/+1
| |
* | boot-loader-spec: add comment about case sensitivity of file namesLennart Poettering2022-09-201-0/+5
| |
* | Delete CNAMEZbigniew Jędrzejewski-Szmek2022-09-201-1/+0
| |
View Lorry Controller Status