Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.mail.uucp
Subject: Re: Bidirectional Modem Lines under SunOS 4.0.1
Message-ID: <1438@auspex.auspex.com>
Date: 15 Apr 89 07:20:27 GMT
References: <160@osc.COM> <743@key.COM> <2209@laidbak.UUCP> <1423@auspex.auspex.com> <3834@ficc.uu.net>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 17

>init execs getty; getty execs login; login calls back and execs the real
>login. There's some reason I have to have the parent of 'sh' be init, though
>I don't recall what it was, it didn't work if it wasn't done that way.

In that case, your "sh", or something, is broken.  The SunOS version
doesn't have this problem; otherwise, neither "rlogin" nor TELNET would
work very well, since the login shell on a remote login is a child of
the rlogin or TELNET daemon, not a child of "init".

For that matter, "ct" won't work very well, either, on a system that
demanded that the parent of a login shell be "init".  (In the future it
is possible that *no* login shells will be children of "init" on some
systems.)

I'm sorry you have a broken system, but that hardly renders SunOS-style
dialin/dialout schemes unusable, except on broken systems such as the
one you have.