[Scotttheking]

I've put OSX on my G3, and I need help on how to get both programs to run.
I don't really have command line experience, and I need to run them.

Can someone give me instructions on how to make it work?
When I downloaded RC5, it was all text files, which doesn't seem right.

[brock76]

Ok, here we go....

RC5

1)Download the 1.x kernel client.
2)Save in a directory that you can remember.
3)Open your terminal window.
4)get your terminal to the directory were RC5 is at
5)the default name of the RC5 client is dnetc
6)configure the client by typing at the prompt ./dnetc -config
7)then run the client by typing at the prompt ./dnetc -run

Same for S@H just rename the client seti.

so do the previous 1-4
1)then type at the terminal ./seti -verbose

any more questions just fire away.

brock


------------------
KWSN - br0ck
Challengers?
----------
Member of KWSN - Migratory Coconuts since 3/14/01

[Scotttheking]

How do I work the terminal?
It isn't like linux, so I don't know how to use it.
the dir command doesn't even work.
And yes, I installed the BSD stuff.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[brock76]

ok, in *nix or fbsd, the dir command is pwd. That will show the current directory you are in.

to move around is much like dos. To move up directories type cd .. To move in a directory type cd <directory name>.

some other nice commands.

ls = to list files
ls -al = to list files and invisibles
top = to see you processor(s) usage
kill <pid#> = to end that task
w = to show users
su = to log in as root

Note: it is not a very good security measure to surf and chat while logged in as root. If you ever need to get to root access, you should use the "su" login via your terminal.

Another Note: if you ever need help with the syntax or usage of a command, try typing: man <command you want help with>

brock

------------------
KWSN - br0ck
Challengers?
----------
Member of KWSN - Migratory Coconuts since 3/14/01

[Scotttheking]

How do I make it run at startup?

I tried setting up cron, but it says permission denied.
I try to login as su, but it has a password, and I don't know what it is.
And I'm the one who installed OSX, and the only one to use it.

So how do I find my password?

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[bipto]

How to get SETI running under OS X for (UNIX) Dummies

1. Go to url=http://setiathome.ssl.berkeley.edu/unix.html and download the powerpc-apple-darwin1.2 client.
2. Unstuff it (your browser should do this for you).
3. Open the Terminal application found in Applications>Utilities.
4. Open the window containing the newly unstuffed 'setiathome' executable.
5. Drag the 'setiathome' executable onto the Terminal window (Hey, this is still a Mac!)
6. Click on the terminal window to make it active, then press enter.

Note two things. The first time it'll ask you if you're new or returning. Also, you'll have to do steps 3-6 every time you reboot unless you know enough about UNIX to set up one of these cron-thingamajigs. I do not. If someone can post detailed directions for us lowly Mac users, that would be appreciated.

That's it!

------------------
b i p t o
p i x e l f i s h . n e t

[zac4mac]

I will be getting OS X in a few days. Was going to pick it up at the University software store, but found out Friday they want 100 bucks for it, so I ordered it thru the Apple education store. Y'all figure out all the problems and post solutions to getting SETI and RC5 to run in auto Probably won't be running SETI on the G4 anymore tho just RC5 and I doubt I'll load X on the 8500/G3.. work is calling, later.

Zack

[OoklaTheMok]

Anyway...

I had seti running under cron in the PB. The README that comes with it explains how to do it.

Basically, I put setiathome in /applications/setiathome . To set up the cron job, you have to add the line to your crontab. I added it to root's crontab.

