Date: Sun, 24 Aug 2008 11:52:02 -0700 From: Sean Bruno <sbruno@miralink.com> To: freebsd-embedded@freebsd.org Subject: Re: PAM errors with NANOBSD Message-ID: <48B1ADD2.1080507@miralink.com> In-Reply-To: <48ADE8D6.1090906@miralink.com> References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com> <48ADE8D6.1090906@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean Bruno wrote: > 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? > Ok, this is excruciating. I can only assume that I am doing something so completely wrong that it is befuddling the build system and it's not generating an error that would be meaningful. I am using a RELENG_6 build machine to build a RELENG_6 image and I can't seem to figure out what is generating this non-sense PAM error. I'm certain that the correct libs are in place and that everything is being built without errors. Is anyone else using RELENG_6 with NanoBSD right now? This worked pre-6.3 and I can't see anything that would be causing this type of absolute failure. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Cell 503-358-6832 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48B1ADD2.1080507>