summaryrefslogtreecommitdiff
path: root/README
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* change req meson versiongregzuro2021-10-261-1/+1
| | | | since `meson compile` first appears in 0.54.0
* sd-boot: Require gnu-efi 3.0.5Jan Janssen2021-10-171-0/+1
| | | | | | | | | This version is from 2017 and should be stale enough to not cause an outrage. All the relevant distros have it or a newer version. We also already depend on some symbols defined in 3.0.5 anyway, so let's take the opportunity to reduce our missing_efi.h baggage.
* README: document LSM BPF requirementsIago López Galeiras2021-10-061-1/+8
|
* add LICENSES/README.md explaining the license situationLuca Boccassi2021-10-011-6/+1
|
* README: add requirements for RestrictNetworkInterfaces=Mauricio Vásquez2021-08-191-1/+3
| | | | Signed-off-by: Mauricio Vásquez <mauricio@kinvolk.io>
* rpm: use a helper script to actually invoke systemctl commandsZbigniew Jędrzejewski-Szmek2021-07-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Instead of embedding the commands to invoke directly in the macros, let's use a helper script as indirection. This has a couple of advantages: - the macro language is awkward, we need to suffix most commands by "|| :" and "\", which is easy to get wrong. In the new scheme, the macro becomes a single simple command. - in the script we can use normal syntax highlighting, shellcheck, etc. - it's also easier to test the invoked commands by invoking the helper manually. - most importantly, the logic is contained in the helper, i.e. we can update systemd rpm and everything uses the new helper. Before, we would have to rebuild all packages to update the macro definition. This raises the question whether it makes sense to use the lua scriptlets when the real work is done in a bash script. I think it's OK: we still have the efficient lua scripts that do the short scripts, and we use a single shared implementation in bash to do the more complex stuff. The meson version is raised to 0.47 because that's needed for install_mode. We were planning to raise the required version anyway…
* docs: update autofs Kconfig nameAndrea Pappacoda2021-06-241-1/+1
|
* README: drop reference to KinvolkLennart Poettering2021-05-261-5/+0
| | | | | | Kinvolk got bought by Microsoft recently, I doubt they'd even be open for engineering services like this, hence let's drop the free advertisement.
* README: point at IRC channel on the new networkMantas Mikulėnas2021-05-251-1/+1
|
* Drop dependency on m4Zbigniew Jędrzejewski-Szmek2021-05-191-1/+1
| | | | | | | | | | | | | | | | m4 was hugely popular in the past, because autotools, automake, flex, bison and many other things used it. But nowadays it much less popular, and might not even be installed in the buildroot. (m4 is small, so it doesn't make a big difference.) (FWIW, Fedora dropped make from the buildroot now, https://fedoraproject.org/wiki/Changes/Remove_make_from_BuildRoot. I think it's reasonable to assume that m4 will be dropped at some point too.) The main reason to drop m4 is that the syntax is not very nice, and we should minimize the number of different syntaxes that we use. We still have two (configure_file() with @FOO@ and jinja2 templates with {{foo}} and the pythonesque conditional expressions), but at least we don't need m4 (with m4_dnl and `quotes').
* meson, mkosi: pull in jinja2 as requiredZbigniew Jędrzejewski-Szmek2021-05-191-0/+1
| | | | In preparation for subsequent changes.
* readme: update README with requirements for bpfJulia Kartseva2021-04-261-1/+20
|
* README: add config_psi as requirement for systemd-oomdAnita Zhang2021-02-231-0/+3
|
* tree-wide: fix links to systemd.io pagesZbigniew Jędrzejewski-Szmek2021-02-191-1/+1
| | | | | Having the extra slash at the end is not a problem, just inconsistent. But the links with .html or .md return 404.
* Adding an explanation for CONFIG_NET requirement (#18600)heretoenhance2021-02-161-1/+1
| | | * README: replace CONFIG_NET with CONFIG_UNIX in requirements list
* Deprecate builds with split-usr, prepare for removalZbigniew Jędrzejewski-Szmek2021-02-031-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | There is no technical reason to support systems with split-usr, except for backwards compatibility. Even though systemd itself makes an effort to support this, many other tools aren't as careful. Despite those efforts, we (collectively) get it wrong often, because doing it "wrong" on systems with merged-usr has no consequences. Since almost all developers are on such systems, any issues are only discovered late. Supporting this split-usr mode makes both code and documentation more complicated. The split is purely artificial and has no justification except to allow old installation to not update. Mechanisms to update existing systems are available though: Fedora did that in https://fedoraproject.org/wiki/Features/UsrMove, Debian has the usrmerge package. The next version of Debian will only support systems with split-usr=false, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978636#178: The Technical Committee resolves that Debian 'bookworm' should support only the merged-usr root filesystem layout, dropping support for the non-merged-usr layout. Let's start warning if split-usr mode is used, in preparation to removing the split in one of the future releases.
* docs: `mesonconf` is not a valid command, `meson configure` isigo958622021-01-121-2/+2
| | | | | Meson documentation for `meson configure` https://mesonbuild.com/Commands.html#configure
* tree-wide: suggest meson command lines instead of ninja onesLennart Poettering2020-12-171-5/+5
| | | | | | | This only changes documentation. In various places we call "ninja" directly. I figured it would be safer to leave those in place for now, given the meson replacement commands lines appears to be supported in newer meson versions only.
* meson: add min version for libfdiskAnita Zhang2020-08-191-0/+1
| | | | | | | | Was trying to run src/partition/test-repart.sh on CentOS 8 and the first resize call kept failing with ERANGE. Turned out that CentOS 8 comes with libfdisk-devel-2.32.1 which is missing https://github.com/karelzak/util-linux/commit/2f35c1ead621f42f32f7777232568cb03185b473 (in libfdisk 2.33 and up).
* README: fix indentationLennart Poettering2020-08-171-8/+8
| | | | All paragraphs are indented to 8 spaces, but one. Fix that.
* nss-mymachines: drop support for UID/GID resolvingLennart Poettering2020-07-141-11/+11
| | | | | | | | | | | | | | Now that we make the user/group name resolving available via userdb and thus nss-systemd, we do not need the UID/GID resolving support in nss-mymachines anymore. Let's drop it hence. We keep the module around, since besides UID/GID resolving it also does hostname resolving, which we care about. (One of those days we should replace that by some Varlink logic between nss-resolve/systemd-resolved.service too) The hooks are kept in the NSS module, but they do not resolve anything anymore, in order to keep compat at a maximum.
* dissect/nspawn: add support for dm-verity root hash signatureLuca Boccassi2020-06-251-1/+5
| | | | | | Since cryptsetup 2.3.0 a new API to verify dm-verity volumes by a pkcs7 signature, with the public key in the kernel keyring, is available. Use it if libcryptsetup supports it.
* coredump: add zstandard support for coredumpsNorbert Lange2020-05-041-0/+1
| | | | | this will hook libzstd into coredump, using this format as default.
* Revert "Drop dbus activation stub service"Lennart Poettering2019-12-201-1/+3
| | | | | | | | | | | | | | | This reverts commit 07125d24eedb71693b3bf2b1f0730cd01aaac2dd. In contrast to what is claimed in #13396 dbus-broker apparently does care for the service file to be around, and otherwise will claim "Service Not Activatable" in the time between systemd starting up the broker and connecting to it, which the stub service file is supposed to make go away. Reverting this makes the integration test suite pass again on host with dbus-broker (i.e. current Fedora desktop). Tested with dbus-broker-21-6.fc31.x86_64.
* resolved: require at least version 3.6.0 of GnuTLS for DNS-over-TLSIwan Timmer2019-10-291-1/+1
| | | Increase the required version to ensure TLS 1.3 is always supported when using GnuTLS for DNS-over-TLS and allow further changes to use recent API additions.
* trivial: rename chromeos to chromiumosTim Teichmann2019-10-071-1/+1
|
* Add missing license file and information for ↵Tim Teichmann2019-10-051-0/+1
| | | | | | tools/chromeos/gen_autosuspend_rules.py (#13729) The license file for the python script that was commited with b61d777abeecd8b6c76035e11899aae210633534 was missing. The license was copied from https://chromium.googlesource.com/chromiumos/platform2/+/master/LICENSE.
* Drop dbus activation stub serviceMichael Biebl2019-08-301-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | This fixes the following problem: > At the very end of the boot, just after the first user logs in > (usually using sddm / X) I get the following messages in my logs: > Nov 18 07:02:33 samd dbus-daemon[2879]: [session uid=1000 pid=2877] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 > Nov 18 07:02:33 samd dbus-daemon[2879]: [session uid=1000 pid=2877] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 These messages are caused by the "stub" service files that systemd installs. It installed them because early versions of systemd activation required them to exist. Since dbus 1.11.0, a dbus-daemon that is run with --systemd-activation automatically assumes that o.fd.systemd1 is an activatable service. As a result, with a new enough dbus version, /usr/share/dbus-1/services/org.freedesktop.systemd1.service and /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service should become unnecessary, and they can be removed. dbus 1.11.0 was released 2015-12-02. Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914015
* codespell: fix spelling errorsBen Boeckel2019-04-291-1/+1
|
* README: mention that we need tzdata >= 2014fZbigniew Jędrzejewski-Szmek2019-02-281-0/+1
| | | | | | | zone1970.tab was added in that version. Not that it makes sense to use outdata timezone tables, but people do strange things. C.f. https://github.com/nodatime/nodatime/issues/319.
* readme: Minor style and spacing fixFilipe Brandenburger2019-02-151-2/+1
| | | | | | Fix section header for stable branches and backports. All the other headings end in a colon and have no blank lines between them and the body of the section, so fix this one accordingly.
* README: mention that meson-0.49 is required to build PIEsYu Watanabe2019-01-131-1/+3
| | | | Follow-up for 4e4bbc439eb7f16a608f457d3eaac08c60633212.
* Revert "pam_systemd: drop setting DBUS_SESSION_BUS_ADDRESS"Zbigniew Jędrzejewski-Szmek2019-01-041-1/+1
| | | | | | | | | | | This reverts commit 2b2b7228bffef626fe8e9f131095995f3d50ee3b. Fixes #11293. Removing the environment variable causes problems, e.g. Xfce and Chromium and ... don't communicate with the running dbus instance. If they attempt to start their own instance, things become even more confusing. Those packages could be fixed one by one, but removing the variable right now is causing too many problems.
View Lorry Controller Status