| Anonymous | Login | Signup for a new account | 11-10-2008 10:40 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000067 | [BusyBox] Documentation | minor | always | 01-27-05 07:10 | 07-31-05 15:34 | ||||
| Reporter | vda | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 1.00 | ||||||
| Summary | 0000067: cp -p produces misleading error message | ||||||||
| Description |
cp -p produces misleading error message: # ln -s symlink1 file1 # ln -s symlink2 file2 # busybox cp -p symlink1 symlink2 unable to remove symlink2: no such file or directory Patch fixes this: # busybox_fixed cp -p symlink1 symlink2 symlink2 exists However, we still differ from coreutils cp, is it worth fixing? # cp -p symlink1 symlink2 # |
||||||||
| Additional Information | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
Notes |
|
|
(0000028) vda 01-27-05 07:12 |
My bad, I shoudn't type commands... ln commands should read: # ln -s file1 symlink1 # ln -s file2 symlink2 |
|
(0000305) pgf 07-19-05 13:47 |
applied in svn 10862 |
| Copyright © 2000 - 2006 Mantis Group |