Xref: utzoo comp.sys.att:3032 comp.unix.wizards:7830
Path: utzoo!utgpu!water!watmath!clyde!att-cb!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ucsd!sdcsvax!ucsdhub!jack!nusdhub!rwhite
From: rwhite@nusdhub.UUCP (Robert C. White Jr.)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Big fun with Sys V Drivers
Message-ID: <1030@nusdhub.UUCP>
Date: 17 Apr 88 08:08:50 GMT
References: <406@paisano.UUCP>
Organization: National University, San Diego
Lines: 73

in article <406@paisano.UUCP>, demasi@paisano.UUCP (Michael C. De Masi) says:
> 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.  This sounds correct
> to me, since I don't think the 'partial restore' actually touches
> the drivers in any way other than to somehow disconnect them
> from the new /unix.

Forgive me if I'm wrong, this is from memory....

This is somewhat what you need to do: [for 3b2(s) only]
	# This Will update all you kernel Drivers
	# This is not strictly necessary, but it can't hurt and
	# dosn't take much time [1 min or so]
	cd /boot
	mkboot -k KERNEL
	for AA
	in [!K]*
	do
		mkboot ${AA}
	done

[This is the part I'm not shure about.... It may be done FOR YOU
in step 4, if you try to complete the procedure without doing this step
NO HARM will result. I havent had to do this whole thing, under SVR3 so
I would NOT do this the first time.  If you skip this step, and
it dosn't work, you may restart from here.  Either way, the results
will be obvious when you get to step four... you may or may not have to:]
	EDIT your /etc/system to have an "INCLUDE" for every "new" driver.
This will be done for you if you have restored the old /etc/system
with the rest of your restore.  

Go to "firmware mode".  This is where you have to be to do the next
little little bit of magic.  Going to firmware mode should be no
mystery to you if you have been doing partal restores.  Go to the
next step when you have gotten to the "what program do you want to
run" firmware prompt.

THIS IS IT!!! The magic part!!  Tell the firmware that you want to
EXECUTE /etc/system.  [yes, I know, /etc/system is NOT executable
in any form, but the firmware will read it's contents and use the
file to rebuld your /UNIX]  You should first see a listing of all
the modules the system will attempt to load.  There will then be a
[frighteningly!] long pause, and then you will get a four [or more]
column load map of your kernel [name, text, data, <and I forget>].
All of this will be followed by the boot sequence you normally
see when you load new drivers from diskette.


I wouldn't suggest editing /etc/system with any regularity, but any
of the other steps can be done safely on a stable system.  The only
real warning in all of this is that removing the SCSI entry from
/etc/system and/or nukeing the edt will make the 600 unbootable until
you do a _full_ restore.

ALWAYS "cp /unix /oldunix" BEFORE DOING _ANY_ OF THIS
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

3B2 Security Hole cum System Saver.: If you loose the root password
for a system you can recover it if you can log in as "sys" this
is done via the "mv" command.  This will probably reduce your
"partial restore" efforts.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<<  All the STREAM is but a page,<<|>>	Robert C. White Jr.		   <<
<<  and we are merely layers,	 <<|>>	nusdhub!rwhite  nusdhub!usenet	   <<
<<  port owners and port payers, <<|>>>>>>>>"The Avitar of Chaos"<<<<<<<<<<<<
<<  each an others audit fence,	 <<|>>	Network tech,  Gamer, Anti-christ, <<
<<  approaching the sum reel.	 <<|>>	Voter, and General bad influence.  <<
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
##  Disclaimer:  You thought I was serious???......  Really????		   ##
##  Interogative:  So... what _is_ your point?			    ;-)	   ##
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^