summary refs log tree commit diff
path: root/nixos/modules/system
Commit message (Collapse)AuthorAge
* Merge pull request #96639 from xfix/support-microsoft-usb-keyboardsTimo Kaufmann2020-11-05
|\ | | | | nixos/availableKernelModules: add microsoft hid
| * nixos/availableKernelModules: add microsoft hidKonrad Borowski2020-08-29
| | | | | | | | This adds support for Microsoft USB keyboards at boot.
* | nixos/systemd-resolved: fix incorrect userPeter Hoeg2020-11-05
| |
* | nixos/modules: deprecation warning for StartLimitInterval in [Service]lf-2020-10-31
| | | | | | | | | | This implements https://github.com/NixOS/nixpkgs/issues/45786#issuecomment-440091879
* | nixos/modules: Reformat `warnings` sectionNiklas Hambüchen2020-10-31
| |
* | nixos/modules: fix systemd start rate-limitslf-2020-10-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These were broken since 2016: https://github.com/systemd/systemd/commit/f0367da7d1a61ad698a55d17b5c28ddce0dc265a since StartLimitIntervalSec got moved into [Unit] from [Service]. StartLimitBurst has also been moved accordingly, so let's fix that one too. NixOS systems have been producing logs such as: /nix/store/wf98r55aszi1bkmln1lvdbp7znsfr70i-unit-caddy.service/caddy.service:31: Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring. I have also removed some unnecessary duplication in units disabling rate limiting since setting either interval or burst to zero disables it (https://github.com/systemd/systemd/blob/ad16158c10dfc3258831a9ff2f1a988214f51653/src/basic/ratelimit.c#L16)
* | Merge pull request #102172 from grahamc/stage-1-datestampsGraham Christensen2020-10-30
|\ \ | | | | | | stage-1: add datestamps to logs
| * | stage-1: add datestamps to logsGraham Christensen2020-10-30
| | | | | | | | | | | | | | | | | | When the stage-1 logs get imported in to the journal, they all get loaded with the same timestamp. This makes it difficult to identify what might be taking a long time in early boot.
* | | Merge pull request #102171 from grahamc/faster-ext-resizeGraham Christensen2020-10-30
|\ \ \ | | | | | | | | stage-1: modprobe ext{2,3,4} before resizing (so resizing takes less than 45 minutes)
| * | | stage-1: modprobe ext{2,3,4} before resizingGraham Christensen2020-10-30
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I noticed booting a system with an ext4 root which expanded to 5T took quite a long time (12 minutes in some cases, 43(!) in others.) I changed stage-1 to run `resize2fs -d 62` for extra debug output and timing information. It revealed the adjust_superblock step taking almost all of the time: [Fri Oct 30 11:10:15 UTC 2020] zero_high_bits_in_metadata: Memory used: 132k/0k (63k/70k), time: 0.00/ 0.00/ 0.00 [Fri Oct 30 11:21:09 UTC 2020] adjust_superblock: Memory used: 396k/4556k (295k/102k), time: 654.21/ 0.59/ 5.13 but when I ran resize2fs on a disk with the identical content growing to the identical target size, it would only take about 30 seconds. I looked at what happened between those two steps in the fast case with strace and found: ``` 235 getrusage(RUSAGE_SELF, {ru_utime={tv_sec=0, tv_usec=1795}, ru_stime={tv_sec=0, tv_usec=3590}, ...}) = 0 236 write(1, "zero_high_bits_in_metadata: Memo"..., 84zero_high_bits_in_metadata: Memory used: 132k/0k (72k/61k), time: 0.00/ 0.00/ 0.00 237 ) = 84 238 gettimeofday({tv_sec=1604061278, tv_usec=480147}, NULL) = 0 239 getrusage(RUSAGE_SELF, {ru_utime={tv_sec=0, tv_usec=1802}, ru_stime={tv_sec=0, tv_usec=3603}, ...}) = 0 240 gettimeofday({tv_sec=1604061278, tv_usec=480192}, NULL) = 0 241 mmap(NULL, 2564096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa3c7355000 242 access("/sys/fs/ext4/features/lazy_itable_init", F_OK) = 0 243 brk(0xf85000) = 0xf85000 244 brk(0xfa6000) = 0xfa6000 245 gettimeofday({tv_sec=1604061278, tv_usec=538828}, NULL) = 0 246 getrusage(RUSAGE_SELF, {ru_utime={tv_sec=0, tv_usec=58720}, ru_stime={tv_sec=0, tv_usec=3603}, ...}) = 0 247 write(1, "adjust_superblock: Memory used: "..., 79adjust_superblock: Memory used: 396k/2504k (305k/92k), time: 0.06/ 0.06/ 0.00 248 ) = 79 249 gettimeofday({tv_sec=1604061278, tv_usec=539119}, NULL) = 0 250 getrusage(RUSAGE_SELF, {ru_utime={tv_sec=0, tv_usec=58812}, ru_stime={tv_sec=0, tv_usec=3603}, ...}) = 0 251 gettimeofday({tv_sec=1604061279, tv_usec=939}, NULL) = 0 252 getrusage(RUSAGE_SELF, {ru_utime={tv_sec=0, tv_usec=520411}, ru_stime={tv_sec=0, tv_usec=3603}, ...}) = 0 253 write(1, "fix_uninit_block_bitmaps 2: Memo"..., 88fix_uninit_block_bitmaps 2: Memory used: 396k/2504k (305k/92k), time: 0.46/ 0.46/ 0.00 254 ) = 88 ``` In particular the access to /sys/fs seemed interesting. Looking at the source of resize2fs: ``` [root@ip-172-31-22-182:~/e2fsprogs-1.45.5]# rg -B2 -A1 /sys/fs/ext4/features/lazy_itable_init . ./resize/resize2fs.c 923- if (getenv("RESIZE2FS_FORCE_LAZY_ITABLE_INIT") || 924- (!getenv("RESIZE2FS_FORCE_ITABLE_INIT") && 925: access("/sys/fs/ext4/features/lazy_itable_init", F_OK) == 0)) 926- lazy_itable_init = 1; ``` I confirmed /sys is mounted, and then found a bug suggesting the ext4 module is maybe not loaded: https://bugzilla.redhat.com/show_bug.cgi?id=1071909 My home server doesn't have ext4 loaded and had 3T to play with, so I tried (and succeeded with) replicating the issue locally: ``` [root@kif:/scratch]# lsmod | grep -i ext [root@kif:/scratch]# zfs create -V 3G rpool/scratch/ext4 [root@kif:/scratch]# time mkfs.ext4 /dev/zvol/rpool/scratch/ext4 mke2fs 1.45.5 (07-Jan-2020) Discarding device blocks: done Creating filesystem with 786432 4k blocks and 196608 inodes Filesystem UUID: 560a4a8f-93dc-40cc-97a5-f10049bf801f Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: done Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done real 0m2.261s user 0m0.000s sys 0m0.025s [root@kif:/scratch]# zfs set volsize=3T rpool/scratch/ext4 [root@kif:/scratch]# time resize2fs -d 62 /dev/zvol/rpool/scratch/ext4 resize2fs 1.45.5 (07-Jan-2020) fs has 11 inodes, 1 groups required. fs requires 16390 data blocks. With 1 group(s), we have 22234 blocks available. Last group's overhead is 10534 Need 16390 data blocks in last group Final size of last group is 26924 Estimated blocks needed: 26924 Extents safety margin: 49 Resizing the filesystem on /dev/zvol/rpool/scratch/ext4 to 805306368 (4k) blocks. read_bitmaps: Memory used: 132k/0k (63k/70k), time: 0.00/ 0.00/ 0.00 read_bitmaps: I/O read: 1MB, write: 0MB, rate: 3802.28MB/s fix_uninit_block_bitmaps 1: Memory used: 132k/0k (63k/70k), time: 0.00/ 0.00/ 0.00 resize_group_descriptors: Memory used: 132k/0k (68k/65k), time: 0.00/ 0.00/ 0.00 move_bg_metadata: Memory used: 132k/0k (68k/65k), time: 0.00/ 0.00/ 0.00 zero_high_bits_in_metadata: Memory used: 132k/0k (68k/65k), time: 0.00/ 0.00/ 0.00 ``` here it got stuck for quite some time ... straceing this 20 minutes in revealed this in a tight loop: ``` getuid() = 0 geteuid() = 0 getgid() = 0 getegid() = 0 prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) fallocate(3, FALLOC_FL_ZERO_RANGE, 2222649901056, 2097152) = 0 fsync(3) = 0 ``` it finally ended 43(!) minutes later: ``` adjust_superblock: Memory used: 264k/3592k (210k/55k), time: 2554.03/ 0.16/15.07 fix_uninit_block_bitmaps 2: Memory used: 264k/3592k (210k/55k), time: 0.16/ 0.16/ 0.00 blocks_to_move: Memory used: 264k/3592k (211k/54k), time: 0.00/ 0.00/ 0.00 Number of free blocks: 755396/780023556, Needed: 0 block_mover: Memory used: 264k/3592k (216k/49k), time: 0.05/ 0.01/ 0.00 block_mover: I/O read: 1MB, write: 0MB, rate: 18.68MB/s inode_scan_and_fix: Memory used: 264k/3592k (216k/49k), time: 0.00/ 0.00/ 0.00 inode_ref_fix: Memory used: 264k/3592k (216k/49k), time: 0.00/ 0.00/ 0.00 move_itables: Memory used: 264k/3592k (216k/49k), time: 0.00/ 0.00/ 0.00 calculate_summary_stats: Memory used: 264k/3592k (216k/49k), time: 16.35/16.35/ 0.00 fix_resize_inode: Memory used: 264k/3592k (222k/43k), time: 0.04/ 0.00/ 0.00 fix_resize_inode: I/O read: 1MB, write: 0MB, rate: 22.80MB/s fix_sb_journal_backup: Memory used: 264k/3592k (222k/43k), time: 0.00/ 0.00/ 0.00 overall resize2fs: Memory used: 264k/3592k (222k/43k), time: 2570.90/16.68/15.07 overall resize2fs: I/O read: 1MB, write: 1MB, rate: 0.00MB/s The filesystem on /dev/zvol/rpool/scratch/ext4 is now 805306368 (4k) blocks long. real 43m1.943s user 0m16.761s sys 0m15.069s ``` I then cleaned up and recreated the zvol, loaded the ext4 module, created the ext4 fs, resized the volume, and resize2fs'd and it went quite quickly: ``` [root@kif:/scratch]# zfs destroy rpool/scratch/ext4 [root@kif:/scratch]# zfs create -V 3G rpool/scratch/ext4 [root@kif:/scratch]# modprobe ext4 [root@kif:/scratch]# time resize2fs -d 62 /dev/zvol/rpool/scratch/ext4 [root@kif:/scratch]# time mkfs.ext4 /dev/zvol/rpool/scratch/ext4 mke2fs 1.45.5 (07-Jan-2020) Discarding device blocks: done Creating filesystem with 786432 4k blocks and 196608 inodes Filesystem UUID: 5b415f2f-a8c4-4ba0-ac1d-78860de77610 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: done Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done real 0m1.013s user 0m0.001s sys 0m0.023s [root@kif:/scratch]# zfs set volsize=3T rpool/scratch/ext4 [root@kif:/scratch]# time resize2fs -d 62 /dev/zvol/rpool/scratch/ext4 resize2fs 1.45.5 (07-Jan-2020) fs has 11 inodes, 1 groups required. fs requires 16390 data blocks. With 1 group(s), we have 22234 blocks available. Last group's overhead is 10534 Need 16390 data blocks in last group Final size of last group is 26924 Estimated blocks needed: 26924 Extents safety margin: 49 Resizing the filesystem on /dev/zvol/rpool/scratch/ext4 to 805306368 (4k) blocks. read_bitmaps: Memory used: 132k/0k (63k/70k), time: 0.00/ 0.00/ 0.00 read_bitmaps: I/O read: 1MB, write: 0MB, rate: 3389.83MB/s fix_uninit_block_bitmaps 1: Memory used: 132k/0k (63k/70k), time: 0.00/ 0.00/ 0.00 resize_group_descriptors: Memory used: 132k/0k (68k/65k), time: 0.00/ 0.00/ 0.00 move_bg_metadata: Memory used: 132k/0k (68k/65k), time: 0.00/ 0.00/ 0.00 zero_high_bits_in_metadata: Memory used: 132k/0k (68k/65k), time: 0.00/ 0.00/ 0.00 adjust_superblock: Memory used: 264k/1540k (210k/55k), time: 0.02/ 0.02/ 0.00 fix_uninit_block_bitmaps 2: Memory used: 264k/1540k (210k/55k), time: 0.15/ 0.15/ 0.00 blocks_to_move: Memory used: 264k/1540k (211k/54k), time: 0.00/ 0.00/ 0.00 Number of free blocks: 755396/780023556, Needed: 0 block_mover: Memory used: 264k/3592k (216k/49k), time: 0.01/ 0.01/ 0.00 block_mover: I/O read: 1MB, write: 0MB, rate: 157.11MB/s inode_scan_and_fix: Memory used: 264k/3592k (216k/49k), time: 0.00/ 0.00/ 0.00 inode_ref_fix: Memory used: 264k/3592k (216k/49k), time: 0.00/ 0.00/ 0.00 move_itables: Memory used: 264k/3592k (216k/49k), time: 0.00/ 0.00/ 0.00 calculate_summary_stats: Memory used: 264k/3592k (216k/49k), time: 16.20/16.20/ 0.00 fix_resize_inode: Memory used: 264k/3592k (222k/43k), time: 0.00/ 0.00/ 0.00 fix_resize_inode: I/O read: 1MB, write: 0MB, rate: 5319.15MB/s fix_sb_journal_backup: Memory used: 264k/3592k (222k/43k), time: 0.00/ 0.00/ 0.00 overall resize2fs: Memory used: 264k/3592k (222k/43k), time: 16.45/16.38/ 0.00 overall resize2fs: I/O read: 1MB, write: 1MB, rate: 0.06MB/s The filesystem on /dev/zvol/rpool/scratch/ext4 is now 805306368 (4k) blocks long. real 0m17.908s user 0m16.386s sys 0m0.079s ``` Success!
* / / nixos/networkd: allow RouteMetric= in [DHCPv6] sectionFlorian Klink2020-10-29
|/ /
* | nixos/initrd-network: fix /etc/resolv.conf when multiple dns servers from DHCPMarc 'risson' Schmitt2020-10-19
| | | | | | | | Signed-off-by: Marc 'risson' Schmitt <marc.schmitt@risson.space>
* | Merge pull request #95746 from Mic92/cloud-initFlorian Klink2020-10-15
|\ \ | | | | | | cloud-init: 0.7.9 -> 20.2 (python3!)
| * | cloud-utils: split of smaller .guest outputJörg Thalheim2020-08-18
| | |
* | | Revert "nixos/systemd-boot: Temporarily ignore errors"Florian Klink2020-09-27
| | | | | | | | | | | | | | | | | | This reverts commit b32701bc5404ae37cfa01429962588b833913d7d. That fix has been included upstream in 246.5.
* | | Merge pull request #98503 from jtojnar/doc-promptsJan Tojnar2020-09-24
|\ \ \
| * | | nixos/doc: Improve code listingsJan Tojnar2020-09-23
| | | | | | | | | | | | | | | | By adding prompts and replaceables and removing unnecessary indentation.
* | | | nixos/stage-1: set up /dev/fdCole Helbling2020-09-22
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Otherwise, stage-2-init.sh will complain about not having access to /dev/fd/62 as of systemd v246. On IRC, flokli said: 15:14 <flokli> cole-h: hmmm... I could imagine some of the setup inside /dev has been moved into other parts of systemd 15:14 <flokli> And given we run systemd much later (outside initramfs only) it doesn't work properly here 15:17 <flokli> We probably don't invoke udev correctly
* | | nixos/systemd-boot: Temporarily ignore errorsTethys Svensson2020-09-10
| | | | | | | | | | | | | | | | | | | | | | | | This is a temporary fix for #97433. A more proper fix has been implemented upstream in systemd/systemd#17001, however until it gets backported, we are stuck with ignoring the error. After the backport lands, this commit should be reverted.
* | | Revert "nixos/raspberrypi-builder: fix cross using buildPackages"Christian Kampka2020-09-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | The commit enforces buildPackages in the builder but neglects the fact that the builder is intended to run on the target system. Because of that, the builder will fail when remotely building a configuration eg. with nixops or nix-copy-closure. This reverts commit a6ac6d00f98c7cc814008c1e6e288feaa2e123c6.
* | | Merge staging-next into stagingFrederik Rietdijk2020-09-04
|\ \ \
| * | | nixos/systemd: Don't use apply for $PATHJanne Heß2020-09-03
| | | | | | | | | | | | | | | | | | | | When not using apply, other modules can use $PATH as a list instead of getting a colon-separated list to each /bin directory.
* | | | cryptsetup, lvm2, systemd: Break cyclic dependency at a different pointAnders Kaseorg2020-09-03
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The cyclic dependency of systemd → cryptsetup → lvm2 → udev=systemd needs to be broken somewhere. The previous strategy of building cryptsetup with an lvm2 built without udev (#66856) caused the installer.luksroot test to fail. Instead, build lvm2 with a udev built without cryptsetup. Fixes #96479. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* | | Merge pull request #96042 from rnhmjoj/loaOfWORLDofPEACE2020-09-02
|\ \ \ | | | | | | | | treewide: completely remove types.loaOf
| * | | treewide: completely remove types.loaOfrnhmjoj2020-09-02
| | | |
* | | | nixos/systemd: support adding and overriding tmpfiles.d via environment.etc ↵Orivej Desh2020-09-02
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#96766) This allows the user to configure systemd tmpfiles.d via `environment.etc."tmpfiles.d/X.conf".text = "..."`, which after #93073 causes permission denied (with new X.conf): ``` ln: failed to create symbolic link '/nix/store/...-etc/etc/tmpfiles.d/X.conf': Permission denied builder for '/nix/store/...-etc.drv' failed with exit code 1 ``` or collision between environment.etc and systemd-default-tmpfiles packages (with existing X.conf, such as tmp.conf): ``` duplicate entry tmpfiles.d/tmp.conf -> /nix/store/...-etc-tmp.conf mismatched duplicate entry /nix/store/...-systemd-246/example/tmpfiles.d/tmp.conf <-> /nix/store/...-etc-tmp.conf builder for '/nix/store/...-etc.drv' failed with exit code 1 ``` Fixes #96755
* | | Merge pull request #96404 from matthewbauer/gcc-crossMatthew Bauer2020-08-26
|\ \ \ | | | | | | | | Fix cycle detected in Darwin->Linux cross GCC
| * \ \ Merge pull request #86236 from ThibautMarty/fix-nullOr-typesLassulus2020-08-26
| |\ \ \ | | | | | | | | | | treewide: fix modules options types where the default is null
| | * | | treewide: fix modules options types where the default is nullThibaut Marty2020-04-28
| | | | | | | | | | | | | | | | | | | | | | | | | They can be caught with `nixos-option -r` on an empty ({...}:{}) NixOS configuration.
* | | | | Merge staging-next into stagingFrederik Rietdijk2020-08-26
|\| | | |
| * | | | extra-utils: build a full lvm2 without udev support, fixes #96197Frederik Rietdijk2020-08-26
| | | | | | | | | | | | | | | | | | | | | | | | | dmsetup was missing symbols. https://github.com/NixOS/nixpkgs/pull/96290#issuecomment-680252830
| * | | | stage-1 find-libs: initialise left to empty arrayLinus Heckemann2020-08-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | declare -a is not sufficient to make the array variable actually exist, which resulted in the script failing when the target object did not have any DT_NEEDED entries. This in turn resulted in some initramfs libraries not having their rpaths patched to point to extra-utils, which in turn broke the extra-utils tests.
* | | | | Merge pull request #94354 from flokli/systemd-246Florian Klink2020-08-24
|\ \ \ \ \ | |/ / / / |/| | | | systemd: 245.6 -> 246
| * | | | nixos/boot: handle systemd-udevd being a symlink to udevadmFlorian Klink2020-08-13
| | | | |
| * | | | nixos/systemd: don't try to install systemd-initctl.{service,socket}Florian Klink2020-08-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These are now only installed by systemd if HAVE_SYSV_COMPAT is true, which only is the case if you set sysvinit-path and sysvrcnd-path (which we explicitly unset in the systemd derivation for quite some time)
| * | | | nixos/systemd: remove mymachines nss module from passwd: and group: linesFlorian Klink2020-08-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From the systemd release notes: nss-mymachines lost support for resolution of users and groups, and now only does resolution of hostnames. This functionality is now provided by nss-systemd. Thus, the 'mymachines' entry should be removed from the 'passwd:' and 'group:' lines in /etc/nsswitch.conf (and 'systemd' added if it is not already there).
* | | | | Merge branch 'master' into staging-nextJan Tojnar2020-08-23
|\ \ \ \ \ | | |_|/ / | |/| | |
| * | | | Merge pull request #89353 from wizeman/u/fix-zfs-ebusyLassulus2020-08-22
| |\ \ \ \ | | | | | | | | | | | | stage-1: retry mounting ZFS root a few times
| | * | | | stage-1: retry mounting ZFS root a few timesRicardo M. Correia2020-06-04
| | | | | | | | | | | | | | | | | | | | | | | | This is a workaround for NixOS/nixpkgs#25383
* | | | | | Merge master into staging-nextFrederik Rietdijk2020-08-17
|\| | | | |
| * | | | | Merge pull request #95342 from flokli/systemd-initctlFlorian Klink2020-08-16
| |\ \ \ \ \ | | | | | | | | | | | | | | nixos/systemd: don't try to install systemd-initctl.{service,socket}
| | * | | | | nixos/systemd: don't try to install systemd-initctl.{service,socket}Florian Klink2020-08-13
| | | |_|_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since systemd 246, these are only installed by systemd if HAVE_SYSV_COMPAT is true, which only is the case if you set sysvinit-path and sysvrcnd-path (which we explicitly unset in the systemd derivation for quite some time)
| * / | | | nixos/systemd.tmpfiles.packages: fix an edge caseVladimír Čunát2020-08-16
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | symlinkJoin can break (silently) when the passed paths contain symlinks to directories. This should work now. Down-side: when lib/tmpfiles.d doesn't exist for some passed package, the error message is a little less explicit, because we never get to the postBuild phase (and symlinkJoin doesn't provide a better way): /nix/store/HASH-NAME/lib/tmpfiles.d: No such file or directory Also, it seemed pointless to create symlinks for whole package trees and using only a part of the result (usually very small part).
* | | / / Merge branch 'staging-next' into stagingJan Tojnar2020-08-13
|\| | | | | |_|/ / |/| | |
| * | | Merge pull request #92964 from lopsided98/initrd-secrets-compressorJörg Thalheim2020-08-13
| |\ \ \
| | * | | nixos/stage-1: fix initrd secrets with custom compressorBen Wolsieffer2020-07-11
| | | | |
* | | | | Merge staging-next into stagingFrederik Rietdijk2020-08-13
|\| | | |
| * | | | nixos/systemd: Add support for `listenDatagrams`John Ericson2020-08-11
| | | | | | | | | | | | | | | | | | | | This works exactly analogously to the existing `listenStreams`.
* | | | | Merge staging-next into stagingFrederik Rietdijk2020-08-11
|\| | | |
| * | | | nixos/*: editorconfig fixeszowoq2020-08-08
| | | | |
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-07 07:59:42 +0000