On Sun, Sep 21, 2003 at 10:35:38AM -0700, Todd Walton wrote:
> On Sun, 21 Sep 2003, Todd wrote:
> 
> > I've installed freenet-0.5.2.r1 on FreeBSD 5.1 with jdk-1.3.1p8_2 from 
> > ports.
> 
> Then you want the pre-NIO version of Freenet.  jdk-1.3.1 can't handle NIO, 
> I believe.
> 
> Download, I think:
> http://freenetproject.org/snapshots/freenet-nio-061803.jar

I doubt very much that that will work... lastGoodBuild is 5029...

> 
> Rename it freenet.jar.  Start node.
> 
> > Also, the normal start and stop scripts are different than what I 
> > encounter in the documentation online. The following are the only 
> > commands I know about:
> > Usage: /usr/local/bin/freenet
> 
> Where did you get your installation from?  If it's from ports then the 
> scripts were probably tailored, which is why they're different.
> 
> If you download from freenetproject.org, there's no 
> /usr/local/bin/freenet.  The whole thing lives in it's own directory, 
> including the commands.
> 
> > So if I get an updated seed node, do I just need to replace the 
> > seednode.ref file and restart freenet (freenet -i) or is there something 
> > further that must be done before it will use the new seednodes?
> 
> If you're using the freenetproject.org install, you'd replace 
> seednodes.ref and the node would automatically detect it, if it's newer 
> than what it already has.
> 
> If you're using FreeBSD's version of freenet, you'll probably have to ask 
> it's maintainer (unless somebody else here uses FreeBSD).
> 
> -todd
> _______________________________________________
> Support mailing list
> [EMAIL PROTECTED]
> http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support

-- 
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support

Reply via email to