Running Lisp on Linux

Where does Linux keep `graphical-read-eval-print-loop` stuff?
It worked fine on Windows.

$ mred
path->complete-path: second argument is not a complete path: "./"

 === context ===
loop
find-library-collection-paths

exception raised by exception handler: standard-module-name-resolver: collection not found: "mzlib" in any of: (); original exception raised: path->complete-path: second argument is not a complete path: "./"
reference to undefined identifier: graphical-read-eval-print-loop

>>15
There should be well defined and consistent environment, that doesnt change every year. The `mred` from OP-post fails to run, because "working directory" isn't present. Windows has no such problem, because every program has it's "c:\program files" directory.

>>17
The sole fact, Linux allows absence of working directory is a big hint to its inconsistency.

>>18
We call that pilot error, since the user needs to define his env vars

>>19
No. We call that "Worse is Better", since OS doesn't care about consistency and allows user to easily put it into incosistent states.