Opened 21 years ago

Closed 20 years ago

Last modified 10 years ago

#322 closed defect (fixed)


Reported by: tushar@… Owned by: blfs-book@…
Priority: high Milestone:
Component: BOOK Version: ~CVS
Severity: normal Keywords:


The instructions for Installing Shadow post FAM should be changed to match LFS so that all files end up in the same location (Also, the patch should probably be renamed to shadow-4.0.3-PAM.patch):

patch -Np1 -i ../shadow-4.0.3.patch && autoconf && LDFLAGS="-lpam -lpam_misc" ./configure --prefix=/usr --libdir=/usr/lib \

--enable-shared --with-libpam &&

make && make install && ln -sf vipw /usr/sbin/vigr && rm /bin/vipw && rm /bin/groups && mv /bin/sg /usr/bin && mv /usr/lib/lib{shadow,misc}.so.0* /lib && ln -sf ../../lib/ /usr/lib/ && ln -sf ../../lib/ /usr/lib/ && cp debian/securetty /etc/securetty

Change History (7)

comment:1 by tushar@…, 21 years ago

sed -e "s:FAM:PAM"

comment:2 by larry@…, 20 years ago

Resolution: fixed
Status: newclosed

comment:3 by larry@…, 20 years ago

Resolution: fixed
Status: closedreopened

The recompile of shadow with PAM fails with autoconf-2.57. It aborts on "make install" in the po directory OR installs libraries without the *.so.0*. One reporter used autoconf-2.54 and instructions worked.

comment:4 by tushar@…, 20 years ago

Maybe it needs the same fix as libfam: libtoolize --force && aclocal && automake --add-missing && autoconf

comment:5 by larry@…, 20 years ago

Did not work, but neither did dropping to autoconf-2.54. Going to try libfam and verify it works with the LFS CVS autoconf/libtool/automake.

comment:6 by larry@…, 20 years ago

Resolution: fixed
Status: reopenedclosed

comment:7 by bdubbs@…, 10 years ago

Milestone: old

Milestone old deleted

Note: See TracTickets for help on using tickets.