mprime not being recognized on ubuntu 16.04

[Dubslow]

Originally Posted by ATH

I always thought that it is more logical to first search in the folder you are currently in before looking everywhere else on the system. But that might be because I am a Windows guy.

An analogy is that you check all your pockets for a missing item without checking what you are actually holding in your hand.

It is considered a major security risk on *nix. https://superuser.com/questions/1565...ath-by-default

[M344587487]

Originally Posted by ATH

I always thought that it is more logical to first search in the folder you are currently in before looking everywhere else on the system. But that might be because I am a Windows guy.

An analogy is that you check all your pockets for a missing item without checking what you are actually holding in your hand.

A properly configured nix system is beautifully ordered, it makes sense to me that you can trust in that order. With the quagmire that is windows registry, multiple directory trees and who knows what else, I'm surprised the laptop I'm typing this on doesn't implode as I type :P

[LaurV]

Originally Posted by Dubslow

It is considered a major security risk on *nix. https://superuser.com/questions/1565...ath-by-default

Which is extremely silly, and easy to cheat, that is nothing "major" in it, and it restricts the "liberty" of the user, in the sense that in windoze I can put all my tools in the current folder and run them *locally* from there without having any idea of other files existing in the system or path that may have same names and do different things. Having tools with the same name in the path, that will execute *before* my tools I put in my folder, THAT is a security risk! The job of restricting my local tools to accessing other things than my folder, etc., it the job of the operating system. The fact that both the *nix and windoze make a very lousy job here, this is another discussion. But even if you think C++ and variant, every "class" has its own local, private methods, which are executed from inside the class, before other global methods with the same name be executed. THIS is secure. It should work in the same way as with the processes, where a "local" process can not access the "protected" or "private" memory of "global" processes. So, let me run my local tool, called "ls" or "dir" or "cat" or whatever, before calling a tool which I have no idea about, which is in another folder, and done by some unknown guy.

Edit: when I say "before" I understand that in exclusive order. "A" is executed "before B", means that only A is executed, and not "A, then B". The OS will preferably call A, and not B, if A is in my local folder, and B is wherever else in the path.

[Dubslow]

You can always modify your path to do exactly that. Nothing stopping you.

[LaurV]

True. Then, where is the major improvement of the major security risk? Either way has advantages and disadvantages, and it is arguable. You put a lock on my door, but are giving me the key. This way you don't stop me entering the house, just make the process annoying for me, which I have to enter the house every day.