| Commit message (Collapse) | Author | Age |
... | |
|\ \ \ \
| | | | |
| | | | | |
graylog: 3.3.2 -> 3.3.3
|
| | |/ /
| |/| | |
|
|/ / / |
|
|\ \ \
| |/ /
|/| | |
nixos/bitcoind: change to multi-instance + add tests
|
| | | |
|
|\ \ \
| | | |
| | | | |
udpt: 2017-09-27 -> 3.1.1
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
nixos/hidpi: Reasonable defaults for high-density displays
|
| | | |
| | | |
| | | |
| | | | |
v32n has more characters.
|
|\ \ \ \
| | | | |
| | | | | |
nixos/manual: add a section about Vulkan drivers
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
- Add a general block about how to configure and test Vulkan
- Add a section about switching between mesa/radv and amdvlk on AMD
GPUs.
|
|/ / /
| | |
| | |
| | | |
Building without specifying an arch attempts to build all,
and fails.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Begin a new chapter "GPU Acceleration", this should also cover
VA-API, OpenGL, Vulkan, etc.
- Add a general blurb about OpenCL and how to check whether OpenCL
devices are found.
- Add a section about enabling OpenCL for AMD GPUs specifically.
|
| | | |
|
|\ \ \
| | | |
| | | | |
nixos/displayManager: make autoLogin options independent of DM type
|
| | | |
| | | |
| | | |
| | | | |
Co-authored-by: volth <volth@volth.com>
|
|\ \ \ \
| |/ / /
|/| | | |
postfix: Replaced config key by recommendation and introduced usage of system trust store
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`sslCACert` was used for trust store of client and server certificates. Since `smtpd_tls_ask_ccert` defaults to no the setup of `smtpd_tls_CApath` was removed.
>By default (see smtpd_tls_ask_ccert), client certificates are not requested, and smtpd_tls_CApath should remain empty.
see http://www.postfix.org/postconf.5.html#smtpd_tls_CAfile
|
|\ \ \ \
| | | | |
| | | | | |
qemu-vm: Fix useBootLoader, remove `/boot` read-only restriction
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There does not seem to be a good reason to do this, and it breaks running
`nixos-rebuild boot --install-bootloader` inside the VM.
|
| | | | | |
|
| |/ / /
|/| | | |
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Virtualbox recommends VMSVGA for Linux guests.
It is also currently the only one supporting 3D acceleration
and it works out of the box with NixOS and auto screen resizing.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With 'set 3 boot on' the error 'file system "/boot" is not a FAT EFI
system partition (ESP) file system' occurs when running
"nixos-install" during the basic installation (tested in in a
VirtualBox VM).
|
|\ \ \ \
| | | | |
| | | | | |
grub: add support for passwords
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This method is similar to wait_for_text but is based on matching
serial console lines instead of the VGA output.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
test-driver.py: delete VM state directory after test run
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Keeping the VM state test across several run sometimes lead to subtle
and hard to spot errors in practice. We delete the VM state which
contains (among other things) the qcow volume.
We also introduce a -K (--keep-vm-state) flag making VM state to
persist after the test run. This flag makes test-driver.py to match
its previous behaviour.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
radicale: 2.1.11 -> 3.0.3
|
| | |/ / /
| |/| | | |
|
|\| | | | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
nixos/doc: add section on Intel DDX drivers
|
| | | | | |
|
|\| | | | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
nixos/resilio: listen on [::1] by default
|
| | | | | |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Enhance the heuristics to make sure that a user doesn't accidentally
upgrade across two major versions of Nextcloud (e.g. from v17 to v19).
The original idea/discussion has been documented in the nixpkgs manual[1].
This includes the following changes:
* `nextcloud19` will be selected automatically when having a stateVersion
greater or equal than 20.09. For existing setups, the package has to
be selected manually to avoid accidental upgrades.
* When using `nextcloud18` or older, a warning will be thrown which recommends
upgrading to `nextcloud19`.
* Added a brief paragraph about `nextcloud19` in the NixOS 19.09 release
notes.
* Restart `phpfpm` if the Nextcloud-package (`cfg.package`) changes[2].
[1] https://nixos.org/nixos/manual/index.html#module-services-nextcloud-maintainer-info
[2] https://github.com/NixOS/nixpkgs/pull/89427#issuecomment-638885727
|
|/ / / |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
nixos/dovecot2: turn `mailboxes`-option into an attr-set
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Specifying mailboxes as a list isn't a good approach since this makes it
impossible to override values. For backwards-compatibility, it's still
possible to declare a list of mailboxes, but a deprecation warning will
be shown.
|
|/ /
| |
| |
| |
| |
| |
| | |
`shell_on_fail` (#89365)
* nixos/manual: document boot.debug1mounts
* nixos/manual: clarify what `exit` does with shell_on_fail
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since cd1dedac67d4b077a556a660ef5724c909da8006 systemd-networkd has it's
netlink socket created via a systemd.socket unit. One might think that
this doesn't make much sense since networkd is just going to create it's
own socket on startup anyway. The difference here is that we have
configuration-time control over things like socket buffer sizes vs
compile-time constants.
For larger setups where networkd has to create a lot of (virtual)
devices the default buffer size of currently 128MB is not enough.
A good example is a machine with >100 virtual interfaces (e.g.,
wireguard tunnels, VLANs, …) that all have to be brought up during
startup. The receive buffer size will spike due to all the generated
message from the new interfaces. Eventually some of the message will be
dropped since there is not enough (permitted) buffer space available.
By having networkd start through / with a netlink socket created by
systemd we can configure the `ReceiveBufferSize` parameter in the socket
options without recompiling networkd.
Since the actual memory requirements depend on hardware, timing, exact
configurations etc. it isn't currently possible to infer a good default
from within the NixOS module system. Administrators are advised to
monitor the logs of systemd-networkd for `rtnl: kernel receive buffer
overrun` spam and increase the memory as required.
Note: Increasing the ReceiveBufferSize doesn't allocate any memory. It
just increases the upper bound on the kernel side. The memory allocation
depends on the amount of messages that are queued on the kernel side of
the netlink socket.
|
|\ \ \
| | | |
| | | | |
nixos/release-notes: Amend note about image compression
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
hardware/u2f: remove module
|