staff blogs staff keep (relatively) up-to-date logs of their activities in .plan files. These were traditionally available via finger, but we've put them on the web for easier consumption.


bovine [24-Feb-2009 @ 17:26]

Filed under: clients,project status @ 17:26 +00:00

:: 24-Feb-2009 17:26 GMT (Tuesday) ::

Howdy all,

We’ve just confirmed receipt of the last OGR-26 stub, thus marking
that project officially complete! We will try to publish who
submitted the most optimal and last stubs, once we confirm that they
don’t mind their identities being revealed.

You should already notice that fresh OGR-27 stubs are already
available on our proxy network. To work on this project, you will
need to be using the v2.9103 client for your architecture. If you run
a personal proxy, you should upgrade to build 347. As usual, you can
find them

If your platform doesn’t appear to have released clients available
yet, that may be because some are still on the pre-release page–we
hope to officially release them in the next couple of days. We
appreciate your patience.

Due to variations in complexity, we expect that OGR-27 will take us
significantly longer than OGR-26 did. It is difficult to provide a
precise estimate but one extremely rough guess is about 7 years,
assuming no increase in computing power and that our size estimation
sampling reflects the entire stubspace.

There is one thing that is different with OGR-27 than with our
previous OGR projects: we are confident that we will discover a better
ruler for OGR-27 than the one we know to be optimal currently.

So get your clients cracking! Thanks again for your participation!

Moo ]:8)


snikkel [27-Jan-2009 @ 18:47]

Filed under: clients @ 18:47 +00:00

:: 27-Jan-2009 18:47 GMT (Tuesday) ::

An updated tarball of our public source is now available at

This includes the work to improve the CUDA platform, initial work on the AMD
STREAM platform, as well as many different bug fixes and feature improvements.
See the change log in the docs directory for additional details.

bovine [27-Jan-2009 @ 05:22]

Filed under: clients,keyservers @ 05:22 +00:00

:: 27-Jan-2009 05:22 GMT (Tuesday) ::

We’ve started upgrading our keyservers to build 347 of our proxy
software so that we can now offer large-sized blocks for rc5-72. This
will allow our clients to waste less time during network transfers and
block transitions. The need for this feature has become increasingly
apparent as our clients have become increasingly faster, particularly
on CellBE, CUDA, and ATI Stream hardware.

The first clients to support this will be version 2.9103-509, which
are just beginning to appear on the pre-release page for testing by
early adopters. The client has a new configuration option to allow
the preferred blocksize to be specified (a larger default blocksize is
automatically used for those three hardware platforms). While version
2.9103-509 is the first to officially allow configuration of the
blocksize, we are able to silently offer slightly larger blocks (size
16) to previously released clients on those three platforms as long
as the client is communicating with a proxy of build 347 or higher.

When the client connects to a keyserver or a personal proxy of build
347 or higher, the server will make a “best-effort” attempt to give
the client blocks of that size. If the server only has larger blocks,
then the server will try to automatically split a block to match the
request. The server cannot combine smaller blocks into larger ones.

Although the new clients and proxies are still only available on the
prerelease page for testing by early-adopters, we appreciate the
patience of those who would prefer to wait until the testing of these
clients are completed and they are moved to the official release page.

Thanks for your attention and participation!
Moo ]:8)


mikereed [23-Jan-2009 @ 01:30]

Filed under: clients @ 01:30 +00:00

:: 23-Jan-2009 01:30 GMT (Friday) ::

The CUDA client betas have expired. They will no longer function if you try
to run them. We will be releasing new versions in due course, but I am unable
to estimate at the present time when that will be. We thank you for your
continuing support.


mikereed [12-Jan-2009 @ 22:57]

Filed under: clients,project status @ 22:57 +00:00

:: 12-Jan-2009 22:57 GMT (Monday) ::

Dear friends,

We are pleased to announce that we passed 50% of OGR-26 completion on January
4, 2009. We thank you for your help in reaching this milestone.

We have just promoted a new set of clients from the pre-release page to the
official release page. These include clients with a faster OGR core which takes
advantage of MMX instructions for a 30% speedup. As usual, you can find them

The list of updated platforms includes:

