| Summary: | clean gentoo 1.4rc2 install hangs at step 10 page www.gentoo.org/doc/en/gentoo-x86-install.xml | ||
|---|---|---|---|
| Product: | Gentoo Release Media | Reporter: | Jim Snyder <jhs> |
| Component: | Everything | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jim Snyder
2003-01-04 13:45:21 UTC
I'm not sure if this is the same "problem" I saw, but when I did my first gentoo install yesterday, I aborted emerge twice because I thought it wasn't working... only to figure out it really takes a lot of patience. How long it takes before you get a response seems to depends on how loaded the rsync servers are. On the other hand, the first time I tried emerge, my firewall was blocking traffic (with DNS still working), and emerge just sat there as well. So there's no way to tell whether things are working and it's just being very slow, or whether things aren't working. Pretty confusing. Nick, Is there any way that we can add an informational pre-rsync message to Portage so that users can more easily detect a non-responsive rsync server? Alain's comment about firewalls explains the problem. I didn't know that rsync used a dedicated port. Mea culpa, mea culpa, mea maxima culpa. However it might be good to mention rsync port 873 so that ignorant people like me don't file bug reports. Sorry, all. thanks Alain. Jim Snyder Adding a reasonable timeout and message in 2.0.46-r10 Moving these so we can remove the "Install CD" component from "Gentoo Linux". I apologize to everyone for this spam, but according to the bugzilla developers, this is the only reasonable way to do this. |