On Mon, 20 Dec 2004 00:38:32 -0000, gheston@hiwaay.net (Gary Heston)
wrote:

In article <Admxd.59853$2e.5346@fe2.texas.rr.com>,
usenet  <reply.in.newsgroup@bitbucket.dave.null.net> wrote:

rcdriver wrote:

There seems to be substantial and even strong support for the old classic 
S@H. As this class results example confirms with WU crunchers are very much 
still active  http://setiathome.berkeley.edu/classpages/days/2453252.html
from the newer members and the hard core WU crunchers in my group. I cannot 
see how you would arbitrarily to turn off classic S@H to disenfranchise all 
these supporters.without some form of backlash.

In view of the rough startup and ongoing reliability issues with BOINC
and the SETI clients, is it any suprise?

Also, the inability to make use of things like SETI Queue to buffer
work units will greatly impact a number of us operating farms, since
each BOINC client must have direct access to the Internet, and not
all of us are set up to allow that. Managing 15 or 20 queues instead
of one also incurrs a lot more work.

So, being one of the continuing Classic crunchers, I'm not suprised
that there are a bunch of us.

One of the next few releases will have a SetiQueue TYPE system built
in!
Have you tried BoincView yet, it lets keep track of remote computers
locally on one.

Maybe there will be a move to "Save ET"!!??

I doubt it.

I don't know the details but I will speculate.  Mine are uneducated guesses.

If the project has become limited by the S@H classic software it may be 
to their advantage to stop it.  Maybe BOINC has the potential to make a 
lot more money for the university than classic.  Maybe the project's 
resources are too limited to produce both BOINC workunits and classic 
workunits on a permanent basis.

AFAIK, the processing done by Classic and the equivalent BOINC SETI@home
are the same--the results returned by both will go into the same post-
processing software.

One of the problems is "forcing" people to update to the newest
versions of the software! Some users are still VERY old versions of
Seti! In Boinc that is not possible, it will AUTOMATICALLY update the
core Seti Client for you or tell you by not downloading any new units.
Berkeley has tried that with Classic and gotten QUITE a bit of flak!

I don't know of any way Berkeley is making money off of S@h, either
Classic or BOINC. They might be getting something from UD in the way
of royalties on software used in BOINC, but I haven't heard of it.

Not sure on the resources, but it does seem to be working for now.

I think the bottom line is if the project decides the scientific 
knowledge gained by classic does not warrant the resources required to 
continue it then it will end.

Or when they get tired of keeping two sets of servers running.

What backlash do you forsee?  Will the angry classic users stop 
crunching in protest?  Switch to other projects?  Storm the university 
grounds with their PCs?

Personally, I'll shut down 18 of my 19 nodes until I get the direct
access issue resolved.


Gary

See above about the upcoming releases!