From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] source browsing via http is back
Date: Fri, 13 Feb 2009 00:10:41 +1100 [thread overview]
Message-ID: <775b8d190902120510g7453b96es102f23667450755e@mail.gmail.com> (raw)
In-Reply-To: <a1d5e8b5186999a3a4660d7730f250f0@quanstro.net>
Stop being sensible! There is no room on this list for such behaviour.
brucee
On Thu, Feb 12, 2009 at 11:49 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>> On Wed, Feb 11, 2009 at 7:28 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> >> > what extra work would that be,
>> >>
>> >> that it pulls files in their entirety (IOW: cp /n/sources/... /)
>> >
>> > i would be very suprised if a single copy of sources had many shared
>> > blocks.
>>
>> He doesn't want a single copy though, he is hoping to mirror
>> sourcesdump. That's 2255 almost-copies of sources. Yes, there will be
>> changes in each snapshot, but how often does something like
>> /extra/python.iso.bz2 change?
>
> exactly. the point i was trying to make, and evidently
> was being too coy about, is that 330 odd gb wouldn't
> be as useful a number as the sum of the sizes of all the
> new/changed files from all the dump days. this would
> be a useful comparison because this would give a
> measure of how much space is saved with venti over
> the straightforward algorithm of copying the changed
> blocks, as ken's fileserver does.
>
> - erik
>
>
next prev parent reply other threads:[~2009-02-12 13:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 18:49 geoff
2009-02-10 19:02 ` Bruce Ellis
2009-02-10 21:10 ` John Barham
2009-02-10 21:15 ` ron minnich
2009-02-10 21:22 ` Nathaniel W Filardo
2009-02-10 21:32 ` erik quanstrom
2009-02-10 21:51 ` Roman V. Shaposhnik
2009-02-10 21:55 ` erik quanstrom
2009-02-10 22:05 ` Roman V. Shaposhnik
2009-02-10 22:13 ` Nathaniel W Filardo
2009-02-10 22:17 ` Roman V. Shaposhnik
2009-02-10 22:08 ` Nathaniel W Filardo
2009-02-10 22:10 ` erik quanstrom
2009-02-10 22:23 ` Roman V. Shaposhnik
2009-02-10 22:28 ` erik quanstrom
2009-02-10 22:45 ` Roman V. Shaposhnik
2009-02-11 0:22 ` Bruce Ellis
2009-02-11 0:28 ` Roman V. Shaposhnik
2009-02-11 6:06 ` Bruce Ellis
2009-02-11 0:32 ` Akshat Kumar
2009-02-11 1:43 ` [9fans] Plan 9 source history (was: Re: source browsing via http is back) Nathaniel W Filardo
2009-02-11 3:40 ` erik quanstrom
2009-02-11 18:07 ` Uriel
2009-02-11 18:19 ` Venkatesh Srinivas
2009-02-11 18:35 ` Roman V. Shaposhnik
2009-02-11 18:46 ` Nathaniel W Filardo
2009-02-12 15:10 ` Venkatesh Srinivas
2009-02-11 19:06 ` Roman V. Shaposhnik
2009-02-12 5:57 ` [9fans] source browsing via http is back sqweek
2009-02-12 12:49 ` erik quanstrom
2009-02-12 13:10 ` Bruce Ellis [this message]
2009-02-12 16:19 ` Roman V. Shaposhnik
2009-02-12 16:28 ` erik quanstrom
2009-02-12 16:42 ` Nathaniel W Filardo
2009-02-12 16:50 ` andrey mirtchovski
2009-02-12 16:56 ` Nathaniel W Filardo
2009-02-12 16:58 ` erik quanstrom
2009-02-12 17:20 ` Bruce Ellis
2009-02-12 16:52 ` erik quanstrom
2009-02-10 22:27 ` Nathaniel W Filardo
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=775b8d190902120510g7453b96es102f23667450755e@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).