| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| | |
nixos/network-interfaces-systemd: don't set network-level domains
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
systemd.network(5) describes Domains= as a "list of domains which should
be resolved using the DNS servers on this link." This setting is read by
systemd-resolved.service, and it's used to configure both search domains
and DNS query routing.
Adding the search domains from `networking.search` is unnecessary
because these are already configured globally in `resolved.conf` through
the default value of `services.resolved.domains`.
Adding the system's `networking.domain` to each network is unexpected
and probably incorrect. A user may not expect that the domain is in
effect automatically added to the search domains even if not specified
in `networking.search`.
Both of these network-level assignments are problematic in cases where
the NixOS networkd module is not managing every interface on the system.
In that scenario, the managed interfaces will have Domains= set while
the others do not. That will cause systemd-resolved to route DNS queries
for the search domains and the system domain to only those managed
interfaces.
|
| |\ \
| | |
| | | |
Fix: WakeOnLan policy
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Adds an option to configure a custom WakeOnLan policy instead of the
hard-coded "magic" policy. To ensure compatibility with current
behavior, "magic" is kept as default.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A further bug to our strange multi-user.target depending on
network-online.target issue is that systemd recently changed the
behaviour of systemd-networkd-wait-online to no longer consider the
absence of interfaces with RequiredForOnline to be sufficient to be
online: https://github.com/systemd/systemd/pull/27825
On the advice of the systemd developers
(https://github.com/systemd/systemd/issues/29388), this commit changes
the configuration of systemd-networkd-wait-online to pass --any by
default, and lets the default DHCP interfaces be RequiredForOnline
as they would be by default if the option is omitted.
It is plausible that systemd-networkd-wait-online may still fail if
there are no interfaces at all. However, that probably cannot be
avoided.
|
| | | |
|
| |/
|
|
| |
See https://github.com/NixOS/nixpkgs/pull/185089
|
| |\
| |
| | |
nixos/network-interfaces-systemd: support `vlans`, `bridges` in systemd-initrd
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
The default just recently changed in 23.11. Users that had
swraid enabled implicitly by NixOS in previous releases got surprised
by warnings even though they do not actually use software RAID.
Fixes #254807
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
I (according to the comment) wrote this somewhere and since then it has
spread to many configs.
https://github.com/search?q=artturin+ENV%7BID_FS_TYPE%7D%3D%3D%22zfs_member%22%2C+ATTR%7B..%2Fqueue%2Fscheduler%7D%3D%22none%22&type=code
https://github.com/NixOS/nixpkgs/issues/169457#issuecomment-1523873402
|
| |\ \
| | |
| | | |
nixos/swraid: fix regression for old initrd and add test coverage
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
My system does not use `bcache` and I sould prever my `systemPackages`
not to have bcache tools.
The change does not change the default but proviced usual `enable` knob.
|
| |/ / |
|
| |/
|
|
|
|
|
|
|
|
| |
policy fragment for each wrapper
This change includes some stuff (e.g. reading of the `.real` file,
execution of the wrapper's target) that belongs to the apparmor policy
of the wrapper. This necessitates making them distinct for each wrapper.
The main reason for this change is as a preparation for making each
wrapper be a distinct binary.
|
| |
|
|
|
| |
This completes changes in #227208
Fixes: #244737, #245089.
|
| |
|
|
|
|
|
| |
Being wanted by and ordered before local-fs.target isn't strictly
correct. And in systemd initrd, it's very incorrect because
local-fs.target is for the initrd file system, not the real root file
system.
|
| | |
|
| |\
| |
| | |
Make swraid optional
|
| | | |
|
| | |
| |
| |
| |
| | |
Since the option affects both stage-1 and stage-2, it does not make
sense to keep it within the boot.initrd namespace.
|
| | |
| |
| |
| |
| |
| | |
swraid support will now only be enabled by default if stateVersion is
older than 23.11. nixos-generate-config will now generate explicit
config for enabling support if needed.
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Introduced in https://github.com/torvalds/linux/commit/aaeca98456431a8d9382ecf48ac4843e252c07b3
with the usual disdain for ZFS.
We have been there in the past with
<https://www.phoronix.com/news/NixOS-Linux-5.0-ZFS-FPU-Drop> /
https://github.com/NixOS/nixpkgs/pull/61076.
This fixes ZFS on aarch64 until the next breakage.
See https://github.com/openzfs/zfs/issues/14555 for original upstream
issue.
|
| |\ \
| | |
| | | |
network-interfaces: restrict ipv6 udev rules
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Only trigger the privacy address override for a given interface when
that interface is added. Without restricting the rule to the
interface, this command would be run when any interface is added.
|
| |\ \ \
| | | |
| | | | |
nixos/lvm: toggle initrd enable option independently of main options
|
| | |/ / |
|
| |\ \ \
| | | |
| | | | |
nixos/*: unhide remaining systemd stage-1 options
|
| | |/ /
| | |
| | |
| | |
| | | |
These options were missed in NixOS/nixpkgs#226237, but they all were
specifically added for systemd stage-1.
|
| |/ / |
|
| | | |
|
| |/
|
|
|
|
| |
a zfs fileSystems entry with an absolute (e.g. device) path rather than
a zfs dataser is parsed as an empty pool name, causing a doomed-to-fail
import job to be created as a boot dependency. Catch this as an assertion
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
There is apparently a bug in the parser of iproute2 where the command
`ip link show <devname>` will not show the device but list all
interfaces (equivalent to `ip link show`) if devname is equal to one of
the flags of `ip-address(8)`. For example, `home`, or `optimistic`.
This bug causes a false positive in the clean up command of the
<devname>-netdev.service, the service fails and the interface is never
configured.
To avoid the bug we can simply use `ip link show dev <devname>`.
|
| |\
| |
| | |
nixos/stratis: initrd support for stratis root volumes
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
it is now possible to supply a stratis pool uuid
for every filesystem, and if that filesystem
is required for boot, the relevant pool will be
started in the initramfs.
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
ReneHollander/fix/nixos-zfs-systemd-unlock-times-out
nixos/zfs: disable unlock timeout with systemd
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
Currently systemd-ask-passwd times out after 1m30s. After 3 tries this
causees systemd to enter the emergency shell and basically lead to an
unbootable system requiring a reboot to be able to try to unlock again.
Also if a pool is imported but not unlocked, the unlock step will no
longer be skipped.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Enable using an erofs filesystem as one of the filesystems needed to
boot the system. This is useful for example in image based deployments
where the Nix store is mounted read only.
[erofs](https://docs.kernel.org/filesystems/erofs.html) offers multiple
benefits over older filesystems like squashfs. Skip fsck.erofs because
it is still experimental.
|
| |/
|
|
|
|
| |
We usually don't want to bring the whole machine into emergency mode
just because we couldn't mount envfs. It's usually not on the critical
path.
|
| |\
| |
| | |
Systemd stage 1 networkd
|
| | | |
|