On Thu, 4 Oct 2001, Albert D. Cahalan wrote:
> Bob Proulx writes:
>
> > I tested this on both HP-UX, IBM AIX and Linux. HP-UX always
> > preserved the previous timestamps. The same with 2.2.x versions of
> > Linux. AIX was different and preserved the previous timestamp if
> > the .. entry was the same as before but updated the timestamp if .. was
> > different than before. But in the case where no real changes occurred
> > none updated the timestamp. It would be interesting to see what
> > Sun's Solaris and other systems do in those cases. This does not seem
> > like a huge deal. There were differences in the different commercial
> > flavors. But I like to think that we can do better than that.
>
> Compaq Tru64 5 No time change in any case.
>
I tested it on Solaris 2.7 . No time stamp change in any of these two
cases ->
mv tmp tmp1
mv tmp ..
In the 1st case there is no justification for time change bcos even the ..
link inside the dir has not changed. In the 2nd case, there may be some
justification but it will lead to a lot of confusion. When there is
nothing to gain and something to lose why make such a change from
traditional behavior ?
thanks
- Nil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Oct 07 2001 - 21:00:33 EST