On Mon, 20 Oct 2014 09:50:15 +0200
Eelco Dolstra eelco.dols...@logicblox.com wrote:
The basic idea is this: To build a system, you use a standard
function from Nixpkgs and pass it a configuration module. The
result is a derivation that represents a complete self-contained
system.
How
Hi,
On 22/10/14 11:55, Ertugrul Söylemez wrote:
How would I refer to multiple systems with different configurations from
within a Nix expression? The change would allow this:
{ system1 = import nixos/build-system.nix module1;
system2 = import nixos/build-system.nix module2;
Have a look at
https://github.com/bluescreen303/bluenix/blob/master/jobs.nix
It's overly complicated and I'm gonna simplify it, but it does build
multiple systems.
Ertugrul Söylemez ert...@gmx.de writes:
On Mon, 20 Oct 2014 09:50:15 +0200
Eelco Dolstra eelco.dols...@logicblox.com wrote:
On Mon, Oct 20, 2014 at 9:50 AM, Eelco Dolstra eelco.dols...@logicblox.com
wrote:
I don't think nixos-install is that complex. Almost all of the
initialisation it
does in the target file system is to make nix-build work in the chroot. The
NixOS initialisation is done by the activation script.
What I find missing is *creation* of the actual partitions, file systems
etc. integrated into the system startup.
This can be accomplished as an idempotent initialization and also be
turned off by default (require boot flag).
Did you see
On Tue, Oct 21, 2014 at 10:27 AM, Domen Kožar do...@dev.si wrote:
What I find missing is *creation* of the actual partitions, file systems
etc. integrated into the system startup.
This can be accomplished as an idempotent initialization and also be
turned off by default (require boot flag).
Can that nixpart be converted to something that uses nix-exec? It looks
useful since I've been doing the initial setup with an initial boot script.
On 21/10/2014 7:27 PM, Domen Kožar do...@dev.si wrote:
What I find missing is *creation* of the actual partitions, file systems
etc. integrated
Hi,
On 16/10/14 13:00, Ertugrul Söylemez wrote:
The basic idea is this: To build a system, you use a standard function
from Nixpkgs and pass it a configuration module. The result is a
derivation that represents a complete self-contained system.
How does that differ from how NixOS is
Hi Ertugrul,
On Thu, Oct 16, 2014 at 1:00 PM, Ertugrul Söylemez ert...@gmx.de wrote:
Proposal
The basic idea is this: To build a system, you use a standard function
from Nixpkgs and pass it a configuration module. The result is a
derivation that represents a complete
Hi there fellow Nixers,
I'd like to propose an installation standard that would make it a lot
easier and more reliable to deploy NixOS to virtual and container-based
systems, including qemu, LXC and Docker. As a nice side effect it would
greatly simplify most NixOS tools, including nixos-install
10 matches
Mail list logo
