summaryrefslogtreecommitdiff
path: root/README
Commit message (Collapse)AuthorAgeFilesLines
...
* 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.
* Drop support for lz4 < 1.3.0Zbigniew Jędrzejewski-Szmek2018-10-291-1/+1
| | | | | | lz4-r130 was released on May 29th, 2015. Let's drop the work-around for older versions. In particular, we won't test any new code against those ancient releases, so we shouldn't pretend they are supported.
* resolved: basic OpenSSL support for DNS-over-TLSIwan Timmer2018-07-271-1/+2
| | | | | | This provides basic OpenSSL support without optimizations like TCP Fast Open and TLS Session Tickets. Notice only a single SSL library can be enabled at a time and therefore journald functions provided by GnuTLS will be disabled when using OpenSSL. Fixes #9531
* pam_systemd: drop setting DBUS_SESSION_BUS_ADDRESSLennart Poettering2018-07-251-1/+1
| | | | | | | Since D-Bus 1.9.14 (2015-03-02) dbus looks in $XDG_RUNTIME_DIR/bus for the system bus on its own, hence we can finally drop setting this environment variable. gdbus since glib 2.45.3 (June 2015) also supports it.
* meson: use has_link_argument() and friendsYu Watanabe2018-07-241-1/+1
| | | | | This bumps the minimum required version of meson to 0.46, as `has_link_argument()` and friends are supported since 0.46.
* meson: use integer type in optionsYu Watanabe2018-07-241-1/+1
| | | | | | This bumps the minimum required version of meson to 0.45 and python to 3.5, as integer type option is supported since meson-0.45 and meson-0.45 requires python-3.5.
* README: clarify that not only systemd should use prefix=/usr, but its deps tooLennart Poettering2018-07-171-4/+6
| | | | See: #9547
* tree-wide: use "polkit" to refer to PolicyKit/polkitZbigniew Jędrzejewski-Szmek2018-07-161-1/+1
| | | | | | | | | | | Back in 2012 the project was renamed, see the release notes for v 0.105 [https://cgit.freedesktop.org/polkit/tree/NEWS#n754]. Let's update our documentation and comments to do the same. Referring to PolicyKit is confusing to users because at the time the polkit api changed too, and we support the new version. I updated NEWS too, since all the references to PolicyKit there were added after the rename. "PolicyKit" is unchanged in various URLs and method call names.
* meson: check whether gnutls supports TCP fast openYu Watanabe2018-06-261-0/+1
| | | | Fixes #9403
* Turn VALGRIND variable into a meson configuration switchZbigniew Jędrzejewski-Szmek2018-05-171-7/+6
| | | | | | | | | | Configuration through environment variable is inconvenient with meson, because they cannot be convieniently changed and/or are not preserved during reconfiguration (https://github.com/mesonbuild/meson/issues/1503). This adds -Dvalgrind=true/false, which has the advantage that it can be set at any time with meson configure -Dvalgrind=... and ninja will rebuild targets as necessary. Additional minor advantages are better consistency with the options for hashmap debugging, and typo avoidance with '#if' instead of '#ifdef'.
* doc: mention the required minimum version of meson and pythonYu Watanabe2018-05-101-1/+1
|
* doc: update hosts nsswitch setting to which consistent to man pagesYu Watanabe2018-05-011-1/+1
|
* doc: drop static user systemd-timesync from READMEYu Watanabe2018-05-011-3/+0
|
* doc: drop static user systemd-journal-gateway from READMEYu Watanabe2018-05-011-2/+2
| | | | and add systemd-journal-remote instead.
* README: mention systemd-stableZbigniew Jędrzejewski-Szmek2018-03-261-0/+11
| | | | | | | Fixes #8564. https://www.freedesktop.org/wiki/Software/systemd/Backports/ has already been adjusted.
* README: fix context for CONFIG_DEVPTS_MULTIPLE_INSTANCESAlan Jenkins2018-01-171-3/+5
| | | | | | | | | | `newinstance` (and `ptmxmode`) options of devpts are _not_ used by PrivateDevices=. (/dev/pts is shared, similar to how /dev/shm and /dev/mqueue are handled). It is used by nspawn containers though. Also CONFIG_DEVPTS_MULTIPLE_INSTANCES was removed in 4.7-rc2 https://github.com/torvalds/linux/commit/eedf265aa003b4781de24cfed40a655a664457e6 and no longer needs to be set, so make that clearer to avoid confusion.
* README: EXT4_POSIX_ACL -> EXT4_FS_POSIX_ACL (#7799)George G2018-01-041-1/+1
| | | | EXT4_POSIX_ACL doesn't exist.
* README: add requirements for IPAddress{Allow,Deny} (#7414)Andrew Jeddeloh2017-11-211-0/+4
| | | Document kernel options needed for IPAddress{Allow,Deny}.
* README,sysusers: complete and order list of default udev groups we needLennart Poettering2017-11-201-1/+1
| | | | | Let's make sure the list of default udev groups we need are ordered in README and in the sysusers.d snippet, and both are complete.
* README: slightly update the section about split /usrLennart Poettering2017-11-201-10/+10
| | | | | It's fine if /usr is actually on a separate fs. What matters is that it is mounted early enough. Say so.
* README: document that prefix *must* be /usr and nss-systemd is not an optionLennart Poettering2017-11-201-0/+10
| | | | See: #7374
* po: add a copy of polkit its rulesZbigniew Jędrzejewski-Szmek2017-11-141-1/+1
| | | | | It's just a few lines, but this way we avoid a dependency on polkit, and can use meson's i18n stuff on older distros.
* i18n: drop intltool use, use meson's merge_file directlyZbigniew Jędrzejewski-Szmek2017-11-131-0/+1
| | | | | | | | | | | | | | | | | | This didn't work during the initial conversion to meson, but should now. A sufficiently new polkit is also required, for the .its rules files. Note that https://github.com/mesonbuild/meson/blob/master/docs/markdown/i18n-module.md says that 'install' argument was added in meson 0.43.0. If this is accurate, warnigs might be generated with older mesons. Fedora has 0.43.0 across the board, but other distros probably don't, but I guess that a warning is prefereable to having to update do latest meson. The advantages are: - one less dependency (intltool) - using the generic implementation instead of our open-coded calls - we don't need to use the fake "_" prefixes in XML Replaces #1609, fixes #7300.
* build-sys: require libmount >= 2.30 (#6795)Zbigniew Jędrzejewski-Szmek2017-09-151-3/+2
| | | | | | | | | | Fixes #4871. The new libmount has two changes relevant for us: - x-* options are propagated to /run/mount/utab and are visible through libmount (fixes #4817). - umount -c now really works (partially solves #6115).
* README: note that installing valgrind-devel maybe useful to developers (#6502)Michal Sekletar2017-08-301-3/+6
| | | | | Commit also mentions that when running under valgrind we actually don't execve() systemd-shutdown. We have a comment about this in the code, but being upfront about this change in behavior doesn't hurt.
* Revert "README: document that gperf 3.1 is required for building now" (#6541)Mike Gilbert2017-08-051-1/+1
| | | | | | This reverts commit 4f5e972279d9ee6192930a0392f49cae9ad45daa. Building with gperf 3.0 works just fine; we had an autoconf check to determine the correct data types, and this check was ported to meson.
* modprobe.d: ship drop-in to set bonding max_bonds to 0 (#6448)Dimitri John Ledkov2017-08-021-5/+4
| | | | | | This allows networkd to correctly manage bond0 using networkd, when requested by the user. Fixes #5971 #6184
* README: document that max_bonds=0 is the way to go for bonding.koLennart Poettering2017-07-241-0/+9
| | | | | | Everything else just is annoying, hence let's list this among the requirements we make on the kernel in order to minimize confusion leading to #6184 and suchlike.
* build-sys: drop automake supportZbigniew Jędrzejewski-Szmek2017-07-181-29/+8
| | | | | v2: - also mention m4
* Merge pull request #5928 from keszybz/libidn2Lennart Poettering2017-05-121-1/+1
|\ | | | | Use idn2 instead of idn
| * resolved: support libidn2 in addition to libidnZbigniew Jędrzejewski-Szmek2017-05-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | libidn2 2.0.0 supports IDNA2008, in contrast to libidn which supports IDNA2003. https://bugzilla.redhat.com/show_bug.cgi?id=1449145 From that bug report: Internationalized domain names exist for quite some time (IDNA2003), although the protocols describing them have evolved in an incompatible way (IDNA2008). These incompatibilities will prevent applications written for IDNA2003 to access certain problematic domain names defined with IDNA2008, e.g., faß.de is translated to domain xn--fa-hia.de with IDNA2008, while in IDNA2003 it is translated to fass.de domain. That not only causes incompatibility problems, but may be used as an attack vector to redirect users to different web sites. v2: - keep libidn support - require libidn2 >= 2.0.0 v3: - keep dns_name_apply_idna caller dumb, and keep the #ifdefs inside of the function. - use both ±IDN and ±IDN2 in the version string
* | README: update util-linux required compilation options (#5949)Zbigniew Jędrzejewski-Szmek2017-05-121-1/+2
|/ | | Fixes #5563.
View Lorry Controller Status