include the closure of /bin/sh. Otherwise all builders that call
/bin/sh will fail when using the new chroot implementation, which
only bind-mounts the inputs of a build rather than the whole Nix
store.
svn path=/nixos/trunk/; revision=13640
USB, some SCSI controllers) in the initrd for mounting the CD.
* Add nix-hardware-scan to the system.
* Upstart: don't use the -v flag.
* Include the NixOS version in the ISO image filename.
* Include testdisk and ms-sys in the CD.
* Some bugfixes in the installer.
svn path=/nixos/trunk/; revision=10556
thanks to unionfs. For instance, nix-env and nixos-rebuild work.
The tricky part was to build a Nix database (in the tmpfs/unionfs)
which is now necessary to prevent store paths on the CD from being
deleted right away because they otherwise wouldn't be valid.
* nixos-install: use the /etc/nixos/configuration.nix from the target
file system (don't copy it anymore). Since the user is supposed to
mount the target file system on /mnt anyway, we may as well require
that configuration.nix is placed in /mnt/etc/nixos. This also makes
upgrading / reinstalling much easier, since it will automatically
use the right configuration.nix.
svn path=/nixos/trunk/; revision=10399
appear writable (though all writes go to a tmpfs). This allows you
to run Nix operations on the Live CD. However, we're not quite
there yet since the CD doesn't have a valid Nix database. So for
instance a garbage collect will cause everything to be deleted,
hanging the system.
svn path=/nixos/trunk/; revision=10276
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
as regular files instead of symlinks to the store.
* Sudo configuration, enabled through security.sudo.enable (on by
default). The contents of the sudoers file is specified in
security.sudo.configFile. The default sudoers file allows members
of the new "wheel" group to run any command.
svn path=/nixos/trunk/; revision=9138
CD-ROM drive, etc.) to the logged in user. Woohoo! Finally, no
more chown /dev/snd/*.
* Get rid of spurious error messages about pam_ldap when we're not
using LDAP.
svn path=/nixos/trunk/; revision=8861
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
error.
* Put the top-level system config on the CD, otherwise root doesn't
get a working login shell on the CD (and the system PATH is broken
as well).
svn path=/nixos/trunk/; revision=8658
accounts. Obviously we cannot put the store path of bash in
/etc/passwd since it's too fragile (it could be garbage collected),
hence this indirection.
svn path=/nixos/trunk/; revision=8383
configuration, and use it as a garbage collection root to prevent
the current configuration from being GC'ed (which was previously
possible if the configuration was activated using "nixos-rebuild
test", or if the configuration's generation symlink had been removed
from the system profile).
This isn't quite right yet due to a layering problem:
activate-configuration.sh doesn't know the top-level store path of
the configuration.
svn path=/nixos/trunk/; revision=8379
* Automatically set up a per-user profile in
/nix/var/nix/profiles/per-user/$USER.
* Initialise ~/.nix-defexpr and ~/.nix-profile.
svn path=/nixos/trunk/; revision=7680
