*BSD News Article 90968


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!arclight.uoregon.edu!news.maxwell.syr.edu!mr.net!newshub.tc.umn.edu!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Using mt with a Wangtek drive
Date: 13 Mar 1997 23:47:35 GMT
Organization: Private BSD site, Dresden
Lines: 38
Message-ID: <5ga3mn$pp@uriah.heep.sax.de>
References: <5g6pm5$kv1@news.gvsu.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36993

behrensm@river.it.gvsu.edu (Matt Behrens) wrote:

> I've recently installed a Wangtek drive using the wt0 driver in my FreeBSD
> 2.2-GAMMA system.  I can retension, erase, and all that fun stuff.  But
> when I try to use mt weof to put multiple files on a tape, it bombs.  Am I
> doing it wrong?  Here's what I'm trying:
> 
> 	tar cvf /dev/rwt0 /dir1 /dir2 /dir3
> 	mt weof
> 	tar cvf /dev/rwt0 /dir4 /dir5 /dir6
> 
> After the first tar, the tape rewinds (I think.)

No idea why it hangs on the `weof' command.  Anyway, you're doing
totally wrong.

First, as you've already noticed, the tape rewinds after the first
recording.  Thus, the second tape file will be the new first one,
written from the very beginning of the tape.  Probably not what you
want.  The no-rewind device is what you're looking for:

	tar cvf /dev/nrwt0 /dir1 etc.
	tar cvf /dev/nrwt0 /dir4 etc.
	mt -f /dev/nrwt0 rewind

Then, you are not supposed to write eof markers manually.  The driver
will do this at the first close of the device.

Finally, if you have really used the mt command as you've been typing
above (and didn't have a TAPE env variable), it would have attempted
to access the first SCSI tape drive.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)