public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Edward Muller <edwardam@interlix.com>
To: gentoo-dev@gentoo.org
Cc: Vik Olliver <vik@olliver.family.gen.nz>
Subject: Re: [gentoo-dev] Gnunet and Gentoo
Date: Tue, 09 Apr 2002 19:21:27 -0400	[thread overview]
Message-ID: <1018394487.5638.132.camel@palin> (raw)
In-Reply-To: <Pine.LNX.4.44.0204091640540.27932-100000@volumehost.com>

This is an awesome idea.

Although after a look through the Gnunet website I'm not convinced that
Gnunet would be what we want to use.

I'm going to start playing around with gnunet and freenet and look at
what it would take to integrate emerge with it.... 




On Tue, 2002-04-09 at 17:46, Jared H. Hudson wrote:
> 
> This sounds a look a good idea. In fact the MD5 checksums are already a 
> part of portage, in the files section of any package directory.
> 
> You should be aware though, that the source files and patches that are 
> downloaded come first from ftp.ibiblio.org, then from the origanal website 
> for that package.
> 
> For example, emerge'ing emacs would try ftp.ibiblio.org then gnu.org. The 
> only files that come from Gentoo's main site is the packages/misc small files 
> like md5 digest, ect. All of this is via rsync or CVS.
> 
> So, the only benefit to a P2P system would be for another place besides 
> ftp.ibiblio.org, its mirrors, or original site to download from.
> 
> -Jared H.
> 
> On Wed, 10 Apr 2002, Vik Olliver wrote:
> 
> > Now that Gnunet has settled down:
> > 
> > http://gecko.cs.purdue.edu/gnet/
> > 
> > Might it be possible to use Gnunet to distribute the source tarballs
> > among Gentoo installations? 
> > 
> > As most users will tend to have their tarballs stored locally and are
> > very likely to have a network connection, Gentoo is an ideal
> > distribution for P2P updating - provided that some trusted GPG signature
> > (or MD5 at a pinch) can be used to verify the integrity of the source.
> > 
> > Implementing this system frees Gentoo and all its applications from the
> > burden and expense of having to maintain a central source repository
> > with high bandwidth, allowing the distribution to grow freely at its own
> > pace. Fixes will percolate through automatically, software that is
> > banned in backward parts of the world will come through via untraceable
> > routes, and the caching will ensure that the file requests are
> > distributed evenly.
> > 
> > I regret that I am already fully comitted (possibly over-comitted) to
> > charitable projects already, but I believe this idea should be aired to
> > those willing and able to implement it.
> > 
> > Regards,
> > 
> > Vik Olliver
> > 
> 
> -- 
> Using the internet as it was originally intended...
> for the further research of pornography and pipebombs.
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev




  reply	other threads:[~2002-04-09 23:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 21:17 [gentoo-dev] Gnunet and Gentoo Vik Olliver
2002-04-09 21:46 ` Jared H. Hudson
2002-04-09 23:21   ` Edward Muller [this message]
2002-04-12  7:06     ` Vik Olliver
2002-04-26  3:03       ` Edward Muller
2002-04-28  7:22         ` Vik Olliver
2002-04-10 17:28 ` Chuck Haines
2002-04-10 17:05   ` Edward Muller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1018394487.5638.132.camel@palin \
    --to=edwardam@interlix.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=vik@olliver.family.gen.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox