public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Erik Van Reeth" <erik@vanreeth.org>
To: <gentoo-dev@cvs.gentoo.org>
Subject: Re: [gentoo-dev] Favor to ask
Date: Wed Jul 18 11:05:04 2001	[thread overview]
Message-ID: <007601c10fab$bfbf63e0$2e22a00f@vanreeth.org> (raw)
In-Reply-To: 411301487662D411ADDB0090274F3A7502260AEE@uswaumsx01medge.med.ge.com

rsync also uses an environment viarable "rsync_proxy".
So, if you do a export rsync_proxy=<your firewall:portnumber> before
doing emerge rsync, things should work.

Erik


----- Original Message ----- 
From: "Greer, Darren (MED)" <Darren.Greer@med.ge.com>
To: <gentoo-dev@gentoo.org>
Sent: Wednesday, July 18, 2001 6:46 PM
Subject: [gentoo-dev] Favor to ask


> GEs firewall/DNS are very tricky to deal with.  And for some reason,
> when I try to do an "emerge rsync" it fails on trying to find
> cvs.gentoo.org.  So, I tried to find the IP and put and entry in
> /etc/hosts to the IP 216.23.235.2, but I still get no luck.
> 
> Does anyone know if the emerge rsync is going over a port that is not
> port 80 or 21?
> 
> Thanks,
> 
> Darren
> 
> GE Medical Systems 
> ________________________________________
> Darren R. Greer
> Webmaster / Web Architect
> Web Solutions
> 
> General Electric Company
> 2607 N. Grandview Blvd.
> Waukesha, WI 53188
> Phone: 262.544.3873
> Cell: 262.424.2954
> Fax: 262.548.4126
> Darren.Greer@med.ge.com
> 
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
> 




  reply	other threads:[~2001-07-18 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 10:47 [gentoo-dev] Favor to ask Greer, Darren (MED)
2001-07-18 11:05 ` Erik Van Reeth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18 11:16 Greer, Darren (MED)

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='007601c10fab$bfbf63e0$2e22a00f@vanreeth.org' \
    --to=erik@vanreeth.org \
    --cc=gentoo-dev@cvs.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