From owner-freebsd-ports@FreeBSD.ORG Sun Dec 12 08:08:51 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8BA116A4CF for ; Sun, 12 Dec 2004 08:08:51 +0000 (GMT) Received: from mail.miketodd.com (ns2.miketodd.com [66.15.3.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9648143D39 for ; Sun, 12 Dec 2004 08:08:51 +0000 (GMT) (envelope-from miketodd@netscape.com) Received: from netscape.com (corp.miketodd.com [66.15.3.240]) by mail.miketodd.com (8.11.6/8.11.6) with ESMTP id iBC88ov06881; Sun, 12 Dec 2004 00:08:50 -0800 (PST) (envelope-from miketodd@netscape.com) Message-ID: <41BBFC0D.9050502@netscape.com> Date: Sun, 12 Dec 2004 00:06:37 -0800 From: Mike Todd User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: fbsd@opal.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org Subject: FreeBSD Port: boinc-setiathome-4.07 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Dec 2004 08:08:52 -0000 Just looking for a hint or clue: I downloaded the boinc-setiathome-4.07 and boinc-client-4.13 "package" files from the FreeBSD Port collection on freebsd.org and did not end up with a README file telling me how to implement what I downloaded nor any kind of make file that would let me do a "make install" nor any scripts or program files that started either an install, configuration, or initialization operation. Could you direct me to a place where I might get enough clues to get started with this? It's been much too long since I shut down my setiathome opeation on my freegsc machines. I "accidentally" "upgraded" an old windows machine to the seti-boinc project and, to my dismay, found that all of my freebsd machines quit communicating with seti. Anyway, thanks for the help... Mike Todd