summaryrefslogtreecommitdiffstats
path: root/NEWS (follow)
Commit message (Collapse)AuthorAgeFilesLines
* NEWS: update dateLuca Boccassi4 days1-1/+1
|
* NEWS: update contributors listLuca Boccassi4 days1-27/+31
|
* NEWS: add blurb thanking Nick OwensVito Caputo7 days1-0/+3
| | | | | Nick's largely responsible for nerd-sniping me into fixing #34516 and did most of the testing.
* NEWS: update dateLuca Boccassi2024-11-151-1/+1
|
* NEWS: update contributors listLuca Boccassi2024-11-151-38/+41
|
* NEWS: systemd-keyutil, --certificate-source, --certificate-providerLuca Boccassi2024-11-151-0/+12
|
* NEWS: add specific versions in key codes entryZbigniew Jędrzejewski-Szmek2024-11-071-8/+7
| | | | | | | | This should be easier for folks to consume. Refs: https://lists.x.org/archives/xorg-announce/2024-October/003543.html https://lists.x.org/archives/xorg-announce/2024-October/003544.html
* NEWS: fix typoYu Watanabe2024-11-071-1/+1
| | | | Follow-up for a6d7cc74d6510378fa6d286352bb987791bed8ab.
* NEWS: various cleanupsLennart Poettering2024-11-061-83/+89
|
* NEWS: various cleanupsLennart Poettering2024-11-061-80/+86
|
* NEWS: finalizeLuca Boccassi2024-11-061-1/+1
|
* NEWS: update list of contributorsLuca Boccassi2024-11-061-0/+52
|
* NEWS: add note about sd-sbsignLuca Boccassi2024-11-061-0/+5
|
* Update NEWS for recent PRsLuca Boccassi2024-11-061-0/+13
|
* networkd: add possibility to specify MulticastIGMPVersionMichele Dionisio2024-11-061-0/+4
|
* Grammar and formatting for DeviceTree docs (#35050)Luca Boccassi2024-11-061-9/+9
|\
| * tree-wide: use Device*T*ree spellingZbigniew Jędrzejewski-Szmek2024-11-061-9/+9
| | | | | | | | | | | | | | | | We used both, in fact "Devicetree" was more common. But we have a general rule that we capitalize all words in names and also we have a DeviceTree= configuration setting, which we cannot change. If we use two different spelllings, this will make it harder for people to use the correct one in config files. So use the "DeviceTree" spelling everywhere.
* | pid1: stop refusing to boot with cgroup v1Zbigniew Jędrzejewski-Szmek2024-11-061-5/+8
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since v256 we completely fail to boot if v1 is configured. Fedora 41 was just released with v256.7 and this is probably the first major exposure of users to this code. It turns out not work very well. Fedora switched to v2 as default in F31 (2019) and at that time some people added configuration to use v1 either because of Docker or for other reasons. But it's been long enough ago that people don't remember this and are now very unhappy when the system refuses to boot after an upgrade. Refusing to boot is also unnecessarilly punishing to users. For machines that are used remotely, this could mean somebody needs to physically access the machine. For other users, the machine might be the only way to access the net and help, and people might not know how to set kernel parameters without some docs. And because this is in systemd, after an upgrade all boot choices are affected, and it's not possible to e.g. select an older kernel for boot. And crashing the machine doesn't really serve our goal either: we were giving a hint how to continue using v1 and nothing else. If the new override is configured, warn and immediately boot to v1. If v1 is configured w/o the override, warn and wait 30 s and boot to v2. Also give a hint how to switch to v2. https://bugzilla.redhat.com/show_bug.cgi?id=2323323 https://bugzilla.redhat.com/show_bug.cgi?id=2323345 https://bugzilla.redhat.com/show_bug.cgi?id=2322467 https://www.reddit.com/r/Fedora/comments/1gfcyw9/refusing_to_run_under_cgroup_01_sy_specified_on/ The advice is to set systemd.unified_cgroup_hierarchy=1 (instead of removing systemd.unified_cgroup_hierarchy=0). I think this is easier to convey. Users who are understand what is going on can just remove the option instead. The caching is dropped in cg_is_legacy_wanted(). It turns out that the order in which those functions are called during early setup is very fragile. If cg_is_legacy_wanted() is called before we have set up the v2 hierarchy, we incorrectly cache a true answer. The function is called just a handful of times at most, so we don't really need to cache the response.
* tree-wide: time-out → timeoutZbigniew Jędrzejewski-Szmek2024-11-051-3/+3
| | | | For justification, see 3f9a0a522f2029e9295ea5e9984259022be88413.
* core: Introduce PrivatePIDs=Daan De Meyer2024-11-051-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This new setting allows unsharing the pid namespace in a unit. Because you have to fork to get a process into a pid namespace, we fork in systemd-executor to get into the new pid namespace. The parent then sends the pid of the child process back to the manager and exits while the child process continues on with the rest of exec_invoke() and then executes the actual payload. Communicating the child pid is done via a new pidref socket pair that is set up on manager startup. We unshare the PID namespace right before the mount namespace so we mount procfs correctly. Note PrivatePIDs=yes always implies MountAPIVFS=yes to mount procfs. When running unprivileged in a user session, user namespace is set up first to allow for PID namespace to be unshared. However, when running in privileged mode, we unshare the user namespace last to ensure the user namespace does not own the PID namespace and cannot break out of the sandbox. Note we disallow Type=forking services from using PrivatePIDs=yes since the init proess inside the PID namespace must not exit for other processes in the namespace to exist. Note Daan De Meyer did the original work for this commit with Ryan Wilson addressing follow-ups. Co-authored-by: Daan De Meyer <daan.j.demeyer@gmail.com>
* update NEWSLennart Poettering2024-11-041-10/+37
|
* Update NEWSLuca Boccassi2024-11-011-1/+6
|
* update NEWSLennart Poettering2024-11-011-0/+11
|
* NEWS: fix typoYu Watanabe2024-10-311-6/+6
|
* NEWS: remove duplicated entryZbigniew Jędrzejewski-Szmek2024-10-301-16/+6
| | | | | | | The same item is described below. Also reflow some paragraphs (presumably indented with emacs, which does this wrong).
* update NEWSLennart Poettering2024-10-301-9/+52
|
* Merge pull request #34245 from bluca/logind_drop_weak_delay_inhibitorZbigniew Jędrzejewski-Szmek2024-10-291-6/+6
|\ | | | | logind: drop new delay-weak inhibitor
| * logind: drop new delay-weak inhibitorLuca Boccassi2024-09-131-6/+6
| | | | | | | | | | | | | | | | It wasn't actually requested, just a misunderstanding, so drop it. Fixes https://github.com/systemd/systemd/issues/34091 Follow-up for 804874d26ac73e0af07c4c5d7165c95372f03f6d
* | NEWS: be less misleading since systemd-run does not support ↵Mike Yuan2024-10-291-1/+1
| | | | | | | | ExtraFileDescriptors= yet
* | update NEWS for v257Lennart Poettering2024-10-281-103/+411
| |
* | Merge pull request #34783 from keszybz/man-nspawn-private-usersZbigniew Jędrzejewski-Szmek2024-10-181-3/+3
|\ \ | | | | | | Change systemd-nspawn man page to strongly recommend private users
| * | tree-wise: use "lightweight" spellingZbigniew Jędrzejewski-Szmek2024-10-181-3/+3
| | | | | | | | | | | | | | | Both spellings were used, but the dictionary says that "lightweight" is the standard spelling.
* | | Bump kernel recommended baseline to v5.4Mike Yuan2024-10-161-0/+6
| | |
* | | NEWS: rearrange incompatible changes, separate from Future RemovalsMike Yuan2024-10-161-39/+39
|/ /
* | Merge pull request #34593 from Werkov/deprecate-aux-scopesLennart Poettering2024-10-091-0/+3
|\ \ | | | | | | core/manager: Deprecate StartAuxiliaryScope() method
| * | core/manager: Deprecate StartAuxiliaryScope() methodMichal Koutný2024-10-081-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The method was added with migration of resources in mind (e.g. process's allocated memory will follow it to the new scope), however, such a resource migration is not in cgroup semantics. The method may thus have the intended users and others could be guided to StartTransientUnit(). Since this API was advertised in a regular release, start the removal with a deprecation message to callers. Eventually, the goal is to remove the method to clean up DBus API and simplify code (removal of cgroup_context_copy()). Part of DBus docs is retained to satisfy build checks.
* | | NEWS: announce the F20/F21/F22/F23 key mangling removal scheduled for v258Lennart Poettering2024-10-091-0/+12
| | | | | | | | | | | | | | | As per: https://github.com/systemd/systemd/pull/34325 And: https://github.com/systemd/systemd/issues/34323
* | | Revert "Preset user units on first boot as well"Lennart Poettering2024-10-011-3/+0
|/ / | | | | | | This reverts commit 0a40325573b91ea71070653865f7f6a9cada2bef.
* | NEWS: Document change to systemd-creds 'cat' verbSimon Pilkington2024-09-251-1/+6
| | | | | | | | See: https://github.com/systemd/systemd/pull/34548
* | Preset user units on first boot as wellDaan De Meyer2024-09-211-0/+3
| | | | | | | | | | | | We need to make sure the presets from /usr/lib/systemd/user-preset are applied as well. Currently only the ones from /usr/lib/systemd/system-preset are applied.
* | NEWS: fix typos and remove backticksJörg Behrmann2024-09-201-5/+5
| |
* | NEWS: fix typoYu Watanabe2024-09-161-2/+2
| | | | | | | | Follow-up for dcc359010c0a0d8366ade913bad72acb98f4f0ef.
* | tmpfiles: introduce an explicit line flag $ for enabling purge logic for a lineLennart Poettering2024-09-151-0/+9
|/ | | | | | | Let's make the risk of accidental misuse, and mark lines that shall be covered by --purge with an explicit new flag "$". See: #33349
* NEWS: correct/complete some entriesMike Yuan2024-09-121-5/+9
|
* NEWS: the first big batch for v257Zbigniew Jędrzejewski-Szmek2024-09-121-2/+228
|
* NEWS: fix typoYu Watanabe2024-09-071-2/+2
| | | | Follow-up for 7a3a49386cc49d3971531ea24efb84232c05cc86.
* NEWS: extend the userdb sshd_config NEWS entry a bitLennart Poettering2024-09-061-2/+13
|
* Merge pull request #34114 from yuwata/resolvconf-pLuca Boccassi2024-08-271-0/+5
|\ | | | | resolve: support 'resolvconf -p'
| * NEWS: mention "resolvconf -p"Yu Watanabe2024-08-261-0/+5
| |
* | core: honor FileDescriptorName= too for Accept=yes socketsMike Yuan2024-08-261-0/+4
|/ | | | | | | | | | | | | | So far we manually hardcoded $LISTEN_FDNAMES to "varlink" in various varlink service units we ship, even though FileDescriptorName=varlink is specified in associated socket units already, because FileDescriptorName= is currently silently ignored when combined with Accept=yes. Let's step away from this, which seems saner. Note that this is technically a compat break, but a mostly negligible one as there shall be few users setting FileDescriptorName= but still expecting LISTEN_FDNAMES=connection in the actual executable. Preparation for #34080
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-01 19:04:51 +0100