home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!darwin.sura.net!mips!odin!fido!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Subject: Re: Problem with Tape Backup -- blocksize mismatch
- Message-ID: <nq85uuo@zuni.esd.sgi.com>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- References: <1992Jul26.123233.29447@ringer.cs.utsa.edu> <npqdqq0@zuni.esd.sgi.com> <1992Jul27.022600.7078@ringer.cs.utsa.edu>
- Date: Mon, 27 Jul 92 04:26:37 GMT
- Lines: 23
-
- In <1992Jul27.022600.7078@ringer.cs.utsa.edu> senseman@ricky.brainlab.utsa.edu (David M. Senseman) writes:
- | I will confess that we have had some problems with links in the
- | past since this machine also has a 1/4" Archive Viper (150 MB QIC)
- | attached and we have done a number of links between the various
- | drivers and drives. What is the best driver for the Viper?
-
- /dev/rmt/tps0d# for 'SGI' compatibility, or /dev/rmt/tps0d#ns if
- you need to exchange tapes with most of the rest of the world, or
- if you want an extra percent or two of tape throughput.
-
- | BTW, this is probably a stupid question, but what is the primary
- | difference between the drivers in /dev/mt/tps* and in /dev/rmt/tps* --
- | when do you use "mt" and when do you use "rmt"?
-
- There is no difference; they are links to each other. Enough people
- were used to using /dev/mt that we supported them via links. At one
- point, the mt/* devices were for block access (i.e., like a
- filesystem), but IRIX has never (so far as I know) supported this,
- althoug some other versions of unix may.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-