Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!cuae2!ihnp4!ihwpt!knudsen
From: knudsen@ihwpt.UUCP (mike knudsen)
Newsgroups: net.micro.6809
Subject: CHX, CHD in OS9 startup?
Message-ID: <991@ihwpt.UUCP>
Date: Mon, 21-Jul-86 13:00:33 EDT
Article-I.D.: ihwpt.991
Posted: Mon Jul 21 13:00:33 1986
Date-Received: Tue, 22-Jul-86 00:49:27 EDT
Distribution: net
Organization: AT&T Bell Laboratories
Lines: 28

Is there a simple way to put chd and chx commands in
the startup file (the shell script that OS9 runs auto'ly
on bootup), such that the effect of these commands will still
be felt after the startup file has bben executed?
Shell scripts, including startup, run under subshells, so
any chd/chx normally has effect only for the duration of that
script.
	What I want is to make bootups easier on my wife's new
Coco, which she will use strictly for word-processing with
OS9 Dynastar & Dynaform.  The working commands directory is on
another disk drive, not /d0/cmds.
	One possibility that occurs to me is to end the startup with
"exec shell </TERM" and hope that the subshell created for this
will inherit the new paths.  Seems to me I already tried something like
it though.
PS: I'm disappointed by James Jones' revelation that the C fcn library
code is so inefficient, apparently not written in assembler in the
first place.  On the other hand, it's nice to know there's another
opportunity for speedup.	--mike k
-- 
Mike J Knudsen  __   ...ihnp4!ihwpt!knudsen
              / NO \
Bell Labs    / BABY \   (312)-979-4132 (work)
 (AT & T)   /ON BOARD\
            \GO AHEAD/
IH 6D-319    \ & HIT/
x4132         \ ME /
                --