Date: Wed, 10 Oct 2001 20:56:45 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: acottrel AT ihug DOT com DOT au Message-Id: <2950-Wed10Oct2001205644+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 CC: djgpp-workers AT delorie DOT com, wojciech DOT galazka AT polkomtel DOT com DOT pl In-reply-to: <006601c15186$1591f8c0$0a02a8c0@acceleron> (acottrel@ihug.com.au) Subject: Re: First round of XP tests References: <250B3114DA16D511B82C00E0094005F8023FC210 AT MSGWAW11> <006601c15186$1591f8c0$0a02a8c0 AT acceleron> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: "Andrew Cottrell" > Date: Wed, 10 Oct 2001 22:21:25 +1000 > > The Tar bninary file is available for download for testing. I just tar'd > some batch files then deleted the batch files and then untared the file. The > process I used was: > > 1) DJGPP_204 D:\temp>tar -c *.txt > TEST.TAR > 2) DJGPP_204 D:\temp>del *.txt > 3) DJGPP_204 D:\temp>dir > Volume in drive D is DATA > Volume Serial Number is 8495-4651 > > Directory of D:\temp > > 10/10/2001 10:18p . > 10/10/2001 10:18p .. > 10/10/2001 10:18p 30,720 TEST.TAR > 1 File(s) 30,720 bytes > 2 Dir(s) 13,947,686,912 bytes free > > 4) DJGPP_204 D:\temp>tar -x < TEST.TAR > 5) DJGPP_204 D:\temp>dir > Volume in drive D is DATA > Volume Serial Number is 8495-4651 > > Directory of D:\temp > > 10/10/2001 10:19p . > 10/10/2001 10:19p .. > 07/10/2001 02:51p 1,750 mkall_out.txt > 11/03/2001 12:07a 19,959 readme.txt > 10/10/2001 10:18p 30,720 TEST.TAR > 3 File(s) 52,429 bytes > 2 Dir(s) 13,947,662,336 bytes free > > Is this enough to test LFN? No, not at all. Tar is an extremely flexible and versatile program, with many switches that completely change its behavior. In addition, there's some DJGPP-specific code in the ported Tar which makes sophisticated use of several system calls. These all should be tested if you want to make sure Tar works on W2K. When I did the port, I made a point of designing a small test case for every command-line switch and for every feature documented in the manual. (That was in addition to the Tar test suite, which is fairly easy to run.) Examples of tricky features include: preservation of time stamps and access attribute bits; support for hard and symbolic links in the archive created on a Unix system; special handling of files whose names are reserved on DOS/Windows, like prn.txt or aux.c; the feature whereby Tar excludes the archive from files being put into the same archive when you say something like "tar cf foo.tar *"; comparison of time stamps and mode bits in the archive with those on disk, so that "tar --diff" works as expected immediately after you untar, even though time stamps have 2-sec granularity. And that's just a list of issues I have after 5 seconds of thought ;-)