🚀 go-pugleaf

In article <62468@pyramid.pyramid.com> csg@pyramid.pyramid.com (Carl S. Gutekunst) writes:
| In article <368@pbseps.UUCP> rdp@pbseps.PacBell.COM (Richard Perlman) writes:
| >System V seems to be only half-heartedly implemented.
| 
| That's not quite fair. Essentially, the Dynix att universe is a mapping layer
| for translating SVR2 semantics into 4.2BSD. A combination of the following
| hooks are employed:

[ discription of the SVAE (System V Application Environment) deleted]

| But I wouldn't call news(1) a "simple thing." Neither the Dynix version nor
| the original SVR2 source works (I tested it myself); it doesn't find any news
| files. The problem is news.c does its own read and scan of the /usr/news
| directory. Dynix cannot (at least, it better not!) manipulate what a program
| gets when it reads a raw directory. And of course, Dynix uses the BSD file-
| system, which doesn't look much like a System V filesystem. 
| 
| So news.c either has to be fixed to use dirent.h (as it does in SVR3) or con-
| verted to read BSD directories. Note that any other machine that uses the BSD
| filesystem will have exactly the same problem, including Pyramid and Sun.
| 
| <csg>

On the contrary, the kernel performs what is called "directory emulation".
Any program using the SystemV read system call to read a directory, gets
a directory formatted with 14 char names.  I think the problems with
news(1) is somewhere else.

Sequent does read the net on a regular basis but maintains a low profile.
-- 
Phil Hochstetler		UUCP:  uunet!sequent!phil
Sequent Computer Systems
Beaverton, Oregon