I will not be compiling a new libc5, I'll be fixing the buffer move in tar that triggered the problem, probably. I have that fix already. > manually until you get it installed in your next release?? I > was just looking at the cpio man pages, and the version > for cygwin (Which I am assuming is gnu-cpio) has a > 100 character name limit for tar compatiblity, which under > WinBlows, could be restrictive. Cpio is actually better with names. The problem is the special gnu-tar name mangling. If you care about long paths and file names, use cpio in the first place, (really cpio format, not tar format from gnu cpio) and you will be safer. The basic thing is that tar has a sane command syntax and convenience of running it, but cpio has a sane file format. Gnu-tar actually is not tar-standard-compatible. Cpio of course doesn't come bundled in cygwin, but I'm sure it will work fine and might be available binarily. If you are going to use the cygwin gnu-tar for longer-than 100 files, you won't want to use the tomsrtbt tar anyway, since you'll be depending on the gnu-tar extensions, you'll want to get a libc5 or static gnu-tar. I can probably upload one of those, um, ok, look in ftp.toms.net /rb/add-ons for gnu-tar.bz2, that is a libc5 gnu-tar. Or make a cygwin cpio.... again, I actually think cpio is safer and better, for example, that 100 character name thing is a kludge in gnu-tar, but cpio has a true variable length filename in the file format. -Tom PS on re-reading, I see you already found the cygwin gnu-cpio. It is important to emphasize that the gnu cpio is really two programs- it can create and read *either* tar files or cpio files. the 100-char thing is only an issue if you use the tar format. If you use the cpio format, it isn't a problem, and of course tar can't read those files at all. -Tom > > Thanks. > > > On Tue, 2 Jan 2001 09:53:13 -0500 (EST), Tom Oehser wrote: > > > > >There is a bug in the libc5 which interacts with it. I have a fix but > >havn't published it yet. I will increase the priority of fixing and > >publishing the fix... I think you can use the gnu-cpio on ftp.toms.net > >/rb/add-ons to create/extract tar files, for now, until I get a fix... > > > >-Tom > > > >On Tue, 2 Jan 2001, Mark Paulus wrote: > > > >> Date: Tue, 02 Jan 2001 00:30:31 -0700 > >> From: Mark Paulus <[EMAIL PROTECTED]> > >> Reply-To: Mark Paulus <[EMAIL PROTECTED]> > >> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > >> Subject: Problem with tar > >> > >> I seem to be having a problem with tar on RTBT 1.7.205. > >> I have a: > >> FIC VA-503+ / AMD K6-3+/450 > >> 256 MB > >> Buslogic BT-958 > >> ST34520N (SCSI 0) > >> ST34583WC (SCSI 1) > >> IBM-PCCO DDRS-39130Y (SCSI 2) > >> CyberDrive 12X CDRom > >> Conner CTMS 3200 Mini-Cartridge > >> > >> LS-120 (IDE 1/0) > >> 3COM 3C905 > >> SB AWE-32 > >> Riva TNT > >> etc > >> etc > >> > >> I doubt any of this makes any difference, but just in case. Anyway, when > >> I try to make a backup of my Win98SE partition, by doing a > >> 'mount -t vfat /dev/sda2 /cdrive', that works fine. But, when I do > >> a 'tar cvf /dev/st0 /cdrive', then tar goes for a while, and then it gets > >> a segmentation fault. I have seen this before on another machine, and > >> it looks like there is a problem when the number of files processed > >> exceeds some limit. I'm not sure if the segmentation causes a > >> core or not. If we need to generate one, I can try. Or maybe > >> we can check to see if there is a small limit on the number of files. > >> Anymore I would think it should be a huge number, like upwards of > >> 20K. Just my opinion, though. > >> > >> > > >> Let me know if you need any more info, or if you can confirm if this > >> is a problem, and if it will be fixed. > >> > >> Thanks. > >> > >> > > > > > > > > >
