Xref: utzoo comp.sys.att:3043 comp.unix.wizards:7847
Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!mailrus!rutgers!ukma!ukecc!lynn
From: lynn@engr.uky.edu (H. Lynn Tilley)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Big fun with Sys V Drivers
Message-ID: <2248@ukecc.engr.uky.edu>
Date: 17 Apr 88 23:39:22 GMT
References: <406@paisano.UUCP>
Reply-To: lynn@engr.uky.edu (H. Lynn Tilley)
Followup-To: comp.sys.att
Organization: Univ. of KY Engineering Computing Center
Lines: 27

In article <406@paisano.UUCP> demasi@paisano.UUCP (Michael C. De Masi) writes:
>
 [much text deleted.]
>
>Now, I've been told that there is indeed a way to
>reassociate a driver with a device short of re-installing
>the whole package for the given device.  
>
	I would be very interested in the answer to this problem and 
	in addition maybe I could get some help on a problem we have 
	around here.  We have several 3b2/310s that we are using on 
	an ethernet.  Everything works great expect for on one machine.
	When this machine is rebooted it never recognizes that it has 
	the ethernet drivers in place.  The instant the machine returns
	to life it starts spewing "Network Down" messages.  We have to
	go into the sysadmin menues, shutdown all network daemons and then
	reinstall the TCP/IP WIN software.  Admittedly not a big task, but
	it is still a problem that I would like to clear up.

	We have tried to check to see that all the files have the correct 
	permissions and that no important files are getting removed, etc.
	Any suggestions appreciated.  Thanks in advance.

-- 
    |   Henry L. Tilley                 UUCP: {cbosgd|uunet}!ukma!ukecc!lynn
    |   University of Kentucky          CSNET: lynn@engr.uky.edu       
    V   Engineering Computer Center     BITNET: lynn%ukecc.uucp@ukma  
    O   voice: (606) 257-1752           ARPANET: lynn@a.ecc.engr.uky.edu