use-revolution Digest, Vol 18, Issue 53

[David Vaughan]

Richard

It is many years since I played much in Terminal and then not with 
tcsh, so let me tell you how I worked my way through this and see if it 
helps you. Watch for the dots I have in here, e.g. in "sudo mv 
./airport /usr/local/bin" there is one at the beginning of the first 
path.

I downloaded the file from macstumbler and decompressed it to the 
desktop, producing a folder "airport".
In Terminal, I typed "cd " and then dragged the airport folder into 
terminal which put in the proper path for me.
I typed "make" which ran and created the executable in the folder. If 
it does not run for you, check your default path or try "/usr/bin/make"
Assuming that works, enter "sudo mv ./airport /usr/local/bin" and your 
password when requested. If you are within the airport folder this 
should copy just the executable, not the whole folder. If you 
accidentally move the whole folder, cd to /usr/local/bin and rename the 
folder ("sudo mv airport airportf") and then move the file up a level 
("sudo mv ./airportf/airport .").
The command "/usr/local/bin/airport" should now run for you. The signal 
data is word 1 of line 2 of the output.

regards
David

On 15/03/2005, at 7:15, use-revolution-request at lists.runrev.com wrote:

> From: Richard Miller <wow at together.net>
> Date: 15 March 2005 6:44:05 GMT+11:00
> To: How to use Revolution <use-revolution at lists.runrev.com>
> Subject: Re: Airport status
> Reply-To: How to use Revolution <use-revolution at lists.runrev.com>
>
>
> Alex,
>
> While I'm not at all familiar with Terminal, I believe I get into the 
> correct folder. Typed MAKE. Received back error COMMAND NOT FOUND.
>
> Richard