Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!mordor!sri-spam!sri-unix!hplabs!cae780!amdcad!sun!dlb!auspyr!sci!phil
From: phil@sci.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Patch Command.Com
Message-ID: <1752@sci.UUCP>
Date: Thu, 12-Feb-87 23:06:19 EST
Article-I.D.: sci.1752
Posted: Thu Feb 12 23:06:19 1987
Date-Received: Sat, 14-Feb-87 19:41:56 EST
References: <380@neoucom.UUCP> <75800019@uiucdcsp>
Organization: Silicon Compilers Inc., San Jose, Calif.
Lines: 19
Summary: real meaning of /p

In article <75800019@uiucdcsp>, vanzandt@uiucdcsp.cs.uiuc.edu writes:
> 
> 
> 	As I understand the /p parameter with the shell command it is
> to be used in conjuction with the /e:nn (set environment size) to signify
> that this is a "permanent" addition to the environment setting. Maybe they
> mean that each child shell should inherit the same environment when the
> /p parameter is specified???...



The actual meaning of /p is PERMANENT. 
It instructs command.com, or whatever shell you might be loading,
that it is the first and master shell and that it should NEVER exit.
It has nothing to do with environment.
As far as I can tell, the increase in environment size for /e is not
passed on to a sub-shell
BUT you do seem to be able to do /e for the command "command" so as
to enlarge environment space for a sub shell!