summaryrefslogtreecommitdiffstats
path: root/README (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Bump kernel recommended baseline to v5.4Mike Yuan2024-10-161-4/+4
|
* README: update requirements for signed dm-verityLuca Boccassi2024-07-041-2/+3
| | | | | | | The newest kconfig enabling DB-verified dm-verity images is queued for 6.11: https://patchwork.kernel.org/project/dm-devel/patch/20240617220037.594792-1-luca.boccassi@gmail.com/
* README: add missing CONFIG_MEMCG kernel config option for oomdJames Hilliard2024-07-031-0/+1
| | | | | | | We need to enable this otherwise systemd-oomd.service fails to start. Fixes: ConditionControlGroupController=memory was not met
* README: update link for backportsZbigniew Jędrzejewski-Szmek2024-05-281-2/+1
|
* various: update links to usr-mergeZbigniew Jędrzejewski-Szmek2024-05-281-2/+2
|
* README: mention fq_codelzzywysm2024-02-221-0/+2
| | | | | | | | | In 2014, systemd started choosing fq_codel as the default_qdisc in order to fight internet bufferbloat. https://github.com/systemd/systemd/commit/e6c253e363dee77ef7e5c5f44c4ca55cded3fd47 https://github.com/systemd/systemd/commit/fa98c99ea7f7c5bec3962fa52f4d3496a9777024 While the subsequent change made this change no longer trigger warnings if fq_codel wasn't present, it is still recommended to have this enabled. Add the necessary kernel configuration to the documentation.
* README: bump the gcc baseline to 8.4Frantisek Sumsal2024-02-051-1/+1
| | | | | | | | | | | We already use __VA_OPT__ in multiple places, which was introduced in gcc 8 [0], so let's bump the baseline to reflect that. I chose gcc 8.4, as that was the lowest 8.x version I could easily get my hands on when I verified this (on Ubuntu Focal with the gcc-8 package). Closes: #31191 [0] https://gcc.gnu.org/gcc-8/changes.html
* Remove a few references to dracutDaan De Meyer2024-01-241-1/+0
| | | | | Let's remove some explicit references to dracut as we prefer initrds built with mkosi these days.
* Document kernel configs required for reading credentials from SMBIOSDaan De Meyer2023-12-041-0/+4
|
* docs: excorcise NIS from nsswitch.confLennart Poettering2023-09-201-6/+7
| | | | | | | | | | | | | | | | Let's replace the "compat" module in our proposed nsswitch.conf configuration with "files", since it is not 1995 anymore. Fedora and other distros have deprecated and removed NIS support a while back. While others still retain some support I am not sure we should advertise it in our examples. Downstream can of course still use "compat" instead of "files" if they want to, but let's not confuse people who don't care about NIS anymore with this. Also, bring the nsswitch.conf snippet in README in line with what our man pages say. Also see: https://fedoraproject.org/wiki/Changes/retire_NIS_user_space_utils
* Drop split-usr and unmerged-usr supportLuca Boccassi2023-07-281-28/+7
| | | | | | | | | | As previously announced, execute order 66: https://lists.freedesktop.org/archives/systemd-devel/2022-September/048352.html The meson options split-usr, rootlibdir and rootprefix become no-ops that print a warning if they are set to anything other than the default values. We can remove them in a future release.
* README: mention that meson 0.60 is now requiredLuca Boccassi2023-07-071-1/+1
|
* README: strenghten wording regarding static libsLennart Poettering2023-06-301-18/+27
| | | | | | | static versions of libsystems.so are not really supportable, and encourages mix&match which we cannot really support. Make the wording about this stronger in the README, since people apparently don'd read to the last paragraph.
* README: drop busybox requirementYu Watanabe2023-05-181-1/+0
| | | | Follow-up for 5656759d0617594ee8e850a258a21d3e187bf02c.
* README: describe how our libraries are linkedZbigniew Jędrzejewski-Szmek2023-05-161-2/+38
| | | | | | | In https://github.com/systemd/systemd/pull/27637#issuecomment-1547517316 we discussed disclaiming warranty when distros do version mixing. But to make this disclaimer meaningful, we need to document what options are available.
* README: require python >= 3.7, clean up module descriptionsZbigniew Jędrzejewski-Szmek2023-05-091-6/+6
| | | | | | | | | | | | | | libpython was added in 2cc86f094a8c316f7feb0336df3827a3264b116d, it seems because of python-systemd module that we built. But libpython by itself is not enough for actual python programs, and now we also list python itself, so let's drop libpython from the list. meson requires >= 3.7. We have CI that runs on CentOS8 with Python 3.6, but let's not provide official support for an EOL Python version. Individual distributions can provide backports, but we don't need to mention that in the user-facing docs. According to [1], 3.7 is on life support and 3.6 is EOL. [1] https://devguide.python.org/versions/
* docs: update unit name for sd-tmpfiles-setupMike Yuan2023-03-181-1/+1
|
* boot: Bring back bootloader buildsJan Janssen2023-03-101-0/+1
| | | | | | | | | | | | This adds back sd-boot builds by using meson compile targets directly. We can do this now, because userspace binaries use the special dependency that allows us to easily separate flags, so that we don't pass anything to EFI builds that shouldn't be passed. Additionally, we pass a bunch of flags to hopefully disable/override any distro provided flags that should not be used for EFI binaries. Fixes: #12275
* tree-wide: Drop gnu-efiJan Janssen2023-03-101-1/+0
| | | | | | | This drops all mentions of gnu-efi and its manual build machinery. A future commit will bring bootloader builds back. A new bootloader meson option is now used to control whether to build sd-boot and its userspace tooling.
* meson: merge our two valgrind configuration conditions into oneZbigniew Jędrzejewski-Szmek2023-02-221-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | Most of the support for valgrind was under HAVE_VALGRIND_VALGRIND_H, i.e. we would enable if the valgrind headers were found. The operations then we be conditionalized on RUNNING_UNDER_VALGRIND. But in a few places we had code which was conditionalized on VALGRIND, i.e. the config option. I noticed because I compiled with -Dvalgrind=true on a machine that didn't have valgrind.h, and the build failed because RUNNING_UNDER_VALGRIND was not defined. My first idea was to add a check that the header is present if the option is set, but it seems better to just remove the option. The code to support valgrind is trivial, and if we're !RUNNING_UNDER_VALGRIND, it has negligible cost. And the case of running under valgrind is always some special testing/debugging mode, so we should just do those extra steps to make valgrind output cleaner. Removing the option makes things simpler and we don't have to think if something should be covered by the one or the other configuration bit. I had a vague recollection that in some places we used -Dvalgrind=true not for valgrind support, but to enable additional cleanup under other sanitizers. But that code would fail to build without the valgrind headers anyway, so I'm not sure if that was still used. If there are uses like that, we can extend the condition for cleanup_pools().
* README: explicitly note that util-linux's mount/swap are requiredLuca Boccassi2023-02-101-1/+3
| | | | | These are the most visible and hard requirements, as we use options that busybox does not provide, so list them explicitly to avoid surprises
* ci: install pefileZbigniew Jędrzejewski-Szmek2022-12-071-0/+1
|
* README: note Kconfig for verifying DDIs via MoK keysLuca Boccassi2022-11-141-0/+5
| | | | Also note them in the mkosi.build kernel config list
* README: use https on one more linkLuca Boccassi2022-11-121-1/+1
|
* README: Fix libbpf minimum versionDaan De Meyer2022-10-171-1/+1
| | | | This didn't get properly updated as part of #24511
* Bump libbpf version to 0.7Daan De Meyer2022-10-061-1/+1
| | | | | | | | We already depend on the skeleton APIs introduced in libbpf 0.7 so let's bump our minimum version to reflect that. We don't enforce bpf compilation on mkosi anymore since not all distros have sufficiently up-to-date libbpf available.
* README: we don't use crypto API in kernel anymoreLennart Poettering2022-09-071-5/+0
| | | | | | | This effectively reverts 9c7f7d86f86322b76fc903ca8a06b87c4be4bd4a. We dropped kernel crypto API use with 1fc8d0c9dd6a21de81e49cfa01af4a4d9a3ed37d, hence catch up in README.
* README: make section title less confusingLennart Poettering2022-09-071-1/+1
| | | | This is about glibc NSS, not about the TLS implementation library NSS.
* README: drop some spurious empty lines, we otherwise don't place after ↵Lennart Poettering2022-09-071-2/+0
| | | | section titles
* README: use right emoji UTF-8 sequences for stop/warning signLennart Poettering2022-09-071-5/+5
|
* README: clarify baseline situation a bit (add emojis!)Lennart Poettering2022-09-061-4/+9
|
* README: gcc now has a minimum requirement of 4.7matoro2022-07-141-1/+2
|
* man: update the description of taint flagsZbigniew Jędrzejewski-Szmek2022-07-091-1/+3
| | | | | | We had a description in README, and an outdated list in the man page. I think we should keep a reference-style list in the man page. The description in README is more free-form.
* tree-wide: streamline wiki linksBenjamin Franzke2022-05-211-1/+1
| | | | | | | | * Avoid traling slash as most links are defined without. * Always use https:// protocol and www. subdomain Allows for easier tree-wide linkvalidation for our migration to systemd.io.
* README: fix typoZbigniew Jędrzejewski-Szmek2022-05-181-1/+1
|
* README: say that recent releases are supportedZbigniew Jędrzejewski-Szmek2022-05-161-0/+20
| | | | | Prompted by the discussion in https://github.com/systemd/systemd/pull/23391.
* README: recommend --no-rebuild for sudo meson installZbigniew Jędrzejewski-Szmek2022-05-161-1/+1
| | | | | sudo and rebuilding don't mix well. C.f. fe2b7631ad20b0e518b9f566608ff5f9b84d4d8b.
* README: add missing colons and wrap to ~80 columnsZbigniew Jędrzejewski-Szmek2022-05-161-66/+59
| | | | | Some paragraphs were narrow for no good reason. Let's make things a bit more uniform.
* README: mention kernel requirement for ambient capabilitiesYu Watanabe2022-05-061-0/+1
| | | | Closes #23231.
* README: recommend zstd over xzZbigniew Jędrzejewski-Szmek2022-04-121-1/+1
| | | | | | | | git archive automatically uses gzip when --output=*.tar.gz is used, but not for other extensions. Thus we need to invoke the compressor separately :( It's a good pattern to use a variable for the repeating number, so let's recommend that.
* docs: stop recommending meson compileZbigniew Jędrzejewski-Szmek2022-04-121-3/+3
| | | | | | | | | | | | | | | | | | With meson-0.60, meson compile stopped working with some targets: $ meson compile -C build update-man-rules ERROR: Can't invoke target `update-man-rules`: ambiguous name. Add target type and/or path: `PATH/NAME:TYPE` This is obviously a regression in meson, but based on a chat with the maintainers, it seems that there's some disagreement as to whether 'meson compile' is useful and how exactly it should work. Since we're already at meson 0.60.3 and this hasn't been fixed, and people generally don't seem to consider this an issue, let's return to documenting the usual practice of 'ninja -C build' that just works everywhere. (Since nobody has raised any fuss in systemd, it means that people are generally using the shorter form during development too. I only noticed because I pasted a command from the release docs when preparing -rc1.)
* Merge pull request #23009 from ↵Lennart Poettering2022-04-081-0/+1
|\ | | | | | | | | keszybz/fix-detection-of-libsystemd-shared-with-suffix Fix detection of libsystemd-shared with suffix
| * README: add one more kernel-version lineZbigniew Jędrzejewski-Szmek2022-04-071-0/+1
| | | | | | | | | | I want to add as many as possible to show people that each kernel version has something nice to entice them to keep moving up ;)
* | core: taint if /usr is unmergedLuca Boccassi2022-04-061-0/+7
|/ | | | | | 9afd5e7b975e8051c011ff9c07c95e80bd954469 introduced a build-time taint, introduce a runtime one as well, in preparation for removing support for unmerged-usr in a future release
* README: describe taint flags and how to check themZbigniew Jędrzejewski-Szmek2022-04-051-8/+25
| | | | | We should have this somewhere. We talk about versions of things in the README, so it seems as good a place as any.
* README: say kernel 4.15 is the minimum recommendedZbigniew Jędrzejewski-Szmek2022-04-051-8/+15
| | | | | | | | | | | | After various long discussions (https://lists.freedesktop.org/archives/systemd-devel/2022-March/047587.html, https://lwn.net/Articles/889610/), there is no clear answer what the minimum version should be. Bumping the version above 3.15 doesn't allow us to make any significant simplifications (unless we went *much* higher). In particular, even renameat2() is not fully supported with latest kernel versions, e.g. nfs still doesn't have it. And the bpf stuff is optional anyway. So let's just say that 4.15 is what we recommend, because it provides fairly complete cgroups-v2, but without any removals of compat in the code.
* time-util: assume CLOCK_BOOTTIME always existsLennart Poettering2022-03-281-1/+1
| | | | | | | | Let's raise our supported baseline a bit: CLOCK_BOOTTIME started to work with timerfd in kernel 3.15 (i.e. back in 2014), let's require support for it now. This will raise our baseline only modestly from 3.13 → 3.15.
* meson: Drop required libfdisk version to 2.32Daan De Meyer2022-02-241-1/+1
| | | | | | | | | | | | We initially pinned this to 2.33 in e71f5585b9b0580428f9530d0a485265c9c25165 because libfdisk 2.32 in CentOS 8 didn't have https://github.com/karelzak/util-linux/commit/2f35c1ead621f42f32f7777232568cb03185b473 backported. If we check now, we can see it has been backported (https://git.centos.org/rpms/util-linux/blob/c8s/f/SOURCES/0048-libfdisk-count-gaps-to-possible-size-when-resize.patch) which means we can drop the required version to 2.32 instead of 2.33.
* README: CONFIG_KCMP is the new kernel compile time option for kcmp()Lennart Poettering2022-02-081-1/+1
| | | | Fixes: #21947
* README: link to the new pageZbigniew Jędrzejewski-Szmek2022-01-121-4/+6
| | | | | Lennart's blog is now mostly of historical interest, and the wiki landing page has been replaced by systemd.io.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-29 19:42:11 +0100