[nycphp-talk] Moving a file

David Krings ramons at
Sun Sep 24 10:57:36 EDT 2006

At 08:15 AM 9/24/2006, you wrote:
>David Krings wrote:
> > At 08:56 PM 9/23/2006, you wrote:
> >> David Krings wrote:
> >>> Yes, but using exec to do mv works on the *nix platform.
> >>> How do I know on which OS my script will end up one day.
> >> I think you might have missed my point. Twice.
> >>
> >> I'm not trying to suggest using the mv command (although that should
> >> suffice). Rather, I'm pointing out that it can also be used to rename
> >> things. These operations are the same.
> >>
> >> In other words, you seem to be equating a violation of your semantic
> >> preferences to abuse.
> >>
> >> Chris
> >
> >
> > That is well possible. And apparently I still don't get it. I guess we
> > better leave it at that. Thanks for trying to explain it to me.
> >
> > David K.
>I think the point Chris is trying to make is that 'moving' a file is
>really just changing the name, in general the operations are the same.
>Saying that a.txt is now named b.txt is really the same thing as saying
>that /mydir1/a.txt is now named /mydir2/a.txt.
>When you 'move' a file it is not actually moved unless you move it from
>one drive (whether physical or logical) to another, you're just changing
>the name that it is known by.  This is why 'moving' a file is more or
>less instantaneous.
>On a side note, if you are moving a file from one drive to another the
>operation is not really a 'move', it is first copied to the destination
>drive then deleted from the source drive.

Ach so!! Why didn't he just say so? I guess he did, I just didn't get it. 
It makes sense and after some refreshing in file system fundamentals it is 
pretty obvious. You just have to use simple words and type slowly so that I 
can understand it. ;) This shows that you can teach an old dog new tricks.

David K.

More information about the talk mailing list