[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

45.0. "System Disk Overfull" by MARTY::FRIEDMAN () Mon Mar 02 1987 15:24

My system disk only has 2000 blocks free on it. Apparently you need to 
have around 7000 free blocks to install the kit (temporary files copied
to SYS$UPDATE?). Is there a workaround that would allow me to install
the kit with so few blocks left on my system disk?

Thanks.

Marty
T.RTitleUserPersonal
Name		DateLines
45.1Maybe a user disk?ATLAST::BOUKNIGHTEverything has an outlineMon Mar 02 1987 23:254
    You don't have to install it on the system disk....do you have another
    disk with more room?
    
    jack
45.2You have to have the room.VAXUUM::KOHLBRENNERTue Mar 03 1987 09:2210
    The answer for the system disk is "no," Marty.
    
    The installation is done in "safety mode" which means that
    VMSINSTAL restores the savesets to a working directory on
    SYS$UPDATE and then when it is all through being told what
    to do by the KITINSTAL.COM file, it actually starts to do it.
    The result is that a huge chunk of space is needed to store
    all the files before any of them actually start getting
    "installed."
45.3AUTHOR::FRIEDMANTue Mar 03 1987 11:367
    Thanks Bill, that's what I thought. Now I am merrily removing the
    system dump file from my system disk.                            
    
    Perhaps the documentation should note the temporary system disk
    requirements (as well as the permanent requirements).
    
    Marty
45.4shifting sandsVAXUUM::KOHLBRENNERTue Mar 03 1987 16:4923
    Well, the documentation is not all that clear because the installation
    command file itself was not clear about how it was going to do things.
    We had one scheme, but discovered it wouldn't work because of a
    VMSINSTAL bug that got fixed in v4.4, and we were trying to install
    on v4.2 or later.  SO then we switched to another scheme, and now
    we are going to require 4.4 or later, so we don't have to code around
    the VMSINSTAL bug.
    
    THe installation command file asks you all the questions up front
    about what you want and then does some calculations about how much
    space it is going to take.  This calculation is sensitive to whether
    you are trying to install on the system disk or a separate disk.
    Then it looks at how much space you have on the system disk and
    on the other disk if you are installing on another disk and stops
    if it looks like you won't have enough in either place.
    
    The "code around" for the VMSINSTAL bug meant that you had to have
    more space than would normally be required.  What with changing
    the requirement for minimum vms version and changing the way the
    LN03 and LN01 fonts are installed, the information may not have
    gotten pinned down for the documentation.
    
    Hopefully we'll get it all right for the field test update...