I have just completed a fresh installation using the experimental stuff: gentoo-2004.0-x86-20040204.iso for installation, stage1-x86-20040204.tar.bz2 as stage file. I have run into a second showstopper here (see #42461 for the first one). After completing an installation and rebooting, I get the following login trouble: fireblade login: root login: PAM Failure, aborting: Critical error - immediate abort I have a suspicion that this is because pam and pam-login were merged, but as I had the USE flag unset (USE="... -pam ...") it hasn't configured pam properly. To fix this I booted from the livecd, mounted partitions, chrooted, unmerge pam & pam-login, remerged shadow. Reproducible: Always Steps to Reproduce: Portage 2.0.50-r1 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.2-r9, 2.6.3) ================================================================= System uname: 2.6.3 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.3.13 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-tbird -O2 -pipe -mmmx -m3dnow -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-tbird -O2 -pipe -mmmx -m3dnow -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc fixpackages sandbox" GENTOO_MIRRORS="http://192.168.0.1/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://212.219.247.10/sites/www.ibiblio.org/gentoo/ http://212.2 19.247.11/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://192.168.0.1/gentoo-portage" USE="3dnow X apm arts avi crypt cups encode foomaticdb gdbm gif gpm gtk gtk2 imlib jpeg libg++ libwww mad mikmod mmx motif mpeg mysql ncurses oggvorbis o pengl pdflib perl png python quicktime readline samba sdl slang ssl svga tcpd truetype x86 xml2 xmms xv zlib"
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?
