From owner-freebsd-questions  Fri Jun 14 08:55:49 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA24429
          for questions-outgoing; Fri, 14 Jun 1996 08:55:49 -0700 (PDT)
Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA24421
          for <freebsd-questions@freebsd.org>; Fri, 14 Jun 1996 08:55:46 -0700 (PDT)
Received: (from amir@localhost) by prozac.neuron.net (8.6.12/8.6.12) id MAA02619; Fri, 14 Jun 1996 12:06:14 -0400
From: "Amir Y. Rosenblatt" <amir@neuron.net>
Message-Id: <199606141606.MAA02619@prozac.neuron.net>
Subject: Re: More info on my tape drive problem
To: branson@widomaker.com (Branson Matheson)
Date: Fri, 14 Jun 1996 12:06:13 -0400 (EDT)
Cc: amir@neuron.net, freebsd-questions@freebsd.org
In-Reply-To: <199606141240.IAA08383@garion.hq.ferg.com> from "Branson Matheson" at Jun 14, 96 08:40:46 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >[root@prozac]/dev# ./MAKEDEV nrst0
> >nrst0 - no such device name
> >[root@prozac]/dev# ./MAKEDEV nrst0.0
> >nrst0.0 - no such device name
> 
>  Read the source luke!!! 

Actually, I did so shortly after sending off the note to the list.  I 
then remade the devices but STILL couldn't access the tape drive.  dmesg 
told me that when I had rebooted the machine this morning (becasue it had 
hung last night, which was the start of all this) the Adaptec card had 
for some reason not seen the tape drive.  That's never happened before.  
So, I rebooted the machine and ran the baqckup, which worked fine.  I'm 
still curious as to what happened to the device files.  I've seen this 
happen a number of times on our HP9000 when people use the wrong flags 
with tar but I've been using this same backup script without a problem 
for weeks.

> >The same thing happened earlier in the week when I tried to MAKEDEV tty.
> 
> Ok...# Terminal ports:
> #       tty*    general purpose serial ports
> #       cua*    dialout serial ports
> #       ttyA*   Specialix SI/XIO dialin ports ('*' = number of devices)
> #       cuaA*   Specialix SI/XIO dialout ports
> #       ttyD*   Digiboard - 16 dialin ports
> #       cuaD*   Digiboard - 16 dialout ports
> 
> So which tty are you trying to make? ...

The dump report specified that /dev/tty was the one with the problem and 
after replacing it with a copy from  a previous backup I no longer got 
the error.  Again I wonder what could have caused it.

	-Amir