after much frustration, the following worked for me:

  1. cpan <-- answer "no" to initial setup.
    This allows (auto configured) Config.pm file (see below) to be initialised. Previously I think this file had "1;" or something helpful in it!
  2. I then added:
    'dontload_hash' => {"Net::FTP" => 1, "LWP" =>1 }, # disable Net::FTP + and LWP which usually hang to: /usr/lib/perl5/5.8.8/CPAN/Config.pm - see section: $CPAN::Config = { ...
    but this alone did not seem to do the job. I'm still not sure if this step had any effect.
  3. (in cpan shell)
    o conf urllist http://ppm.activestate.com/CPAN http://cpan.perl.org o conf commit quit

worked for me - thanks!

20100528 Janitored by Corion: Added formatting, code tags, as per Writeup Formatting Tips


In reply to Re^4: Problem Starting CPAN Shell with ftp.perl.org by Anonymous Monk
in thread Problem Starting CPAN Shell with ftp.perl.org by monkfan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.