Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm working on some additions to an existing BLFS 8.2 system which should be using Linux-PAM-1.3.0 and Shadow-4.5. After installing these, I am unable to log in.
I have heeded the warning on the Shadow page to the letter, double-checking all of the configuration files from these two packages, and even recompiling both. I do notice, though, that the files in /etc/pam.d are all exactly one byte larger than the corresponding files in one of my other working systems.
Is there anything else I can check here before giving up and recompiling shadow without LibPAM?
Turns out this was due to the way I was testing it. This is for a headless setup and I was still chrooted. I had to wait until I got openssh / iptables going, boot up natively, and then ssh in as a regular user.
Indeed PAM locks you out if you chroot in as an ordinary user (chroot --userspec ...) and then try to get root. I'm not sure this is a bug or by design, but in any case I jumped the gun and tried to test it out too soon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.