On 10/15/06, juras256 <[EMAIL PROTECTED]> wrote:
Dan Nicholson napisał(a):
> On 10/14/06, juras256 <[EMAIL PROTECTED]> wrote:
>> Dan Nicholson napisał(a):
>> (...)
>> > I think you're right. It looks like we're missing something crucial in
>> > the host.def. I think you need to add
>> >
>> > #define HasPam
>> #define HasPam YES
>
> There's one more actually, used by the Xserver.
>
> #define HasPamMisc YES
>
> I'm not sure what it does, but I don't think you need it if you're
> just trying to control xdm.
After having added "HasPam" everything worked OK
However I didn't try 'startx' then.
I made another try: I added "HasPamMisc" - no difference in xdm.
Then I tried to issue 'startx' - pam refused telling me that I don't
have console ownership.
Right, that's becuase adding PamMisc links PAM into the xserver. If
you don't want it to work this way, leave out HasPamMisc. Then only
xdm will use PAM. It's up to you.
I had to write another pam file: /etc/pam.d/xserver
with auth and account sections.
auth required pam_localuser.so
account required pam_unix.so
Good. Just to warn you that running pam on the xserver seems to be
unusual. In the xorg-server package in Xorg-7.1, you can't link
against pam unless you manually add the libraries and flags to the
command line. You can't choose the option from configure. But if it's
working for you, great.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
