1 |
On Saturday 29 March 2008, Per-Erik Westerberg wrote: |
2 |
> fre 2008-03-28 klockan 09:21 +0000 skrev Mick: |
3 |
> > On Thursday 27 March 2008, Neil Bothwick wrote: |
4 |
> > > On Thu, 27 Mar 2008 20:33:53 +0200, Uwe Thiem wrote: |
5 |
> > > > > I'd say, try http. |
6 |
> > > > |
7 |
> > > > Jeez. You didn't read the original posting, did you? It's FTP, |
8 |
> > > > period. |
9 |
> > > |
10 |
> > > It's FTP, which is blocked by the firewall, so use only HTTP mirrors |
11 |
> > > in /etc/make.conf. There is no requirement to use FTP for downloads. If |
12 |
> > > rsync is also blocked, use emerge-webrsync to update the portage tree |
13 |
> > > over HTTP. |
14 |
> > |
15 |
> > export ftp_proxy=XXX.XX.XXX.XX:80 && emerge -uaDv world, should do what |
16 |
> > you're after. You can also try export http_proxy of course. It assumes |
17 |
> > that you know the LAN IP address of your web gateway/firewall at work - |
18 |
> > i.e. that your work's MSWindows configuration allows plain users to view |
19 |
> > the MSIE Internet Settings, or your sysadmin will let you know what the |
20 |
> > address is. If not, boot a LiveCD on a works computer, mount its |
21 |
> > MSWindows C:\ drive and search for "proxy". It should lurk somewhere in |
22 |
> > the registry settings. BartsPE CD will also help you find that, as it can |
23 |
> > search natively the registry. |
24 |
> > |
25 |
> > BTW, if this is anything like my work, then only outbound connections to |
26 |
> > port 80 are allowed and rsync will not work. Follow the webrsync advice |
27 |
> > above. |
28 |
> > |
29 |
> > HTH. |
30 |
> |
31 |
> Hi, |
32 |
> |
33 |
> You should also set RSYNC_PROXY to "hostname:port" in order for "emerge |
34 |
> --sync" to work. |
35 |
|
36 |
I've tried that and had no success behind my work's firewall, but the OP may |
37 |
be luckier. |
38 |
|
39 |
-- |
40 |
Regards, |
41 |
Mick |