Ideally, libnss_sss should be part of stdenv.
That's not going to happen because there are any number of NSS modules that we
can't possibly all add to stdenv.
Indeed, I was not thinking about making it part of stdenv by default.
What about enrich stdenv ( through config.nix or
Hi,
On 23/06/15 14:50, Adrien Devresse wrote:
If possible, you could also enable chroot builds. It might be possible to
override /etc/nsswitch.conf in the chroot by setting the Nix option
build-chroot-dirs = /etc/nsswitch.conf=/path/to/my-nsswitch.conf (where
my-nsswitch.conf doesn't contain
Would this work as a non-root user ?
No, you need to be root to do chroot builds.
This is unfortunately a problem: Nix is advertised to work in non-root
environment and is used as this.
You have common situations where root access is just not possible.
A Linux cluster configured with LDAP (
My guess: zerotier-one calls a binary that's not available to the script
On Wed, 24 Jun 2015 07:27 stewart mackenzie setor...@gmail.com wrote:
So, I'm setting up a service for ZeroTier-One, the issue arises when
the ZeroTierOne service tries to start.
After doing a `sudo nixos-rebuild
So, I'm setting up a service for ZeroTier-One, the issue arises when
the ZeroTierOne service tries to start.
After doing a `sudo nixos-rebuild build-vm -I
nixpkgs=~/nixdev/nixpkgs/ --fallback -j 8 --cores 8 --fast`
then `./result/bin/run-rivergod-vm`
once logged in to the vm I issue `sudo
(back on this problem)
Ah, sorry, I'm not really familiar with nss. Does the libnss_sss
version have to match what's installed system-wide, rather than e.g.
being a build input?
I would say no.
It need to be verified but it is very likely that any libnss_sss version
able to connect on the sss
Hi,
On 23/06/15 11:47, Adrien Devresse wrote:
Ideally, libnss_sss should be part of stdenv.
That's not going to happen because there are any number of NSS modules that we
can't possibly all add to stdenv.
Do you have any elegant way in Nix to add a module / modify the stdenv
without
I'm trying to deploy a small network of cassandra servers. These servers
will communicate with each other over an internal GCE network. I've
specified a gce network like so:
resources.gceNetworks.foo = credentials // {
addressRange = 10.0.0.0/16;
firewall.allow-cassandra = {
