Linux-kernel mailing list archive 1998-50,: mv command wierdness. (error in VFS?)

# mv command wierdness. (error in VFS?)

Marcin Dalecki (dalecki@cs.net.pl)
Thu, 17 Dec 1998 16:09:17 +0100

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Trond Myklebust: "Re: NFS client write out corrupted file?"
- Previous message: Daniel Engstrom: "Re: (no subject)"
- Next in thread: Khimenko Victor: "Re: mv command wierdness. (error in VFS?)"
- Reply: Khimenko Victor: "Re: mv command wierdness. (error in VFS?)"
- Reply: Tom Eastep: "Re: mv command wierdness. (error in VFS?)"
- Reply: dalecki: "Re: mv command wierdness. (error in VFS?)"
- Reply: Tom Eastep: "Re: mv command wierdness. (error in VFS?)"
- Reply: Anthony Barbachan: "Re: mv command wierdness. (error in VFS?)"

Just recently I have noticed a quite interresting thing:

I have just moved an backup version of a file in an compilation tree
over the orignal:

mv backup.c~ backup.c

That's nothing special of course. However the interresting thing
was that make didn't notice this at all. In esp. it didnt notice this
as a change to backup.c and didn't therefore any recompilation work.
I would suspect that in this case the modification time of the
inode corresponding to backup.c~ didn't get updated.

Is this correct behaviour?

Marcin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Trond Myklebust: "Re: NFS client write out corrupted file?"
- Previous message: Daniel Engstrom: "Re: (no subject)"
- Next in thread: Khimenko Victor: "Re: mv command wierdness. (error in VFS?)"
- Reply: Khimenko Victor: "Re: mv command wierdness. (error in VFS?)"
- Reply: Tom Eastep: "Re: mv command wierdness. (error in VFS?)"
- Reply: dalecki: "Re: mv command wierdness. (error in VFS?)"
- Reply: Tom Eastep: "Re: mv command wierdness. (error in VFS?)"
- Reply: Anthony Barbachan: "Re: mv command wierdness. (error in VFS?)"