On Tue, 15 Dec 1998 [EMAIL PROTECTED] wrote:
> Ok assuming you can do 3 __where__ is the standard place for the property files
> per user per machine? I think it is best to write a software installer program
> to do this task. It would write the property file to `user.home' say and the
> main application would know where to look for it and load that file and make it
> a environment settings default.
>
There is a convention on unix that user's config stuff ins written in ~/
with the result my home directory's become littered with dozens of .*rc
files.
I've settled on putting mine in ~/etc/
You can find the home directory from the system properties and build a
valid directory name for the runtime environment using other information
there. I don't know what MACs impose, but on OS/2 it's reasonable to assume
long file names (HPFS is optional, but lots of other software requires it
possibly including java: I have OS/2 plus java, but as I have no FAT
partitions the question didn't come up. NT's NTFS also allows long names:
neither's case sensitive though so AB.DATA = ab.datA. Don't know the rules
for WIN9x, but I assume that it's compatible in this respect with NT.
>
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
