That was a simple tar cvf TAR_FILE TARRED_FILE, but not as the root user (as my own ID). I would not expect my UID or GID to necessarily be present on your server, but that doesn't normally cause a problem when running tar -x as an unprivileged user.
> -----Original Message----- > From: Glenn Fowler [mailto:[email protected]] > Sent: Thursday, September 10, 2009 12:18 AM > To: [email protected]; [email protected]; > [email protected]; Wiersba, John (Healthcare USA) > Subject: Re: Position-dependent ksh bug > > > thanks John, I should have been more specific > I own the ast pax command and it didn't recognize your > original tar file > so I'm interested is how you generated *that* one to see if I can > narrow down the problem to either my pax or "your" tar > > On Wed, 9 Sep 2009 22:16:46 -0400 wrote: > > I recreated the bug.tar file with everything owned by root, so you > > shouldn't have any issues. I have included two driver > files which show > > up the bug, both with and without strace. Diff'ing the > trace files, I > > can see that the position where the bug occurs is at a 8196 byte > > boundary, so there must be some issue there in the code, at least in > > version sh (AT&T Labs Research) 1993-12-28 q. > > > _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
