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