Hi all,
Original Question:
> I am trying to figure out a way to keep track of non-setld
> patches from Compaq (SSRTs mainly) without repackaging the
> original patch with a setld/pkgadd/rpm kit. We are on 4.0F.
>
> Do I lose all my admin points by adding fake patch entries
> in /usr/.smdb.? Is there a "standard" way to manage SSRTs?
> I see there is a "Tru64 UNIX Patching" topic on the "Future
> Best Practices" page of the Compaq site but nothing current.
> I cant turn up much in the archives except for the recent(?)
> thread on pkgadd for Tru64 and setld-specific questions.
Alan Davis was the only one to reply and he offered the following
which I havent tried yet but looks promising:
If you use the /usr/lbin/ils program to create a .inv file for the
files in a custom patch it's possible to get allverify (and probably
sys_check) to stop complaining about them.
For example, the SSRT0588U for v4.0e has the files
./usr/ccs/lib/libsecurity.a
./usr/shlib/libsecurity.so
# cd /
# /usr/lbin/ils ./usr/ccs/lib/libsecurity.a ./usr/shlib/libsecurity.so >
OSFPATSSRT0588U.inv
# cat OSFPATSSRT0588U
0 407758 52292 3 4 100644 3/25/99 010 f
./usr/ccs/lib/libsecurity.a unknown -
0 368640 11292 3 4 100644 3/25/99 010 f
./usr/shlib/libsecurity.so unknown -
The 010 (product version) should be changed to 435
The unknown (subset) should be changed to OSFPATSSRT0588U. The OSFPAT is
required by the allverify code,
it's probably not required for sys_check.
# cp OSFPATSSRT0588U /usr/.smdb.
# touch /usr/.smdb./OSFPATSSRT0588U.lk
# /usr/local/bin/allverify.tcl OSFC2SEC435
OSFC2SEC435:
./usr/ccs/lib/libsecurity.a to be checked in OSFPATSSRT0588U.
0 verification errors encountered.
0 corrections performed.
Received on Mon Apr 16 2001 - 14:25:16 NZST