On Thu, Sep 26, 2002 at 10:41:54PM -0700, Ian Clarke wrote: > From yesterday's FF: > > -- > Recent changes to Freenet configuration mean that everybody needs to > update their configuration file or lose fproxy access. I haven't updated > my main node recently so I'm not exactly sure of the changes required, > but anybody worried about upgrading is advised to check out the Freenet > development mailing list archives for further information. Also, the > Windows installer apparently no longer works, so a reinstall won't fix > any update woes either. > -- > > We need to address this problem ASAP, probably by modifying the Java to > deal with this (if only temporarily). The problem is that some people have hardcoded services= (if they use the default, since months ago, which is commented out, they'll get the default list of services). They need to remove fproxy and nodeinfo, and add mainport. They also need to add mainport.bindAddress, mainport.allowedHosts and mainport.port, in some cases. But it's not hard. > > In future, we should be careful of modifications which could stop > people's nodes from working on an upgrade without modifications to > freenet.conf. > > Perhaps we need a more generic way to handle this type of situation. > Suggestions are welcome. > > Ian. > > -- > Ian Clarke ian at freenetproject.org > Founder & Coordinator, The Freenet Project http://freenetproject.org/ > Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ > Personal Homepage http://locut.us/
-- Matthew Toseland mtoseland at blueyonder.co.uk amphibian at sourceforge.net Freenet/Coldstore open source hacker. Employed full time by Freenet Project Inc. from 11/9/02 to 11/11/02. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020927/b684a057/attachment.pgp>
