ADSM-L

Re: ADSM V3.1 PTF IP21354

1998-05-12 17:27:46
Subject: Re: ADSM V3.1 PTF IP21354
From: Bruce Huang <brucelee AT US.IBM DOT COM>
Date: Tue, 12 May 1998 17:27:46 -0400
Al,

When you installed the new PTF for Solaris 2.6, the original ADSM device
drivers had to be removed from the kernel and the new (PTF) device drivers
needed to be added.  The install program removed the original ADSM drivers, but
you have to add the PTF drivers manually.  The command is (executed as
superuser) "/usr/sbin/add_drv lb" (similarily for op and mt).  The reason the
install program does not add the ADSM drivers automatically is that the Solaris
program "add_drv" does not seem to have a deterministic method of assigning the
device special file names.  That is, there is no guarantee that by adding the
PTF device drivers now, you will get the same device special names as when you
added the original ADSM device drivers.  So you will need to follow the same
procedures as from the original installation to figure out the device special
names for your library (s) or drive(s) once you "add_drv" the ADSM device
drivers.

Most likely, you will get /dev/rmt/4lb as your library once you "add_drv" the
PTF device drivers.  But follow the instructions to be sure.

-Bruce-
 ADSM-L @ VM.MARIST.EDU
 ADSM-L @ VM.MARIST.EDU
 05/12/98 10:06 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU

To: ADSM-L @ VM.MARIST.EDU
cc:
Subject: ADSM V3.1 PTF IP21354

Hello, I applied PTF IP21354 to my Solaris 2.6 V3.1.1.0 server. The pkgadd
went ok. BUT, the devices that were created by add_drv on the initial
install no longer point to anything!!? So /dev/rmt/4lb, which defined the
tape library, no longer works. I tried a boot -r with no luck. Prior to
applying the patch, I could do a DEFINE LIBRARY to /dev/rmt/4lb. It would
blow up, but now it doesn't even find the device anymore. Is this a feature
of the patch? What kind of support is this? Anybody else run across this
situation?

Al Cheski
Gulf Canada Resources



<Prev in Thread] Current Thread [Next in Thread>