Eelco Dolstra 54664b6fb7 * The write() system call can write less than the requested ... number of bytes, e.g., in case of a signal like SIGSTOP. This caused `nix --dump' to fail sometimes. Note that this bug went unnoticed because the call to `nix --dump' is in a pipeline, and the shell ignores non-zero exit codes from all but the last element in the pipeline. Is there any way to check the result of the initial elements in the pipeline? (In other words, is it at all possible to write reliable shell scripts?)		2003-07-16 21:24:02 +00:00
..
Makefile.am	* Generate the scripts so that we can substitute the prefix	2003-07-13 18:58:03 +00:00
nix-collect-garbage.in	* Get the garbage collector to work again.	2003-07-14 10:45:04 +00:00
nix-profile.sh.in	* Generate the scripts so that we can substitute the prefix	2003-07-13 18:58:03 +00:00
nix-pull.in	* Substitute fixes.	2003-07-16 20:00:51 +00:00
nix-push.in	* The write() system call can write less than the requested	2003-07-16 21:24:02 +00:00
nix-switch.in	* Generate the scripts so that we can substitute the prefix	2003-07-13 18:58:03 +00:00
prebuilts.conf	* The policy-free derivate sharing now *almost* works. :-) For any	2003-07-10 15:11:48 +00:00