Andreas
> I wrote a program to generate a script containing multiple mv commands to
> rename files, but when I ran it, mv kept says x file and y file are the
> same. Some, I guess it renamed, but the bulk of my files are missing.
I am guessing that you have a bug in your program that is producing a
bug in your script that is renaming files. I really doubt this is a
bug in mv. And the filesystem is part of the operating system.
Although possible it would be most unlikely to trigger a bug in both
mv and the filesystem at the same time. Again I doubt there is a
problem there either.
You might try replacing all of the 'mv' commands with 'echo mv' and
then tracing the results. You might find a logical error in your
script by that method. It is also a safer way to develop scripts
since no actual actions are taken. In this case you are twice removed
since you have a program which is writing a second program script.
That leaves twice as much room for problems to sneak in.
> Please find attached both the script to rename the files and a tree command
> done on the root directory.
>
> Content-Type: application/x-zip-compressed;
> name="roottree.zip"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;
> filename="roottree.zip"
>
> UEsDBBQAAAAIACCOMyhgF53BmdoFAAqrLgAMAAAAcm9vdHRyZWUudHJlxJ1Lc+NYkqX38ytyObOg
> ku73RW3arLqyulvWHVNlyrbp2lWCJCQxxQdEgBIlG5vfPqAUCvq5fhTKxWROWZUV/T7PcQL3gl8I
> wMV/+9+TyQ/z1fa//e8ffvjh9LnZL+7OQQ+fL/qhGVaLc9FhszpONqvtatOsz6VP9z9M/umH2/H/
Sending zip attachments is really not a very friendly way of sending
in a bug reports. I can't vouch for the maintainers of fileutils but
I personally work on UNIX machines and I do not have PC zip style of
file archive programs available to me. As you can see it comes out
bit packed and unreadable. It is friendlier to include scripts such
as that in the message, may I suggest at the bottom of your mail
message, for all to read plainly. However in your case I believe your
script is too big.
Bug reports are most effective if you can reduce the scope of the
problem to small examples. The best reports strive to illustrate the
problem with only a few lines of text. I fear that your script can
only be quite large since it occupies 521kb of space when compressed.
Also, the mailing list is replicated to many individuals on the
network. Mailings which are large frequently cannot make it them.
Less than 100kb is generally the rule for network mail.
Much of the available software on the net is developed and maintained
by volunteers who donate their time to this activity. Therefore it is
critical to reduce the size of the problem as much as possible.
Otherwise the maintainers simply will be overwhelmed by the problem
and will be unable to help. If you could reduce the problem from
being "something is wrong with my script" to "here is the operation
that fails" it would be most effective.
Bob Proulx
A side party which reads on the bug list.
