filepro and file permissions

[Fairlight]

In the relative spacial/temporal region of
Fri, Apr 27, 2007 at 07:46:36PM -0400, Bob Stockler achieved the spontaneous
generation of the following:
> 
> When I had a Linux system running, as I recall, linking /bin/sh to
> /bin/pdksh, rather than to /bin/bash, screwed up booting Linux.

Greaaaaaaat.  *sigh*  Was actually going to try that with a system, but now
I think, "Not so much."

> Maybe linking /bin/sh to /bin/ksh (the Real KornShell, which is available
> for -free-)  might work for filePro -and- booting Linux.

Depends if it was pdksh that's limited in ability, or if linux relied on
bash-isms.

> Maybe it would be so simple as having filePro recognize the environmental
> parameter SHELL for executing its programs, rather than just defaulting to
> /bin/sh, and SHELL could point to any shell that suited the user's needs.
> 
> Bob (whose environment includes SHELL=/bin/ksh)

TTBOMK, that only works for programs that just fork/exec off -only- the
shell when you type "!" or whatnot.  The system() function in C uses
/bin/sh to launch its argument list independant of what shell you're
running.  I run tcsh, my env says tcsh, and yet /bin/sh is -always- used
for system() calls.  Really, this is tightly bound to how system() is
written in libc, not anything filePro is doing internally.  Short of
changing models so that they don't use system(2), which would be pretty
complex and a bad ROI given the marginal gain in functionality from their
perspective, there's not much to be done for it.

mark->
-- 
No matter what your problems, modern medicine can help!
http://members.iglou.com/fairlite/fixital/