Is it ok to create links between /usr/sbin and /bin binaries?
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.
Is it ok to create links between /usr/sbin and /bin binaries?
I normally use my slackware 9.0 box logged in as a normal user (ie; not root). I recently installed hping after executing an SU so that I could be the root user installing hping. I want to be able to use this program as a normally logged in user not root. However, the binary was installed in /usr/sbin thus making it available to root only. So I decided to create a symbolic link to this binary file from my /bin directory. Were there other methods I overlooked to accomplish the same thing? Any considerations?
Well, first see if your user has permissions to execute it --
/sbin/hping
If it works, then you can move it to the /bin or /usr/bin directory to have it in everyone's path.
There's really no reason to symlink it, and no reason to restrict access to root. Sudo would be an option, but I don't see how it's necessary. Simply mv it from one to the other.
I always add my default user to the 'wheel' group and then run visudo and give members of 'wheel' permission to run all commands(with or without password). You'll still have to give the full path in order to run stuff that's not in the users path, though. This is the easiest way to give yout own default user a little extra 'power' without having to run as root or 'sudo' each time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.