> Those will be user and distro specific in most cases. Suse,
> Arch and most others I know have put /opt package config files with the installs
> in /opt. All of my themes go in /opt/trinity/share/apps/tdm/themes and the tdm
> related configs go in /opt/trinity/share/config/tdm.

Same here, although the Slackware tradition is to create a sym link to /etc/trinity/tdm. On reflection, I don't know why changing those four keys made a difference. At the moment I think something else was the cause of the failure. I'll have to find another copy and test more methodically.

> I hope they are not hard coded in the code or we might just
> have found out why my tdm login for o2_enterprise, etc.. just quit working. Did
> you change the path information in the GIT tree??

No, only the active copy on my system. The only comment I can offer with certainty is themes did not work until after I grabbed an older copy of tdmrc and replaced the new copy.

From what I understand browsing through the code, the file paths are not fully hard-coded. They are defined like this:

{ "X-*-Core", "Setup", "%s/tdm/Xsetup",  0 },
{ "X-*-Core", "Startup", "%s/tdm/Xstartup",  0 },
{ "X-*-Core", "Reset", "%s/tdm/Xreset",  0 },
{ "X-*-Core", "Session", "%s/tdm/Xsession",  0 },

The tdmrc file needs to be generated during the build process and does not exist anywhere until generated using the gentdmconf command. There are several parameters that can be used. One of which is "--no-old" which then ignores xdm configurations. The traditional way of generating the tdmrc file in the Slackware build script:

$PKG${PREFIX}/bin/gentdmconf --no-old --no-old-scripts --no-backup --in $PKG/etc/trinity/tdm

Darrell