Hi!
Think, that Boinc should be avaliable for people who are using FreeBSD system.

BSD was developed at Berkeley University.
Why their own system is abandoned as a Boinc client?

I verly liked the seti@home classic multi platform avaliability.

> Hi!
> Think, that Boinc should be avaliable for people who are using FreeBSD
> system.
>
> BSD was developed at Berkeley University.
> Why their own system is abandoned as a Boinc client?
>
> I verly liked the seti@home classic multi platform avaliability.

There is a Linux version, at this time it is still a command line interface, the same with the Mac. The work is suposed to have been started, as I understand it, on the GUI for the Linux and Mac versions.
<p>
Click Me!

> > BSD was developed at Berkeley University.
> > Why their own system is abandoned as a Boinc client?
> >
> > I verly liked the seti@home classic multi platform avaliability.
>
> There is a Linux version, at this time it is still a command line interface,
> the same with the Mac. The work is suposed to have been started, as I
> understand it, on the GUI for the Linux and Mac versions.

Well, I think that making command version for FreeBSD much easier than making a GUI version for Mac & Linux.

> Well, I think that making command version for FreeBSD much easier than making
> a GUI version for Mac & Linux.

I think I recall someone actually running BOINC on FreeBSD - not sure though. He was using the compile-it-yourself option if I remember correctly...

> > Well, I think that making command version for FreeBSD much easier than
> making
> > a GUI version for Mac & Linux.
>
> I think I recall someone actually running BOINC on FreeBSD - not sure though.
> He was using the compile-it-yourself option if I remember correctly...
>
Compile yourself option is not working - I've got some compiling errors.
Both using gmake and bsdmake.
:-/

> > Well, I think that making command version for FreeBSD much easier than
> making
> > a GUI version for Mac & Linux.
>
> I think I recall someone actually running BOINC on FreeBSD - not sure though.
> He was using the compile-it-yourself option if I remember correctly...

I don't know if you're referring to me, but I did that (although I posted about it under a different account) on FreeBSD 5.2. That was back with version 3.x. I haven't been able to successfully compile 4.x yet (with either gcc 3.3.3, or 3.4.2). I also wasn't able to recompile 3.x when FreeBSD upgraded to gcc 3.4.2. Aside from my one lowly windows box, I've been out of commission as far as BOINC goes since the 4.x transition. I'd really like to be able to run BOINC/Seti again.

> Hi!
> Think, that Boinc should be avaliable for people who are using FreeBSD
> system.
>
> BSD was developed at Berkeley University.
> Why their own system is abandoned as a Boinc client?
>
> I verly liked the seti@home classic multi platform avaliability.

Have you tied compiling the Linux source on FreeBSD?

Can you program? With the source, maybe you could debug your way through a compilation and create a port?

> Have you tied compiling the Linux source on FreeBSD?
>
> Can you program? With the source, maybe you could debug your way through a
> compilation and create a port?

I can program but only a little.

I will be very pleased to see official Boinc release for FreeBSD.

Many strong machines are getting bored :-(

I just posted instructions for building the most recent cvs of boinc and
the most recent cvs of seti_boinc on the FreeBSD questions mailing list.
This is on FreeBSD 4.10.

They have done some pretty horrible stuff on the cvs with ugly includes
and hard-coded directory hacks and I had to do
some icky things to get it to build. But once done it does appear to
send and receive work units. I haven't tested it extensively to see
if it does indeed crunch the work units properly.