* Linux [ARM/ELF] v2.9102.508
* Linux [ARM/eabi] v2.9102.508
* Linux [CellBE] v2.9102.508b
* FreeBSD [7.x/x86/ELF] v2.9102.508
* FreeBSD [6.x/x86/ELF] v2.9102.508
* FreeBSD [4.x/x86/ELF] v2.9102.508
* NetBSD [x86] v2.9102.508
* NetBSD [MIPSEL/ELF] v2.9102.508
* OpenBSD [x86/ELF] v2.9102.508
* OS/2 [x86] v2.9102.508
* PC-DOS, MS-DOS [x86] v2.9102.508
* Windows 32bit [x86/Zipped] v2.9102.508b
* Windows 32bit [x86/Installer] v2.9102.508b
* Solaris/SunOS [x86] v2.9102.508
* BeOS [Haiku/x86] v2.9102.508
* BeOS [x86] v2.9102.508
* Acorn RISC OS [ARM] v2.9102.508

Our work on clients for graphics cards is continuing. Our CUDA client for
nVidia cards is in public beta testing, while a core for new ATI cards is due
to enter closed testing shortly.

We also have new clients in public beta testing. You should only run these if
you have the time and inclination to monitor them regularly, as they may be
removed at short notice.

* Mac OS X/Darwin [x86] v2.9103.509
* Mac OS X/Darwin [PPC] v2.9103.509
* Linux [ARM/ELF] v2.9103.509
* Linux [ARM/eabi] v2.9103.509
* Acorn RISC OS [ARM] v2.9103.509

Moo! ]:8)


bovine [22-Nov-2008 @ 22:38]

Filed under: clients,project status @ 22:38 +00:00

:: 22-Nov-2008 22:38 GMT (Saturday) ::

We’ve just promoted a new set of OGR-NG capable clients from the
pre-release page to the official release page. As usual, you can find
them at:

The list of updated platforms includes:
* MorphOS [PPC] v2.9101.507c
* AmigaOS [PPC/WarpOS] v2.9101.507
* AmigaOS [PPC/PowerUp] v2.9101.507
* AmigaOS [m68k] v2.9101.507
* AmigaOS [PPC/OS4] v2.9101.507b
* Solaris/SunOS [AMD64] v2.9101.507
* Solaris/SunOS [Sparc64] v2.9101.507
* Solaris/SunOS [Sparc/Ultrasparc] v2.9101.507
* Solaris/SunOS [x86] v2.9101.507
* OpenBSD [x86/ELF] v2.9101.507
* OpenBSD [AMD64/ELF] v2.9101.507
* FreeBSD [6.x/x86/ELF] v2.9101.507
* FreeBSD [4.x/x86/ELF] v2.9101.507
* FreeBSD [Sparc64/ELF] v2.9101.507
* FreeBSD [7.x/AMD64/ELF] v2.9101.507
* FreeBSD [6.x/AMD64/ELF] v2.9101.507
* FreeBSD [7.x/x86/ELF] v2.9101.507
* Linux [AMD64/ELF] v2.9101.507
* Linux [CellBE] v2.9101.507
* Linux [x86/ELF] v2.9101.507
* OS/2 [x86] v2.9101.507
* Mac OS X/Darwin [PPC/OS X] v2.9101.507
* Mac OS X/Darwin [x86] v2.9101.507
* PC-DOS, MS-DOS [x86] v2.9101.507
* Windows 32bit [x86/Zipped] v2.9101.507b
* Windows 32bit [x86/Installer] v2.9101.507c

There are also some new OGR-NG capable personal proxies available for
download on the official proxy download page:

We’re working on updates for some of the remaining platforms (like
NetBSD and OpenBSD) plus some exciting new ones (like nVidia CUDA), so
look forward to future announcements. Feel free to contact our
friendly support crew at if
you have any questions. Bug reports should be entered at or through our support crew.

In other news, we are already more than 10% complete with OGR-26 since
we started it almost one month ago! We may finish the project in
early 2009 at this rate. You can view the OGR-26 progress at:

Thanks again for your participation! MOO!


bovine [26-Oct-2008 @ 09:52]

Filed under: clients,project status @ 09:52 +00:00

:: 26-Oct-2008 09:52 GMT (Sunday) ::

Dear friends,

It is with great excitement that we announce our upcoming project to
find the Optimal Golomb Ruler with 26 marks. Optimal Golomb Rulers
have many applications including sensor placements for X-ray
crystallography and radio astronomy. Golomb rulers can also play a
significant role in combinatorics, coding theory and
communications. Dr. Golomb was one of the first to analyze them for
use in these areas.

