From: michael.auria@philips.com
Date: Mon Apr 14 2003 - 03:30:40 EDT
The turnkey systems we sell have been upgraded from 2.5.1 to Sol 8. One of
the things that we've been seeing is that once these systems are released to
the field, something happens where the custom dtwmrc menu we release in the
~/.dt directory gets set
to default. For now, our work-around is to copy our custom dtwmrc file to the
newly created "locale" directory (C/ or en_*/).
What I've seen so far is that a directory called C or en_* get's created in
the ~/.dt directory and this directory gets created w/a default dtwmrc. The
custom dtwmrc in ~/.dt doesn't get read anymore. This directory name seems to
correspond to the
Locale settings listed in the first option menu after a sys-unconfig.
Our sys-unconfig instructions tell our field people to use the C option
however since I also have seen en_*, I'm figuring that if the drive is
installled after the default jumpstart config (which I think uses one of the
en_* options), that some event
happens where the en_* directory is created and if the drive is
sys-unconfig'ed then since the locale of C was chosen that a C directory is
created when that event occurs.
Unfortunately, X / CDE is my Achilles heel; 2 questions. Can anyone help me
figure what is triggering this "locale" directory creation and/or what I can
do to prevent it or use it to my advantage. Even an RTFM pointer would be
appreciated at this point
:-)
Michael H.
Auria
800-232-2123 / option 3
Senior Technical Support
Engineer
fax: 408-965-2974
Philips Radiology Oncology Systems (formerly RTP) email:
pros.support@philips.com
Have you registered at the Customer Connection yet?
http://apps1.medical.philips.com
Countless, unseen details are often the only difference between mediocre and
magnificent ...t
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:11 EDT