Subject: | |
From: | |
Reply To: | |
Date: | Tue, 25 May 1999 10:55:18 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
PATCHMAN v1.1 MPE Patch analysis tool.
--------------------------------------
Patchman is a patch management tool that analyzes the patches previously
installed on your system, looking for:
patches that have been marked bad
patches that have been superseded
patches that are unrecognized (generally alpha or beta patches)
Patchman then suggests which new patches you might want to download and
install:
new patches superseding any of your previously installed patches
new patches for FOS or HPSWINFO-patched subsystems
new patches for other subsystems
Patchman is willing to optionally download and unpack any recommended
patches.
See patchman -h for full usage information. If run with no parameters, the
default behavior is just to report on installed patches and recommend new
patches.
Download patchman from:
ftp://ftp.cccd.edu/pub/mpe/patchman-1.1
or
http://www.cccd.edu/ftp/pub/mpe/patchman-1.1
Comments? Questions?:
Coast Community College District
District Information Services
ATTN: Mark Bixby
1370 Adams Ave
Costa Mesa, CA 92626-5429
email: [log in to unmask]
phone: +1 714 438-4647
web : http://www.cccd.edu/~markb/
README README README README README README README README README README README
This tool is not a substitute for exercising your own good judgement or
talking to the HP Response Center!!!!!
I make some critical assumptions in this script:
1) Patch names must match the regexp [A-Z]{2}[0-9A-Z][A-Z]{2}[0-9A-Z]{2}[A-Z]
2) A superseding patch will have a name alphanumerically greater than the
superseded patch.
3) HPSWINFO is NOT examined chronologically. Thus if you installed a patch,
then supersede it, then at some later date re-install the old version,
this script won't know it and will think you're still using the
superseding patch.
4) "Interesting" new non-superseding patches for FOS are identified by a
fixed list of prefixes. I don't know if the prefixes are 100% accurate.
Take a look and let me know. Thanks.
5) "Interesting" new non-superseding patches for HPSWINFO are identified by
existing HPSWINFO prefixes. Thus if a new non-FOS subsys patch appears
in the catalog, and you don't already have any patches in HPSWINFO for
this subsys, the new patch won't be listed in the HPSWINFO section (but
it WILL be listed in the other section).
6) No attempt is made to analyze dependency information. That's a job for
Patch/iX anyway. (You ARE using Patch/iX, aren't you?)
README README README README README README README README README README README
CHANGE HISTORY
--------------
v1.1 May 25, 1999
Perform additional patch server analysis looking for consistency
problems (patches that exist in the catalog but not in the download
directory, and patches that exist in the download directory but not in
the catalog).
Added the -a parameter to tell patchman to exit after completing the
patch server consistency analysis.
Added the -l parameter to specify a local HFS override file containing
the list of patch truck files available in the patch server download
directory (instead of doing an FTP directory listing).
After all patches have been unpacked, scan the remark files looking
for patches that have been marked bad or suffer from MOVER635
corruption.
v1.0 May 11, 1999
Initial public release.
--
Mark Bixby E-mail: [log in to unmask]
Coast Community College Dist. Web: http://www.cccd.edu/~markb/
District Information Services 1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)
|
|
|