From: Mario Frasca <mfrasca@zonnet.nl>
To: Steve Murray <stevem@eng.uts.edu.au>
Cc: Linux-8086@vger.kernel.org
Subject: Re: ELKS sources - just how can the latest version be obtained?
Date: Tue, 7 Nov 2006 15:14:15 +0100 [thread overview]
Message-ID: <20061107141415.GA23124@kruiskruid.demon.nl> (raw)
In-Reply-To: <45508BA8.8020306@eng.uts.edu.au>
On 2006-1108 00:35:36, Steve Murray wrote:
> Mario Frasca wrote:
>
> are you using cvs from the command line or -say- from emacs?
>
> Thanks for responding - I'm attempting to checkout just by invoking cvs
> from a terminal session.
nice, this makes things easier...
> session seems to be suspended at that point. When I request ...
>
> cvs -d:pserver:anonymous@elks.cvs.sourceforge.net:/cvsroot/elks login
>
> ... I get the response of ...
>
> Logging in to
> :pserver:anonymous@elks.cvs.sourceforge.net:2401/cvsroot/elks
> CVS password:
>
> ... almost immediately, but then when I hit the return key, I get nothing
> for about 30 seconds, then ...
>
> cvs [login aborted]: connect to
> elks.cvs.sourceforge.net(66.35.250.85):2401 failed: Connection timed out
strange... tried exactly the same from my computer at work and a mac at
home (copy & paste from your message to an xterm) and both log in then
get the whole tree without problems... the IP address you see matches
what I see here... I would think about a lower level network problem...
have you got an account really somewhere else?
Mario
--
[quello che cito] non esprime in alcun modo il mio pensiero personale
Papa Ratzinger
prev parent reply other threads:[~2006-11-07 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 12:34 ELKS sources - just how can the latest version be obtained? Steve Murray
2006-11-07 13:16 ` Mario Frasca
[not found] ` <45508BA8.8020306@eng.uts.edu.au>
2006-11-07 14:14 ` Mario Frasca [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061107141415.GA23124@kruiskruid.demon.nl \
--to=mfrasca@zonnet.nl \
--cc=Linux-8086@vger.kernel.org \
--cc=stevem@eng.uts.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox