Jim Meyering wrote: > Bas van Schaik <[EMAIL PROTECTED]> wrote: > >> Package: coreutils >> Version: 5.97-5 >> Severity: normal >> >> When using >> >>> cp -lar srcdir/* targetdir >>> >> on a srcdir containing files (no matter how deep in srcdir) with spaces in >> their filenames, cp complains: >> >>> cp: cannot create hard link `targetdir/(...)/filename' to >>> `targetdir/(...)/filename': No such file or directory >>> > > Thanks for the report. > I am unable to reproduce that. > > Please try to create a small test case that demonstrates the problem. > For example, here's one of the things I've just tried: > > $ rm -rf a x; mkdir a x; touch 'a/b ' 'a/d e'; /bin/cp --verbose -lar a/* x > `a/b ' -> `x/b ' > `a/d e' -> `x/d e' > Hmmm... This indeed works. Weird. Check my directory listing which contains the files causing problems: > # ls | grep 17256 > 17256 > 17256
A fsck pointed out that the filesystem is consistent, so I assumed there was a space at the end of one of those filenames (I saw that once before). However, I can't discover the difference in the filename. Maybe someone else can suggest a method to find the difference? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
