Date: Thu, 21 Aug 2008 15:14:46 -0700 From: Sean Bruno <sbruno@miralink.com> To: freebsd-embedded@freebsd.org Subject: Re: PAM errors with NANOBSD Message-ID: <48ADE8D6.1090906@miralink.com> In-Reply-To: <48ACAD2D.9090107@miralink.com> References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48ADE8D6.1090906>