| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
https://discourse.nixos.org/t/conflict-between-glibc-and-glibclocales-workaround-inside/7608
|
| |\
| |
| | |
Use zstd for ISO and SD images
|
| | | |
|
| | |
| |
| |
| |
| | |
2.4 has its own completion script which collides with
nix-bash-completions.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes the output of "hostname --fqdn" (previously the domain name
was not appended). Additionally it's now possible to use the FQDN.
This works by unconditionally adding two entries to /etc/hosts:
127.0.0.1 localhost
::1 localhost
These are the first two entries and therefore gethostbyaddr() will
always resolve "127.0.0.1" and "::1" back to "localhost" [0].
This works because nscd (or rather the nss-files module) returns the
first matching row from /etc/hosts (and ignores the rest).
The FQDN and hostname entries are appended later to /etc/hosts, e.g.:
127.0.0.2 nixos-unstable.test.tld nixos-unstable
::1 nixos-unstable.test.tld nixos-unstable
Note: We use 127.0.0.2 here to follow nss-myhostname (systemd) as close
as possible. This has the advantage that 127.0.0.2 can be resolved back
to the FQDN but also the drawback that applications that only listen to
127.0.0.1 (and not additionally ::1) cannot be reached via the FQDN.
If you would like this to work you can use the following configuration:
```nix
networking.hosts."127.0.0.1" = [
"${config.networking.hostName}.${config.networking.domain}"
config.networking.hostName
];
```
Therefore gethostbyname() resolves "nixos-unstable" to the FQDN
(canonical name): "nixos-unstable.test.tld".
Advantages over the previous behaviour:
- The FQDN will now also be resolved correctly (the entry was missing).
- E.g. the command "hostname --fqdn" will now work as expected.
Drawbacks:
- Overrides entries form the DNS (an issue if e.g. $FQDN should resolve
to the public IP address instead of 127.0.0.1)
- Note: This was already partly an issue as there's an entry for
$HOSTNAME (without the domain part) that resolves to
127.0.1.1 (!= 127.0.0.1).
- Unknown (could potentially cause other unexpected issues, but special
care was taken).
[0]: Some applications do apparently depend on this behaviour (see
c578924) and this is typically the expected behaviour.
Co-authored-by: Florian Klink <flokli@flokli.de>
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Show the config option triggering the assertion, so people don't
necessary lookup the nixpkgs source code.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
now that passwdArray and shadowArray aren't used anymore, these can be
folded.
|
| | |
| |
| |
| | |
We keep the conditional on only adding if nscd is enabled for now.
|
| | |
| |
| |
| |
| |
| | |
We keep the "only add the nss module if nscd is enabled" logic for now.
The assertion never was triggered, so it can be removed.
|
| | |
| |
| |
| | |
Motivation: #86350
|
| |\ \
| | |
| | | |
nixos/nsswitch: Make databases more configurable
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of hardcoding all nss modules that are added into nsswitch,
there are now options exposed.
This allows users to add own nss modules (I had this issue with
winbindd, for example).
Also, nss modules could be moved to their NixOS modules which would
make the nsswitch module slimmer.
As the lists are now handled by the modules system, we can use mkOrder
to ensure a proper order as well as mkForce to override one specific
database type instead of the entire file.
|
| |/ |
|
| |\
| |
| | |
nixos/qt5: support adwaita-dark theme
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This prevents duplication in cross-compiled nixos machines. The
bootstrapped glibc differs from the natively compiled one, so we get
two glibc’s in the closure. To reduce closure size, just use
stdenv.cc.libc where available.
|
| | |
| |
| |
| | |
We can’t cross-compile the cache, so just skip it for now.
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
When blocklists are built with a derivation, using extraHosts would
require IFD, since the result of the derivation needs to be converted to
a string again.
By introducing this option no IFD is needed for such use-cases, since
the fetched files can be assigned directly.
|
| |/ |
|
| |
|
|
|
| |
So that applications can find hunspell dictionaries installed through
environment.systemPackages.
|
| |\
| |
| | |
rngd: Start early during boot and encrypted swap entropy fix
|
| | |
| |
| |
| | |
avoid entropy starvation during boot
|
| |\ \
| | |
| | | |
flatpak: 1.4.2 → 1.6.1
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.6.0
* https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.5.4
* https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.5.3
* https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.5.2
* https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.5.1
* https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.5.0
|
| | |/
|/| |
|
| | |
| |
| |
| | |
Never had any effect
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This commit changes the console colors implementation
to use the kernel parameters instead of relying on terminal
escape sequences. This means the palette is applied by the
kernel itself with no custom code running in the initrd
and works for all virtual terminals (not only tty0).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This commit moves all the virtual console related options
to a dedicated config/console.nix NixOS module.
Currently most of these are defined in config/i18n.nix
with a "console" prefix like `i18n.consoleFont`,
`i18n.consoleColors` or under `boot` and are implemented
in tasks/kbd.nix.
Since they have little to do with actual internationalisation
and are (informally) in an attrset already, it makes sense to
move them to a specific module.
|
| |
|
|
|
|
|
|
| |
A centralized list for these renames is not good because:
- It breaks disabledModules for modules that have a rename defined
- Adding/removing renames for a module means having to find them in the
central file
- Merge conflicts due to multiple people editing the central file
|
| |
|
|
|
|
|
|
| |
This PR is part of the networking.* namespace cleanup. We feel that
networking.hostConf is rarely used and provides little value compared to
using environment.etc."host.conf" directly.
Provide sensible default: multi on
|
| |
|
|
|
|
|
| |
This is a more sane default since we do not magically (without opt-in)
pull in binaries from `~/bin`. That is not really an expected behavior
for many users. Users that still want that behavior can now just flip
that switch.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This PR is part of the networking.* namespace cleanup.
The Cisco VPN module is currently of limited value since it just creates
config files but does not manage services. The same functionality can be
achieved by using _environment.etc_ instead.
It would be a different situation if we had a full service module. So if
you are annoyed by this change, please consider write a more featureful
module and put its options unter _services.networking.vpnc_.
Note that this change removes options for *Cisco VPN*, not
*networkmanager-vpn*.
|
| | |
|
| |\
| |
| | |
nixos/gnome3: add sound-theme-freedesktop
|
| | | |
|
| | |
| |
| |
| | |
This module has been obsolete for several years now.
|