Alexander Skwar wrote:
>
> So sprach SI Reasoning am Thu, May 17, 2001 at 10:14:43PM -0700:
> > I don't see how the project I mentioned could not be
> > run that much differently than other Mandrake Open
> > Source projects... Since most of the coding and bug
> > checking is done by the community.... the only thing
> > Mandrake would be doing is getting the ball rolling as
> > another service.... diversification often makes a
> > company stronger and more able to handle the twists
> > and turns of the market.
>
> Uhm, the problem I see with this is, that it'll require quite a lot of
> bandwith and expensive hardware.
> Both are no-no's, if you're trying to save money.
>
> Alexander Skwar
> --
> How to quote: http://learn.to/quote (german) http://quote.6x.to (english)
> Homepage: http://www.digitalprojects.com | http://www.iso-top.de
> iso-top.de - Die g�nstige Art an Linux Distributionen zu kommen
> Uptime: 4 days 1 hour 54 minutes
Right. Bandwidth is expensive.
Is there a way that the freenet-network could be used to distribute
patches?
Since information in freenet automatically moves around to the place
where it is most in demand, you have completely automatic and
transparent
load-balancing.
Bandwidth cost for Mandrake would be zero. (or just the cost of
uploading
once)
Freenet keys are unique, and can only be altered or removed by the
original author, and pgp-keys can be used as they are now to further
authenticate the packages.
It would be slow at first, but after a few people have downloaded a
certain
item, it gets faster and faster. In contrast to ftp-sites, where if more
people start downloading something, it goes slower.
People are already used to trying different avenues to download
something,
(say the newest Mandrake distro), like I would first try ftp, then http
and then maybe rsync. Freenet could be used as just another way to
download stuff.
Also, freenet is a worthy cause to support in and of itself, and by
nature
by using it, you make it stronger.
Think about it,
Roland Nagtegaal
