Date: Tue, 7 Apr 2009 11:13:25 -0400 From: Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> To: Lars Eggert <lars.eggert@nokia.com> Cc: "stable@freebsd.org" <stable@freebsd.org>, Julian Stacey <jhs@berklix.org> Subject: Re: more automated fetch of ISO-IMAGES & ports Message-ID: <a333b2be0904070813mec16492nf124ca8751e2c762@mail.gmail.com> In-Reply-To: <24269939-A622-44A6-9F9C-F816E03BE31F@nokia.com> References: <200904071121.n37BLhbY007253@fire.js.berklix.net> <24269939-A622-44A6-9F9C-F816E03BE31F@nokia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
BitTorrent is NOT always a good solution . I tried it on an approximately 4.5 Giga Bytes iso which came out to be unusable because - direct download is taken minimum 12 hours with a 1024 kilo bits per second down load speed , in average 18 hours from Turkey . - BitTorrent download is reaching in average to 45 hours due to 256 kilo bits up loads where my PC is also used as a server for down loaders to share my downloaded parts . I am not escaping to help to other people but to find a 45 hours continuous time without destructive voltage fluctuations and nearly dedicate a PC so much time is difficult . On Tue, Apr 7, 2009 at 8:55 AM, Lars Eggert <lars.eggert@nokia.com> wrote: > On 2009-4-7, at 14:21, Julian Stacey wrote: > >> Perhaps some SOC student might like to develop some extension to >> fetch, or a new tool to intelligently save net bandwidth & human >> time (if not this year if SOC bids are in, then next) : >> Intelligently & automatically sniff fetch list to see where >> stuff is, measure the bandwidth, perhaps on a preliminary >> README, & automatically decide where to fetch from. >> & as 2nd stage, give up & try elsewhere if the server >> connection gets too bad. >> > > Use BitTorrent for all file distribution, it does all that. Yes, I'm half > serious. > > Lars
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a333b2be0904070813mec16492nf124ca8751e2c762>