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
..
nar.fix	* Get `nix-push' working again. It now uses Nix/Fix to create Nix	2003-07-10 13:41:28 +00:00
nar.sh	* The write() system call can write less than the requested	2003-07-16 21:24:02 +00:00
unnar.fix	* The policy-free derivate sharing now *almost* works. :-) For any	2003-07-10 15:11:48 +00:00
unnar.sh	* Doh!	2003-07-16 20:49:59 +00:00