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.
just wondering why it's such a bad idea for non-roots to have ./ in path?
For my part, simply because I am used to use ./ to execute scripts in current directory, say it is for a personal habit
I found that this would yield a null string for $PATH.
P.S. I do not know perl at all
Ok, I have a home directory with a 'bin' subdirectory which is in my PATH and if I consider a custom script stable, I put it here. So I used to do a difference between 'temp' scripts like, experiencing script, configure script from programs packages etc...
I simply used to ./ all scripts that are not in my PATH and I don't want to be able to execute them directly by their name.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.