by Setup: Sol8 (intel) Recent install from Media kit 4/01
I think I've uncovered a sinister plot to turn away non expert users
from running Sol8, at least in KDE gui... : )
Trying to discover the mechanics of a desktop login as regards
sourcing of init scripts, I began to read the contents of
~/.dtprofile.
It explains how the desktop sources ~/.profile/~/.login depending
on shell, and explains at some length how to enclose certain kinds of
code in `if' clauses to prevent it being used in GUI login but allow it
in console.
All this based on a test of boolean truth of a variable called DT.
I have not found a DT variable set after logging in.
And `if [ "$DT" ];then echo YES;fi'
Finds no value either. I see several variables displayed by `env'
that begin with DT.. but not sure which are reliable indicators.
Moving on to check error logs... maybe some clues there.
In ~/.dt/errorlog I find three entries all pointing to non existent
lines:
Tue Jun 19 09:50:48 2001
Workspace Manager: Invalid key specification on line 7 of
configuration file /home/reader/.dt/en_US.ISO8859-1/dtwmrc
Tue Jun 19 09:50:48 2001
Workspace Manager: Invalid key specification on line 8 of
configuration file /home/reader/.dt/en_US.ISO8859-1/dtwmrc
Tue Jun 19 09:50:48 2001
Workspace Manager: Invalid key specification on line 9 of
configuration file /home/reader/.dt/en_US.ISO8859-1/dtwmrc
The first 31 lines of /home/reader/.dt/en_US.ISO8859-1/dtwmrc are
commented out boilerplate.
The next 17 are more boilerplate but uncommented, none of which
contains any key specifications.
What are these errors pointing at?
So, where does one look for a non *y trapped unraveling of dt
login, init process.