Re: side-effect implementing the mv command

[Eric Blake]

According to Derick Centeno on 1/15/2010 2:58 PM:

Hello Derick,

Apologies for a long delay with no response.  I'm weeding through my
inbox, and saw this thread.

> 
> Recently I executed the following:
> 
> $ sudo mv ./libjavaplugin_oji.so /usr/lib/mozilla/plugins
> 
> Explanation:  I was within the directory where the java plugin existed
> which is: /opt/ibm/java-ppc-60/jre/plugin/ppc/ns7.  The above was
> executed from within the ns7 directory.  The intention was to move *.so
> into the plugins directory.
> 
> The above may have created an unintended side effect; I
> noticed that mv did not erase the original location of *.so but
> created in fact a link from the within the plugins directory to *.so
> within the ns7 directory! I don't have a theory why this happened other
> than to guess that as I did not provide a new filename for 
> the mv command to rename the *.so file mv proceeded to create a link to
> the original *.so file.

I'm not quite sure what you saw or what you are asking.  If this is still
an issue for you, could you post more context, such as some 'ls -l *.so'
listings in both the source and destination directories?  Also, are the
two directories on the same disk, where rename(2) would work, or was it a
cross-device move, where mv(1) has to create the copy before deleting the
original?

-- 
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden

signature.asc
Description: OpenPGP digital signature