I have BOINC running and reporting back to, for
example, the Sudoku Project. Now, the scheduler
request for this project contains:

<scheduler_request>
  …
    <platform_name>i386-ecce-mirbsd</platform_name>
    <alt_platform>
        <name>i686-pc-linux-gnu</name>
    </alt_platform>
  …
</scheduler_request>

But the server responds with:

platform 'i386-ecce-mirbsd' not found

SZTAKI Desktop Grid, ABC@home and Riesel Sieve
have the same problems; I reported it there too.
Please fix your server.

Some minirosetta-1.13 results on MirBSD succeed (if I
patch the BOINC binary to identify itself as Linux).
Thus I urge you to fix that on the server.

One of the validated examples:

https://ralph.bakerlab.org/result.php?resultid=922456

From the list of applications for this project (link on the front page), I can not see one for MirBSD platform. It appears to be not supported on this project.
The admins could confirm this if they read this thread.

---

This is *EXACTLY* what alt_platform is for.

MirBSD can execute applications for MirBSD, OpenBSD 3.8, and Linux.
The alt_platform says it can run i686-pc-linux-gnu applications, but
is ignored by RALPH.

If I run a hacked BOINC which reports i686-pc-linux-gnu INSTEAD of
i386-ecce-mirbsd as platform, I get WUs, process them, return them,
and they validate. So there is ABSOLUTELY NO reason to not send out
WUs to MirBSD clients.