linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: schinder@pobox.com
To: Justin Shore <macdaddy@vinnie.ksu.ksu.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: RC5 client and LPPC R5
Date: Fri, 15 Oct 1999 08:44:54 -0400	[thread overview]
Message-ID: <19991015084454.A4206@pobox.com> (raw)
In-Reply-To: <v04220700b42c89dfdc72@[192.168.1.5]>


On Fri, Oct 15, 1999 at 02:39:01AM -0500, Justin Shore wrote:
} 
} Has anyone gotten the two to mix successfully?  One of the binaries I 

Yes.  I'm using 2.7100.412.

} tried died right off the bat.  The second worked fine for basically 
} everything except for when it tried to access the key server for a 
} new set of blocks to hack on (basically it works except for network 
} access).  I emailed distributed about a month back and never got a 
} response.  Has anyone gotten it to work with R5?  I can't remember 
} the specific error.  I think it just bitched about not being able to 
} resolve the DNS for the key server.  If ya know something please let 
} me know.  Thanks!

If that's what it bitched about, it sounds like you have something set
up incorrectly.  Anyway, I don't remember where exactly I got the one
I'm using, but a quick check shows there's an rpm on the Yellow Dog CS
1.1 install CD, so it must be on their site.  I don't see it on my
LinuxPPC Q3 install CD, but it might be on the other one, and I'll bet
they have it somewhere on linuxppc.com.

} 
} Justin
} 

-- 
Paul Schinder
schinder@pobox.com

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-10-15 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-15  7:39 RC5 client and LPPC R5 Justin Shore
1999-10-15 12:44 ` schinder [this message]
1999-10-15 17:13   ` Justin Shore

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=19991015084454.A4206@pobox.com \
    --to=schinder@pobox.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=macdaddy@vinnie.ksu.ksu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).