Return to BSD News archive
Xref: sserve comp.unix.msdos:1535 comp.unix.bsd:7842 comp.unix.sysv386:25529 comp.unix.xenix.misc:441 comp.unix.xenix.sco:6220 comp.unix.pc-clone.32bit:428 comp.unix.sys5.r4:477 comp.unix.wizards:27479
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!yale.edu!think.com!ames!haven.umd.edu!umd5!roissy.umd.edu!mark
From: mark@roissy.umd.edu (Mark Sienkiewicz)
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: <17013@umd5.umd.edu>
Date: 16 Nov 92 19:01:46 GMT
References: <BxJ7qx.2An@avalon.nwc.navy.mil> <1992Nov12.212714.6615@thunder.mcrcim.mcgill.edu> <1992Nov12.234822.1273@leland.Stanford.EDU>
Sender: news@umd5.umd.edu
Organization: University of Maryland
Lines: 21
In article <1992Nov12.234822.1273@leland.Stanford.EDU> dkeisen@leland.Stanford.EDU (Dave Eisen) writes:
>This probably still won't make him happy. He'll want to read tapes
>that were created with a blocking factor of 20 using a blocking
>factor of 20 and tapes that were created with a blocking factor of
>2 using a blocking factor of 2. In other words, he wants tar to
I agree the client is being unreasonable, but I can't remember _ever_
working for a client who was not unreasonable at least some of the time.
>be clairvoyent. If this is the case, all you can do is tell him that
>he wants something impossible and hope you don't lose the business.
On most systems I've used, you can detect the block size of a tape by
doing something like:
char buffer[BIGGEST_POSSIBLE_RECORD_SIZE];
n=read(fd,buffer,sizeof(buffer));
printf("block size is %d bytes\n",n);
Mark S.