__/ [ Dave {Reply Address In.sig} ] on Saturday 24 June 2006 18:40 \__
> Gordon Henderson wrote:
>> In article <1151165820.21588.0@xxxxxxxxxxxxxxxxxxxxxx>,
>> Enigma <dd@xxxxxx> wrote:
>>> Hi
>>>
>>> I am jsut strarting with Linux and trying to install software for my
>>> Weather Station.
>>>
>>> " * ./configure
>>>
>>> * make
>>>
>>> * make install
>>>
>>> Just run `wx200d' by hand to get started. Add -r if your station is a
>>> WMR918/968 "
>>>
>>> When I go to directory where it has been installed and try to run wx200d
>>> I get the message
>>>
>>> "command not found"
>>>
>>> Please can someone help me?
>>
>> Try:
>>
>> ./wx200d
>>
>> It's possible that your $PATH doesn't have "." in it.
...And for what it's worth, in some installation processes, the above will
result in:
Permission denied
Take Google Earth for example. This requires the file to be made executable,
which it isn't always by default.
,----[ Command ]
| chmod 700 ./wx200d
| ./wx200d
`----
Surely, the other route would be to use the fine GUI's
(Konqueror/Nautilus/whatever) to change permissions and then just click on
the file to execute. Makes it a lot better...
> And so it shouldn't, it's a security risk. The best approach is to find
> where the software has been installed and (as root) install a link to it
> from /usr/local/bin (assuming that's in the path). Most things should
> work that way. It might have needed to be installed as root in the first
> place, of course.
There is also the issue of collisions, ambiguity and calls for executables
that are overriding one another. As in programming, this leads to confusions
that are often a debugging nightmare.
|
|