Thanks Greg,
That clears things up some.
Can you tell me how to perform an upgrade with loosing all of my
routing info? It appears when I restart freenet it starts all over
trying to learn the network.
For instance:
Do I need to maintain the seedNodes file to include only those
hosts I am likely to connect to?
>
> You're still using the node from Debian unstable, yes?
>
Yes, I noticed that it was a little newer than what I was running
so I have upgraded from 465 -> 468
> $ apt-cache show freenet-unstable
> Package: freenet-unstable
> [...]
> Version: 0.4.3+20020618-1
Yup, that's the one.
>
> So it's from June 18th. That was before the build 474 (or 475)
> mandatory upgrade. It will not talk to any post-474 nodes at all;
> but if you can manage to find a bunch of other nodes that are as
> old as yours, it will happily talk to them, and you'll have a little
> miniature Freenet of your own.
cute.
According to my routing table I have successfully connected to nodes as
late as 476.
>
> If you expect to talk to the mainstream Freenet, you'll have to
> upgrade to a newer build. File a bug report against the Debian
> package (http://bugs.debian.org/freenet-unstable) and tell the
> maintainer that not only does a new Freenet mandatory update (build
> 474) exist, but build 480 is supposed to fix important bugs.
>
> Or just replace your freenet.jar file with the latest snapshot, and
> restart Freenet. (This will mean that debsums won't recognize the
> md5sum of your freenet.jar file any longer, but that's OK as long as
> you don't run debsums.... ;-) )
I will try that next.
I can always force apt to comply regardless of md5sums.
_______________________________________________
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
