While installing Gentoo Linux on my Gateway Solo laptop, from behind the corporate firewall, the emerge sync always hangs immediately upon startup (before listing the number of files it's scanning) the first time it is run (after booting up my machine). Despite being behind a firewall, the rsync port is not blocked, as demonstrated by cancelling the first attempt and running it again. I do have http_proxy and ftp_proxy set, and they seem to be set correctly, since everything else works fine. I have not tried it since finishing the install of Gentoo, however.
if you arent running the latest version of portage, please update and then try again if its *still* a problem, post `emerge info`
I believe I am running the latest version, 2.0.46-r6. Here is the result of running emerge info: Portage 2.0.46-r6 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r2) ================================================================= System uname: 2.4.20 i686 Pentium III (Coppermine) GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/usr/tmp" PORTDIR_OVERLAY="" USE="oss avi crypt cups encode gnome libwww motif qt qtmt quicktime spell svga xml2 xv gdbm berkdb slang readline pam ssl python esd X gtk apm arts directfb dvd evo fbcon gpm gtk2 imap imlib java jpeg mikmod mmx mozilla mpeg mysql ncurses oggvorbis opengl pcmcia pdflib perl pic png pnp sdl samba tiff truetype xmms zlib x86 -3dnow -gif -kde -libg++ -nls -tcpd" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -Os -pipe" CXXFLAGS="-march=pentium3 -Os -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
-r9 is the latest ...
Ummmmm... This isn't really something I can fix. The firewall may not be blocking interaction on that port, but I'd bet it's doing something. Unless you can provide a lot more detail on what's going on, I can't do anything on this one.
db fix