Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ihnp4!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: V4 manditory patch
Message-ID: <6333@ucbvax.ARPA>
Date: Wed, 17-Apr-85 19:08:23 EST
Article-I.D.: ucbvax.6333
Posted: Wed Apr 17 19:08:23 1985
Date-Received: Thu, 18-Apr-85 04:24:00 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 114

From: LEICHTER <Leichter@YALE.ARPA>

    What does that floppy that came with my 4.0 s/w marked V4 Manditory Update
    (or something like that) do exactly?
It applies a total of 7 patches to various pieces of the system.  One of the
"patches" actually adds an image that is missing from the V4.0 kit.

					   What happens if I don't do it?
Depends on your processor.  780's have been known to overheat.  There are
reports that 785's, which use faster technologies, can explode.  No one has
dared to try this on a 8600.  Smaller VAXes, you should be ok on.

Seriously, "Mandatory" MEANS "Mandatory".  The system may not work, or it
may exhibit serious bugs.  It's expensive to create and ship the mandatory
update; if it were not the case that at least one patch on there was consi-
dered essential, DEC would not have gone to the expense and bother of produ-
cing it.  (If you installed VMS V3.0, left off ITS Mandatory Update, and
turned on DECnet, you would find that DECnet security was non-existent -
anyone could create a process with all privilege bits turned on, trivially.)

For the truely curious, I've attached the update record produced from instal-
ling the upgrade on a MicroVAX.

    Can I upgrade to 4.1 first, and then apply it?
In general, no.  Patches have to be applied in the right order, for obvious
reasons.  Further, even when no files are patched in both updates, it's
possible that the 4.1 update produces an image that assumes something in the
4.0 Mandatory has already taken place.

You might get away with it, but what's the point?

    Thanx,
    
    Ron 
							-- Jerry    

 1) DCL (patch image)

    ! DCL.EXE
    !
    !	ECO001	HWS			18-Sep-1984
    !		MODULE: STATUS
    !		Remove special handling of forced exit and exceeded cpu
    !		errors.
    !
    !
    !
    ! Patch STATUS
    !


 2) F11BXQP (patch image)

    ! F11BXQP.EXE
    !
    !	ECO01	(Used in VMS V4.1)
    !
    !	ECO02	ACG0470		27-Sep-1984
    !		MODULE: RWATTR
    !		Correct the file access checks related to ACL modification.
    !


 3) JOBCTL (patch image)

    ! JOBCTL.EXE
    !
    !	ECO01	JAK0001		20-SEP-1984
    !		MODULE: EXECUTOR
    !		Allow a process 5 seconds to be rundown before reissuing the
    !		forced exit call in the next higher access mode.


 4) NETACP (patch image)

    ! NETACP.EXE
    !
    !	ECO01	PRB0001		18-SEP-1984 21:35 
    !		MODULE: NETCONECT.MAR
    !		Use EPID, not IPID, in type 1 NCBs. This way, EPID will
    !		appear in SYS$NET.


 5) SDLNPARSE (new image)

    ! SDLNPARSE.EXE
    !
    !	ECO01	KDM0001		10-OCT-1984
    !		Provide image left off MicroVMS PROG kit.
    !


 6) SYS (patch image)

    ! SYS.EXE
    !
    !  ECO03	ACG0469		21-Sep-1984
    !		MODULE: SYSDASSGN
    !		When waiting for pending I/O to finish on a channel
    !		being deassigned, reverify the channel on each check.
    !		Failing to do so could result in the channel being
    !		deassigned twice, resulting in a negative reference
    !		count on the device.
    !


 7) VMSKITBLD (new file)

    ! VMSKITBLD.DAT
    !
    !	ECO01	KDM0001			10-OCT-1984
    !		Add SDLNPARSE.EXE to PROG_I option for MicroVMS.
    !
-------