Date: Sun, 30 Sep 2007 19:44:56 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Aryeh Friedman <aryeh.friedman@gmail.com> Cc: Kris Kennaway <kris@freebsd.org>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: 7.0-CURRENT Ports Collection? Message-ID: <20070930164456.GA3754@kobe.laptop> In-Reply-To: <bef9a7920709291315i32fc4cadka121590800e6ab85@mail.gmail.com> References: <972994690709291217t3bdd7d5bh2890c783f2cf4cc7@mail.gmail.com> <46FEA7B7.50104@FreeBSD.org> <bef9a7920709291303s7d1b7530ldc1cfacd8f5f8a6a@mail.gmail.com> <46FEB1B9.2090807@FreeBSD.org> <bef9a7920709291315i32fc4cadka121590800e6ab85@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2007-09-29 20:15, Aryeh Friedman <aryeh.friedman@gmail.com> wrote:
>On 9/29/07, Kris Kennaway <kris@freebsd.org> wrote:
>>Aryeh Friedman wrote:
>>> Are you attempting to download ports on 6.2 before you move to 7 or on
>>> 7? If the and your on a SMP (dual core don't know about physically
>>> seperate) there are some known issues in the protocol stack
>>
>> Er, what issues, pray tell? :)
>
> Namely hangs and lacks of connects (in some cases you will need to
> manually fetch the dist file [it may take several attempts {*DO NOT*
> erase the old dist file after each attempt}])
That's odd. Are you sure this is a bug in 6.2, and not some local
networking setup problem?
If you have tcpdumps and/or other useful data to track this down, then
please open a bug report, as 6.2 is used by _many_ people and a bug like
this would be annoying.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070930164456.GA3754>