Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!hao!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.bugs.4bsd
Subject: Re: 4.2BSD TU78 driver does not agree with mtio(4)
Message-ID: <8184@umcp-cs.UUCP>
Date: Wed, 29-Aug-84 22:11:13 EDT
Article-I.D.: umcp-cs.8184
Posted: Wed Aug 29 22:11:13 1984
Date-Received: Sat, 1-Sep-84 11:08:34 EDT
References: <3201@CSL-Vax.ARPA>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 17

With a TU77 *and* a TU78, we had to do something even more different.
We made mt0 the TU77 at 800 BPI, mt8 the 77 at 1600, mt1 the 78 at
1600, and mt9 the 78 at 6250.  Our /dev entries don't all correspond to
the minor device numbers since the two drives are on different
formatters (naturally).

We found that typing ``/dev/rmt13'' all the time was a pain, so we made
links called mu0, mu4, mu8, mu12 (and rmu versions of the same) and use
'alias mu "mt -t /dev/rmu12"'.

Personally, I think there should be two /dev names for every raw tape
drive at every density: the ``standard'' one (rmt0 etc.) and a
``verbose'' one (/dev/tu77_800 or some similar garbage).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland