If I set virtualisation.nova.enableSingleNode = true; in configuration.nix,
then nixos-rebuild build fails as follows:
building Nix...
building the system configuration...
these derivations will be built:
/nix/store/00yyan1p9zgnw1mj7q8v1ga1pp3hx9lr-nixos-13.07pre4944_6246d75-1f2ecd0.drv
Thank you. I tried prefetching it, but it makes no difference. The result of
prefetching goes in different store location to the one it is looking for.
Perhaps the package has the wrong hash for python-novaclient-2012.1.tar.gz ?
What is the process for updating the package ?
$ nix-prefetch-url
I am trying to install nilfs-utils.
According to the wiki ( http://nixos.org/wiki/Install/remove_software ), I can
install a package by 'nix-env -i package for one user, or I can install it
for all users by adding it to environment.systemPackages . The second way does
not work for me for
I would like to be able to boot from nixos installation media, then do
automated partitioning, LVM setup and filesystem creation, then let nixops do
the rest. What is the best way to automate partitioning, LVM setup and
filesystem creation ? I wrote a shell script to do this (just for one disk, so
On further reflection, I think I see how it almost might work using
derivations. Assume it is possible to have a derivation that is only
considered to be built (hand-waving part here ...) if the required filesystem
exists. Then that derivation depends on another that is only considered to be
aszlig writes:
So you could use it, but it's not yet ready for being part of the
nixos installation procedure.
Here is the repository: https://github.com/aszlig/nixpart
And it is in nixpkgs as well.
Thank you very much. I have had a play, and it looks very helpful.
There is one small
The nixos bind package* does not seem to include any root hints, or any way to
configure it to use them. Is it only intended to be used in a forwarding setup?
I would like to configure a stand-alone DNS server to be deployed by nixops...
For root hints, the bind config should include a zone like
Peter Simons writes:
The nixos bind package* does not seem to include any root hints, or
any way to configure it to use them. Is it only intended to be used
in a forwarding setup?
my impression is that generating a fully fledged BIND config within
NixOS is overkill, i.e. there
Tim Barbour writes:
I have modified the bind package to add a rootHints option.
For backwards compatibility, I have the rootHints option defaulting to false,
but one could reasonably argue that it should default to true.
At least, when there are no forwarders, it should provide root
Peter Simons writes:
personally, I think it's okay to use fetchurl because it guarantees that
we notice updates in the cache file.
How will we notice ? When bind fails to install ?
The named.cache file does contain a
version number (i.e. a date stamp), so can reliably detect that a
Tim Barbour writes:
The DNS HOWTO (http://www.tldp.org/HOWTO/DNS-HOWTO-8.html) recommends using
dig to get the root hints. Since dig is included with bind, it should be
available by the time preStart runs, so I think we could use dig in preStart
to fetch the root hints each time preStart
Tim Barbour writes:
The DNS HOWTO (http://www.tldp.org/HOWTO/DNS-HOWTO-8.html) recommends using
dig to get the root hints. Since dig is included with bind, it should be
available by the time preStart runs, so I think we could use dig in preStart
to fetch the root hints each time preStart
Tim Barbour writes:
Now I am reading elsewhere
http://grokbase.com/t/centos/centos/132e099w4y/bind-built-in-root-hints
that modern bind does not need the root hints file, because it is capable of
finding the information itself. But it may need root.key for DNSSEC.
Indeed, it works
I understand that one advantage of nixops is being able to deploy a set of
services atomically, possibly including data that is needed by the services.
What is the recommended way to get nixops to deploy some data for a service at
the same time it deploys the service ?
I would like to be able to
Jeremy Hughes writes:
Never mind. Got it now. Bizarre.
You might be interested to know that the image in question does not work with
RPis that use the Hynix chipset (in some later RPis), as I discovered when
trying to use it. I have made a modified image that does work with the Hynix
chipset,
It seems that some versions of haskellPackages define ghcWithPackages, and
others do not.
I have been following the approach described at
https://nixos.org/wiki/Haskell#Using_cabal_in_the_direct_installation_scenario
under the heading Local use via Nixpkgs config.
If I use
This message somehow did not make it to the list, so I am sending it again.
---BeginMessage---
Mateusz Kowalczyk writes:
[...]
haskellPackages_ghc783.ghcWithPackages should work just fine, I just
tried it myself. Considering haskellPackages.ghcWithPackages gives you
7.6.3, it simply makes
This message somehow did not make it to the list, so I am sending it again:
Mateusz Kowalczyk writes:
[...]
haskellPackages_ghc783.ghcWithPackages should work just fine, I just
tried it myself. Considering haskellPackages.ghcWithPackages gives you
7.6.3, it simply makes me think that you
Starting from the installation image on the Wiki, I managed to get my
Raspberry Pi Model B up-to-date WRT nixos-13.10 . I then changed the channel
to nixos-14.04, updated the channel, and ran nixos-rebuild build, resulting
in the following output:
building Nix...
error: user-thrown exception: the
vcu...@gmail.com writes:
That's trivial. armv6l-linux was not in the all platform set. I
fixed that in master 7323d5e12 and 14.04 5f2f1b05e.
Thank you. I am still getting the same error, I think because your change has
not reached the
14.04 channel yet - presumably it is still working its
Tim Barbour writes:
vcu...@gmail.com writes:
That's trivial. armv6l-linux was not in the all platform set. I
fixed that in master 7323d5e12 and 14.04 5f2f1b05e.
Thank you. I am still getting the same error, I think because your change
has not reached the
14.04 channel yet
NILFS2 is a log-structured filesystem which is now in the Linux kernel source
tree, and supported by GRUB2. It should appeal to NixOS users because it
avoids destructive update (changing a file produces a new version of the
file).
I have installed NixOS with all filesystems on NILFS2, but
I would like to set up a nix build server, particularly for use with nixops.
Is there a definitive document about how to do this, including cross-platform
builds (e.g. ARM) ?
Can it be done declaratively, or does one need to set environment variables ?
So far I have found the following
Tim Barbour writes:
I would like to set up a nix build server, particularly for use with nixops.
Is there a definitive document about how to do this, including cross-platform
builds (e.g. ARM) ?
Well, I got it working (no cross-build yet) using nix.buildMachines as
described here:
http
aszlig writes:
On Tue, Sep 30, 2014 at 09:08:41PM +1000, Tim Barbour wrote:
The most serious problem is that NILFS2 needs to update /etc/mtab when
mounting a filesystem, so that it can store information about the
[...]
I don't have any experience with NILFS2 yet, but you might want
Nicolas Pierron writes:
Looking at the details of NILFS2, I saw that it does a linear search
within directories. This is far from ideal for the /nix/store as this
directory is HUGE. This might have a noticeable cost at the start-up
of a computer / programs.
Ouch! I missed that bit. I
Wout Mertens writes:
FWIW, btrfs and ZFS also do non destructive writes, they're Copy on Write.
As a bonus you get unlimited instant snapshots and lots of other wonderful
things.
I prefer btrfs as it has more of a desktop focus and feature set as well as
being in the kernel, but
Wout Mertens writes:
On Mon, Oct 6, 2014 at 8:04 AM, Tim Barbour t...@categorical.net wrote:
One nice property of NILFS is that every write results in a new checkpoint,
which makes it very cheap to check whether a filesystem has been modified
(other than via low-level disk-editing
I would also like to be able to run Nixos on ARM. I have three Raspberry Pis
(indeed an aging platform), and an MK802IV (much more powerful that the
Raspberry Pi, but a similar price).
I also would prefer to avoid x86 PC hardware in the future, the problem being
the power consumption (100-200W
At Mon, 26 Jan 2015 09:29:21 +,
Marc Weber wrote:
Is anybody interested in these?
https://github.com/MarcWeber/nixpkgs/commit/1bb2f95c9ab792422a89c11e1f629dcff2cbf322
marc-nixos/postfix
Yes, please.
Tim
___
nix-dev mailing list
At Mon, 2 Feb 2015 15:45:31 +,
Daniel Shahaf wrote:
[ tl;dr: NixOS should sign any code that makes it into users' systems. ]
[...]
I would therefore suggest that NixOS starts signing any code that gets
installed on users' machines, and that Nix should, by default, verify
signature against
At Sat, 31 Jan 2015 13:22:09 +0100,
Ertugrul Söylemez wrote:
[...]
I have actually experimented with using Haskell (and a few other FP
languages) as a substitute for shells.
[...]
You might be interested why Curry didn't work. Simple: I couldn't figure
out how to write a program. Actually
On Sat, 26 Dec 2015 09:07:38 +,
Wout Mertens wrote:
> If web-of-trust is the best solution, and the only blocker is build
> reproducability, how about trying to classify
> build differences?
>
> Each of the differences will have a reason, and either we can fix the build
> to be
I agree there is no conflict between your proposal and my suggestion.
The reason I mentioned it is that I do not like the idea of relying on
a single trusted party for security (to whic your proposal makes no
difference, because the trusted party will control all build
machines). If someone (use
What is the recommended way to run Eclipse on Nixos ?
When I install a Nixos eclipse package (e.g. eclipse-cpp), I find that it
cannot install plugins in the normal way, because the plugin installation
process tries to modify the Nix store.
I would like to be able to run Eclipse with i.a. the
I have some STM32 boards (e.g. Maple Mini) to play with. I am not trying to
port Nixos to them, because they are not really powerful enough to run Linux;
instead I plan to run ChibiOS/RT on them.
I would appreciate suggestions as to a good way to setup an STM32
cross-development environment on
On Tue, 06 Sep 2016 21:03:45 +1000,
Aloïs Cochard wrote:
> I'm currently trying to upgrade my system to the latest unstable, but I keep
> running into errors like:
>
> unpacking source archive
> /nix/store/calj3b4gz6vq99d6wxc1760q66w101k3o147jen_linuxufrII_0290.zip
> do not know how to unpack
Thank you Philip and Alexey.
I have tried gcc-arm-embedded as you suggested, and had no trouble building
the ChibiOS UART demo for a Maple Mini board (I did have to change GPIOC_LED
to GPIOB_LED; presumably the demo was written for a board with more LEDs).
$ file build/ch.elf
build/ch.elf: ELF
On Fri, 26 Aug 2016 22:23:46 +1000,
Alexey Shmalko wrote:
> [...]
> Resources you may check out:
> - my kernel for STM32F4Discovery which is 100% Rust
> (https://github.com/rasendubi/bkernel).
Interesting. How large is your kernel ? Would it fit in a small STM32 (128k
flash, 20k RAM) ?
Tim
On Sat, 27 Aug 2016 03:28:49 +1000,
Alexey Shmalko wrote:
>
> I usually produce raw binary file first:
>
> $ arm-none-eabi-objcopy -O binary build/ch.elf ch.bin
>
> and then flash that with openocd:
>
> $ openocd -f openocd.cfg
> poll
> reset halt
> flash probe 0
> flash write_image erase
40 matches
Mail list logo
