summaryrefslogtreecommitdiff
path: root/TODO
Commit message (Collapse)AuthorAgeFilesLines
* codespell: fix spelling errorsBen Boeckel2019-04-291-5/+5
|
* Merge pull request #12226 from poettering/22bit-pidsLennart Poettering2019-04-111-2/+0
|\ | | | | sysctl: let's by default increase the numeric PID range from 2^16 to …
| * sysctl: let's by default increase the numeric PID range from 2^16 to 2^22Lennart Poettering2019-04-091-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This should PID collisions a tiny bit less likely, and thus improve security and robustness. 2^22 isn't particularly a lot either, but it's the current kernel limitation. Bumping this limit was suggested by Linus himself: https://lwn.net/ml/linux-kernel/CAHk-=wiZ40LVjnXSi9iHLE_-ZBsWFGCgdmNiYZUXn1-V5YBg2g@mail.gmail.com/ Let's experiment with this in systemd upstream first. Downstreams and users can after all still comment this easily. Besides compat concern the most often heard issue with such high PIDs is usability, since they are potentially hard to type. I am not entirely sure though whether 4194304 (as largest new PID) is that much worse to type or to copy than 65563. This should also simplify management of per system tasks limits as by this move the sysctl /proc/sys/kernel/threads-max becomes the primary knob to control how many processes to have in parallel.
* | Merge pull request #12037 from poettering/oom-stateLennart Poettering2019-04-111-4/+0
|\ \ | | | | | | add cgroupv2 oom killer event handling to service management
| * | update TODOLennart Poettering2019-04-091-4/+0
| |/
* | bootctl: check if files specified by boot entry exist, and warn if notZbigniew Jędrzejewski-Szmek2019-04-051-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | Example output: title: Fedora 30 (Workstation Edition) (5.0.5-300.fc30.x86_64) id: 08a5690a2eed47cf92ac0a5d2e3cf6b0-5.0.5-bad-300.fc30.x86_64 source: /boot/efi/loader/entries/08a5690a2eed47cf92ac0a5d2e3cf6b0-5.0.5-bad-300.fc30.x86_64.conf version: 5.0.5-300.fc30.x86_64 machine-id: 08a5690a2eed47cf92ac0a5d2e3cf6b0 linux: /08a5690a2eed47cf92ac0a/5.0.5-300.fc30.x86_64/linux (No such file or directory) initrd: /08a5690a2eed47cf92ac0a/5.0.5-300.fc30.x86_64/initrd (No such file or directory) /08a5690a2eed47cf92ac0a/5.0.5-300.fc30.x86_64/initrd2 (No such file or directory) options: ...
* | bootctl: replace "type" with "source" in outputZbigniew Jędrzejewski-Szmek2019-04-051-1/+0
|/ | | | | | | | | | | | | | | | | | | | | | I think this is more useful (because it's easy to stick the path into an editor command when one wants to change the options or inspect the files), and more self-explanatory. Example output: title: Fedora 30 (Workstation Edition) (4.20.16-200.fc29.x86_64) id: 08a5690a2eed47cf92ac0a5d2e3cf6b0-4.20.16-200.fc29.x86_64 source: /boot/efi/loader/entries/08a5690a2eed47cf92ac0a5d2e3cf6b0-4.20.16-200.fc29.x86_64.conf version: 4.20.16-200.fc29.x86_64 ... title: Fedora 30 (Workstation Edition) id: fedora-30 source: /boot/efi/EFI/Linux/linux-5.0.5-300.fc30.x86_64-08a5690a2eed47cf92ac0a5d2e3cf6b0.efi linux: EFI/Linux/linux-5.0.5-300.fc30.x86_64-08a5690a2eed47cf92ac0a5d2e3cf6b0.efi ... title: Reboot Into Firmware Interface id: auto-reboot-to-firmware-setup source: /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
* update TODOLennart Poettering2019-04-021-3/+0
|
* update TODOLennart Poettering2019-04-021-5/+0
|
* update TODOLennart Poettering2019-03-291-2/+0
|
* Merge pull request #12140 from poettering/copy-earlyZbigniew Jędrzejewski-Szmek2019-03-291-2/+0
|\ | | | | chattr/copy.c fixes
| * update TODOLennart Poettering2019-03-281-2/+0
| |
* | Merge pull request #12137 from poettering/socket-var-runZbigniew Jędrzejewski-Szmek2019-03-291-3/+0
|\ \ | | | | | | warn about sockets in /var/run/ too
| * | update TODOLennart Poettering2019-03-281-3/+0
| |/
* | update TODOLennart Poettering2019-03-281-0/+6
|/
* update TODOLennart Poettering2019-03-261-0/+7
|
* update TODOLennart Poettering2019-03-201-17/+0
|
* TODO: add some bootctl itemsZbigniew Jędrzejewski-Szmek2019-03-201-0/+4
|
* update TODOLennart Poettering2019-03-121-0/+3
|
* TODO: updateYu Watanabe2019-03-071-3/+0
|
* update TODOLennart Poettering2019-03-051-5/+0
|
* update TODOLennart Poettering2019-03-051-1/+4
|
* update TODOLennart Poettering2019-03-011-8/+0
|
* Merge pull request #11226 from keszybz/enable-remount-fs-dynamicallyLennart Poettering2019-02-181-0/+1
|\ | | | | Enable systemd-remount-fs.service dynamically
| * man: describe better when remount-fs.service and gpt-auto-generator are activeZbigniew Jędrzejewski-Szmek2019-01-031-0/+1
| |
* | journal: drop _packed_ attribute in a few placesZbigniew Jędrzejewski-Szmek2019-02-041-0/+2
| | | | | | | | The justification is the safe as for the grandparent commit.
* | cgroup: s/cgroups? ?v?([0-9])/cgroup v\1/gIChris Down2019-01-031-1/+1
|/ | | | | | | | | | Nitpicky, but we've used a lot of random spacings and names in the past, but we're trying to be completely consistent on "cgroup vN" now. Generated by `fd -0 | xargs -0 -n1 sed -ri --follow-symlinks 's/cgroups? ?v?([0-9])/cgroup v\1/gI'`. I manually ignored places where it's not appropriate to replace (eg. "cgroup2" fstype and in src/shared/linux).
* Merge pull request #10912 from poettering/gpt-root-rwZbigniew Jędrzejewski-Szmek2018-12-201-3/+0
|\ | | | | make sure to propagate GPT root partition r/w flag into mount r/w flag
| * update TODOLennart Poettering2018-12-181-3/+0
| |
* | update TODOLennart Poettering2018-12-181-26/+1
|/
* update TODOLennart Poettering2018-12-101-0/+7
|
* Merge pull request #10935 from poettering/rlimit-nofile-safeZbigniew Jędrzejewski-Szmek2018-12-061-0/+4
|\ | | | | | | Merged by hand to resolve a trivial conflict in TODO.
| * update TODOLennart Poettering2018-12-011-1/+3
| |
* | update TODOLennart Poettering2018-12-011-0/+4
|/
* update TODOLennart Poettering2018-11-301-3/+7
|
* update TODOLennart Poettering2018-11-291-0/+23
|
* Merge pull request #10357 from poettering/import-fsZbigniew Jędrzejewski-Szmek2018-11-291-5/+4
|\ | | | | machinectl import-fs command and other fixes
| * update TODOLennart Poettering2018-11-261-0/+3
| |
| * import: drop logic of setting up /var/lib/machines as btrfs loopback mountLennart Poettering2018-11-261-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's simplify things and drop the logic that /var/lib/machines is setup as auto-growing btrfs loopback file /var/lib/machines.raw. THis was done in order to make quota available for machine management, but quite frankly never really worked properly, as we couldn't grow the file system in sync with its use properly. Moreover philosophically it's problematic overriding the admin's choice of file system like this. Let's hence drop this, and simplify things. Deleting code is a good feeling. Now that regular file systems provide project quota we could probably add per-machine quota support based on that, hence the btrfs quota argument is not that interesting anymore (though btrfs quota is a bit more powerful as it allows recursive quota, i.e. that the machine pool gets an overall quota in addition to per-machine quota).
* | update TODOLennart Poettering2018-11-271-2/+0
|/
* update TODOLennart Poettering2018-11-261-0/+2
|
* TODO: add entryZbigniew Jędrzejewski-Szmek2018-11-161-0/+2
|
* Merge pull request #10785 from poettering/cgroup-join-removalLennart Poettering2018-11-161-1/+1
|\ | | | | remove JoinControllers= setting
| * update TODOLennart Poettering2018-11-161-1/+1
| |
* | man: let's deprecate PermissionsStartOnly=Lennart Poettering2018-11-161-1/+1
|/ | | | | | The concept is redundant and predates the special chars that do the same in ExecStar=. Let's settle on advertising just the latter, and hide PermissionsStartOnly= from the docs (even if we continue supporting it).
* update TODOLennart Poettering2018-11-141-3/+2
|
* update TODOLennart Poettering2018-11-131-0/+4
|
* update TODOLennart Poettering2018-11-121-0/+3
|
* update TODOLennart Poettering2018-11-121-2/+0
|
* update TODOLennart Poettering2018-11-121-0/+6
|
View Lorry Controller Status