BS> Yes it looks hardcoded, gotta find the place where it's.. Anyway I
 BS> wouldn't matter mutch as long as you have symlinks in Linux ;-)

 MT> I would consider it a "design decision" and not dink 
 MT> with it.  That warning's been in the docs since 2.0x.  
 MT> The Linux port might not operate correctly with 
 MT> existing CTLs which have both according to "Scott's 
 MT> rules" if you ignore the case sensitivity where it 
 MT> already exists.

With Wes's decision to put a number of configuration files in /var/max/etc
instead of /var/max (by default), there are already a number of items that
don't work exactly like the DOS, OS/2 and Win32 version.  Also, the current
path "kludge" fix has left me needing to use full path
specifications in places where I should be relative to either /var/max or
/var/max/etc, but I haven't gotten relative paths to work....  I've ignored
the problem so far by having full paths specified in places that I normally
wouldn't.....

File case names is another area that gets interesting.  Under OS/2 using
HPFS partitions, you see some of the interesting CASE usage that Scott
implemented.  But I believe it wasn't always consistant.  Since the DOS,
OS/2 and Win32 code was at best case insenstive (at worst, forced to all
upper case by the OS file system), this didn't matter (or get caught in
debugging) on those platforms.  It does catch us on the Unix / Linux
platforms, where file names are (normally) case sensitive....

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01