GRASS on NeXT. Anyone?

[Allan B Branscomb]

At present we are stalled in our effort to run GRASS 4.0 on the NeXt due to a
bug in the maknod function.  This funtion is used, among other things, for
creating the 'named pipes' by means of which GRASS communicates with 
X-windows (via inter-process communication - IPC).  In many UNIX's, including
Sun OS, maknod is available as a command. In the case of MACH it's available
only as a procedure, which isn't the problem.

The problem is that once the pipes are created MACH does not properly
initialize the data structures between uses.  NeXt has said they may fix it in
the forthcoming release of MACH, maybe not.

Clearly there are several ways to work around this problem, but we haven't had
the time or inclination to develop one.

This concerns the NeXt as a server, but what about when it's just a client? 
You could run GRASS on a system that didn't have the maknod problem and perhaps
still use the NeXt as the display/control station.  We plan to try this out in
the next few weeks.

allan