[comp.sys.amiga] Archive bit behavior - possible bug?

louie@trantor.umd.edu (Louis A. Mamakos) (03/28/88)

I noticed some interesting behavior in the Amiga system software in version
1.2.  I just got an A2090 disk controller/host adaptor, and a ST251 hard
disk drive.  (Real nice, BTW!)  After loading 10 meg of stuff on it, I was
getting nervious, so I backed up the disk to 15 floppies using Steve Drew's
SDBackup program.  It set all of the archive bits, and everything was fine.

I was glad I had done this, just hours before the lightning storm that night.
Happily, there were no disk problems.

I fired up the machine today, and made a new directory.  I renamed a file
that was backed up into the new directory, and noticed that the state of the
archive bit didn't change.  That is, it was still ON indicating that the
file was backed up.

Now, I remember the flame wars regarding file modification dates and the
COPY command.  I really don't want to start anything like that again.  But,
do you think this is correct?  My initial, gut feeling was that the file
should not be marked as being saved, as this is a "different" file.

Is the behavior intentional, a bug, or did it just work out that way?


Louis A. Mamakos  WA3YMH    Internet: louie@TRANTOR.UMD.EDU
University of Maryland, Computer Science Center - Systems Programming