about summary refs log tree commit diff
path: root/nixos/modules/tasks
Commit message (Collapse)AuthorAge
* nixos: zfs: correct the networking.hostId error messageGraham Christensen2017-12-20
| | | | | Users were confused that the error message said config.networking.hostId, and indeed that did nothing to fix their problem. Update the error message to specify the option they should actually set.
* nixos/btrfs: add services.btrfs.autoScrubFlorian Jacob2017-12-13
| | | | | for automatic regular scrubbing of mounted btrfs filesystems, similar to what's already there for zfs.
* nixos/network-interfaces: Add " around network interface namesFlorian Jacob2017-11-09
| | | | in assertion messages to avoid misinterpretations when the interface name contains a dot.
* Merge pull request #30127 from florianjacob/limit_interface_name_lengthJörg Thalheim2017-11-08
|\ | | | | nixos/network-interfaces: assertion for too long interface names
| * nixos/network-interfaces: assertion for too long interface namesFlorian Jacob2017-10-05
| |
* | network-interfaces-scripted: fix NixOS/nixops#640Bas van Dijk2017-10-30
| | | | | | | | | | | | | | Reverse the PartOf dependency between network-setup and network-addresses-* This was joint work of: @nh2, @domenkozar, @fpletz, @aszlig and @basvandijk at the NixCon 2017 hackathon.
* | Merge pull request #30339 from pvgoran/fileSystems-silentFormatOptionsFranz Pletz2017-10-25
|\ \ | | | | | | filesystems: use non-interactive formatOptions by default
| * | filesystems: use non-interactive formatOptions by defaultPavel Goran2017-10-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | When autoFormat is enabled, in order to successfully create a filesystem, certain filesystems require specific options to be passed to mkfs to prevent it from asking questions. This commit sets default formatOptions to "-q" for "jfs" and "reiserfs" filesystems for this purpose. Resolves #29140.
* | | nixos/ecryptfs: initedef2017-10-20
| | | | | | | | | | | | | | | | | | Currently, ecryptfs support is coupled to `security.pam.enableEcryptfs`, but one might want to use ecryptfs without enabling the PAM functionality. This commit splits it out into a `boot.supportedFilesystems` switch.
* | | encrypted devices: provide working examplelassulus2017-10-16
| | |
* | | encrypted devices: don't override default cryptoModuleslassulus2017-10-16
|/ /
* | Merge pull request #30204 from lheckemann/powertop-fixJörg Thalheim2017-10-07
|\ \ | | | | | | powertop module: add kmod to path
| * | powertop module: add kmod to pathLinus Heckemann2017-10-07
| |/ | | | | | | | | | | | | | | | | powertop attempt to load some kernel modules like msr by calling modprobe. This is the counterpart to 88e43eb39bcda5f8fdf41d566bc6799596177cd0 which has the powertop executable search PATH for modprobe rather than hardcoding /sbin, and actually adds the directory containing modprobe to its PATH for the systemd service.
* / nixos/filesystems/ext: Don't try to load ext3 moduleTuomas Tynkkynen2017-10-07
|/ | | | | This module doesn't exist since v4.3, where the ext3 driver was removed as ext4.ko can mount ext3 filesystems as well.
* assertion should check for encrypted.label of the defined fileSystemRok Garbas2017-09-29
|
* network-interfaces: device routes for default gatewayFranz Pletz2017-09-28
| | | | Iff interface is set, it makes sense to add device route by default.
* kbd service: systemd-vconsole-setup is triggered by udevFranz Pletz2017-09-27
| | | | cc #22470
* Revert "kbd service: use /dev/tty1 for systemd-vconsole-setup"Alexander Ried2017-09-27
| | | | | | | This reverts commit 0c81594a29d99d9ee9c9c88c680340d56823cfb2. It's no longer needed since systemd-vconsole-setup enumerates all ttys until it finds a suitable one since systemd v234.
* nixos/zfs: import encrypted datasets by default for zfsUnstableJörg Thalheim2017-09-26
|
* nixos/network-interfaces: ensure slave interfaces are upFranz Pletz2017-09-25
| | | | Fixes #28620.
* nixos/network-interfaces: cannot delay device unitsFranz Pletz2017-09-25
| | | | | | | Systemd is complaining that it can't delay the startup of device units. We have a before dependency on the respective device unit for every netdev service, which doesn't make any sense because we create the actual interface in this service.
* nixos/network-interfaces: IPs must always be setFranz Pletz2017-09-25
| | | | | | | | | | | | Previously, depending on the environment and the type of interface that was created, the configured IPs of an interface wouldn't be applied on a nixos-rebuild switch. It works after a reboot. This patch ensures that the network-addresses service is started either via the network-link service or if the networking target is activated (i.e. on system activation). Fixes #28474 #16230.
* encrypted devices: add label set assertion (#29651)Silvan Mosberger2017-09-23
|
* Revert "nixos: add option for bind to not resolve local queries (#29503)"Peter Simons2017-09-23
| | | | | | | | | | | | | | This reverts commit 670b4e29adc16e0a29aa5b4c126703dcca56aeb6. The change added in this commit was controversial when it was originally suggested in https://github.com/NixOS/nixpkgs/pull/29205. Then that PR was closed and a new one opened, https://github.com/NixOS/nixpkgs/pull/29503, effectively circumventing the review process. I don't agree with this modification. Adding an option 'resolveLocalQueries' to tell the locally running name server that it should resolve local DNS queries feels outright nuts. I agree that the current state is unsatisfactory and that it should be improved, but this is not the right way. (cherry picked from commit 23a021d12e8f939cd0bfddb1c7adeb125028c1e3)
* Merge pull request #29344 from ↵Jörg Thalheim2017-09-22
|\ | | | | | | | | Moredread/fix/fileystem-encrypted-keyfile-missing-initrd-support nixos/fileystems: Fix boot fails with encrypted fs
| * nixos/fileystems: Fix boot fails with encrypted fsAndré-Patrick Bubel2017-09-14
| | | | | | | | | | | | | | | | | | | | | | Boot fails when a keyfile is configured for all encrypted filesystems and no other luks devices are configured. This is because luks support is only enabled in the initrd, when boot.initrd.luks.devices has entries. When a fileystem has a keyfile configured though, it is setup by a custom command, not by boot.initrd.luks. This commit adds an internal config flag to enable luks support in the initrd file, even if there are no luks devices configured.
* | Merge pull request #29581 from eqyiel/fix-rpc-gssdJörg Thalheim2017-09-22
|\ \ | | | | | | nixos/nfs: allow setting the path to krb5.keytab
| * | nfs-utils: set /etc/krb5.keytab as default path for rpc-gssdRuben Maher2017-09-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the `rpc-gssd.service` has a `ConditionPathExists` clause that can never be met, because it's looking for stateful data inside `/nix/store`. `auth-rpcgss-module.service` also only starts if this file exists. Fixes NixOS/nixpkgs#29509.
* | | fuse3: init at 3.1.1Michael Weiss2017-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This includes fuse-common (fusePackages.fuse_3.common) as recommended by upstream. But while fuse(2) and fuse3 would normally depend on fuse-common we can't do that in nixpkgs while fuse-common is just another output from the fuse3 multiple-output derivation (i.e. this would result in a circular dependency). To avoid building fuse3 twice I decided it would be best to copy the shared files (i.e. the ones provided by fuse(2) and fuse3) from fuse-common to fuse (version 2) and avoid collision warnings by defining priorities. Now it should be possible to install an arbitrary combination of "fuse", "fuse3", and "fuse-common" without getting any collision warnings. The end result should be the same and all changes should be backwards compatible (assuming that mount.fuse from fuse3 is backwards compatible as stated by upstream [0] - if not this might break some /etc/fstab definitions but that should be very unlikely). My tests with sshfs (version 2 and 3) didn't show any problems. See #28409 for some additional information. [0]: https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
* | | nixos: add option for bind to not resolve local queries (#29503)gwitmond2017-09-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the user specifies the networking.nameservers setting in the configuration file, it must take precedence over automatically derived settings. The culprit was services.bind that made the resolver set to 127.0.0.1 and ignore the nameserver setting. This patch adds a flag to services.bind to override the nameserver to localhost. It defaults to true. Setting this to false prevents the service.bind and dnsmasq.resolveLocalQueries settings from overriding the users' settings. Also, when the user specifies a domain to search, it must be set in the resolver configuration, even if the user does not specify any nameservers. (cherry picked from commit 670b4e29adc16e0a29aa5b4c126703dcca56aeb6) This commit was accidentally merged to 17.09 but was intended for master. This is the cherry-pick to master.
* | | nixos/networking: network is online if default gw setFranz Pletz2017-09-18
|/ / | | | | | | | | | | | | | | | | | | Previously services depending on network-online.target would wait until dhcpcd times out if it was enabled and a static network address configuration was used. Setting the default gateway statically is enough for the networking to be considered online. This also adjusts the relevant networking tests to wait for network-online.target instead of just network.target.
* / zfsUnstable: init at 2017-09-12Jörg Thalheim2017-09-15
|/
* nixos/bcachefs: init moduledavidak2017-08-31
|
* network-interfaces-scripted: don't add 'lo' as device dependencyJörg Thalheim2017-08-30
| | | | | systemd does not create device units for loopback devices, since they are not physical.
* tasks/filesystems: Make sure /dev/pts/ptmx is 0666 (#28490)Richard Yang2017-08-30
| | | | | This is required for running commands likes screen and tmux, especially inside containers. See also : https://www.kernel.org/doc/Documentation/filesystems/devpts.txt
* zfs, spl: 0.6.5.11 -> 0.7.0Robin Gloster2017-07-27
|
* Merge pull request #26170 from kirelagin/wlan-fixJoachim F2017-06-17
|\ | | | | wirelessInterfaces: Add a missing parameter
| * wirelessInterfaces: Add a missing parameterKirill Elagin2017-05-28
| |
* | nixos/bcache: add services.udev.packages = [ bcache-tools ]Bjørn Forsman2017-06-10
|/ | | | | | | | | Adds /dev/disk/by-{id,label}/* symlinks for bcache device nodes, in the final rootfs. Symlinks will only be created for bcache devices that contain filesystems. So if you have a blank bcache device or run LVM on top of bcache you will not get this kind of symlink.
* typo: powerManagment -> powerManagement (#25813)Matthew Maurer2017-05-16
|
* zfs: zed service is now called zfs-zedJörg Thalheim2017-05-07
| | | | fixes #25566
* Add Elantech ETPS/2 Trackpoint (ThinkPad Yoga 260)Ismaïl Senhaji2017-04-22
|
* network-interfaces-scripted: Add static parameter for default gatewayMarkus Mueller2017-04-16
|
* powertop: add moduleJörg Thalheim2017-04-15
|
* nixos/filesystems: skip filesystem check for bindfs (#24671)0xABAB2017-04-06
| | | Bindfs (FUSE) provides a pseudo-filesystem and as such does not benefit from a file system check.
* network-link-*.service: Set stopIfChanged = falseEelco Dolstra2017-04-04
| | | | | | | | | | | | This reduces the time window during which IP addresses are gone during switch-to-configuration. A complication is that with stopIfChanged = true, preStop would try to delete the *new* IP addresses rather than the old one (since the preStop script now runs after the switch to the new configuration). So we now record the actually configured addresses in /run/nixos/network/addresses/<interface>. This is more robust in any case. Issue https://github.com/NixOS/nixops/issues/640.
* network-interfaces: reload bridges on conf changesArnold Krille2017-03-26
| | | | | | | | | | | And adopt the tests to add an interface and remove it again. It should work when deactivating rstp, it will not work when activating rstp for the first bridge as then the userspace daemon is not yet available. But once one bridge is active with stp, it should work with the reload for any further bridge. Fixes #21745. Also see #22547.
* networkd: fix setting both defaultGateway{,6}Robin Gloster2017-03-25
|
* nixos/treewide: systemd.time is in manvolume 7Franz Pletz2017-03-21
| | | | cc #23396
* nixos/treewide: remove boolean examples for optionsFranz Pletz2017-03-17
| | | | | | | They contain no useful information and increase the length of the autogenerated options documentation. See discussion in #18816.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-27 04:36:19 +0000