EC2 instances don't have a console, so it's pointless to start
emergency mode if a mount fails. (This happened to me with an
encrypted filesystem where the key wasn't sent on time using "charon
send-keys".) Better to cross fingers and continue booting.
were obtained from the NixOS channel. "nixos-install" copies this
to the installed system as well.
* In the installation CD, set GC_INITIAL_HEAP_SIZE to a low value for
the benefit of memory-constrained environments.
svn path=/nixos/trunk/; revision=33887
currently activated NixOS. This is "0.1pre-svn" when built from a
SVN tree, but contains the actual revision when installed from the
NixOS channel or from the ISO.
svn path=/nixos/trunk/; revision=33730
* Load scsi_wait_scan after all other kernel modules to ensure that
all SCSI device nodes have been created.
* Increase the timeout for the appearance of the root device to 20
seconds.
* Do a "udevadm settle" just after the root device has appeared to
make sure that udev isn't accessing the device anymore (hopefully).
On EC2 (Xen), I've seen fsck on the root fail randomly with "device
in use" errors.
svn path=/nixos/trunk/; revision=33650
You can now set the forwardX11 config option for the ssh client and server separately.
For server, the option means "allow clients to request X11 forwarding".
For client, the option means "request X11 forwarding by default on all connections".
I don't think it made sense to couple them. I might not even run the server on some machines.
Also, I ssh to a lot of machines, and rarely want X11 forwarding. The times I want it,
I use the -X/-Y option, or set it in my ~/.ssh/config.
I also decoupled the 'XAuthLocation' logic from forwardX11.
For my case where ssh client doesn't want forwarding by default, it still wants to set the path for the cases I do need it.
As this flag is the one that pulls in X11 dependencies, I changed the minimal profile and the no-x-libs config to check that instead now.
svn path=/nixos/trunk/; revision=33407
reiserfs now have separate modules that are conditional on
boot.supportedFilesystems and boot.initrd.supportedFilesystems.
By default, these include the filesystems specified in the fsType
attribute in fileSystems. Ext2/3/4 support is currently
unconditional.
Also unbreak the installer test (http://hydra.nixos.org/build/2272302).
svn path=/nixos/trunk/; revision=32954
just does what it says (enable a "graphical" configuration).
* Enable KDM in the graphical CD. The "auto" display manager doesn't
properly handle shutdowns etc.
svn path=/nixos/trunk/; revision=30331
all-hardware.nix. This allows base.nix (which should probably be
renamed to something more descriptive) to be reused without getting
the hardware configuration of the installation CD.
svn path=/nixos/trunk/; revision=30327
problem in stage 1 should cause a panic. (Actually, the latter
should probably kill the instance since we can't repair it
anyway...)
svn path=/nixos/trunk/; revision=30215
The sshfsFuse package -- which is part of the system profile already -- doesn't
work without fuse. It tries to run /var/setuid-wrappers/fusermount, which then
can't find fusermount. Adding fuse to the system profile remedies this problem.
svn path=/nixos/trunk/; revision=27754
xulrunner is a big package (> 105 MiB); 2) it breaks the CD build
(http://hydra.nixos.org/build/1057258); 3) currently it doesn't do
much yet.
Note that if we do add it, we might as well add Firefox to the CD
(since it's only a few MiB more on top of xulrunner).
svn path=/nixos/trunk/; revision=26993
This has the advantage that it doesn't depend on networking being
up.
* Move common QEMU/KVM guest configuration to profiles/qemu-guest.nix.
svn path=/nixos/trunk/; revision=26421
