Hi,
How would you go about bringing the benefits of Nix to the users of a compute
cluster?
Assume the following cluster: A login node, a file-system node, and a number of
compute nodes. All nodes run on a recent CentOS and are fairly homogeneous. The
fs node holds all user data and some
Hey Wout,
I’m glad :)
And you’ve taught me, too: I’ll correct my statement about the division
operator and credit you.
And yeah, good catch on the TODO! Thanks!
James
On 8 Oct 2014, at 17:50, Wout Mertens wout.mert...@gmail.com wrote:
Hi James,
great reading, I learned a few things!
Hey Colin,
Thanks for the praise. I concentrated a lot on laziness because I think it’s
really critical to understanding how Nix works and is probably unfamiliar to
everyone outside Haskell land.
You might be right about the white lies” approach. It’s a tricky balance to
get right — at one
I think you could do this. You would set it up so the nix server does the
compiles and the grid runs distcc. See the wiki, the raspberry pi page has
explanations about distcc.
Note that only one node can write to nix store at the same time due to the
db.
Another option is to have private nix
Thank you for the detailed answer.
On Friday 10 October 2014 15:32:52 Wout Mertens wrote:
I think you could do this. You would set it up so the nix server does the
compiles and the grid runs distcc. See the wiki, the raspberry pi page has
explanations about distcc.
Oh, I didn't know that this
I also have a working NixOS on a laptop now (The live-usb recognized
this harddrive).
I added the kernelConfig parameter in my configuration.nix file (attached),
but
there are build errors. Specifically, after running nixos-rebuild
switch, it ends with the following output:
GOT:
GOT: #
GOT: #
I also have a working NixOS on a laptop now (The live-usb recognized
this harddrive).
I added the kernelConfig parameter in my configuration.nix file (attached),
but
there are build errors. Specifically, after running nixos-rebuild
switch, it ends with the following output:
GOT:
GOT: #
GOT: #
On Fri, Oct 10, 2014 at 4:34 PM, Andreas Herrmann andreas...@gmx.ch wrote:
Thank you for the detailed answer.
On Friday 10 October 2014 15:32:52 Wout Mertens wrote:
I think you could do this. You would set it up so the nix server does the
compiles and the grid runs distcc. See the wiki,
Hmmm, maybe it's missing other required kernel parameters?
http://cateee.net/lkddb/web-lkddb/SCSI_SAS_ATA.html seems to suggest you
also need to set CONFIG_SCSI_SAS_LIBSAS. I don't know how to run the kernel
configurator on nixos :(
As part of the install, it downloads the nixpkgs expressions to
Good evening,
I've been playing around with NixOS for a while, I have my own NIXPKGS repo
with a custom version of dwm, the window manager.
The problem is I can install my custom dwm build, but when I boot the old
dwm remains(the one in the NixOS original channel) in
On Friday 10 October 2014 17:49:20 Wout Mertens wrote:
On Fri, Oct 10, 2014 at 4:34 PM, Andreas Herrmann andreas...@gmx.ch wrote:
On Friday 10 October 2014 15:32:52 Wout Mertens wrote:
I think you could do this. You would set it up so the nix server does the
compiles and the grid runs
Dash in package names are cool, because they map to the real package name.
However I just found a breaker: bash does not support variables with dash.
$foo-bar or ${foo-bar} or whatever does not work.
Shall we reconsider the use of dash and prefer the underscore instead for
package names?
Hi Javier,
On 10 October 2014 18:39, Javier Aguirre j...@javaguirre.net wrote:
Good evening,
I've been playing around with NixOS for a while, I have my own NIXPKGS repo
with a custom version of dwm, the window manager.
The problem is I can install my custom dwm build, but when I boot the
On 10 October 2014 22:56, Luca Bruno lethalma...@gmail.com wrote:
Dash in package names are cool, because they map to the real package name.
However I just found a breaker: bash does not support variables with dash.
$foo-bar or ${foo-bar} or whatever does not work.
I don't understand. Why/when
derivation {
inherit foo-bar;
buildPhase = ''
use $foo-bar...
'';
}
Apart ${foo-bar}.
On Fri, Oct 10, 2014 at 11:18 PM, Bjørn Forsman bjorn.fors...@gmail.com
wrote:
On 10 October 2014 22:56, Luca Bruno lethalma...@gmail.com wrote:
Dash in package names are cool, because they map to
Hi,
On Tue, Oct 7, 2014 at 10:28 AM, Wout Mertens wout.mert...@gmail.com wrote:
On Tue, Oct 7, 2014 at 4:49 AM, Joseph Joe j...@reed.edu wrote:
I am still a bit confused. I added the following lines to
/etc/nixos/configuration.nix
nixpkgs.config.packageOverrides = pkgs:
{ linux_3_4 =
Wouldn't it make more sense to simply map foo-bar on a derivation to
foo_bar as a shell variable? Are there any significant cases where
this would be problematic?
On 10 October 2014 22:39, Luca Bruno lethalma...@gmail.com wrote:
derivation {
inherit foo-bar;
buildPhase = ''
use
I particularly prefer camelCase!
2014-10-10 19:35 GMT-03:00 Shell Turner cam.t...@gmail.com:
Wouldn't it make more sense to simply map foo-bar on a derivation to
foo_bar as a shell variable? Are there any significant cases where
this would be problematic?
On 10 October 2014 22:39, Luca Bruno
18 matches
Mail list logo
