[SOLVED] executables in yptools package installed in different directory from what's specified in /var/yp/Makefile
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
executables in yptools package installed in different directory from what's specified in /var/yp/Makefile
The executables are installed in /usr/lib64/yp, but the make file expects them to be in /usr/lib/yp. I noticed this when I tried to build the NIS databases. Any reason for the directory mismatch?
This is a bug in Slackware64 that's been around for ages. I've reported it a long time ago, and I don't know why it hasn't been fixed yet. Here's a workaround:
I've seen the same issue and just modified /var/yp/Makefile at line 66 to read "YPBINDDIR = /usr/lib64/yp", but I've never been successful at actually getting yp to work, so take my advice at your own risk :P
When upgrading yptools using slackpkg, I was not offered the option to overwrite the existing files with the .new files. Shouldn't I have been given that option?
When upgrading yptools using slackpkg, I was not offered the option to overwrite the existing files with the .new files. Shouldn't I have been given that option?
If the files have the same MD5 hash, doinst.sh will automatically delete the .new versions during the upgradepkg process. It will check the following new files to see if they match with the existing files. If they don't match, then the .new files will remain in place.
I am not familiar enough with slackpkg to know when it will prompt for config files. It might occur on any slackpkg upgrade [package-name] or it might only occur when running slackpkg upgrade-all.
Either way, you can verify whether those .new files exist by running slackpkg new-config at any time.
I checked the file /usr/libexec/slackpkg/functions.d/post-functions.sh, which is run by slackpkg --new-config, and I noticed that only the /etc directory is searched for .new files: if I change the find command on line 125 from '... find /etc ..' to '... find /etc /var/yp ...', install-new then sees all the .new files in the yptools package.
I checked the file /usr/libexec/slackpkg/functions.d/post-functions.sh, which is run by slackpkg --new-config, and I noticed that only the /etc directory is searched for .new files: if I change the find command on line 125 from '... find /etc ..' to '... find /etc /var/yp ...', install-new then sees all the .new files in the yptools package.
Good catch! Might be worth mentioning on the stickied "Requests for -current" thread. Otherwise these might be missed if people do the upgrades with slackpkg or just assume that all .new files only occur within /etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.