hi simon, i faced the same problem.the pam.d directory was corrupted and i could'nt log on.i solved it by booting into fedora,and then rewriting the files in the pam.d directory from the chroot environment. this is a much better solution though.rather prevent a problem than fix it!!
On 3/26/07, Simon Geard <[EMAIL PROTECTED]> wrote:
For anyone interested, Shadow 4.0.18.1 (just gone into LFS) has an annoying little feature I've just discovered. If built with PAM, it installs default configs into /etc/pam.d, which do things like *require* pam_selinux.so. Basically, it'll break the PAM installation, giving you a system without a working login command. So, I've disabled this by running the following command, not sure if it's the preferred solution. Something like it probably should go in BLFS when it upgrades Shadow though... sed -i 's/pam.d//' etc/Makefile Hoping this helps save other people a bit of grief... Simon. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
