From owner-freebsd-ports@FreeBSD.ORG Thu Feb 19 09:38:39 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 0B0E816A4CE for ; Thu, 19 Feb 2004 09:38:39 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB15243D1D for ; Thu, 19 Feb 2004 09:38:38 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id A9F01299; Thu, 19 Feb 2004 11:38:38 -0600 (CST) Date: Thu, 19 Feb 2004 11:38:38 -0600 From: Tillman Hodgson To: FreeBSD-Ports Message-ID: <20040219173838.GT68388@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.6i Subject: net/freenet -- how does one use it? (possibly broken) 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: Thu, 19 Feb 2004 17:38:39 -0000 Hody, Note that this is net/freenet, not net/freenet6 (I tripped over that in google enough times). After installing the freenet port, I'm at a bit of a loss as to how to actually /use/ it. The port doesn't install 'start-freenet.sh' which is referenced in /usr/local/share/doc/freenet/README. Instead, it appears that /usr/local/bin/freenet replaces it (though I might be wrong as I haven't gotten it to work you). Running that script produces: $ freenet Usage: /usr/local/bin/freenet [-h] [-i|-o] Options: -h Display this help message -c Configure FreeNet node -i Start a FreeNet node -o Stop a FreeNet node Running 'freenet -c' does the same thing, however. Delving into /usr/local/bin/freenet (it's a shell script), I notice lines like this: HOME_DIR=${HOME}/.freenet configure_freenet () { echo "Configuring FreeNet node" cd ${HOME_DIR} && ${JAVAVM_CALL} -jar ./${JAR_START} freenet.node.Main --config "${@}" } Which don't see right ... I don't have a ~/.freenet, and the jar files are actually in /usr/local/share/java/jar/freenet. If I manually do: /usr/local/bin/javavm -jar /usr/local/share/java/jar/freenet/freenet.jar freenet.node.Main --config I enter a configuration system. I haven't followed this track because I have no idea if I'm on the right track or not. Is there some documentation on how to properly install this port that I've overlooked? I'm not even sure if I'm supposed to run it as my regular user or as root, or how to configure a permanenet node, or ... :-) Thanks for your time, -T -- ... the most palpable description of bread is that of hunger. Tadeusz Rozewicz