David, that modification worked and set the hard drive parameter. Thanks!
I now would like to create an image file from the configuration.
I issued the command:
$ export NIX_PATH=$NIXREPOS
But, the command:
$ nix-build -A iso_graphical.x86_64-linux $NIXREPOS/nixos/release.nix
returns with the
There was a typo, I think. It should be:
/nix/store/*/nixos/nixos/release.nix
I also usually find this directory using ~/.nix-defepr
Also, I think that using nix-build with this release.nix is not enough,
you should copy it and make there some changes to embed your kernel
configuration. Because
Hi,
On Sat, Oct 11, 2014 at 8:20 AM, Joseph Joe j...@reed.edu wrote:
I now would like to create an image file from the configuration.
I issued the command:
$ export NIX_PATH=$NIXREPOS
check both variables
$ echo $NIX_PATH
/nix/var/nix/profiles/per-user/root/channels/nixos
You could also set
PRoot has given me the easiest and nicest Nix install in user land
*EVER*. PRoot tricks Linux in adding a /nix/store mounted on $HOME
somewhere.
I have updated the wiki:
https://nixos.org/wiki/How_to_install_nix_in_home_%28on_another_distribution%29
Finally a Nix that is happy in $HOME, and
Hi,
On Sat, Oct 11, 2014 at 12:09 PM, Pjotr Prins pjotr.publi...@thebird.nl wrote:
PRoot has given me the easiest and nicest Nix install in user land
*EVER*. PRoot tricks Linux in adding a /nix/store mounted on $HOME
somewhere.
I have updated the wiki:
On Sat, Oct 11, 2014 at 12:41:40PM +0300, Paul Colomiets wrote:
Hm, that's nice. But given the PRoot works using ptrace, it's probably
very slow, right?
Good point. I'll need to see what the impact is on individual
applications.
Also I think it's nicer and easier to setup similar thing using
In my experience, the majority of scripts in nixpkgs either put
dependend packages in buildInputs or interpolate them directly into
scripts; adding a package directly as an env var is rare. Why is this
worth giving up the superior readability and fidelity to actual package
name provided by dashes?
On 10/11/2014 02:55 PM, Shea Levy wrote:
In my experience, the majority of scripts in nixpkgs either put
dependend packages in buildInputs or interpolate them directly into
scripts; adding a package directly as an env var is rare. Why is this
worth giving up the superior readability and fidelity
On Sat, Oct 11, 2014 at 03:09:37PM +0200, Vladimír Čunát wrote:
On 10/11/2014 02:55 PM, Shea Levy wrote:
In my experience, the majority of scripts in nixpkgs either put
dependend packages in buildInputs or interpolate them directly into
scripts; adding a package directly as an env var is rare.
On 10/11/2014 03:16 PM, Shea Levy wrote:
If you do { inherit gcc; }, then $gcc just points to gcc's out path at
build time.
Yes, I know, but I did not find that much useful yet. As you point out,
packages are typically put into *buildInputs or used on nix-level (in
strings). The probability
As far as I know, dwm is configured by source-patching some files. It
doesn't use anything like '~/.dwmrc' files, it really modifies C
source code!
Well, we can use some derivation like patches = [ patch1 patch2 ];
2014-10-10 18:00 GMT-03:00 Bjørn Forsman bjorn.fors...@gmail.com:
Hi Javier,
On Tuesday, September 30, 2014 13:51:56 Tobias Pflug wrote:
i was wondering if anyone on this list has any experiences running nixos on
the latest macbook air. I googled and searched the nixos wiki for some info
on this but could not find anything. I just wonder if there are problems
that
Thanks for the suggestion, James. I just installed a completely clean
system using nixos-unstable plus my patches, and found one error.
Will commit the fix that along with the comment that it worked based
off of the latest nixos-unstable channel.
On Sat, Oct 4, 2014 at 11:57 AM, James Cook
On Fri, Oct 10, 2014 at 7:06 PM, Andreas Herrmann andreas...@gmx.ch wrote:
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.
14 matches
Mail list logo
