*BSD News Article 7818


Return to BSD News archive

Xref: sserve comp.unix.msdos:1536 comp.unix.bsd:7869 comp.unix.sysv386:25552 comp.unix.xenix.misc:442 comp.unix.xenix.sco:6224 comp.unix.pc-clone.32bit:433 comp.unix.sys5.r4:479 comp.unix.wizards:27496
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!agate!stanford.edu!rutgers!utcsri!newsflash.concordia.ca!sifon!thunder.mcrcim.mcgill.edu!mouse
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: comp.unix.msdos,comp.unix.bsd,comp.unix.sysv386,comp.unix.xenix.misc,comp.unix.xenix.sco,unix-pc.general,comp.unix.pc-clone.32bit,comp.unix.sys5.r4,comp.unix.wizards
Subject: Re: HELP! problem with tar PC <-> SUN
Message-ID: <1992Nov12.212714.6615@thunder.mcrcim.mcgill.edu>
Date: 12 Nov 92 21:27:14 GMT
References: <BxJ7qx.2An@avalon.nwc.navy.mil>
Organization: McGill Research Centre for Intelligent Machines
Lines: 33

In article <BxJ7qx.2An@avalon.nwc.navy.mil>, dejesus@archimedes.nwc.navy.mil (Francisco X DeJesus) writes:

> [transferring files with tar between SunOS 4.1.2 and "a PC running
> Unix" (which dejesus says "refers to trying this with SCO Unix,
> Interactive Unix, and Intel Unix").

> Here's the problem: [...] [i]f a tape is written on the Sun with a
> blocking fator of 2, the PC reads it as a blocking factor of 20.
> [T]his is where the *REAL* problem comes in: [t]he client specifies
> that the "tar" command *HAS* to be used _WITHOUT_ telling it a
> specific blocking factor on either end [...].

Comes a point where you have to tell the client "I'm sorry, you're
being too stupid.  If you insist on that go find someone else to do
it.".  IMO this is pretty close to the line where that begins to be
called for.

> So... any ideas?  Please, we are wide open to suggestions.  ANY
> possibilities will be explored... a different tape driver, another PC
> Unix version, rebuilding tar on the PC (if we can get the sources)...
> anything goes.

In that case, why not just pick up any of the good free tars and build
it on one or both ends?  In that case, if it turns out to be a
system-level bug (ie, tar is doing its best and the system is mangling
things), you can patch the source to act as if it had the b option even
when it doesn't.  (Where are these tars?  At least one of them is
somewhere on uunet, and I wrote another one....)

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu