Searched hist:118367 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-9.3-release/tools/regression/bin/mv/ | ||
| H A D | Makefile | 174657 Sun Dec 16 06:11:38 MST 2007 dds Regression tests for upcoming makeup of mv. Case 20 corresponds to PR bin/118367. |
| H A D | regress.t | 174657 Sun Dec 16 06:11:38 MST 2007 dds Regression tests for upcoming makeup of mv. Case 20 corresponds to PR bin/118367. |
| H A D | regress.sh | 174657 Sun Dec 16 06:11:38 MST 2007 dds Regression tests for upcoming makeup of mv. Case 20 corresponds to PR bin/118367. |
| /freebsd-9.3-release/usr.bin/truss/ | ||
| H A D | ia64-fbsd.c | diff 118367 Sat Aug 02 20:29:10 MDT 2003 marcel Fix truss on ia64. The syscall arguments are written to the trap frame, occupying scratch registers r16 and up. We don't have to save any scratch registers for syscalls, so we have plenty of room there. Consequently, when we fetch the registers from the process, we automaticly have all the arguments and don't need to read them seperately. |
| /freebsd-9.3-release/bin/mv/ | ||
| H A D | mv.c | diff 174664 Sun Dec 16 12:14:31 MST 2007 dds When moving a directory across devices to a place where a directory with the same name exists, delete that directory first, before performing the copy. This ensures that mv(1) across devices follows the semantics of rename(2), as required by POSIX. This change could introduce the potential of data loss, even if the copy fails, violating the atomicity properties of rename(2). This is (mostly) mitigated by first renaming the destination and obliterating it only after a succesfull copy. The above logic also led to the introduction of code that will cleanup the results of a partial copy, if a cross-device copy fails. PR: bin/118367 MFC after: 1 month |
Completed in 55 milliseconds