On Wed, Nov 08, 2017 at 09:13:34AM -0500, Mark Gregory wrote:
> On 11/06/2017 03:00 PM, [email protected]
> wrote:
> > checking for pam_getenv in -lpam... no
> > checking security/pam_modutil.h usability... yes
> > checking security/pam_modutil.h presence... yes
> > checking for security/pam_modutil.h... yes
> > checking security/pam_ext.h usability... yes
> > checking security/pam_ext.h presence... yes
> > checking for security/pam_ext.h... yes
> > checking for pam_syslog in -lpam... no
> >
> > The two lines ending in "no" appear to be the problem. What do I need
> > to look at to diagnose / fix this?
> >
> > Thanks,
> >
> >> Hi Mark,
>
> >> looking at my own logs I agree that the two 'no' items are the
> >> problem. When we install Linux-PAM, after 'make install' we run
> >> chmod and then we move some libraries from /usr/lib to /lib, and
> >> finally we make symlinks to them from /usr/lib.
> >>
> >> I guess some or all of your symlinks are broken : try running 'file'
> >> on them to see if that reports breakage.
> >>
Just to be clear, this is what a working install results in:
/usr/lib/libpamc.so: symbolic link to ../../lib/libpamc.so.0.82.1
/usr/lib/libpam_misc.so: symbolic link to ../../lib/libpam_misc.so.0.82.1
/usr/lib/libpam.so: symbolic link to ../../lib/libpam.so.0.84.2
> >> If the symlinks are indeed broken, please review what you did in the
> >> last install of Linux-PAM. The instructions in the book should
> >> work. And to fix that : if you can login with PAM then what is in
> >> /lib should be fine, so just recreate the symlinks from /usr/lib for
> >> each of libpam*.so.
> >>
>
> Ken,
>
> Thank you for the reply. I tried running 'file' but don't know enough
> about it to interpret what I was seeing. While researching 'file' I
> ran across 'find', which seemed to turn up something that to me appears
> might be important. Below is the command line, and results:
>
> mark [ /usr/lib ]$ find -L ./ -mindepth 15 | grep find:
> find: './libpam_misc.so/libpamc.so.0': Too many levels fo symbolic links
> find: './libpam_misc.so/libpam.so.0': Too many levels fo symbolic links
> find: './libpam_misc.so/libpam.so.0.84.2': Too many levels fo symbolic links
> find: './libpam_misc.so/libpamc.so.0.82.1': Too many levels fo symbolic
> links
Errk. How did /usr/lib/libpam_misc.so become a directory ?
> I did a "sudo make uninstall" in the Linux-PAM source directory, which
> removed the /usr/lib "libpam" files, but I am uncertain about what to do
> with the "libpam" files in /lib. Can I safely remove them using "rm
> -rf" without breaking something? My thinking is that I should remove
> them and then reinstall Linux-PAM, followed by reinstalling Shadow.
>
> Am I on the right track? I have learned a lot in this trek through LFS
> and into BLFS, so would like to continue.
>
> Regards,
>
I would take the simple approach: keep the files in /lib, as I said
earlier - you have managed to login, so those files are ok.
When we move the libs, we use readlink - fine for the first time,
but a source of problems if run a second time. The easiest fix is
ln -svf /lib/libpamc.so.0.82.1 /usr/lib/libpamc.so
ln -svf /lib/libpam_misc.so.0.82.1 /usr/lib/libpam_misc.so
ln -svf /lib/libpam.so.0.84.2 /usr/lib/libpam.so
ĸen
--
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
- Unseen Academicals
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
