Questions and Answers :
Unix/Linux :
How do I install SETI on SuSE 9.1?
Message board moderation
Author | Message |
---|---|
JF Send message Joined: 3 Apr 99 Posts: 1 Credit: 0 RAC: 0 |
I have just installed SuSE 9.1 and so I am a bit of a Linux n00b. I have downloaded the boinc_3.18_i686-pc-linux-gnu.gz file but I don't understand what I need to do next. Could someone please explain it to me? Thanks |
Darren Send message Joined: 2 Jul 99 Posts: 259 Credit: 280,503 RAC: 0 |
It should be quite easy to get it going. First, you need to put it into the directy where you want to run it then extract the file by typing: gunzip boinc_3.18_i686-pc-linux-gnu.gz and pressing enter. That should get it unzipped and ready to go, with a name of just boinc_3.18_i686-pc-linux-gnu. After that, in your terminal just type: ./boinc_3.18_i686-pc-linux-gnu and it should start up and ask you for the url and your account number that you got in the email. If anywhere along the line it says "permission denied" when you try to do one of the above steps, it just needs to be made executable by typing: chmod +x filename where "filename" is its name at whichever step you're at. |
Tim Essman Send message Joined: 19 May 99 Posts: 1 Credit: 23,240 RAC: 0 |
I too am using SUSE 9.1 and am new to Linux. Your instructions were very helpful for the install, however, I am still curious whether SETI requires having to be run from a terminal? Are there other options? Thx! > It should be quite easy to get it going. > > First, you need to put it into the directy where you want to run it then > extract the file by typing: > > gunzip boinc_3.18_i686-pc-linux-gnu.gz > > and pressing enter. That should get it unzipped and ready to go, with a name > of just boinc_3.18_i686-pc-linux-gnu. After that, in your terminal just > type: > > ./boinc_3.18_i686-pc-linux-gnu > > and it should start up and ask you for the url and your account number that > you got in the email. > > If anywhere along the line it says "permission denied" when you try to do one > of the above steps, it just needs to be made executable by typing: > > chmod +x filename > > where "filename" is its name at whichever step you're at. > > > > |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.