🚀 go-pugleaf

In article <49720sINNc44@seurat.syd.dit.csiro.au> ken@syd.dit.csiro.au (Ken Yap) writes:
>|I have important source code in ~/fe, and an old backup as ~/fe.tgz.
>|It has been some time since I made a backup, and I plan to make
>|some wild changes I might need to back out - time for a backup!
>|OK, here goes: 'tar zxf fe.tgz fe'.  (the 'x' should be 'c')
>|One damn little typo, and instantly the latest code is replaced
>|with very old code.  Backups?  I thought I was making one!
>|
>|This really should be fixed 2 ways: an undelete, and a --force
>|option for tar.  Overwrite is a crappy default.
>
>Like another poster said, you really should be using RCS; or at least
>separate aliases or scripts for backup and restore, or maybe a makefile
>target for it rather than inviting trouble by using a bare command
>which differs only in one character from another one. Yes, I have made
>the other mistake, overwritten a tape with tar c when I wanted tar x.
>
>There are reasons for unrm, but this isn't one of them.

People are missing the point here ANYWAYS!  You do NOT want to radically 
change tar, and rely on those changes.  TAR is a STANDARD UNIX routine,
and *I* for one, want it to stay similar to that standard.  As for 
one little typo causing a major problem?  If you have worked LATE, you will
know that even a complex error can be made!

Steve