To make a root password, open netinfomanager in the utilities folder. Click the lock to make changes. There is a "users" or something pane (I'm not on that computer at the moment). Find your account, find the password box. It will be encrypted. Select it and copy it. Now find the root account. Its password box will say "*". Select it and paste your encrypted password there. Quit. Save changes. Really save changes. Now your root password is the same as your account password.

Now open a terminal. type "su root". put in the password.

Now type "crontab -e". This will open up root's crontab in vi (i think). In it add the line that's in the README, with the correct path specified. You may have to press "i" or "s" or something like that in order to get it to start typing. After you have typed it (make sure you spell it right) press esc and then type ":wq" and hit return. It should say crontab installed.

That's it. The cron job is set up. It actually may take an hour or so before seti starts automatically.

Now, this may need some revising because I haven't done it in months. I haven't done it on my retail copy yet.

[Scotttheking]

Ok, I can get in as superuser, but how do I edit the crontab?
I can get into it, but how do I save the changes I make?

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[bipto]

how do I edit the crontab?

Yes! How do you edit the crontab? Us lowly old Mac users will need more detailed instructions...

------------------

[OoklaTheMok]

How to edit the crontab:

Ok, I'll try to give better instructions. Mucking about in vi is not fun for me at all. I barely know any of the commands. However, I can tell you enough to get by.

The easiest thing to do is write out ahead of time the line you want to put in the crontab, in anything else such as TextEdit, and then paste it in. Make your own version of this:

0 * * * * cd <setidir>; ./setiathome -nice 19 > /dev/null 2> /dev/null

for me, this is

0 * * * * cd /applications/setiathome; ./setiathome -proxy proxy1.byu.edu:8000 -nice 19 > /dev/null 2> /dev/null

However yours needs to be, write it out and copy it.

Then to edit the crontab:

in the terminal, after you go to root, type:

crontab -e

and hit return. You will now be in vi. Hit the "i" key, for "insert," and you can start typing. But instead of typing, just paste in the text. Now you are done. To save it and quit, press the escape key, and then type

:wq

That's colon, w for "write," and q for "quit." If you realize you made a mistake, instead of saving, just hit esc and type

:q!

which means "quit without saving changes." Then write the correct line in textedit and start the process over again.

If you are in vi and only want to erase one line or a letter instead of trashing the whole thing, you can use some vi commands...the remainder of what I know! press esc again, position your cursor, and press "d" for "delete." If you press "d" again, the whole line will get erased. If after the "d" you press the forward arrow key, the character after the cursor will get deleted. I don't know any of the other commands...so to delete a 5 letter word I press d-arrow 5 times. Perhaps something like d-w deletes the whole word; I don't know. I don't care to use vi. For normal text editing I do it in textedit if I can or in pico if I can't. If you have ever used PINE for email you know what pico is like. But I'm not sure how to edit the crontab without using vi, especially if there is no crontab for that user to begin with (when you type "crontab -e" the first time, you are given a blank document. I think this means you are creating it on the spot).

Anyway this works for seti. This crontab entry will start seti at the top of every hour, so if you want to install it for the first time, do it at like quarter till so your computer isn't sitting idle for a whole hour. This means it will restart it on the hour if it somehow stops because it couldn't connect to the server or whatever. Not that it will run multiple copies if one's already running in the same directory. It won't. If you have a dual processor machine, make install seti in 2 different folders, or use the symbolic linking explained in the README if you are confident, and put 2 lines in your crontab, one for each instance of seti. Something like

0 * * * * cd /applications/setiathome; ./setiathome -proxy proxy1.byu.edu:8000 -cpu 0 -nice 19 > /dev/null 2> /dev/null
0 * * * * cd /applications/setiathome2; ./setiathome -proxy proxy1.byu.edu:8000 -cpu 1 -nice 19 > /dev/null 2> /dev/null

Actually, not sure if the -cpu flag works. Better yet if you have a dual processor machine, run rc5 since it eats dual g4s for breakfast. I don't have OS X installed on any dual g4s though, just my iMac, so I can't comment at all on installing rc5, though it shouldn't be that different.

Good luck.

[Scotttheking]

Ok, it works.
Both SETI and RC5 start up on the hour.
Problem: RC5 starts another copy EVERY hour.
I went to bed, and when I checked my comp the next morning, I had 8 copies of it running.
How do I fix that?
I did the same cron line as SETI, except I didn't do the >dev/null stuff.

[This message has been edited by Scotttheking (edited 03-28-2001).]

[OoklaTheMok]

OK...yeah...that's a problem. Seti only allows 1 copy to be run in a directory, but apparently RC5 has no such compunction. That's no good...mmm.

RC5 doesn't need to restart every hour, because it doesn't have the nasty habit of quitting all by itself like the seti client may.

If someone knows how to add lines to startup scripts, let us know how to do rc5 that way...

Or perhaps reading the man pages for cron will reveal a way to have it start only if it isn't started already.

This Linux-thread at Ars might give some info on autostart and cronjobs.
Haven't tested it myself though. http://arstechnica.infopop.net/OpenT...mp;m=843094864


And Ookla ...newer seen seti crash on mac or winnt.
/bed

[OoklaTheMok]

I haven't seen it crash, but I have seen the nt client many times simply quit all by itself. This happens often when the Berkeley servers are down and it can't connect. It's supposed to just try again in an hour, but instead it often just quits.

I haven't seen it quit at other times, but with the frequency at which Berkeley goes down, this is bad enough.

[Scotttheking]

URL doesn't work.

Anyone know how to edit the start up items for the command line?

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[OoklaTheMok]

OK...see my repost in the new Ars mac forum.
http://arstechnica.infopop.net/OpenT...p;m=8600981331

nibs explains below how to add startup items like dnetc.

[Scotttheking]

Ookla, his instructions still confuse me (just a little though ).
Can someone make the instructions even simpler, or better yet, do all that stuff and code it, then email the file to anyone who wants it(or put it on their idisk).
I'd really like to get it to work, but I'm just too confused.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[OoklaTheMok]

They confuse me too. I haven't had time to look through them all the way...

[Scotttheking]

Well, if anyone gets it to work and can explain it better, please let me know.
I really need it working.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[zac4mac]

Big X's are all over the place. I'm wearing my "X" t-shirt, the X-PB's up on the shelf, the release version showed up today. I should be studying this weekend, but I know what I'll be doing. Does SETI run any faster in X?

Weekend, ya right. 9.1's installed on a fresh 13 gig partition. Time for X and a pot of spaghetti.

z

X is up. Animations seem slow, but better than PB. More time to play with it tonite.

[This message has been edited by zac4mac (edited 03-30-2001).]

[iBook]

Originally posted by zac4mac:
Does SETI run any faster in X?

The command line version is alot faster than the GUI version. Atleast in my experience. It took about 15/W/U and only 10 or less in the command line.

[Scotttheking]

GUI=Graphics
Graphics=Lots of processing power
Lots of processing power for graphics=Less for SETI crunching

And there you have it.

I have SETI on all my slow machines, because it isn't stealthy enough to put on windows.
I still have the little green antenna in the tasklist.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[OoklaTheMok]

actually...in my experience, the command-line version is slower in OS X than the normal screensaver Mac OS 9 version. I don't have any idea why. The windows CLI is faster than the windows screensaver.

I submitted a couple benchmarks to the benchmark site

[Scotttheking]

Well, I got dnetc to run at startup, so, to celebrate, I'm taking out my stock drive and putting in the 75GB from my firewire case, which has not worked for more then 5 minutes.

Ookla, the times are easy to explain.
If you have a dual monitor machine, (I do), put process viewer on one monitor, then do your normal work on the other.
OSX eats processor time like there is no tomorrow, leaving much less for SETI.
SETI and Dnet combined get maybe 60% of my processor time while I'm working (browsing the web), and many times it drops to 20%.
Thus, it is much slower.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[OoklaTheMok]

Actually, no, that doesn't explain the slow time.

OS X, being based off unix, keeps track of how long each process runs exactly. If, for a particular second, seti only uses 60% of the processor, then it gets credited with only 0.6 seconds of use during that time. This is the time that seti reports back to the server.

If you watch carefully in top (run top from the command line) you'll see that the seti total time increases slower than one second per second.

So even though it may actually take a work unit 19 hours 45 minutes, it gets recorded as 19 hours 20 minutes (for example). And both times are longer than the OS 9 seti. It really doesn't have to do anything with the kernel task eating processor time. The client itself really is slower.

[kman42]

Well, I installed the darwin1.2 version of SETI and edited my crontab as instructed above. I missed the top of the hour by about 2 minutes so I set my clock back to :59. At the top of the hour, nothing happened. Shouldn't it have started up? I checked the process viewer and there was no seti process running. Any help?

kman

[kman42]

One other question. Now that I have edited the crontab, will seti run when no one is logged in?

kman

[Scotttheking]

I've made some system modifications, and now neither seti nor dnetc are on the hard drive that has X on it.
How do i set the cron job and the startup item to point to the drive they are on?
I know the drive name (dev/disk0s9).
How do i set it up?

[kman42]

Okay, I now have seti running under my user account with cron. Is there a good way to check on the status? On initial install the app told me that I could check the progress in a certain file, but I haven't been able to locate this info in the readme or on the seti site and none of the files in the seti folder seem like the one that the app mentioned. I found lots of status apps and front ends, but they were all for kde, etc. Is anyone working on one for osx?

kman

[kman42]

Okay. Conveniently, Ookla's screenshot above shows that the file name is state.sah. There is no such file in my setiathome folder. Is it located elsewhere?

A little off-topic: what is in the /dev directory and what is /dev/null? Is it a temp file? I haven't used unix for many many years...bits and pieces are coming back. I think I know how a recovering amnesiac feels.

kman

[Scotttheking]

/dev/null is probably just oblivion.
Don't know.

Can anyone help me with my above question?
I really need cron and startup running again.
Making an alias didn't work, and anyway, that is too hard to do for tons of stuff.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[djohnson]

I figured out that to set up the cron job, you will need to cd down to the root folder and then type in volumes/whateveryourvolumeis/folders... that will take you to where ever you want it to go.

[Scotttheking]

OK, so it is "volumes" not "dev"?

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[djohnson]

Originally posted by Scotttheking:
OK, so it is "volumes" not "dev"?

yes

[Scotttheking]

Yay, it works again.
Yipee.
I still hate OSX, but I'm using it again.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

[beverson]

Okay, I haven't set up this crontab thing yet 'cause I'm still getting used to mucking around in the terminal, but I did get the client started manually (woohoo!).

Now, though, I can't close the terminal window or it kills the setiathome process.

So do I have to keep the terminal window open (I guess minimized) at all times to run setiathome in this manner?

I'd like to feel it out for a day or two to see if it affects system performance before I mess with the crontab.

[This message has been edited by beverson (edited 04-07-2001).]

[Scotttheking]

Yes, it must be left open.
With cron running, it doesn't have to be.

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB

Actually, you can start up the SETI client and then close your Terminal. Here's the command:

cd setiathome
./setiathome &

The ampersand (& tells the application to run in the background. Then, close your Terminal, open another and run top to see that setiathome is taking up close to 100% of CPU.

--Bernie

[OoklaTheMok]

Or, after you already started it, press control-Z. It will say suspended. type bg and then it will start again in the background.

[Scotttheking]

anyone know how to setup a startup item for dnetc and cron for seti in linux?
cron should be the same (I hope), but startup won't be.

Any ideas?

------------------
G3 400, 384, 12 + 75 GB
PM 8500 - 150, 48, 1 GB
PM 7100 - 66, 32, 700 MB
PM 6100 - 66, 40, 4.5 GB