Hi all,
[my earlier posting didnt seem to make it. I perhaps sent it to the
wrong list address. here it goes again]
I have been entrusted the task of verifying a large webserver
running digital alpha 4.0B for y2k compliance and if it is not, make it
compliant. (The info I gathered so far is at the tail end of the email).
In addition to the standard distribution, it also runs some freeware
components (DNS bind, sendmail, apache, radius etc).
Being new to digital-unix as well as y2k-issues, I am looking
advice on the general gameplan, resources I could use etc. Specifically,
any case studies of real systems or templates of y2k compliance imple-
mentation are very welcome. Any other resources (books, websites,
tutorials etc etc) would be very helpful too. (Always willing to learn
from others' and my own mistakes :)
A specific question I'd like to pose to the admins who have
been there - what sort of time commitment is expected (I've been working
with unix systems for quite a while, but not digital/ultrix and no y2k
involvment) ?
To me, the general scheme appears as follows -
inventory, compare versions, upgrade where necessary, testing. Do this
for firmware, OS, freeware in that order. Are there any automated tools
that could help with one or more of these steps (while keeping the
system in production as much as possible). I have looked at "sunscan2000"
for solaris machines and am looking for equivalents in the digital
world.
Thank you all in advance.
-vijay
The system configuration is as follows:
Function Software Version
---------------------------------------
Mail sendmail 8.9.1
PopMail ipop3d 4.44
Webserver Apache 1.2.5
DNS BIND 8.1.1
DialupAuth Radius 2.0.1
hardware/Firmwear etc
---------------------
Digital AlphaPC 164LX 533 MHz system
Digital UNIX V4.0B (Rev. 564)
Firmware revision: 4.9
Digital UNIX PALcode version 1.22
IntraServer ROM Version V1.0 c1997
(ethernet i/f) DECchip 21140-AA: Revision: 2.0
Received on Mon Jun 14 1999 - 19:10:01 NZST