<<< VMSZOO::DISK$NOTES:[NOTES$LIBRARY]VMS_POSIX.NOTE;2 >>>
                     -< POSIX for OpenVMS - Public forum >-
================================================================================
Note 1306.0                 Posix 2.0 legacy on V7.0                  No replies
MUCTEC::BECKER "Hartmut B., VMS & Languages, Munich" 35 lines   6-MAR-1996 09:03
--------------------------------------------------------------------------------
The Release Notes for V7.0 are incomplete, they say:

     (VAX) If you try to start ... version 2.0 ... the system will crash ...

There is no problem with starting there are system loadable images which
cause the crash of the system.

%EXECINIT-E-LOADERR, error loading <SYS$LDR>POSIX$KERNEL.EXE status = 00002398

%SYSINIT-W- Couldn't load POSIX$CFS_SERVICES
 %SYSINIT-E-error loading  <SYS$LDR>POSIX$CFS

**** OpenVMS (TM) Alpha Operating System V7.0     - BUGCHECK ****
** Code=0000036C: PROCGONE, Process not in system ...

$ exit %x00002398
%SYSTEM-W-SYSVERDIF, system version mismatch; please relink
$ exit %x0000036C
%SYSTEM-F-SHMGSNOTMAP, shared memory global section not mapped during creation

Obviously it's not only VAX.

There should be mentioned that the only supported way to circumvent this is
to remove the product with PRODUCT REMOVE POSIX (hmm, that's what I know
will work on Alpha, I'm not sure if there is a PCSI kit for VAX).

If someone is already trapped he has to manually remove some images from the
VMS$SYSTEM_IMAGES.DATA base. To get the system up it should be sufficient
to rename the database. Later he can remove the loadable images with:

	SYSMAN> sys_loadable remove _local_ posix$kernel
	SYSMAN> sys_loadable remove _local_ posix$cfs_services
	@SYS$COMMON:[SYSUPD]VMS$SYSTEM_IMAGES.COM

Hartmut