talexander
/
freebsd_amp_hwpstate
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
freebsd_amp_hwpstate/usr.bin/chpass/Makefile

26 lines
882 B
Makefile
Raw Normal View History

BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
# @(#)Makefile 8.2 (Berkeley) 4/2/94
PROG= chpass
SRCS= chpass.c edit.c field.c pw_copy.c pw_scan.c pw_util.c table.c util.c
BINOWN= root
BINMODE=4555
.PATH: ${.CURDIR}/../../usr.sbin/pwd_mkdb ${.CURDIR}/../../usr.sbin/vipw
CFLAGS+=-I${.CURDIR}/../../usr.sbin/pwd_mkdb -I${.CURDIR}/../../usr.sbin/vipw
Take the ypchfn/ypchsh stuff that was removed from passwd and graft it into chpass. Chpass can now tell when it's being asked to operate on an NIS user and it displayes the appropriate message in the editor template ("Changing NIS information for foo"). After the changes have been made, chpass will promte the user for his NIS password. If the password is correct, the changes are committed to yppasswdd. Hopefully, this should make NIS more transparent to the end user. Note that even the superuser needs to know a user's password before he can change any NIS information (such is the nature of yppasswdd). Also, changes to the password field are not permitted -- that's what yppasswd is for. (The superuser may specify a new password, but again, he needs to know the user's original password before he can change it.)
1995-08-13 16:12:28 +00:00
LINKS= ${DESTDIR}${BINDIR}/chpass ${DESTDIR}${BINDIR}/chfn
LINKS+= ${DESTDIR}${BINDIR}/chpass ${DESTDIR}${BINDIR}/chsh
LINKS+= ${DESTDIR}${BINDIR}/chpass ${DESTDIR}${BINDIR}/ypchpass
LINKS+= ${DESTDIR}${BINDIR}/chpass ${DESTDIR}${BINDIR}/ypchfn
LINKS+= ${DESTDIR}${BINDIR}/chpass ${DESTDIR}${BINDIR}/ypchsh
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
MLINKS= chpass.1 chfn.1 chpass.1 chsh.1
Take the ypchfn/ypchsh stuff that was removed from passwd and graft it into chpass. Chpass can now tell when it's being asked to operate on an NIS user and it displayes the appropriate message in the editor template ("Changing NIS information for foo"). After the changes have been made, chpass will promte the user for his NIS password. If the password is correct, the changes are committed to yppasswdd. Hopefully, this should make NIS more transparent to the end user. Note that even the superuser needs to know a user's password before he can change any NIS information (such is the nature of yppasswdd). Also, changes to the password field are not permitted -- that's what yppasswd is for. (The superuser may specify a new password, but again, he needs to know the user's original password before he can change it.)
1995-08-13 16:12:28 +00:00
COPTS+=-DYP
SRCS+= pw_yp.c
LDADD+=-lrpcsvc -lcrypt
Add a beforeinstall rule to turn off the immutable flag on chpass so you can install a new copy of it.
1994-05-30 14:03:53 +00:00
beforeinstall:
Take the ypchfn/ypchsh stuff that was removed from passwd and graft it into chpass. Chpass can now tell when it's being asked to operate on an NIS user and it displayes the appropriate message in the editor template ("Changing NIS information for foo"). After the changes have been made, chpass will promte the user for his NIS password. If the password is correct, the changes are committed to yppasswdd. Hopefully, this should make NIS more transparent to the end user. Note that even the superuser needs to know a user's password before he can change any NIS information (such is the nature of yppasswdd). Also, changes to the password field are not permitted -- that's what yppasswd is for. (The superuser may specify a new password, but again, he needs to know the user's original password before he can change it.)
1995-08-13 16:12:28 +00:00
[ ! -e ${DESTDIR}${BINDIR}/chpass ] || \
chflags noschg ${DESTDIR}${BINDIR}/chpass
Add a beforeinstall rule to turn off the immutable flag on chpass so you can install a new copy of it.
1994-05-30 14:03:53 +00:00
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
afterinstall:
Take the ypchfn/ypchsh stuff that was removed from passwd and graft it into chpass. Chpass can now tell when it's being asked to operate on an NIS user and it displayes the appropriate message in the editor template ("Changing NIS information for foo"). After the changes have been made, chpass will promte the user for his NIS password. If the password is correct, the changes are committed to yppasswdd. Hopefully, this should make NIS more transparent to the end user. Note that even the superuser needs to know a user's password before he can change any NIS information (such is the nature of yppasswdd). Also, changes to the password field are not permitted -- that's what yppasswd is for. (The superuser may specify a new password, but again, he needs to know the user's original password before he can change it.)
1995-08-13 16:12:28 +00:00
chflags schg ${DESTDIR}${BINDIR}/chpass
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
.include <bsd.prog.mk>