From owner-freebsd-embedded@FreeBSD.ORG Thu Aug 21 22:14:51 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4FDF1065678 for ; Thu, 21 Aug 2008 22:14:51 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 8754B8FC0A for ; Thu, 21 Aug 2008 22:14:51 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 5D4B21A9182 for ; Thu, 21 Aug 2008 15:06:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zZSkoWXiFGpA for ; Thu, 21 Aug 2008 15:06:41 -0700 (PDT) Received: from [10.0.0.40] (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id 359A71A90DE for ; Thu, 21 Aug 2008 15:06:41 -0700 (PDT) Message-ID: <48ADE8D6.1090906@miralink.com> Date: Thu, 21 Aug 2008 15:14:46 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: freebsd-embedded@freebsd.org References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com> In-Reply-To: <48ACAD2D.9090107@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: PAM errors with NANOBSD X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2008 22:14:51 -0000 Sean Bruno wrote: > Sean Bruno wrote: >> I seem to be stumped by my latest issue with NANOBSD. >> I can't login to the console due to missing pam libs and such. Any >> and all calls to sudo seem to be blowing up as well. I can only >> assume that something from my build system is causing pam to be >> configured. Even though I have explicitly set NO_PAM=YES in my >> NANOConf, I seem to be jamming up on pam. If I remove the NO_PAM >> entry, I get the same failure. So perhaps NO_PAM doesn't mean what I >> think it means? >> >> Anyone have a clue what the heck is going on here? >> >> ------------------------------------------------------------------------ > Here's an example from my last build. The system seems to boot fine, > but then is completely useless at startup: > > FreeBSD/i386 (Amnesiac) (ttyd0) > > login: root > Aug 21 07:50:22 login: in openpam_load_module(): no pam_unix.so found > Aug 21 07:50:22 login: pam_start(): system error > > FreeBSD/i386 (Amnesiac) (ttyd0) > > login: > > adding or removing "NO_PAM=YES" from the NANOBSD configuration has no impact on whether or not PAM get's built. So, I'm not sure what the heck is going on now. I mounted the diskimage on my system and verified that /usr/lib/pam_unix.so exists and is properly built. Any ideas as to why my disk image is acting like this? -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com Yahoo: sean_bruno@yahoo.com