public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: bdharring <bdharring@wisc.edu>
To: Kurt Lieber <klieber@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Proposal: re-organizing our source mirrors into two categories: full and partial
Date: Fri, 25 Jul 2003 09:33:07 -0500	[thread overview]
Message-ID: <E8932F4E-BEAC-11D7-B67A-00306580AC5C@wisc.edu> (raw)
In-Reply-To: <20030725141108.GI9959@mail.lieber.org>


On Friday, July 25, 2003, at 09:11 AM, Kurt Lieber wrote:

> Folks --
>
> I'd like to propose the following reorg for our mirrors.  Right now, 
> all
> mirrors are required to carry all directories.  I'd like to break that 
> into
> two categories: full mirrors and distfile mirrors.
>
> Full mirrors would still be required to carry all directories.  Full 
> means
> full, after all. :)
>
> distfile mirrors would be required to carry two directories: 
> /distfiles and
> /snapshots.  /snapshots contains snapshots of the portage tree and is 
> used
> by emerge-webrsync for folks that are behind restrictive firewalls.
> Typically, the /snapshot directory is under 250MB.
>
> This gives mirrors who are short on disk space an option to still 
> support
> Gentoo without having to set aside nearly 50GB of space for us.  For
> mirrors who do have enough disk space, they can continue to mirror the 
> full
> tree.
>
> We will of course continue to work at reducing the overall amount of 
> data
> that we have.  However, over time, our space requirements will 
> undoubtedly
> continue to increase.  This proposal is meant as a longer term 
> solution to
> give mirror admins an option on how best they can support Gentoo in 
> their
> environment.
Going a bit longer term, I'd wonder about adding a mirror 
classification that handles just diff's (or whatever format is used).
While distfile diff's aren't currently included/existing, I can't help 
but believe that this feature will be integrated into portage at some 
point, mainly due to the fact people request it and more importantly, 
the fact that people are working on this problem.
Also, are you advocating the distfile mirrors carry a *complete* 
distfile mirror, or a partial?  I'm curious what the space savings 
would be...
~bdh


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-25 14:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 14:11 [gentoo-dev] Proposal: re-organizing our source mirrors into two categories: full and partial Kurt Lieber
2003-07-25 14:33 ` bdharring [this message]
2003-07-26 12:37   ` Kurt Lieber
2003-07-26 12:40     ` Stuart Herbert
2003-07-26 13:42       ` Alec Berryman
2003-07-27  1:25         ` Chris Gianelloni
2003-07-27  1:31         ` Chris Gianelloni
2003-07-26 18:53       ` Jon Portnoy
2003-07-27 10:05     ` bdharring
2003-07-27 11:41       ` Kurt Lieber
2003-07-26 20:38   ` paul

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=E8932F4E-BEAC-11D7-B67A-00306580AC5C@wisc.edu \
    --to=bdharring@wisc.edu \
    --cc=gentoo-dev@gentoo.org \
    --cc=klieber@gentoo.org \
    /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