How about NEON
Nix Expression Object Notation
On 28 feb. 2016, at 15:49, stewart mackenzie wrote:
> Excellent idea, this removes quite a lot of manual steps.
>
> Recently wrote some dirty python scripts to automate the checking and
> replacing of sha256s, this approach
I’ve used a shared nix store between VMs in the past, until the sqlite database
got corrupted…
If I’d do it again, I would configure a single build VM ( nix.buildMachines )
and set nix.maxJobs to 0. That guarantees all builds are executed on this one
machine. Any nix store copying after the
Hi list!
Today I’m excited to announce 2 new images available for running nix on SmartOS:
1) NixOS as lx-branded zone:
Running NixOS in SmartOS’ container native linux-system-call-table-emulated
environment: https://wiki.smartos.org/display/DOC/LX+Branded+Zones
Special thanks to Eelco for
On Mon, 1 Feb 2016 16:18:17 +0100
> "deCube.net | Danny Wilson" <da...@decube.net> wrote:
>
>> 1) NixOS as lx-branded zone:
>>
>> Running NixOS in SmartOS’ container native
>> linux-system-call-table-emulated environment:
>> https://wiki.smarto
Congrats on the release! :-)
When will nixpkgs/master be updated?
(
https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/package-management/nix/default.nix#L91
)
I’d like to release a new SmartOS-nixpkgs image, for the first time with
nixpkgs from the official git repo.
Cheers,
Danny
On 21 nov. 2015, at 01:59, Mathnerd314 wrote:
> On Wed, Nov 18, 2015 at 7:04 AM, Hajo Möller wrote:
> "Documentation should teach, not tell."
> As Rok said, handing somebody who is learning a new language a
> dictionary would not help them learn.
On 18 nov. 2015, at 16:00, Augustin Borsu wrote:
> What about having a documentation field in pkgs that allows for markdown?
> Can't get closer to the code than that.
This.
Documentation that’s seperated from code always rots. Even when you hire
technical writers...
It shouldn’t be difficult, if only...
While adding support for SmartOS I’ve encountered many “autoconf” packages
that claim to be shell agnostic, yet are riddled with BASH-isms. SmartOS comes
with KSH installed in /bin/sh by default, that’s how I noticed.
In order to make some progress and
Hoi Roelof,
My guess is you didn’t read the error message. :-D
Do you know about the nix-env -K option ( —keep-failed). It keeps the failed
build in a folder in /tmp.
There you can see that extracting cjs-2.0.0.tar.gz creates another directory
where all the source files are.
But your patch:
Dolstra eelco.dols...@logicblox.com
Subject: Re: [Nix-dev] Mount /nix/store from NFS during Stage 1 boot
To: nix-dev@lists.science.uu.nl
Message-ID: 528a2bb9.2020...@logicblox.com
Content-Type: text/plain; charset=windows-1252
Hi,
On 18/11/13 14:22, deCube.net | Danny Wilson wrote:
I?m
/2013 04:01 PM, Eelco Dolstra wrote:
Hi,
On 18/11/13 14:22, deCube.net | Danny Wilson wrote:
I?m having 2 issues:
1) DHCP is not queried during stage 1.
BusyBox (used in the initrd) contains a DHCP client called udhcpc that might
be
useful here.
Googling around it looks like NFS
Hi list,
I have another challenge for you :-)
I’m trying to get /nix/store mounted during boot from an NFS server. I
completed nixos-install successfully on this NFS mount.
I’m having 2 issues:
1) DHCP is not queried during stage 1.
- worked around this for now by booting into recovery
and see if it works?
On Fri, Nov 8, 2013 at 5:01 PM, deCube.net | Danny Wilson da...@decube.net
wrote:
I found something, after adding boot.shell_on_fail:
https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/tasks/filesystems/zfs.nix#L63
this imports nothing for me.
If I run
13 matches
Mail list logo