[Info-vax] Looking into C-include files on VMS

[Joerg Schilling]

In article <7lgqknF3d7uatU8 at mid.individual.net>,
Bob Eager  <rde42 at spamcop.net> wrote:

>> The short answer is that it doesn't matter. Conformance with the current
>> POSIX standard would require system() to always call "sh".
>> 
>> This is the same on UNIX. UNIX has the equivalent of the UAF, you can
>> set the user's shell to an arbitrary executable, but system() still can
>> be counted on to call "sh".
>
>Yet the C standard appears just to say that the system "command 
>processor" shall be called...!

POSIX compliance is a superset of C compliance.

The POSIX standard requires that there is a way to switch the system 
into a mode where POSIX compliance is the default. POSIX compliance requires
system("command") to run command to be run via sh -c "command" where "sh"
has to be a POSIX compliant shell (this is a subset of "ksh93").

The documented was to start a POSIX compliant shell environment is to call:

	PATH=`getconf PATH`
	export PATH
	sh

If VMS has a way to switch into POSIX mode, then there must be a different shell
than bash as bash is not POSIX compliant and there must be a different way to
go into POSIX mode.


-- 
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
      js at cs.tu-berlin.de		(uni)  
      joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily