packages that we need rather than just /var/run/current-system/sw.
This ensures consistency when upgrading a system (e.g. you don't end
up with a mix of KDE versions at runtime). This partially reverts
r14148 (in particular the update-mime-database hack in the
systemPath post-build).
svn path=/nixos/trunk/; revision=14887
the advantage that KDE applications work when logging in via ssh,
and that you don't need to logout to have KDE upgrades take effect.
On the downside, since the various KDE packages and shared-mime-info
all have their own MIME databases, if we put them in one symlink
tree (systemPath), we need to rerun update-mime-database on the
symlink tree. Also, systemPath is getting very large.
svn path=/nixos/trunk/; revision=14148
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
This patch makes the `at' commands setuid `atd' (instead of `root')
and fixes the ownership of `/etc/at/at.deny'.
svn path=/nixos/trunk/; revision=13515
This makes the initrd a few megabytes smaller.
* Use run-init from klibc to delete everything in the initrd ramfs
prior to switching to the real root FS.
* Removed the stage2Init argument.
svn path=/nixos/trunk/; revision=12544
file systems. The main advantage is that this allows mounting of
such file systems from the `filesystems' configuration option at
boot time, e.g.
fileSystems = [
...
{ mountPoint = "/windows";
device = "/dev/disk/by-uuid/9EA4B22EA4B208B3";
fsType = "ntfs-3g";
}
];
The list of file system helpers should of course be made
configurable.
svn path=/nixos/trunk/; revision=12516
automatic copying of build results from remote Nix stores work
more-or-less automatically. All you have to do is mount the remote
FS on a subdirectory of /var/run/nix/remote-stores, e.g.
$ sshfs remote_machine:/ /var/run/nix/remote-stores/foo
* Set $NIXPKGS_ALL.
svn path=/nixos/trunk/; revision=12411
description) to allow all kernel-related packages to be overriden
easily. For instance, you can now say in configuration.nix
boot = {
kernelPackages = pkgs: pkgs.kernelPackages_2_6_25;
};
to use Linux 2.6.25.x. Externel kernel module packages (like
the NVIDIA drivers) appropriate for this kernel will then be used
automatically.
svn path=/nixos/trunk/; revision=11880
add `/var/run/current-system/sw/lib' to `LD_LIBRARY_PATH'. This should allow
NSS modules to be added and taken into account by applications without
the need to reboot.
svn path=/nixos/trunk/; revision=11290
Currently, the solution is a bit hackish since running applications
will not work after a `nixos-rebuild' because `libnss_mdns' is not
in their `LD_LIBRARY_PATH'.
svn path=/nixos/trunk/; revision=11162
This is really a hack since programs not known to `system.nix' will not be in the path
of `activate-configuration', which consequently creates empty `.real' files under
`/var/setuid-wrappers'. I don't know what the best way to address this is: let admins
write `.real' files by hand? Add a `setuidPackages' attribute, listing the names of
packages that contain the binaries listed in `setuidPrograms'?
svn path=/nixos/trunk/; revision=11153
