home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.ncr:545 comp.unix.questions:14761
- Newsgroups: comp.sys.ncr,comp.unix.questions
- Path: sparky!uunet!mcsun!sun4nl!echelon!kees
- From: kees@echelon.uucp (Kees Hendrikse)
- Subject: Re: NCR Unix to SCO Unix Tar incompatability question
- Organization: Echelon Consultancy, Enschede, The Netherlands
- Date: Thu, 17 Dec 1992 09:33:23 GMT
- Message-ID: <BzED7p.6q1@echelon.uucp>
- References: <1992Dec15.035339.24343@jpradley.jpr.com> <1992Dec15.182031.16597@unislc.uucp> <1992Dec16.183827.24752@donner.SanDiego.NCR.COM>
- Lines: 24
-
- In <1992Dec16.183827.24752@donner.SanDiego.NCR.COM> David Lord writes:
-
- > First off, the original poster didn't say what hardware he was running
- > on and that makes a difference. Presumably it is a Tower, but some
- > models of Tower require byte-swapping, while others do not. Unfortunately
- > I don't recall which is which, however if byte-swapping were the problem
- > I would expect tar to complain that the tape wasn't in tar format.
-
- No, if tar tries to read a byte-swapped file, it complains with the
- message: "tape block size error", even when the file is a regular file:
-
- tar -cvf - some files | dd conv=swab of=/tmp/testfile
- tar -tvf /tmp/testfile
-
- Tar complains as if it were a tape... (Remember, tar means tape-archiver :-))
-
- Anyway, I always had to swap bytes when reading tapes from SCO on a
- Tower or the other way round.
-
- --
- Kees Hendrikse | email: kees@echelon.uucp
- |
- ECHELON consultancy and software development | phone: +31 (0)53 836 585
- PO Box 545, 7500AM Enschede, The Netherlands | fax: +31 (0)53 337 415
-