From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Pratical question about portage tree
Date: Thu, 29 Sep 2005 10:22:42 +0800 [thread overview]
Message-ID: <1127960562.18845.33.camel@localhost> (raw)
In-Reply-To: <20050929131831.5401.NICK@rout.co.nz>
Not a lot: I came in late on the thread.
One thing to investigate is if his ISP keeps a local cache of gentoo as
many of the ones in Oz do - they usually dont charge for local (to the
ISP) traffic. Then unless its openoffice which is a bit big, a
pre-fetch from the ISP at night is a good scenario.
BillK
On Thu, 2005-09-29 at 13:27 +1200, Nick Rout wrote:
> On Thu, 29 Sep 2005 08:57:57 +0800
> W.Kenworthy wrote:
>
> > Here's another way I started using (~1 month) and it seems both simple
> > and problem free. Run http-replicator on the machine with good net
> > access, then point the rest at it. Its a distfile caching proxy and
> > best of all, its in potage and there is a gentoo wiki doc on how to set
> > it up. Nice!
>
> Yes a good setup if there is fast and easy access between the two
> machines.
>
> Sorry how does this help the OP who has a machine at home on dialup and
> a fast connection at work? (and who doesn't want to download from home
> if he can help it?)
>
> --
> Nick Rout <nick@rout.co.nz>
>
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-09-29 2:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 1:05 [gentoo-user] Pratical question about portage tree Allan Spagnol Comar
2005-09-28 1:13 ` Nick Rout
2005-09-28 2:52 ` Dave Nebinger
2005-09-28 4:08 ` Norberto Bensa
2005-09-28 4:41 ` Nick Rout
2005-09-28 11:03 ` Allan Spagnol Comar
2005-09-28 11:58 ` Norberto Bensa
2005-09-28 21:24 ` Nick Rout
2005-09-28 23:22 ` Norberto Bensa
2005-09-29 0:57 ` W.Kenworthy
2005-09-29 1:27 ` Nick Rout
2005-09-29 2:22 ` W.Kenworthy [this message]
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=1127960562.18845.33.camel@localhost \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.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