Would it be possible to use a script to achieve the same outcome? I've tried re-uploading/downlaoding the files in multiple modes, to no avail.
Also, I ftp'd these files TO a Windows box FROM my BSD box, so I believe that the default mode for that would be binary? Are there any other reasons this may have happened? Any way to test? p. on 1/4/03 6:50 PM, Stephen Hovey at [EMAIL PROTECTED] wrote: > > windows ftp defaults to ascii more, not binary, so its adds a \r to each > \n - you might save your tar files if you upload ascii to get them > stripped out again. > > On Sat, 4 Jan 2003, Phillip Smith wrote: > >> >> Hi, >> >> Wondering what (if anything) can be done about this? >> >> freedom# tar -xf www.tar >> tar: Skipping to next file header... >> tar: Unknown file type '' for >> 8˟ܫ[+n_}M2žV28(Uvjuש, extracted as >> normal file >> tar: Skipping to next file header... >> >> >> I don't understand what's happened to this archive (and serveral others that >> represent my entire system backup)? I'm having the same problem with a whole >> set of archives that I ftp to a remote Windows machine... the ones I stored >> on my other FreeBSD machine are fine. Did something happen during the >> transfer? >> >> Also, for each archive, the first few items are extracted properly and then >> there all this junk... any thought _really_ appreciated. If these are >> corrupt, I've lost a pile of data. >> >> Many thanks in advance, >> >> phillip. >> >> >> To Unsubscribe: send mail to [EMAIL PROTECTED] >> with "unsubscribe freebsd-questions" in the body of the message >> > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
