| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit d170c98d13a7b622c57c9b9f727a6bfec95a9181.
niksnut argues that we need smaller system closures, not bigger.
So users facing the trouble of getting gcc rebuilds after nix-collect-garbage
for any minimal nixos configuration change should use other means of
not losing the stdenv output.
One way is to keep one somewhere: nix-build -A stdenv -o stdenv '<nixpkgs>'.
Another may be to use nix.conf options like gc-keep-outputs, gc-keep-derivations
or env-keep-derivations.
|
| |
|
|
|
|
|
|
| |
This will help a lot on ARM, where nix-collect-garbage erases gcc; then, any
change to a small system config file requires rebuilding gcc again.
I don't know why it does not happen on x86. Maybe it just pulls the gcc from
hydra, if garbage is collected.
|
| |
|
|
|
|
|
|
|
| |
It boots, but some things still don't work:
1) Installation of DTBs
2) Boot of initrd
Booting still needs a proper config.txt in /boot, which could probably be
managed by NixOS.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
ec2.metadata = true, as the existing (default) blackhole will not be cleared.
(cherry picked from commit ccf672ca6b055e5e862e45b65d122754c16cf7d1)
|
| |\| |
|
| | |\
| | |
| | | |
/run/mysqld now 0755 (instead 0700)
|
| | | |
| | |
| | |
| | | |
see https://github.com/NixOS/nixpkgs/pull/7482
|
| | | |
| | |
| | |
| | | |
closes #7651
|
| | | |
| | |
| | |
| | |
| | | |
Added option to set user. Use unpriviledged user by default. Add sane
default for configuration location.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This service only needs to run once on system startup, so it doesn't
need to be restarted by switch-to-configuration.
|
| | | | |
|
| | | | |
|
| | |\ \
| | | |
| | | | |
nixos: fix infinite recursion in isoImage.isoName
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This adds support for authenticating using a U2F device such as a
yubikey neo.
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | | |
nixos: add confd module
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Rather than shipping our own startkde script, we will go back to
patching upstream's script. This will be less confusing to potential
contributors.
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* add verbosity setting
* don't set mbpfan as a setuid program
|
| | | | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Added BRLTTY package
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
During the refactor of the networkd stuff in f8dbe5f, a lot of the
options are now needed by systemd.nix as well as networkd.nix but
weren't moved by that commit as well.
For now, this fixes all networkd VM tests except for the macvlan one and
thus it should fix #7505 for at least DHCP-based configuration.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In f8dbe5f, the default value for networking unit "enabled" option
suddenly flipped to false. I have no idea of whether this happened by
accident, but I'm setting it to true again, because it essentially
breaks systemd networking support and we have systemd.network.enable to
have a "turn the world off" switch.
And of course, because the mentioned commit obviously wasn't done with
even a run of the simplest run of one of the network VM tests, we now
get an evaluation error if we switch useNetworkd to true.
Fixes the core issue of #7505.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| | | | | | |
|
| |\| | | | |
|
| | | | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Mediawiki updates
|
| | | | | | | |
|
| | | | | | | |
|
| | | | |/ /
| | |/| | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It was broken due to 57b05765c968c1ad5245c59513d11d679ed7130d.
ZFS requires `networking.hostId` to be set.
|
| | | | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
kubernetes: update to 0.15, module fixes
|
| | | | |/ /
| | |/| | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
nixos/nginx: enable service/config reload
|
| | | |/ / / |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
nixos/ripple-data-api: add import mode option
|
| | | |/ / / |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Passing the chroot flag to nixos-install without arguments should now give you a
Bash shell as intended rather than try an empty path.
This was masked by the user's shell (usually /bin/bash) being defaulted to by
chroot, and being found since their paths used NixOS conventions.
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When bootstrapping from other distributions, nixos-install is unable to find
various tools in the chroot since their paths aren't aware of NixOS conventions.
This makes a small change to existing code by specifying nixpkgs/nixos instead
of just nixos when running nix-instantiate in the chroot. I haven't tested this
outside of bootstrapping, but the same specification is used elsewhere in the
code so I don't see why it wouldn't work.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is already set in profiles/minimal.nix.
Probably fixes #7589.
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | | |
add actkbd; nixos: add support for volume control with media keys
|
| | | | | | |
|