Summary: | New install, cant login: login: PAM Failure, aborting: Critical error - immediate abort | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Drake (RETIRED) <dsd> |
Component: | [OLD] Core system | Assignee: | Gentoo Release Team <releng> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | pam-bugs+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Drake (RETIRED)
2004-02-22 09:26:48 UTC
Got the same problem, applied the same solution... Stage 1 2004.1, portage 2.0.50-r6, gcc 3.3.2-r5, glibc 2.3.2-r9, kernel 2.6.5-r1 how is this a bug with releases? if -pam is set, then it would make sense that pam is borked ;) This was originally a misunderstanding of what pam was. I thought I didn't want it, but I actually do :) Either way - I didn't do anything special other than set the "-pam" USE flag. I bootstrapped, emerge system, did the usual, rebooted, and had a broken system. pam and pam-login had been merged presumably with the system packages, I hadn't specified them. The issue here is that if you install with USE="-pam" you'll have a broken system. Unless you intend users to "know what they are doing" and make the proper changes before rebooting, then perhaps this should be looked into? |