Perhaps UCB should post the latest stable version of the BOINC Core Client on C'NET Downloads and on Download.com and refer new users to download the BOINC client from there for the time being, until after the December 15th closing of Seti Classic. This could free up a considerable amount of bandwidth, and help clear the log jam of dropped connections... Thoughts about this anyone?

Regards, Daniel.

---

When you download from 'there' don't they just link you to the softwares web site, I think you really mean we need a mirror site.

And as for that wouldn't it be possible for the other projects to act as mirrors, for software downloads, especially BOINC versions.

---

When you download from 'there' don't they just link you to the softwares web site, I think you really mean we need a mirror site.

And as for that wouldn't it be possible for the other projects to act as mirrors, for software downloads, especially BOINC versions.

I have gone to download a few programs, and the websites have referred me to either C'NET or download.com to download the program from there, but yes, we could definitely use a mirror site. Sourceforge acts as a mirror for all kinds of software and source code as well. And it would also be a huge help if the other BOINC projects also hosted the BOINC client. I think this would free up quite a bit of bandwidth that could be used for W/U uploads/downloads, thus clearing the log jam of dropped connections.

Regards, Daniel.

---

I have enough bandwidth (sort of) to mirror the download, but it would be @ 32Kb/s download speed as that is as fast as I can upload to the web. Like the idea?

---

with the current rapid succesion of version I don't think this would be a good idea, as it could confuse a lot of people.
on the other hand, what is the current status of the mirror-network Janus was working on for BURP work and finished clips?

An Aussie ISP is mirroring the file locally, Telstra Bigpond (Only Telstra customers can download it however)

---

How come nobody has mentioned bittorrent? It's ideal for this kind of distribution.

---

Sondre
It's intolerant not to tolerate the intolerant

How come nobody has mentioned bittorrent? It's ideal for this kind of distribution.

Explain further how bittorrent can be used for d/l, u/l and reporting.

---

How come nobody has mentioned bittorrent? It's ideal for this kind of distribution.

Explain further how bittorrent can be used for d/l, u/l and reporting.

It can't. But then the proposal wasn't for u/l, d/l and reporting - just for the 10Mb BOINC distribution...

---

I think that the bit torrent idea is sound on the face of it. When we look at the need, we see that it probably wouldn't be of any significant benefit after about December 20th. Ok maybe Christmas. Is it worth setting up for two or three weeks?

How come nobody has mentioned bittorrent? It's ideal for this kind of distribution.

Explain further how bittorrent can be used for d/l, u/l and reporting.

I do not claim that bittorrent is useful for sending out workunits, returning results and reporting, since it obviously is not.

However bittorrent is useful when MANY peers wants/needs the same file(s). That's the case with the client software. If 100.000 (think of a number) users needs the client software, thats nearly a terabyte combined. Not many knows how to use bittorrent, but a fraction of a terabyte is still a lot.

---

Sondre
It's intolerant not to tolerate the intolerant

How come nobody has mentioned bittorrent? It's ideal for this kind of distribution.

Because bit torrent is a P2P client, and it is a HUGE security risk. I would NEVER allow any P2P clients to run on my network. I have seen for myself some of our customer's machines brought in for repair, and found that the P2P client they were running to download MP3's or whatever, had turned their machine into a zombie for spamming, or to distribute porn, virii, and all sorts of garbage. The only reason I mentioned distributing the core client on someplace like CNET or download.com was because I had read in the tech news that downloads of the core client were eating almost 40Mbps of the campus bandwidth, so they put the client downloads onto a server on the Cogent connection. After this, the trouble with dropped connections soon began. The Cogent line is a 100Mbps connection, and if core client downloads are still eating up 40Mbps, temporarily posting the latest stable client on CNET would free up 40% of available bandwidth to use for W/U uploads/downloads. But, as someone pointed out, the versions of the core client are being revised so fast lately, that this is not as good an idea as I had originally thought.

Hopefully, someone at UCB will come up with a solution soon. There will be another minimum 3 hour regular outage today, but from the looks of things, it won't make any difference, as very few uploads are successful on any of my machines for the last couple of days. If this is not a hardware issue, and just a bandwidth issue, as is what I have inferred from the tech news postings, then this problem will not be resolved until well after the December 15th shutdown of Seti Classic, and all their bandwidth becomes available to Seti-BOINC.

If this is the case, and I hope I'm wrong, then there will be many thousands of Seti Classic migrants that will be frustrated by the inability to transfer work. Those of us that have been here for a long time are familiar with these outages, and know that it will eventually get ironed out and things will return to normal. But the people newly migrating from Classic will be quite disappointed if the UL/DL issues are not resolved before next Thursday when Classic shuts down.

Regards, Daniel.

---

How come nobody has mentioned bittorrent? It's ideal for this kind of distribution.

Because bit torrent is a P2P client, and it is a HUGE security risk. I would NEVER allow any P2P clients to run on my network. I have seen for myself some of our customer's machines brought in for repair, and found that the P2P client they were running to download MP3's or whatever, had turned their machine into a zombie for spamming, or to distribute porn, virii, and all sorts of garbage. [...]

Obviously this could happen with any program and not only p2p programs. The standard bit torrent client is as safe as any other application for windows.

---

Obviously this could happen with any program and not only p2p programs. The standard bit torrent client is as safe as any other application for windows.

This is simply not true. If you don't _use_ it to download anything, then sure, it's as safe as Solitaire. If you use it to download MP3's, it's fine; worst case, you ask for Yellowcard but get Barry Manilow. But if you download an executable using any kind of P2P system, you are trusting the unknown peer (and whoever he got it from) to have left that executable "as received". Any one person could write the worst trojan you can imagine, name it "boinc", replace the real one, and infect thousands. Yes, there are some safeguards, but they aren't insurmountable.

Downloading from "berkeley.edu", you are trusting that the people there maintain decent security on their server. Downloading from any P2P network, you're trusting every other person on that network. No thanks.

Obviously this could happen with any program and not only p2p programs. The standard bit torrent client is as safe as any other application for windows.

This is simply not true. If you don't _use_ it to download anything, then sure, it's as safe as Solitaire. If you use it to download MP3's, it's fine; worst case, you ask for Yellowcard but get Barry Manilow. But if you download an executable using any kind of P2P system, you are trusting the unknown peer (and whoever he got it from) to have left that executable "as received". Any one person could write the worst trojan you can imagine, name it "boinc", replace the real one, and infect thousands. Yes, there are some safeguards, but they aren't insurmountable.

Downloading from "berkeley.edu", you are trusting that the people there maintain decent security on their server. Downloading from any P2P network, you're trusting every other person on that network. No thanks.

I do not agree. If this site creates a torrent and places a link to it on the website, it's as safe as clicking on a regular download link.

I did not mean that the users should visit a tracker site and search for "boinc". That's as unsafe as searching for it on google and download it from any site in the search result.

---