NXHost, Mach Ports

Article View: comp.sys.next.sysadmin

Article #1442

Back to comp.sys.next.sysadmin Previous Next

#1442

From: Geoffrey S Knauth
Date: Mon, 12 Oct 1992 12:20

23 lines
1492 bytes

In article <BvyM8w.Iqy.2@cs.cmu.edu> beatty+@cs.cmu.edu writes:
> I wasn't trying to say that NXHost over SLIP was made slow
> intentionally.  I was trying to say that it might be deliberately hard
> to make it work at all.  So far as I know, to NXHost over SLIP, you
> have to have the same IP address for both the ethernet and the slip
> interfaces, and to make that work, you have to rather carefully adjust
> the routing tables, in the case of a standalone machine.

Aha.  Now I get you.  Several months ago, Ray Bloom <ray@marble.com>
came up with the same solution you did.  This solution is required any
time MACH PORTS are involved.  Information presented to Mach Ports
circulates via en0, the single ethernet interface on a NeXT computer.
Mach Port data doesn't route.

> Making it hard to set up NXHost over SLIP (not the speed) could have
> been a design decision at NeXT, Inc.

I doubt this.  I truly think it was an oversight.

Geoffrey
-- 
Geoffrey S. Knauth, Marble Associates, Inc.                Member BCS-NeXT, LPF
gsk@marble.com, (617) 891-5555 work, (617) 547-5247 home   Standard Disclaimers

Technical Details

Message-ID: <Bw0Cxt.6ur@world.std.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!world!gsk

References: <Bvy9vq.6s4@world.std.com> <BvyM8w.Iqy.2@cs.cmu.edu>

Show Full Headers

Complete Article Headers

Newsgroups: comp.sys.next.sysadmin
Path: arc1-ca.pugleaf.net!sparky!uunet!world!gsk
From: gsk@world.std.com (Geoffrey S Knauth)
Subject: NXHost, Mach Ports
Message-ID: <Bw0Cxt.6ur@world.std.com>
Organization: The World Public Access UNIX, Brookline, MA
References: <Bvy9vq.6s4@world.std.com> <BvyM8w.Iqy.2@cs.cmu.edu>
Date: Mon, 12 Oct 1992 12:20:17 GMT
Lines: 23

Reply to Parent Message