🚀 go-pugleaf

In article <991@ihwpt.UUCP>, knudsen@ihwpt.UUCP (mike knudsen) writes:
> Is there a simple way to put chd and chx commands in
> the startup file 
> such that the effect of these commands will still
> be felt after the startup file has bben executed?
> -- 
> Mike J Knudsen  __   ...ihnp4!ihwpt!knudsen

Starting a shell from inside the startup file will work.  You can
change directories and start a shell but be sure to redirect standard 
input for it.  The only problem I remember having with this approach is
that if you pop out of the shell (with an EOF) you get back to the startup
file and wind up in a shell that hasn't been chd'd.

Using tsmon is another trick.  The password file lets you specify directories
and an initial program to execute (typically shell).

If you want to go back to the beginning you can fuss with init and
(perhaps) sysgo.  The default directories and program for the system
are given in init.  Sysgo looks at init and gets things going.  On my 6809
system I use sysgo to change the execution directory and system disk from
/d0 to /h0 after the system is mostly booted.  OS9boot is on /d0, but
everything else (CMDS and startup) is on /h0.

Peter Dibble