I'm setting up RIS for Tru64 v5.1A, in preparation for end of support
for 5.1. As part of this, I'm creating config.cdf files using "sysman
-clone -save", to clone configurations.
For some reason the config.cdf file won't validate across patch levels
of the OS. If I create the file on 5.1A, no patch kit, then it won't
validate on the RIS server, which is running 5.1A with PK3 - I get:
>sysman -clone -validate config.cdf.original
Validating checksum for CDF file config.cdf.original. Please wait,
this will take several moments ..................................
Error: The checksum for CDF file config.cdf.original failed
to validate. This is most likely a result of the
CDF file not being created on this revision of the
operating system. Please use a CDF file that has
been created using the operating system version
Tru64 UNIX V5.1A (Rev. 1885).
Similarly, if I apply PK3 on the "template" system before creating the
config.cdf file, it won't validate on an unpatched system. This is much
worse, of course, as the installation procedure then fails to apply it
after reboot.
I suppose that now I know why things weren't working, it shouldn't be
so much of a problem, but it doesn't seem right - should patch kits
have this effect on config cloning?
Graham
--
-------------------------------------------------------------------------
Graham Allan - I.T. Manager - gta_at_umn.edu - (612) 624-5040
School of Physics and Astronomy - University of Minnesota
-------------------------------------------------------------------------
Received on Wed Nov 20 2002 - 17:41:30 NZDT