[plans] distributed.net .plan update

plans at nodezero.distributed.net plans at nodezero.distributed.net
Tue Jun 11 01:00:04 EDT 2002

distributed .plan updates in the last 24 hours:

jt :: 10-Jun-2002 17:05 GMT (Monday) ::

For Sony PlayStation 2 users:

Yes, Linux[mips/PS2] is the first client for PlayStation 2!

The RC5 core is mips-crunch.cpp.
Special thanks to Michael Mallory,
 -pedantic solution was discovered by him.
I didn't change mips-crunch.cpp
 because it might make an influence to other platform.

It's *REQUIRED* "Linux for PlayStation 2" kit.
There is no method which runs it without this kit.
You may think it's able to boot from PS2 Memory Card, but it's impossible.
PS2 Linux (or any unix variants for PS2) is booted
 only from the Runtime Environment in Disk1.
Therefore, if you don't have this kit, please purchase it!

(for Japanese: We can't buy it now.
 See http://www.jp.playstation.com/linux/ )

If you have PS2Linux, you can run it without HDD(or BB) unit.
http://achurch.org/ps2/    (written by Japanese language)
Install ps2linux-boot-ntsc.tar.gz and dnetc to /mnt/MC00.

Once you do it,
 you may install the "Final Fantasy XI online" to HDD :-)
Both "Linux for PlayStation 2" and "PlayStation2 BB Unit" are
 kiting the same HDD and Ethernet unit.

Please feel free comments to me (language available: English and Japanese)

jt at distributed.net

decibel :: 10-Jun-2002 18:45 CDT (Monday) ::

For those who have noticed differences in the numbers, this is most likely
due to bugs that were present in the old stats code. We run an audit script
at the end of every daily run of the new system that does a sanity check on
the numbers represented by all the different parts of the system. It would be
difficult to overstate it's value; at least a dozen bugs have been identified
thanks to this script as the new stats code evolved from it's inception.

Because of this audit script, I have a very high degree of confidence in the
new stats code. We migrated the rc5 data from the old system into the new
system several months ago. Part of that migration was modifying the raw data as
best we could so that everything would actually pass the audit script. Since
that time, rc5 logs have been processed by the new system each night, as well
as the old system. This period of both systems running is what has allowed
people to do most of the before/after comparisons I've seen.

What this boils down to is that any rc5 stats processed by the new system
(ie: anything in the past month or two) can be assumed to be 100% correct and
accurate as compared to the logs provided by the master. Anything prior to that
time could still be off.

At some time in the future, I would like to start re-processing all of the rc5
logs from the beginning of the project. This should correct any other errors
that might exist in the rc5 stats.

To unsubscribe, send 'unsubscribe plans' to majordomo at lists.distributed.net

More information about the plans mailing list