seti-boinc status on USA Labour Day

[Martin 53N 1W]

(OK, note the non-Amerikan spelling for their day off (:-))


Here's a rather good and 'true to life' 'alternative' translated view of
happenings at Berkeley based on the brief notes rushed out on:
http://setiweb.ssl.berkeley.edu

See:
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=3773
###

Posted: 5 Sep 2004 17:34:07 UTC
in response to Message ID 22681.
Last modified: 5 Sep 2004 17:39:52 UTC

[ *lol* started typing with 0 replies seen, ended up as No. 7 after
finishing ;) ]

Hm, while I'm not 100.0% sure what "layman terms" exactly stands for, I
assume you mean either a) fun or b) "so that normal human beings can
understand it"

I'm going for a mix of both (just for the fun of it) ;)

Free "GeekTalk-to-Human" translation to follow :
=============================
The SnapApp Emergency Task force (Quick Reaction-Team for urgent repairs
of catastrophic events occuring on their supported Hardware) was here
for most of the afternoon.
Not knowing exactly what was wrong with the machine, they thought it was
always a good Idea to upgrade the System's Processors as a first step.
While that didn't fix the Problem by itself, the machine was able to
reproduce the errors at a much higher performance ;)
Most importantly, however, heavy arguments were exchanged and heated
discussion was held between us and the SnapApp people, as to how to
stabilize the affected machine.
The current plan is to simplify the Hardware by removing unneeded
components, as well as minimizing the amount of running services
performed by it in order to narrow down on the elusive error that causes
the machine to stumble.
(having observed the recent 'non-advertised product features' and shared
the 'special experiences' we've had with the machine, they will continue
analysis on a deeper level in their own laboratories)

We have changed the Software configuration so that the System is (for
now) running with an absolutely minimum of Services.
Additionally, we have modified the storage setup, which is now
exclusively limited to the "SnapAppliance 18000"
(See this Link for details and specifications)

The available SnapDisk 30 Storage array (Look here for Details and
specifications) is presently not used anymore to store data.

Due to this, alot of Data has to be moved around in the entire Setup.
In order to complete this migration of Data, we first have to move the
upload/download data to a temporary volume on the SnapDisk 30, then
reconfigure the space on the SnapAppliance 18000 System, then move the
Upload/Download data back to the SnapAppliance 18000 again.

The move to the temp volume is happening right now. Since this seems to
take forever even on our high-performance Storage System, Tomorrow
morning we will do the reconfiguration and start final move.
With (more) luck (than we've had the last weeks) we will have the
project up by
End of the Day ("EOD") tomorrow :)
==============================
###

See also:
http://www.sunstarco.com/Network%20Attached%20Storage/Snap%20Appliance/Snap%20Appliance%20Snap%20Server%2018000.htm
http://www.snapappliance.com/page.cfm?name=30Main&nav=30

Good description and thanks due to Falconfly!
http://setiweb.ssl.berkeley.edu/show_user.php?userid=1313


(There's various other translations in the thread also. One good one
goes: "????????????????????????????????
??????????"... (:-))


Enjoy,
Martin

[Martin 53N 1W]

Martin 53N 1W wrote:
[...]

Post by Martin 53N 1W
(There's various other translations in the thread also. One good one
goes: "???????????????????????????????? ??????????"... (:-))

That was supposed to be:
"$B$=$l$O$"$J$?$N$?$a$N3Z$7$_$G$"$k$+$b$7$l;d$OCN$C$F$$$k;d$N$?$a$KJsCNE*(B
$B$G$"$k$3$H$r!#(B"!

(If I get the charset right...)

Happy crunchin',
Martin

[€]

Martin 53N 1W wrote in message ...
(OK, note the non-Amerikan spelling for their day off (:-))

(..)

=============================
The SnapApp Emergency Task force (Quick Reaction-Team for urgent repairs

of catastrophic events occuring on their supported Hardware) was here

for most of the afternoon.
Not knowing exactly what was wrong with the machine, they thought it was
always a good Idea to upgrade the System's Processors as a first step.
While that didn't fix the Problem by itself, the machine was able to
reproduce the errors at a much higher performance ;)

(.....)
??? Computer glitches...???
Where are the results from all these years
Is that it ?
http://setiathome.berkeley.edu/process_page/

Maybe someone should reconsider the approach.
€

[Martin 53N 1W]

¤ wrote:
[...]

Post by €
(.....)
??? Computer glitches...???
Where are the results from all these years
Is that it ?
http://setiathome.berkeley.edu/process_page/
Maybe someone should reconsider the approach.
¤

Maybe you should read around a LOT more before shoving your big arse in
to dump your 'rubbish'...


And you reconsider what?

(I won't bother replying to further glib crap.)
Martin