From owner-freebsd-current Sun Oct 6 23:45:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DC0D37B401 for ; Sun, 6 Oct 2002 23:45:28 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A67CC43E77 for ; Sun, 6 Oct 2002 23:45:27 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g976ivOo047973; Mon, 7 Oct 2002 02:44:58 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 7 Oct 2002 02:44:57 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: suken woo Cc: freebsd-current Subject: Re: xdm can not login on current In-Reply-To: <3DA11221.90603@mail.gddsn.org.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 7 Oct 2002, suken woo wrote: > xdm broken on current when login . i knew this is the pam module > problem,but how could i fix it? Chances are, you built your X11 with an old -CURRENT system, and since then the ABI for the PAM stuff has changed in -CURRENT, so your old X11 no longer talks happily with your new PAM. Remove and rebuild X11 (specifically xdm) and see if that helps. Of course, you don't provide any real details as to what the failure mode is, making this a little hard to debug. You might want to take a look at /var/log/messages and see if xdm gives any specific errors. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message