🚀 go-pugleaf

I'd like to suggest the following changes to etc/MACHINES in Emacs,
for the description of Ultrix systems.  They take care of the
following things:

1. The description of X problems is moved from the "Machines" section
   to the "Systems" section, since it is not machine-dependent.

2. DEC MIPS machines are listed under "DEC", not "PMAX", which is
   really just a nickname.  (Though it is the name used for the m-
   file.)  I added the official DEC system names.

3. s-bsd4-3.h should not be used with Ultrix, at least up to Ultrix
   3.1.  I looked pretty carefully, and found only two significant
   differences between s-bsd4-2.h and s-bsd4-3.h.  They are:

   a. s-bsd4-2.h defines INTERRUPT_INPUT and s-bsd4-3.h undefines it.
      Ultrix does not correctly handle Meta-Delete (and perhaps other
      keystrokes) when it is compiled with s-bsd4-3.h.

   b. s-bsd4-3.h defines MAIL_USE_FLOCK.  The /bin/mail on Ultrix
      appears to use the old-style .lock files for mail, not flock.

   I hope someone else can confirm these observations.  etc/MACHINES
   currently says that s-bsd4-3.h works with Ultrix, so it would be
   useful to know why someone believed this.

Here are the changes:


*** MACHINES.old	Wed Jul 19 22:23:44 1989
--- MACHINES	Fri Dec 22 14:50:25 1989
***************
*** 59,66 ****
    They will be supported in the future.
  
! Ultrix
  
!   This is DEC's name for Berkeley 4.2.
  
  Uniplus 5.2 (s-unipl5-2.h)
  
--- 59,81 ----
    They will be supported in the future.
  
! Ultrix (s-bsd4-2.h)
  
!   This is DEC's name for Berkeley 4.2.  The 4.3 features that Emacs
!   uses are not yet supported correctly (as of Ultrix 3.1).
  
+   Ultrix 3.0 has incompatibilities in its X library if you have the
+   Ultrix version of X.  To solve them, you need to prevent XvmsAlloc.o
+   in Xlib from being used.  Israel Pinkas says:
+ 
+     I added the following lines to config.h after the X defines:
+ 
+     #if defined(ultrix) && defined(X11)
+     #define OBJECTS_SYSTEM calloc.o
+     #endif
+ 
+     Then I ran the following:
+ 
+     ar x /usr/lib/libc.a calloc.o
+ 
  Uniplus 5.2 (s-unipl5-2.h)
  
***************
*** 183,186 ****
--- 198,206 ----
    working in a newer version.  This has not been fixed.
  
+ DECstation 2100, 3100 (PMAX), DECsystem 3100, 5400, 5800 (m-pmax.h; s-bsd4-2.h)
+ 
+   These are DEC machines with MIPS R2000/R3000 processors.  Works, as
+   of 18.55.  (See notes on Ultrix above for use of X with Ultrix 3.0.)
+ 
  Dual running System V (m-dual.h; s-usg5-2.h)
  
***************
*** 409,416 ****
    Works as of 17.56.
  
- Pmax, Mips from DEC (m-pmax.h; s-bsd4-3.h)
- 
-   Minor changes merged in 18.55.
- 
  Prime EXL (m-intel386.h, s-usg5-3.h)
  
--- 429,432 ----
***************
*** 523,543 ****
    Works.
  
! Vax running Ultrix (m-vax.h; s-bsd4-2.h or s-bsd4-3.h)
! 
!   Works.  Note that "ultrix" is essentially 4.2 or 4.3, depending on version.
! 
!   Ultrix 3.0 has incompatibilities in its X library if you have the
!   Ultrix version of X.  To solve them, you need to prevent XvmsAlloc.o
!   in Xlib from being used.  Israel Pinkas says:
! 
!     I added the following lines to config.h after the X defines:
! 
!     #if defined(ultrix) && defined(X11)
!     #define OBJECTS_SYSTEM calloc.o
!     #endif
! 
!     Then I ran the following:
  
!     ar x /usr/lib/libc.a calloc.o
  
  Vax running System V rel 2 (m-vax.h; s-usg5-2.h)
--- 539,545 ----
    Works.
  
! Vax running Ultrix (m-vax.h; s-bsd4-2.h)
  
!   Works.  (See notes on Ultrix above for use of X with Ultrix 3.0.)
  
  Vax running System V rel 2 (m-vax.h; s-usg5-2.h)