13 Jan
2012
13 Jan
'12
8:06 p.m.
On 13/01/2012 19:52, Darrell Anderson wrote:
Thanks Darrell, sometimes I just can't see the obvious and the kdebase
prompt has, I'm sure, pointed me in the right direction.
Cheers,
Mike.
--
Michael Howard mike at dewberryfields dot co dot uk
Lancashire
England
When building
and installing TDE from scratch on a clean,
'X'-less system, how do I get authentication working? I
assume that TDE just passes on the task to the underlying
OS. However, having done a clean build I don't know how to
get the necessary configuration and auth bits in place, like
Pam modules, init scripts etc. When you install from
packages it's all taken care of.
I can (and will) hack about to create the above but just
wondered if there was something ready rolled.
I don't know how much I can
help. I work with Slackware, which does not use PAM.
I build all of my packages in an X-less chroot build environment. I never had any problem
logging into Trinity. With that said, perhaps there is something specific you are seeking
that I'm not seeing. :)
Trinity works with the underlying login authentication process. If you are having
problems logging into Trinity, possibly the correct build options are not being set in
your kdebase build script? For example, in Slackware I use -DWITH_SHADOW=ON and
-DWITH_PAM=OFF, but with Debian set that last option to ON.
Additionally, check your KDM configuration settings: Control Center, System
Administration, Login Manager.
Darrell