[802] in Release_7.7_team
Re: Consider memory upgrades for public SPARC Classics.
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Thu Dec 26 19:03:19 1996
From: Jonathon Weiss <jweiss@MIT.EDU>
To: Bill Cattey <wdc@MIT.EDU>
Cc: Jonathon Weiss <jweiss@MIT.EDU>, release-team@MIT.EDU
In-Reply-To: Your message of "Mon, 23 Dec 1996 12:16:44 EST."
<smjftwQGgE6e0fmp80@mit.edu>
Date: Thu, 26 Dec 1996 19:03:13 EST
[trimmed acmg from the cc list]
> One clarification here: The current Solaris update finds insufficient
> room on the root partition to keep two copies of the kernel. The effect
> of this has been that if a private workstation botches the update, the
> only redress is to re-install from scratch.
>
> If the root partition were bigger, the old version could be kept around
> as a fall back.
WEll, my initial reaction to this was: well, that's a no-brainer,
let's just steal some space from /var and make root and /usr bigger.
The problem is that while it isn't too hard to do this at install time
(I think it's about an hours work for each type of disk we want to
partition differently.) It would be nearly impossible to change all of
the machines that are already out there. I believe that we have disks
in several sizes 400M, 500M, 1G, and 2G. Since we have not configured
our installers to deal with 2G disks yet, we have a fairly clean slate
for them (I kluged the install to install moira3 and one of ASO's
spare machines, but I don't think tha is too big of a deal). Should
we say, summarily double the size of root and /usr compared to what
we're doing on 1G disks? We could change the installers to also
double the size of these partitions on the 1G disk new installs.
However, I suspect doubling on the 400M and 500M disks might make /var
a little smaller than we would like.
Opnions?
Jonathon
