perms on file linux redhat 9 filepro 5.0

[Fairlight]

In the relative spacial/temporal region of
Tue, Jun 08, 2004 at 01:17:47PM -0400, Brian K. White achieved the spontaneous
generation of the following:
> 
> I _never_ said replace bash with ksh. Especialy not in-place.
> I advise simply to _use_ ksh.

Knowing firsthand how annoying it is to be misattributed, I apologise and
retract.  My mistake.

> Bash on linux is an annoying perversion in that it doesn't act like everyone

IYO.  I never have a problem with it because I don't use Bourne-esque
shells in general.  Even root uses tcsh on my systems.

> stuff. Just as if you were to remove /bin/sh from a sun or sco box and make
> it a symlink to bash. Linux's "sh" scripts are really all broken "bash"
> scripts that need bash specifically, but say they want "sh".

*shrug*  If it works, I don't give a fieg.  :)  The shell purists can
thrash it out to their hearts' content--I'm -already- odd man out because I
prefer csh variants.  It's very convenient to be automagically librated
from having to argue the merits of which 'sh' is best.

It's Linux, not UNIX[tm], and bash has come with the territory in 99% of
the dists since time immemorial.  Get over it.  :)  (Actually, it's GNU's
bash, but most linux systems are largely GNU-based.)  If you have problems
with bash, best bet is to go back to bash 1.14, based on the release notes
that say it is compatible with more legacy code that won't work with v2.
That should also fix the EUID issue for fP, actually, as that came about in
the v2 releases.
 
mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html