Martin Grosup wrote:
> Hello. Sorry for my bad english. I will try my best:
Thank you for that very detailed report. Details such as you provided
are most appreciated.
However, what you are seeing is not a bug. You are seeing behavior by
the shell trying to help you but instead is only confusin
>> crikey% ls -lR tmp/test_18
>> tmp/test_18:
>> total 4
>> drwxr-xr-x2 layerfi 4096 Nov 21 11:29 bar/
>> lrwxrwxrwx1 layerfi 3 Nov 21 11:29 foo -> bar/
>>
>> tmp/test_18/bar:
>> total 4
>> -rw-r--r--1 layerfi 51 Nov 21 11:29 foo_18
>>
>>
>I have tried this:
>
> export POSIXLY_CORRECT=1
> mkdir mv_test
> cd mv_test
> mkdir a c
> ln -s a b
> mv -v b/ c
> alias mv
> which mv
>
> I expected, as is written, that the directory a will be moved into
> directory c (the symbolic link b to d
> export POSIXLY_CORRECT=1
> mkdir mv_test
> cd mv_test
> mkdir a c
> ln -s a b
> mv -v b/ c
> alias mv
> which mv
>
> I expected, as is written, that the directory a will be moved into
> directory c (the symbolic link b to directory a will be derefer
Thank you for the report!
The way mv works depends on the behavior of `rename' (per POSIX),
and it looks like rename's behavior has changed in Linux within
the last few kernel releases.
When I wrote the section you quote below, mv did indeed
work as described when using the latest version of Linux
> I don't know if this has been reported before, s
Unfortunately it is a popular one. :-) Thanks for the report anyway.
It might not have been.
> [root@kcasep18 local]# mv include/php/ ~/include.php.old
> mv: basename.c:67: base_name: Assertion `all_slashes || *(p - 1) != '/''
Please u
Michael Mess <[EMAIL PROTECTED]> wrote:
| I think, I found a bug in the mv-command:
|
| :/ide/altrechner/test/bug>dir
| total 0
| :/ide/altrechner/test/bug>mkdir a
| :/ide/altrechner/test/bug>touch b
| :/ide/altrechner/test/bug>mkdir test
| :/ide/altrechner/test/bug>mv * test/
| mv: test/test/a: w
ing <[EMAIL PROTECTED]>
> To: Mark Laws <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Subject: Re: bug in mv
>
> This time I actually read your entire message :-)
> That bug is fixed in the latest test release.
> ftp://al
This time I actually read your entire message :-)
That bug is fixed in the latest test release.
ftp://alpha.gnu.org/gnu/fetish/fileutils-4.0.41.tar.gz
With that, I get this:
$ mv bla* blah_stuff
mv: cannot move `blah_stuff' to a subdirectory of itself, `blah_stuff/blah_stuff'
[Exit 1]
Ma
n Genesis Evangelion
On 4 Mar 2001, Jim Meyering wrote:
> Date: 04 Mar 2001 19:40:24 +0100
> From: Jim Meyering <[EMAIL PROTECTED]>
> To: Mark Laws <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Subject: Re: bug in mv
>
> Mark Law
Mark Laws <[EMAIL PROTECTED]> wrote:
| $ mkdir blah_stuff
| $ mkdir blah_a
| $ mv blah_* blah_stuff
| mv: Segmentation fault
|
| The directory is successfully moved, but I thought I should report the bug
| anyway. I'm running Linux 2.2.18 with glibc-2.1.3.
Thanks for the report.
What version of m
Thanks for the reports.
Igor Bukanov <[EMAIL PROTECTED]> wrote:
| When I use mv to rename sym link to directory via:
|
| mv sym_link/ new_name
|
| mv actually rename the directory link point to. In some situation I also got:
That is known behavior -- it's not expected to change. See below.
Lobb
12 matches
Mail list logo
