[738] in Info-AFS_Redistribution
Re: Upgrading an O/S with package?
daemon@ATHENA.MIT.EDU (Daniel Edward Lovinger)
Wed Apr 22 19:15:11 1992
Date: Wed, 22 Apr 1992 17:58:25 -0400 (EDT)
From: Daniel Edward Lovinger <dl2n+@andrew.cmu.edu>
To: Info-AFS@transarc.com
In-Reply-To: <9204222103.AA18439@oaunx1.CTD.ORNL.GOV>
Jamey Maze <jnm@ornl.gov> writes:
> Has anyone actually upgraded the operating system on an AFS client via
> package (e.g., SunOS 4.1.1 to 4.1.2)? Can it be done? If so, any words of
> wisdom? I was under the impression that this was possible, but some folks
> here are skeptical.
Yup. That's the way we do everything over here. It is "just" a
matter of creating the appropriate package description for your new
operating system and letting 'er rip. The pckg-tree Perl script I
distributed a month or so ago is the first step. We've done SunOS
4.0.3 -> SunOS 4.1.1 and Ultrix 3.1 -> Ultrix 4.2 recently.
Caveat: our package structure bears zero resemblance to the
way Transarc does things. Our machines have an /etc/package.proto
which is processed by mpp to generate a description which is then
handed to package. A package.proto typically contains stuff like
%define beta
%define betalocal
%define betacont
%include /afs/andrew.cmu.edu/wsadmin/public/src/public.proto
in other words, not much. Our machines run package on each boot, and
the whole thing is centralized so that we just pull a switch and
machines start upgrading on their own. No central intervention except
in the odd case - you have to make sure you don't overload disk
partitions by accident. (urg)
Take a look at our wsadmin area (starting from the
public.proto). Feel free to kick questions back in my direction.
dan
