| Commit message (Collapse) | Author | Age |
|\
| |
| | |
nixos/filesystems: succeed mount-pstore.service without backend
|
| | |
|
|\ \ |
|
| | | |
|
|\ \ \
| | | |
| | | | |
nixos/{syncoid,sanoid}: Improve ZFS permission delegation
|
| | | |
| | | |
| | | |
| | | | |
behind
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
When making new snapshots we only need to delegate permissions to the
specific dataset rather than the entire pool.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When sending or receiving datasets with the old implementation it
wouldn't matter which dataset we were sending or receiving, we would
always delegate permissions to the entire pool.
|
| | | |
| | | |
| | | |
| | | | |
This regression was fixed by 51d83077ffb.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This also prints and screenshots the output of chrome://version which
contains useful information.
Outputs (stable, beta, ungoogled, chrome-stable, chrome-beta, chrome-dev):
Chromium 92.0.4515.107 (Official Build) (64-bit)
Chromium 92.0.4515.107 (Official Build) (64-bit)
Chromium 91.0.4472.164 (Official Build, ungoogled-chromium) (64-bit)
Google Chrome 92.0.4515.107 (Official Build) (64-bit)
Google Chrome 92.0.4515.107 (Official Build) beta (64-bit)
Google Chrome 93.0.4577.8 (Official Build) dev (64-bit)
|
|\ \ \ \
| |/ / /
|/| | /
| | |/
| |/| |
nixos/filesystems: mount-pstore.service improvements
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the pstore module is builtin, it nonetheless can take considerable
time to register a backend despite /sys/fs/pstore already appearing
mounted, so the condition is moved into the main script to extend
waiting for the backend to this case.
|
| | |
| | |
| | |
| | |
| | |
| | | |
systemd's modprobe@.service does not require success so mount-pstore
executed despite a non-present pstore module, leading to an error about
the /sys/fs/pstore mountpoint not existing on CONFIG_PSTORE=n systems.
|
|\ \ \
| | | |
| | | | |
nixos/iwd: add settings option
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
nixos/syncoid: split in multiple systemd services and harden them
|
| | | | | |
|
| | | | |
| | | | |
| | | | | |
Co-authored-by: Kim Lindberger <kim.lindberger@gmail.com>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
nixos/klipper: Allow lists as values for gcode_macro
|
| | | | | | |
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
grocy: 3.0.1 -> 3.1.0
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ChangeLog: https://github.com/grocy/grocy/releases/tag/v3.1.0
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* tuxguitar: Ensure that tuxguitar is launched with java 8 comtabilbe jre and libraries as greate java version is not supported
* tuxguitar: Added test to verify application starts without problems
* tuxguitar: 1.5.2 -> 1.5.4
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
nextcloud: remove expires header
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
nextcloud default nginx config did not include the expires config
see: https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/swap: allow luks discards if swap discards are enabled
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| |_|_|/ / / / /
|/| | | | | | | |
chromium: Check the text rendering
|
| | |_|/ / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This should catch regressions like #131074 in the future. In that case a
glibc update caused a regression that caused most of the text to become
invisible (just not the "Web Store" we've already been checking for).
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
nixos/swap: add options option
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/iio: mention iio-sensor-proxy in option description
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In https://github.com/NixOS/nixpkgs/pull/131094 I mistakenly created a new NixOS module for iio-sensor-proxy because I did not know about `hardware.sensor.iio`.
To help people find `hardware.sensor.iio`, include the string "iio-sensor-proxy" in the description.
To search for an iio-sensor-proxy module, I tried in vain:
* `find -iname '*iio-sensor-proxy*'`
* https://search.nixos.org/options?channel=unstable&from=0&size=50&sort=relevance&query=iio-sensor-proxy
* This PR will ensure this search query finds `hardware.sensor.iio`
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
nixos/systemd: fix NSS database ordering
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
- The order of NSS (host) modules has been brought in line with upstream
recommendations:
- The `myhostname` module is placed before the `resolve` (optional) and `dns`
entries, but after `file` (to allow overriding via `/etc/hosts` /
`networking.extraHosts`, and prevent ISPs with catchall-DNS resolvers from
hijacking `.localhost` domains)
- The `mymachines` module, which provides hostname resolution for local
containers (registered with `systemd-machined`) is placed to the front, to
make sure its mappings are preferred over other resolvers.
- If systemd-networkd is enabled, the `resolve` module is placed before
`files` and `myhostname`, as it provides the same logic internally, with
caching.
- The `mdns(_minimal)` module has been updated to the new priorities.
If you use your own NSS host modules, make sure to update your priorities
according to these rules:
- NSS modules which should be queried before `resolved` DNS resolution should
use mkBefore.
- NSS modules which should be queried after `resolved`, `files` and
`myhostname`, but before `dns` should use the default priority
- NSS modules which should come after `dns` should use mkAfter.
|
|\ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
The pppd daemon starting with version 2.4.9 uses rtnetlink to configure
the ipv6 peer address on the ppp interface. It therefore requires
allowing AF_NETLINK sockets.
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
The kernel before version 5.7 required CAP_SYS_ADMIN to conduct BPF
operations. After that a separate capability CAP_BPF was created, which
should be sufficient in this scenario and will further tighten the
sandbox around our pppd service.
Tested on my personal DSL line.
|
|\ \ \ \ \ \ \ \ \ \ \
| |_|/ / / / / / / / /
|/| | | | | | | | | | |
|
| | | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | |
| | | | | | | | | | | | |
zsh: fix nixUnstable completions
|
| | | | | | | | | | | | |
|