about summary refs log tree commit diff
path: root/nixos/modules/tasks
Commit message (Collapse)AuthorAge
* Merge pull request #312317 from tom-kuca/replace-existing-network-addressesMichele Guerini Rocco2024-06-03
|\ | | | | nixos/network-interfaces: prevent failure when a network address already exists
| * nixos/network-interfaces: prevent failure when a network address already existsTomáš Kuča2024-05-17
| | | | | | | | | | | | | | | | | | | | | | The original code tests output of `ip addr add` command to detect if an adress already exists. The error message was changed in the past and the test no longer works. The patch replaces `ip addr add` with `ip addr replace`. The new command replaces an existing address or creates a new one if there isn't any. fixes 306841
* | Revert "nixos/networking: use mkIfs on the inner attributes"Maximilian Bosch2024-05-31
| |
* | nixos/networking: use mkIfs on the inner attributesLinus Heckemann2024-05-23
| | | | | | | | This is a bit more compact and yields the same evaluation results.
* | nixos/networking: use optionalAttrs -> mkIf for networkd route generationMaximilian Bosch2024-05-20
| | | | | | | | Suggested in https://github.com/NixOS/nixpkgs/pull/312472#discussion_r1605894882
* | nixos/networkd: get rid of *Config attributes in listsMaximilian Bosch2024-05-20
|/ | | | | | | | | | | | | | | | | | | | | | | | This patch is about removing `wireguardPeerConfig`, `dhcpServerStaticLeaseConfig` - a.k.a. the AbstractSingletonProxyFactoryBean of nixpkgs - and friends. As a former colleague said > worst abstraction ever I second that. I've written enough networkd config for NixOS systems so far to have a strong dislike. In fact, these don't even make sense: `netdevs.wireguardPeers._.wireguardPeerConfig` will be rendered into the key `[WireGuardPeer]` and every key from `wireguardPeerConfig` is in there. Since it's INI, there's no place where sections on the same level as wireguardPeerConfig fit into. Hence, get rid of it all. For the transition, using the old way is still allowed, but gives a warning. I think we could drop this after one release. The tests of rosenpass and systemd-networkd-dhcpserver-static-leases were broken on the rev before, hence they were updated, but are still not building.
* Merge pull request #287505 from jpds/zfs-scrub-trim-randomizedDelaySecFranz Pletz2024-05-10
|\
| * nixos/zfs: Added a randomizedDelaySec option to ZFS autoscrub/trim timersJonathan Davies2024-05-03
| | | | | | | | | | Allows operators to space out these IO operations across a fleet of machines, rather than have them all happen at the same time.
* | nixos/zfs: Default autoscrub interval to monthlyJonathan Davies2024-05-03
|/
* nixos: remove all uses of lib.mdDocstuebinm2024-04-13
| | | | | | | | | | | | | | these changes were generated with nixq 0.0.2, by running nixq ">> lib.mdDoc[remove] Argument[keep]" --batchmode nixos/**.nix nixq ">> mdDoc[remove] Argument[keep]" --batchmode nixos/**.nix nixq ">> Inherit >> mdDoc[remove]" --batchmode nixos/**.nix two mentions of the mdDoc function remain in nixos/, both of which are inside of comments. Since lib.mdDoc is already defined as just id, this commit is a no-op as far as Nix (and the built manual) is concerned.
* nixos/zfs: install zfs udev rules on stage1Luís Fonseca2024-04-08
| | | | Install zfs udev rules on initrd, so that /dev/zvol gets populated.
* nixos/bcachefs: support unlock with clevis in systemd stage 1Matt Moriarity2024-04-05
|
* Merge pull request #298068 from posch/manage-gidsAaron Andersen2024-04-01
|\ | | | | nixos/nfsd: settings for /etc/nfs.conf
| * nixos/nfsd: settings for /etc/nfs.confTobias Poschwatta2024-03-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | services.nfs.settings is added for options that go into /etc/nfs.conf. There are services.nfs.server.extraNfsdConfig and services.nfs.extraConfig, but they have drawbacks. They overlap in scope (nfs.extraConfig can also add nfsd options). They require that one writes INI syntax. They often produce nfs.conf files with duplicate section names, which is confusing. This deprecates services.nfs.server.extraNfsdConfig and services.nfs.extraConfig. services.nfs.settings cannot be used together with services.nfs.server.extraNfsdConfig or services.nfs.extraConfig.
* | envfs: 1.0.3 -> 1.0.6Jörg Thalheim2024-03-24
|/ | | | Diff: https://github.com/Mic92/envfs/compare/1.0.3...1.0.6
* Add missing closing parens.Attila Oláh2024-03-02
| | | https://xkcd.com/859
* Merge pull request #291951 from amarshall/zfs-pkgs-renamingAdam C. Stephens2024-03-01
|\ | | | | zfs: rename zfsStable -> zfs_2_2; zfsUnstable -> zfs_unstable; remove enableUnstable option in favor of package
| * nixos/zfs: Remove enableUnstable in favor of setting packageAndrew Marshall2024-02-27
| | | | | | | | | | | | | | This just adds complexity and confusion. Once-upon-a-time, there was no `package` and only `enableUnstable`, but now it is just confusing to have both, as it would be possible to do e.g. `package = pkgs.zfs` and `enableUnstable = true`, but then `enableUnstable` does nothing.
| * zfs_unstable: Rename from zfsUnstableAndrew Marshall2024-02-27
| | | | | | | | This matches the naming of other zfs_* pkgs.
| * nixos/zfs: Fix typo in option docAndrew Marshall2024-02-27
| |
* | zfs_2_1: 2.1.14 -> 2.1.15Alyssa Ross2024-02-27
|/ | | | | | | | | | This adds compatibility with newer kernels, which fixes nixosTests.zfs.series_2_1, which broke when the default kernel version was bumped. This means we no longer need the removeLinuxDRM option at all, but I've kept it around as a no-op so people can leave it set in case the same thing happens again in future.
* zfs: update latestCompatibleLinuxPackagesAlyssa Ross2024-02-26
| | | | | | | ZFS no longer tries to use GPL-only symbols on aarch64. Tested by building nixosTests.zfs.stable (modified to use Linux 6.6) and nixosTests.zfs.unstable.
* nixos/filesystems: make supportedFilesystems an attrsetpennae2024-02-19
| | | | | | | | this lets us *dis*able filesystem explicitly, as is required by e.g. the zfs-less installer images. currently that specifically is only easily possible by adding an overlay that stubs out `zfs`, with the obvious side-effect of also removing tooling that could run without the kernel module loaded.
* nixos/filesystems: init overlayfsnikstur2024-02-07
|
* Merge pull request #279852 from Madouura/pr/bcachefsJörg Thalheim2024-01-25
|\ | | | | bcachefs: update comments, release-notes, only use IFS for bcachefs, update bcachefs-tools and module
| * nixos/bcachefs: add 'bcachefs-tools' to (udev/systemd).packagesMadoura2024-01-16
| |
| * nixos/bcachefs: clarify 'FIXME' comment on when to removeMadoura2024-01-16
| |
* | Merge pull request #279923 from jopejoe1/sshfsLassulus2024-01-24
|\ \ | | | | | | nixos/filesystems: set `system.fsPackages` for sshfs
| * | nixos/filesystems: init sshfsjopejoe12024-01-10
| | |
* | | Merge pull request #280658 from simonhollingshead/add-fixedrandomdelayLuke Granger-Brown2024-01-22
|\ \ \ | |_|/ |/| | nixos/auto-upgrade: add system.autoUpgrade.fixedRandomDelay
| * | nixos/auto-upgrade: add system.autoUpgrade.fixedRandomDelaySimon Hollingshead2024-01-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From systemd 247, timers can be configured to randomize their delay once and to apply the same random delay for all future executions. This allows users to have less jitter between auto-upgrade executions while still avoiding multiple timers firing simultaneously on a machine or multiple machines all performing their upgrades simultaneously. The default option value (false) is backwards compatible. All supported versions of NixOS (in fact, back to and including 21.05) use systemd 247 or later.
* | | Merge pull request #278179 from sinanmohd/network-interfaces-sitFranz Pletz2024-01-16
|\ \ \ | | | | | | | | nixos/network-interfaces: fix implicit dependency on underlying device
| * | | nixos/network-interfaces: fix implicit dependency on underlying devicesinanmohd2024-01-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | the bug causes a hard dependency on an underlying device which might not be valid for all interfaces, also broke the example for networking.sits. this is due to calling hasAttr first and checking for null afterwards, the bug was made more apparent in commit 76a3c30
* | | | Merge pull request #280296 from ancathri/getKeyLocations-nosnapshotsWill Fancher2024-01-15
|\ \ \ \ | | | | | | | | | | nixos/zfs: fix getKeyLocations when listsnaps=on
| * | | | nixos/zfs: fix getKeyLocations when listsnaps=onancathri2024-01-12
| | |_|/ | |/| | | | | | | | | | Encountered boot errors in pool with `listsnapshots=on` getKeyLocations should ignore snapshots as they will not be well-handled by createImportService later on
* | | | Merge pull request #272169 from nyabinary/remove-deprecated-network-interfacesGuillaume Girol2024-01-14
|\ \ \ \ | | | | | | | | | | nixos/network-interfaces: remove network-interfaces.target
| * | | | nixos/network-interfaces: remove network-interfaces.targetNiko2024-01-12
| |/ / / | | | | | | | | | | | | Co-authored-by: Martin Weinelt <mweinelt@users.noreply.github.com>
* | | | Merge pull request #280708 from thillux/fix-trackpointnikstur2024-01-13
|\ \ \ \ | |_|_|/ |/| | | modules/trackpoint: fix quote
| * | | modules/trackpoint: fix quoteMarkus Theil2024-01-13
| |/ / | | | | | | | | | | | | | | | | | | | | | Fixes: [ 7.106281] systemd[1]: /etc/systemd/system/trackpoint.service:10: Unbalanced quoting, ignoring: "/nix/store/iidxwcyp8pqhrq3iji17shs4m6gin0kv-systemd-254.6/bin/udevadm trigger --attr-match=name="TPPS/2 IBM TrackPoint" Signed-off-by: Markus Theil <theil.markus@gmail.com>
* | | Merge pull request #272794 from dcarosone/zpool-import-dRyan Lahfa2024-01-12
|\ \ \ | |/ / |/| | nixos/zfs: check pool state with -d, like import
| * | nixos/zfs: check pool state with -d, like importDaniel Carosone2023-12-08
| | | | | | | | | | | | | | | This can avoid unnecessary wait-looping for pool to be 'ready' on some systems when the paths don't match
* | | nixos/bcachefs: use linuxPackages_latestK9002024-01-08
| | |
* | | Merge branch 'master' into pr/bcachefsJörg Thalheim2024-01-07
|\ \ \ | | |/ | |/|
| * | Merge pull request #195805 from Luflosi/grub-use-correct-zfs-versionRyan Lahfa2023-12-31
| |\ \ | | | | | | | | nixos/grub: use the correct ZFS version
| | * | nixos/grub: use the correct ZFS versionLuflosi2023-12-29
| | | | | | | | | | | | | | | | | | | | When `config.boot.zfs.enableUnstable` is set to true, grub was built with the `zfs` package even though the rest of the system uses the `zfsUnstable` package. The effect of this can only be seen when `zfs` and `zfsUnstable` actually differ (which is not currently the case), for example when overriding one of them locally.
| * | | nixos/trackpoint: replace activationScriptnikstur2023-12-29
| |/ / | | | | | | | | | Replace with a separate systemd service ordered before sysinit.target
| * | Merge pull request #271326 from philiptaron/shutdown.targetnikstur2023-12-27
| |\ \ | | | | | | | | treewide: depend on `shutdown.target` if `DefaultDependencies=no` in almost every case
| | * | nixos/network-interfaces: ensure correct ordering w.r.t. shutdown.targetPhilip Taron2023-11-30
| | | | | | | | | | | | | | | | Also, mark this service as `oneshot`, since it is.
| | * | nixos/zfs: ensure correct ordering w.r.t. shutdown.targetPhilip Taron2023-11-30
| | | |
| | * | nixos/bcachefs: ensure correct ordering w.r.t. shutdown.targetPhilip Taron2023-11-30
| | | |