Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!decvax!harpo!seismo!hao!hplabs!sri-unix!MBM@mit-xx From: MBM@mit-xx@sri-unix.UUCP Newsgroups: net.unix-wizards Subject: [James E. Kulp : [Jonathan Payne : Suspending login shell]] Message-ID: <4459@sri-arpa.UUCP> Date: Mon, 22-Aug-83 13:26:00 EDT Article-I.D.: sri-arpa.4459 Posted: Mon Aug 22 13:26:00 1983 Date-Received: Wed, 24-Aug-83 01:26:00 EDT Lines: 37 From: Michael B McIlrath Return-path: Received: from SCRC-HOUSATONIC by SCRC-TENEX with CHAOS; Mon 22-Aug-83 09:07:03-EDT Date: Monday, 22 August 1983, 09:07-EDT From: James E. Kulp Subject: [Jonathan Payne : Suspending login shell] To: Michael B McIlrath Cc: jek@SCRC-TENEX In-reply-to: The message of 22 Aug 83 08:13-EDT from Michael B McIlrath Date: 22 Aug 1983 0813-EDT From: Michael B McIlrath Date: Fri, 19 Aug 83 9:06:39 EDT From: Jonathan Payne Recently I was wondering why you can't detach yourself from the system, and then attach from somewhere else, like on tops-20. Then I remembered what csh says when you try to suspend your login shell: Can't suspend a login shell (yet). Does that mean somebody is planning to implement the equivilent of detach and attach? And would it be difficult? ------- I've thought about this a lot, since its the main outstanding UNIX network functionality lossage that I can think of. Unfortunately there is no appropriate data structure which can hold that state of a "session" after your carrier (virtual or otherwise) drops. The cheap way to do this is by creating a new software tty driver which is just a detached tty that doesn't do anything. The right way is to have a data structure called a session, but this would involve many global changes. But my days of making major changes to UNIX (and probably my ability to get them adopted by Berkeley) are over. I'm almost to the point of doing this (the former), since its so annoying. (Sometimes one more message is enough to get me going). -------