1 |
emerge-webrsync should work fine over port 80. Can't you configure the |
2 |
firewall to accept this port. You could also write a script that opens the |
3 |
port calls emerge-webrsync and then locks it back down if you don't want |
4 |
that port open. Another safe way to do it is to run it through a proxy |
5 |
server. I'm not sure if this is the best way but certainly should work. |
6 |
|
7 |
On 2/24/06, Rick van Hattem <Rick.van.Hattem@××××.nl> wrote: |
8 |
> |
9 |
> On Monday 13 February 2006 19:40, Daniel da Veiga wrote: |
10 |
> > I have this server at work, it has been running ok for a long time, |
11 |
> > but I'd like to install some new apps to it, but I have a strongly |
12 |
> > configured firewall (no rsync) and emerge-webrsync seems to fail every |
13 |
> > time. |
14 |
> > |
15 |
> > Is there another way to update portage tree? For my first update I |
16 |
> > downloaded the snapshot and decompressed it directly to the filesystem |
17 |
> > (but that requires a reboot and its kinda "brute force"). Is there a |
18 |
> > way to download the snapshot and make emerge or even emerge-webrsync |
19 |
> > to use the downloaded file instead of trying to download a new one? |
20 |
> > |
21 |
> > Thanks for any sugestion. |
22 |
> > |
23 |
> > -- |
24 |
> > Daniel da Veiga |
25 |
> > Computer Operator - RS - Brazil |
26 |
> > -----BEGIN GEEK CODE BLOCK----- |
27 |
> > Version: 3.1 |
28 |
> > GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- |
29 |
> > PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ |
30 |
> > ------END GEEK CODE BLOCK------ |
31 |
> And it isn't possible to enter the proxy data for emerge-webrsync (if |
32 |
> there is |
33 |
> any) |
34 |
> |
35 |
> Btw, just packing /usr/portage from another system and unpacking it again |
36 |
> shouldn't need a reboot, after unpacking it should be able to run. |
37 |
> |
38 |
> -- |
39 |
> Rick van Hattem Rick.van.Hattem(at)Fawo.nl |
40 |
> |
41 |
> |
42 |
> |