New clients and proxies will be required to support the new project,
which we are calling “OGR-NG”. The new clients will have version
2.9101.507 or higher. Clients with version numbers prior to this will
only be able to work on the RC5-72 project. Similarly, Personal Proxy
version 343 or higher is required.

Updated clients and proxies are being made available for early-adopter
testing at for many
major platforms. Builds for additional platforms are gradually being
produced and will be made available on that page as soon as
possible. If you do not feel comfortable helping with this
early-adopter testing and reporting bugs, then we recommend waiting
for a few days when we will move those clients to the official release
page. Not all of our public keyservers have finished upgrading to the
new version, so not all will have OGR-NG workunits yet. Stats for the
new project will also be launching in a couple of days. As with all of
our pre-release software, we encourage you to file bug reports for any
problems you find at

The OGR node rate for these new clients may appear to be slower than
those for the OGR-25p2 project. This isn’t a cause for concern. The
effective search rate for the overall project is actually more
efficient as these new clients are using an improved algorithm. The
new algorithm is named FLEGE (Feiri-Levet Enhanced GARSP Engine). It
has been developed by Didier Levet and Michael Feiri over the course
of the past few months. We are especially grateful to them for this
Herculean effort. In technical terms, the number of elements in the
‘choose lookup table’ has been increased from 48K to 2M
elements. Although this will slightly increase the size of the dnetc
binary, this optimization will significantly reduce the number of
nodes that we have to search through, sometimes a node improvement of
ten-fold or more.

We estimate that OGR-26 will take much less time to complete than
OGR-25 and will probably be more similar to OGR-24, in terms of
computational effort. Beyond that, we’re looking forward to OGR-27 and
OGR-28 because the current solutions to at least one of the two is
very likely not optimal. OGR-26 is on the way and must be done first
since higher-order rulers depend on the proven optimality of previous

We are grateful for your continuing support and enthusiasm.


bovine [24-Oct-2008 @ 06:39]

Filed under: clients @ 06:39 +00:00

:: 24-Oct-2008 06:39 GMT (Friday) ::

Some clients that were previously on the pre-release page have just
been moved to the official release page:

* Solaris/SunOS [x86] v2.9015.505
* FreeBSD [4.x/x86/ELF] v2.9015.505
* FreeBSD [7.x/AMD64/ELF] v2.9015.505
* FreeBSD [6.x/AMD64/ELF] v2.9015.505
* FreeBSD [7.x/x86/ELF] v2.9015.505
* FreeBSD [6.x/x86/ELF] v2.9015.505
* Linux [ARM/eabi] v2.9015.505
* Linux [AMD64/ELF] v2.9016.506
* Linux [CellBE] v2.9016.506
* Linux [x86/ELF] v2.9016.506
* Windows 32bit [x86/Zipped] v2.9015.505
* Windows 32bit [x86/Installer] v2.9015.505

Download links are on:


bovine [15-Feb-2008 @ 18:04]

Filed under: clients @ 18:04 +00:00

:: 15-Feb-2008 18:04 GMT (Friday) ::

As was previously indicated last month, OGRp2 results from the older
PlayStation 3 (CellBE) Linux clients earlier than version 2.9015-505
will no longer be accepted. If you are still using the older version,
you are encouraged to upgrade as soon as possible. See this
announcement for further details:


mikereed [05-Feb-2008 @ 00:40]

Filed under: clients @ 00:40 +00:00

:: 05-Feb-2008 00:40 GMT (Tuesday) ::

Dear friends,

We have recently been in communication with a number of vendors of anti-virus
software, regarding their false detections of dnetc. Many of them have been
brought around to our point of view that dnetc is benign, peaceful and able to
happily co-exist on a busy workstation. Our attempts to bring McAfee around to
our point of view have failed, despite our best efforts.

We would like to re-open hailing frequencies with McAfee and we need your help
to do this. On their site is a page describing dnetc as a ‘potentially unwanted
program’. You can see it here:-

At the side of the page is a link ‘Rate This Potentially Unwanted Program’. We
would like as many of you as possible to visit the page and let McAfee know
that dnetc should not be detected.

We remain grateful for your continued support and enthusiasm.

Moo! ]:8)

« Newer PostsOlder Posts »