From owner-freebsd-current Thu Mar 7 8:49:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id DDD8037B41A; Thu, 7 Mar 2002 08:49:28 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA83234; Thu, 7 Mar 2002 18:49:17 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h182.229.dialup.iptcom.net [212.9.229.182]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id SAA84102; Thu, 7 Mar 2002 18:49:14 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g27Gm3B13569; Thu, 7 Mar 2002 18:48:03 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C8799F2.13E4E3F6@FreeBSD.org> Date: Thu, 07 Mar 2002 18:48:50 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Mark Murray Cc: des@FreeBSD.org, current@FreeBSD.org Subject: Re: 5-CURRENT source upgrade path is broken in PAM References: <3C878A9E.C07C6056@FreeBSD.org> <200203071555.g27FtWRV022137@grimreaper.grondar.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit 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 Mark Murray wrote: > > > Bah, just completed `make world' after doing `make includes' and found > > that I can't login as *any* user, not only root!!!!!!! Login just > > hangs after entering password and nothing goes on. DES! PLEASE FIX > > THAT FSKING PAM - within a very short timeframe it's the second time > > I'm having problems due to it and this just isn't acceptable even for > > -current. > > That is _my_ fault, not DES'. It was a crypt() problem which I have fixed. Ok, I see now. Could we please make a rule to send a heads-up in such cases (i.e. in the cases when some serious misbehaviour was introduced and then fixed shortly). This would save me (and probably others) roughly a hour that I spent debugging what's going wrong. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message