default since it doesn't seem to have the legal issues of
the Intel 2200 firmware.)
* Firmware loader: don't write in /tmp. Also a hack to quickly
test new firmwares.
* Revert r10105 since the build fails if configuration.nix
is a symlink. Anyway copying configuration.nix does not
necessarily make sense since it can import other expressions,
which would also have to be copied. Perhaps a better
approach would be to write a serialisation of the config
to a file (maybe with builtins.toXML).
svn path=/nixos/trunk/; revision=10127
Did this for Nagios. Soon we can rename upstart-jobs to
services/plugins/whatever (i.e. an Upstart job will just be
one kind of configuration item that a plugin can declare).
svn path=/nixos/trunk/; revision=9778
Just set nix.distributedBuilds to true and nix.buildMachines
to a list of machines that can perform Nix builds via SSH,
and local builds will be forwarded appropriately. So now
any user can say something like
nix-build /etc/nixos/nixpkgs/ --arg system '"powerpc-linux"' -A libxml2
and the build for powerpc-linux will be forwarded to a machine
of that type.
svn path=/nixos/trunk/; revision=9696
for cables being plugged in or unplugged. When this occurs, the
dhclient service is restarted to automatically obtain a new IP
address. This is useful for roaming users (laptops).
svn path=/nixos/trunk/; revision=9124
list of user accounts that the job needs to run. For instance, the
SSH daemon job says:
{ name = "sshd";
uid = (import ../system/ids.nix).uids.sshd;
description = "SSH privilege separation user";
home = "/var/empty";
}
The activation script creates the system users/groups and updates
them as well. So a change in the Nix expression can be realised in
/etc/{group,passwd} by running nixos-rebuild.
svn path=/nixos/trunk/; revision=8846
