trouble with up2date

Andy Green fedora at
Mon Nov 17 16:57:48 UTC 2003

Hash: SHA1

On Monday 17 November 2003 16:14, Dave Roberts wrote:

> I was actually thinking about just this same thing the other day. What
> if we crossed yum with bittorrent?

A really neat way to do this would be to make a new <protocol>:// thing, 
however that works, for example bittorrent://server/path/to/.torrent, which 
fetches the .torrent 'metadata' file over http as usual, using the given 
path, but then 'dereferences' the .torrent into the payload file using 
bittorrent, in one step.  The result of the bittorrent:// thing is the 
payload file as far as the program can tell.  With this method no changes 
would be needed to yum or other things, its just a new protocol like ftp:// 
or http://.

> downloading new packages and updates. While there is bound to be a surge
> right after an update comes out, I'm sure it pales in comparison to a

Bittorrent actually gets better the more people there are contributing 
bandwidth.... and I think many many users would be willing to leave a 5Kbps 
(or whatever they could afford) upload throttled BT session up permanently 
serving ISOs or updates, this would be like their contribution.  In fact that 
could be part of 'up2date', it could be napsterized that to use it you must 
share your updates.

> For the first time with Fedora, I downloaded my ISOs with bittorrent and
> it was fantastic. If you have never used this method before, I highly

Couldn't agree more, plus its great that as you are pulling you are also 
giving to other people.

- -Andy

Version: GnuPG v1.2.2 (GNU/Linux)


More information about the fedora-list mailing list