I discovered this list last week, and BOY AM I GLAD I DID. Already I have found
more answers and guidance
through "Tru64 UNIX" (ahem -- is this an effort to contradict the ole UNIX
veteran's intonation of "unix is unix is unix is unix"?) than in the stacks of
Digital documentation on my desk. Thanks to this list (and a great tech Mike
on the
support line), the task facing me has been somewhat simplified.
I have a small complex of 4 Alphas (1 4100 & 3 2100s), all needing to be
upgraded to 4.0D and patched to be
brought into Y2K compliance. These systems are highly critical to our daily
business, and have a 4 hour maintenance
window on Saturday nights only. I have solved part of my problem by using a
recently retired 2100 to build from the
ground up to replace the first system, then the replaced system can be built to
replace the next box. Since none of these
systems had been built according to any defined standards and all of the boxes
had been "personalized" by a long
procession of long-gone admins, this is a positive move for the complex. The
last two systems are the most critical,
and must be upgraded in place. The problems facing me with the last two are
the ever-popular "root-is-too-small"
PLUS "root-and-usr-is-ADVFS."
All this is complicated by root and user being encapsulated and mirrored. I
know I will have to unmirror, disassociate plexes and unencapsulate. But I want
to use the small swap partition on the root disk to increase root's size. Using
Dirk Bergl's summary posting (8/5/99) as a template, I think I can accomplish
this. But can I convert the root and usr
filesystems to UFS during this process? I will be retaining ADVFS for larger
application and data disk storage, but
using ADVFS for root and usr complicates upgrade issues, etc.
Any advice you could offer would be greatly appreciated.
Annette Lee
aelee_at_household.com
831-772-6762
Received on Thu Sep 02 1999 - 19:54:02 NZST