Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!sri-spam!mordor!lll-tis!ptsfa!ihnp4!ihwpt!knudsen From: knudsen@ihwpt.ATT.COM (mike knudsen) Newsgroups: comp.sys.m6809 Subject: Re: Remote terminal in Level II Message-ID: <1789@ihwpt.ATT.COM> Date: Mon, 6-Jul-87 13:30:50 EDT Article-I.D.: ihwpt.1789 Posted: Mon Jul 6 13:30:50 1987 Date-Received: Tue, 7-Jul-87 06:21:27 EDT References:Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 30 Summary: I understand the problem but can't fix it > I'm trying to set up a remote terminal to work through /t2 on a CoCo III, 128K, > level II system. I have the following commands in my /dd/startup file: > xmode /t2 baud=7 > date t>/t2 > ex shell i=/t2 > Whenever I do this though the original shell doesn't go away. It waits for > me to send it a signal, then it wakes back up. I though the ex should've taken > care of that! I believe this is yet another limitation of the way OS9 executes shell script files. Your bootup shell creates a sub-shell to run the startup file. Your EX gets rid of that subshell, but the parent shell is still alive & well as you noted. This same problem has kept me from putting CHD and CHX commands in startup files. They work great for the rest of the file script but apply only to the subshell, so you're back to the defaults after the file is finished. UN*X fortunately has a special '.' operator that means "don't run this in a subshell; do it exactly as if I were typing it on /TERM." Maybe OS9/68K has, or will get, this feature -- not holding my breath for 6809 version, but would love it. -- Mike J Knudsen ...ihnp4!ihwpt!knudsen Bell Labs(AT&T) Delphi: RAGTIMER CIS: "Just say NO to MS-DOS!"