Freenet 0.7 build 1143 was released yesterday, and is mandatory tomorrow.
Sorry for the lack of changelogs. Here they are for the last few builds:
1141:
- Don't give up so easily when loading plugins. We were having some problems
with plugins failing to load.
1142:
- Show one-line summaries of
Freenet 0.7 build 1139 is now available, please upgrade, it will be mandatory
on Wednesday. The only change in 1139 (other changes require further testing
and will be released in 1140 soon), is that we now ignore nodes with less
than 40% uptime when deciding whether we are the closest node for
Freenet 0.7 build 1139 is now available, please upgrade, it will be mandatory
on Wednesday. The only change in 1139 (other changes require further testing
and will be released in 1140 soon), is that we now ignore nodes with less
than 40% uptime when deciding whether we are the closest node for
Freenet 0.7 build 1138 is now available. Please upgrade, it will be mandatory
on Sunday. Major changes:
- Stop trying to contact seednodes after announcement has succeeded.
- Make the opennet warning dismissable, but it will come back after a restart.
- Some stats fixes that hopefully will help
Freenet 0.7 build 1136 is now available. Please upgrade. I forgot to announce
1135; a big part of 1136 is fixing bugs in 1135. Apologies for the recent
node crashes...
Changes:
1135:
- Increase the redundancy on splitfiles from 150% to 200%. Your node only
needs to download 100% of this to
On Thursday 03 April 2008 19:13, Matthew Toseland wrote:
> Freenet 0.7 build 1132 is now available, and will be mandatory on Saturday.
> Please upgrade ASAP. The main change in this build is a large number of
> bugfixes to the client layer, which hopefully have fixed the stalling
> downloads
Freenet 0.7 build 1132 is now available, and will be mandatory on Saturday.
Please upgrade ASAP. The main change in this build is a large number of
bugfixes to the client layer, which hopefully have fixed the stalling
downloads bug. Please tell us if you still get downloads progressing quickly
Freenet 0.7 build 1131 is now available, please upgrade. Major changes:
- Stop sending the old-format (very large) SSK messages. Other minor changes
aimed at avoiding sending huge packets (which frequently cause connectivity
problems, excessive resends etc).
- Improvements to the stats that
Freenet 0.7 build 1131 is now available, please upgrade. Major changes:
- Stop sending the old-format (very large) SSK messages. Other minor changes
aimed at avoiding sending huge packets (which frequently cause connectivity
problems, excessive resends etc).
- Improvements to the stats that
Freenet version 0.7 Release Candidate 1 is now available for public testing.
Freenet is a global peer-to-peer network designed to allow users to publish
and consume information without fear of censorship. To use it, you must
download the Freenet software, available for Windows, Mac, Linux and
Freenet version 0.7 Release Candidate 1 is now available for public testing.
Freenet is a global peer-to-peer network designed to allow users to publish
and consume information without fear of censorship. To use it, you must
download the Freenet software, available for Windows, Mac, Linux and
Freenet 0.7 build 1130 is now available. Please upgrade. This build fixes
various bugs mostly in the client layer, hopefully including the bug that was
causing downloads to stall, and including a bug causing bogus collisions on
SSKs, which may have harmed Freemail and ARKs. 1130 is mandatory on
Freenet 0.7 build 1129 is now available and will be mandatory on Sunday.
Please upgrade. Changes include an important stats bug which was causing
major problems for some nodes, and a few minor bugs. Also, we have been
working on the installer: it now creates a firefox profile customised for
Freenet 0.7 build 1129 is now available and will be mandatory on Sunday.
Please upgrade. Changes include an important stats bug which was causing
major problems for some nodes, and a few minor bugs. Also, we have been
working on the installer: it now creates a firefox profile customised for
>
>* Matthew Toseland [2008-03-25 19:41:59]:
>
>> Sorry, I'm the idiot who decided to create a firefox profile. I was simply
>> trying to avoid some major performance issues we have because the default
>> settings are not good for Freenet, and asking users to change them globally
>> also
* Matthew Toseland [2008-03-25 19:41:59]:
> Sorry, I'm the idiot who decided to create a firefox profile. I was simply
> trying to avoid some major performance issues we have because the default
> settings are not good for Freenet, and asking users to change them globally
> also sucks.
>
>
* Matthew Toseland [EMAIL PROTECTED] [2008-03-25 19:41:59]:
Sorry, I'm the idiot who decided to create a firefox profile. I was simply
trying to avoid some major performance issues we have because the default
settings are not good for Freenet, and asking users to change them globally
also
Okay, having investigated this, I'm fairly confident of the current theory:
- If a copy of Firefox is already running with the default profile, and we
launch a copy with our profile (-no-remote -P ), everything
works fine (as long as our copy exits before the default one does).
- The default
Sorry, I'm the idiot who decided to create a firefox profile. I was simply
trying to avoid some major performance issues we have because the default
settings are not good for Freenet, and asking users to change them globally
also sucks.
Freenet has not destroyed any data, it has simply created
1128 fixes a couple of serious bugs in 1127. Please upgrade. Sorry folks.
On Tuesday 25 March 2008 14:15, Matthew Toseland wrote:
> Freenet 0.7 build 1127 is now available. It will be mandatory on Thursday.
> Please upgrade ASAP. This build includes a wide range of bugfixes and one or
> two new
Freenet 0.7 build 1127 is now available. It will be mandatory on Thursday.
Please upgrade ASAP. This build includes a wide range of bugfixes and one or
two new features:
- Transport layer fixes related to losing key trackers, resulting in hanging
packet throttle - we were no longer able to send
Freenet 0.7 build 1127 is now available. It will be mandatory on Thursday.
Please upgrade ASAP. This build includes a wide range of bugfixes and one or
two new features:
- Transport layer fixes related to losing key trackers, resulting in hanging
packet throttle - we were no longer able to send
1128 fixes a couple of serious bugs in 1127. Please upgrade. Sorry folks.
On Tuesday 25 March 2008 14:15, Matthew Toseland wrote:
Freenet 0.7 build 1127 is now available. It will be mandatory on Thursday.
Please upgrade ASAP. This build includes a wide range of bugfixes and one or
two new
Sorry, I'm the idiot who decided to create a firefox profile. I was simply
trying to avoid some major performance issues we have because the default
settings are not good for Freenet, and asking users to change them globally
also sucks.
Freenet has not destroyed any data, it has simply created
* Matthew Toseland [EMAIL PROTECTED] [2008-03-25 19:41:59]:
Sorry, I'm the idiot who decided to create a firefox profile. I was simply
trying to avoid some major performance issues we have because the default
settings are not good for Freenet, and asking users to change them globally
also
Freenet 0.7 build 1126 is now available (sorry). Please upgrade, it will be
mandatory on Saturday. This contains a series of bugfixes for the last two
builds, relating to the new SSK messages, and the output bandwidth stats
(which affect the number of requests the node accepts, so are
Freenet 0.7 build 1125 is available, please upgrade as it will be mandatory on
Saturday. There are a couple of major changes:
- Transfer backoff. Ordinary backoff was not dealing with transfer failures,
we now have a separate mechanism for backoff after a transfer failure.
- Split up some SSK
Freenet 0.7 build 1125 is available, please upgrade as it will be mandatory on
Saturday. There are a couple of major changes:
- Transfer backoff. Ordinary backoff was not dealing with transfer failures,
we now have a separate mechanism for backoff after a transfer failure.
- Split up some SSK
Freenet 0.7 build 1126 is now available (sorry). Please upgrade, it will be
mandatory on Saturday. This contains a series of bugfixes for the last two
builds, relating to the new SSK messages, and the output bandwidth stats
(which affect the number of requests the node accepts, so are
Freenet 0.7 build 1124 is now available. Please upgrade, it will be mandatory
on Friday. Changes include:
- Send queued blocks in the order they were queued, rather than in "random"
notify order. This should reduce the number of failing block transfers.
- Fix a few NullPointerException's,
Freenet 0.7 build 1124 is now available. Please upgrade, it will be mandatory
on Friday. Changes include:
- Send queued blocks in the order they were queued, rather than in random
notify order. This should reduce the number of failing block transfers.
- Fix a few NullPointerException's,
after downloading again it worked.
thank you!
David Sowder schrieb:
> It looks like your freenet.jar is either missing or corrupt. Perhaps
> running ./update.sh will fix that up for you.
>
> Max Giesbert wrote:
>> I just gave the installation a try but get the following errors in
>>
after downloading again it worked.
thank you!
David Sowder schrieb:
It looks like your freenet.jar is either missing or corrupt. Perhaps
running ./update.sh will fix that up for you.
Max Giesbert wrote:
I just gave the installation a try but get the following errors in
wrapper.log:
I just gave the installation a try but get the following errors in
wrapper.log:
STATUS | wrapper | 2008/03/17 14:49:55 | --> Wrapper Started as Daemon
STATUS | wrapper | 2008/03/17 14:49:55 | Launching a JVM...
ERROR | wrapper | 2008/03/17 14:49:55 | Unable to start JVM: No such
file or
It looks like your freenet.jar is either missing or corrupt. Perhaps
running ./update.sh will fix that up for you.
Max Giesbert wrote:
> I just gave the installation a try but get the following errors in
> wrapper.log:
>
> STATUS | wrapper | 2008/03/17 14:49:55 | --> Wrapper Started as Daemon
I just gave the installation a try but get the following errors in
wrapper.log:
STATUS | wrapper | 2008/03/17 14:49:55 | -- Wrapper Started as Daemon
STATUS | wrapper | 2008/03/17 14:49:55 | Launching a JVM...
ERROR | wrapper | 2008/03/17 14:49:55 | Unable to start JVM: No such
file or
It looks like your freenet.jar is either missing or corrupt. Perhaps
running ./update.sh will fix that up for you.
Max Giesbert wrote:
I just gave the installation a try but get the following errors in
wrapper.log:
STATUS | wrapper | 2008/03/17 14:49:55 | -- Wrapper Started as Daemon
Freenet 0.7 build 1123 is now available. Please upgrade (hopefully your node
will do this for you). Major changes:
- Fix a bunch of problems with the link level / connection setup code, found
in simulations.
- Tune the database parameters to try to avoid long stalling waiting for
background
Freenet 0.7 build 1123 is now available. Please upgrade (hopefully your node
will do this for you). Major changes:
- Fix a bunch of problems with the link level / connection setup code, found
in simulations.
- Tune the database parameters to try to avoid long stalling waiting for
background
Has anyone else had problems installing freenet on an Ubuntu Linux system?
--Joel
Has anyone else had problems installing freenet on an Ubuntu Linux system?
--Joel
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at
Freenet 0.7 build 1122 is now available, and will be mandatory on Wednesday.
Please upgrade. This build includes many improvements/bugfixes, including:
- Fix a bug that was causing a large number of BlockTransmitter's to get stuck
when a connection was lost.
- Reduce the max HTL to 10, after 10
Freenet 0.7 build 1122 is now available, and will be mandatory on Wednesday.
Please upgrade. This build includes many improvements/bugfixes, including:
- Fix a bug that was causing a large number of BlockTransmitter's to get stuck
when a connection was lost.
- Reduce the max HTL to 10, after 10
Freenet 0.7 build 1119 is available and will be mandatory on Monday. Please
upgrade. The last few builds were seriously broken in various ways. Sorry for
the recent mess... :| Some bug fixes, and some minor features, exposed (or
sometimes caused) larger bugs, and I didn't properly test
Apologies for the new mandatory just after the last build, but it's worth it.
Build 1116 has various improvements to connectivity for nodes with low MTUs
and/or evil firewalls. Such nodes cannot successfully send or receive large
UDP packets. Connecting to seednodes has always used such big
Freenet 0.7 build 1115 is now available, and will be mandatory on Monday.
Please upgrade. Changes:
- Link level congestion control should work better.
- More HTL changes: 10 hops at HTL 15, then 14 hops, then 4 hops at HTL 1. We
will reduce the max HTL to 10 in the next build and that'll be it.
Freenet 0.7 build 1115 is now available, and will be mandatory on Monday.
Please upgrade. Changes:
- Link level congestion control should work better.
- More HTL changes: 10 hops at HTL 15, then 14 hops, then 4 hops at HTL 1. We
will reduce the max HTL to 10 in the next build and that'll be it.
1117 is out with a bugfix to that code (and a fix for subdirs in implicit
containers). Mandatory on Monday. Sorry folk.
On Friday 29 February 2008 18:46, Matthew Toseland wrote:
Apologies for the new mandatory just after the last build, but it's worth
it.
Build 1116 has various improvements
Please could you uninstall Freenet and then try again (from the download
page) ? Nextgens has fixed some bugs in the installer that might have caused
your problems.
On Sunday 24 February 2008 02:02, Craig Kiczek wrote:
> I've installed freenet, but opening the "first time wizard" gives me an
>
Freenet 0.7 build 1113 is now available (and will be mandatory tomorrow).
Changelog:
- Various fixes to how we handle HTL.
- Lots of client layer fixes (mostly relating to splitfile downloads and the
cooldown queue).
- Major bugfixes to per-node failure tables and ULPRs.
- Improvements to the
I've installed freenet, but opening the "first time wizard" gives me an
"Internet Explorer cannot display this page" error. Here is the text shown
in the installation dialog box. It looks like there is some problem.
Registering .fref file extension
Downloading update.cmd
Downloading the
I've installed freenet, but opening the first time wizard gives me an
Internet Explorer cannot display this page error. Here is the text shown
in the installation dialog box. It looks like there is some problem.
Registering .fref file extension
Downloading update.cmd
Downloading the
Freenet 0.7 build 1112 is now available. It will be mandatory on Thursday so
please update ASAP (if your node has auto-update enabled it will do this for
you). This build features a number of substantial changes (I apologise for
the length of this mail!):
- Major changes to HTL (the means by
Freenet 0.7 build 1112 is now available. It will be mandatory on Thursday so
please update ASAP (if your node has auto-update enabled it will do this for
you). This build features a number of substantial changes (I apologise for
the length of this mail!):
- Major changes to HTL (the means by
Freenet 0.7 build is now available. Please upgrade! This build will be
mandatory on Monday, and includes many improvements:
- Much faster swapping (via queueing swap requests for a short period rather
than rejecting them).
- Don't delete downloads.dat.gz (the file containing the persistent
Freenet 0.7 build is now available. Please upgrade! This build will be
mandatory on Monday, and includes many improvements:
- Much faster swapping (via queueing swap requests for a short period rather
than rejecting them).
- Don't delete downloads.dat.gz (the file containing the persistent
Freenet 0.7 build 1109 is now available. Please upgrade ASAP. This build will
be mandatory on Tuesday, and includes some critical bugfixes and major new
features:
- The "my node stops using bandwidth after N hours" bug is fixed.
- Ultra-Lightweight Passive Requests and Per-node Failure Tables
Freenet 0.7 build 1109 is now available. Please upgrade ASAP. This build will
be mandatory on Tuesday, and includes some critical bugfixes and major new
features:
- The my node stops using bandwidth after N hours bug is fixed.
- Ultra-Lightweight Passive Requests and Per-node Failure Tables are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Nyhus wrote:
> On Monday 04 February 2008 14:45:31 Ermanno Baschiera wrote:
>> IMHO that's a problem of process priority. Anybody knows how to rise
>> the priority of freenet? (or JVM, I don't know which one)
>> (My CPU isn't too slow for
Thanks a lot boys!
I edited run.sh (priority 0) and also added PORTAGE_NICENESS="15" in make.conf.
I tested my new configuration with a quick kernel compilation...
That's fine now!
-ermanno
2008/2/5, Bob :
> Hi,
>
> On 2008-02-04 13:45, Ermanno Baschiera wrote:
> > Hello,
> > I'm running my node
Hi,
On 2008-02-04 13:45, Ermanno Baschiera wrote:
> Hello,
> I'm running my node on a Gentoo Linux machine.
> You know... we gentooers sometimes have to compile updates and new
> packages. Ok, we OFTEN have to compile stuff. :-)
> During those compile sessions, my node pings higher and higher. Up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Nyhus wrote:
On Monday 04 February 2008 14:45:31 Ermanno Baschiera wrote:
IMHO that's a problem of process priority. Anybody knows how to rise
the priority of freenet? (or JVM, I don't know which one)
(My CPU isn't too slow for Freenet. My
Hi,
On 2008-02-04 13:45, Ermanno Baschiera wrote:
Hello,
I'm running my node on a Gentoo Linux machine.
You know... we gentooers sometimes have to compile updates and new
packages. Ok, we OFTEN have to compile stuff. :-)
During those compile sessions, my node pings higher and higher. Up to
Thanks a lot boys!
I edited run.sh (priority 0) and also added PORTAGE_NICENESS=15 in make.conf.
I tested my new configuration with a quick kernel compilation...
That's fine now!
-ermanno
2008/2/5, Bob [EMAIL PROTECTED]:
Hi,
On 2008-02-04 13:45, Ermanno Baschiera wrote:
Hello,
I'm running
On Monday 04 February 2008 14:45:31 Ermanno Baschiera wrote:
> IMHO that's a problem of process priority. Anybody knows how to rise
> the priority of freenet? (or JVM, I don't know which one)
> (My CPU isn't too slow for Freenet. My monitoring tool says it's 25%
> busy average)
I'm not sure how
Hello,
I'm running my node on a Gentoo Linux machine.
You know... we gentooers sometimes have to compile updates and new
packages. Ok, we OFTEN have to compile stuff. :-)
During those compile sessions, my node pings higher and higher. Up to
22sec! Also if there's heavy use of samba, my node gets
Hello,
I'm running my node on a Gentoo Linux machine.
You know... we gentooers sometimes have to compile updates and new
packages. Ok, we OFTEN have to compile stuff. :-)
During those compile sessions, my node pings higher and higher. Up to
22sec! Also if there's heavy use of samba, my node gets
Freenet 0.7 build 1108 is now available. Please upgrade, it is mandatory on
Tuesday. This build includes lots of changes, bugfixes and improvements:
- Some memory optimisations in the client layer code (the client layer is
responsible for most of Freenet's memory usage if you have
Sorry folks, we need yet another pre-0.7-alpha-2 testing build. This one is
mandatory at midnight tonight. Changes:
- Even more messaging layer fixes, affecting data transfer and possibly
swapping.
- Crypto paranoia.
- IP hint related fixes, and detect when an ipAddressOverride is invalid and
Freenet 0.7 build 1105 is now available. Please upgrade and test this build,
report any bugs you find to the bug tracker. Changes:
- Fix the default bookmarks: when I rerordered the indexes I accidentally
deleted the description for Index des sites Fran?ais ... and this was causing
Freenet 0.7 build 1104 is now available. Please upgrade ASAP. This build will
be mandatory at 1800 UCT on Saturday (tomorrow), because we want to get an
alpha out as soon as early as possible next week, and we need further testing
of the important bug fixes in 1104 (and most people are on
Freenet 0.7 build 1104 is now available. Please upgrade ASAP. This build will
be mandatory at 1800 UCT on Saturday (tomorrow), because we want to get an
alpha out as soon as early as possible next week, and we need further testing
of the important bug fixes in 1104 (and most people are on
Freenet 0.7 build 1103 is now available, please upgrade ASAP. Hopefully the
auto-update system will work, but if it doesn't please use the update script.
The build will be mandatory tomorrow (0:00 25 jan UTC) as it contains a fix
to a critical bug which was breaking requests. There is also a
Freenet 0.7 build 1102 is now available. Please upgrade ASAP. This will be
mandatory on Friday. The build includes a couple of internal features
relating to noderefs (and therefore to getting rid of big packets which can
be a problem for many users), and some request optimisations and bug fixes
Freenet 0.7 build 1102 is now available. Please upgrade ASAP. This will be
mandatory on Friday. The build includes a couple of internal features
relating to noderefs (and therefore to getting rid of big packets which can
be a problem for many users), and some request optimisations and bug fixes
Freenet 0.7 build 1103 is now available, please upgrade ASAP. Hopefully the
auto-update system will work, but if it doesn't please use the update script.
The build will be mandatory tomorrow (0:00 25 jan UTC) as it contains a fix
to a critical bug which was breaking requests. There is also a
Freenet 0.7 build 1101 is now available. Please upgrade ASAP; the auto-update
should work. The only major change in this build is to turn off request
coalescing, a feature which wasn't properly thought out and has caused
request timeouts since the beginning of 0.7. It is mandatory on Monday so
Freenet 0.7 build 1101 is now available. Please upgrade ASAP; the auto-update
should work. The only major change in this build is to turn off request
coalescing, a feature which wasn't properly thought out and has caused
request timeouts since the beginning of 0.7. It is mandatory on Monday so
Freenet 0.7 build 1100 is now available. This build will be mandatory on the
23rd (Wednesday), please upgrade. Especially if you are a seednode:
announcement via seednodes was broken in 1099. Other changes:
- Various improvements to the queue page, you can now upload directories as
well as
On Thursday 17 January 2008 19:49, niel wrote:
> On Thursday 17 January 2008 19.56.30 Matthew Toseland wrote:
> > Freenet 0.7 build 1099 is now available. Please upgrade ASAP, this build
> > will be mandatory on Monday. Major changes include:
> > - Fix a major bug that was causing downloads to
Freenet 0.7 build 1099 is now available. Please upgrade ASAP, this build will
be mandatory on Monday. Major changes include:
- Fix a major bug that was causing downloads to hang.
- Fix a bug that was causing us to start too many requests for the same keys
when under load.
- Fix a bug causing us
On Thursday 17 January 2008 19:49, niel wrote:
On Thursday 17 January 2008 19.56.30 Matthew Toseland wrote:
Freenet 0.7 build 1099 is now available. Please upgrade ASAP, this build
will be mandatory on Monday. Major changes include:
- Fix a major bug that was causing downloads to hang.
-
Freenet 0.7 build 1098 is now available. Please upgrade. This build includes
major optimisations to handling of messages, data transfer and requests
thanks to Robert Hailey, much better datastore reconstruction (we now keep
the LRU order of the data, and we keep SSKs), deadlock fixes,
On Friday 04 January 2008 15.48.17 Matthew Toseland wrote:
> On Friday 04 January 2008 06:51, niel wrote:
> > On Friday 04 January 2008 00.51.33 Matthew Toseland wrote:
> > > Freenet 0.7 build 1097 is now available. Please upgrade. This is mostly
> > > bugfixes, but some of them are fairly
On Friday 04 January 2008 06:51, niel wrote:
> On Friday 04 January 2008 00.51.33 Matthew Toseland wrote:
> > Freenet 0.7 build 1097 is now available. Please upgrade. This is mostly
> > bugfixes, but some of them are fairly significant. There is much improved
> > support for running the node on
On Friday 04 January 2008 00.51.33 Matthew Toseland wrote:
> Freenet 0.7 build 1097 is now available. Please upgrade. This is mostly
> bugfixes, but some of them are fairly significant. There is much improved
> support for running the node on GCJ thanks to xor, although much remains to
> be done
On Friday 04 January 2008 06:51, niel wrote:
On Friday 04 January 2008 00.51.33 Matthew Toseland wrote:
Freenet 0.7 build 1097 is now available. Please upgrade. This is mostly
bugfixes, but some of them are fairly significant. There is much improved
support for running the node on GCJ
Freenet 0.7 build 1097 is now available. Please upgrade. This is mostly
bugfixes, but some of them are fairly significant. There is much improved
support for running the node on GCJ thanks to xor, although much remains to
be done (the web interface isn't very responsive on GCJ for example).
Freenet 0.7 build 1097 is now available. Please upgrade. This is mostly
bugfixes, but some of them are fairly significant. There is much improved
support for running the node on GCJ thanks to xor, although much remains to
be done (the web interface isn't very responsive on GCJ for example).
On Friday 04 January 2008 00.51.33 Matthew Toseland wrote:
Freenet 0.7 build 1097 is now available. Please upgrade. This is mostly
bugfixes, but some of them are fairly significant. There is much improved
support for running the node on GCJ thanks to xor, although much remains to
be done (the
On Wednesday 26 December 2007 20:28, Sean Machado wrote:
> Hi all,
>
> Im running Freenet 0.7 (latest version downloaded on
> December 23rd) on a Windows xp sp2 machine with an
> Intel Pentium 4 3.2Ghz dual core with 1.5GB ram of DDR
> 400 and my CPU is hitting near to 100% with no other
>
Hi all,
Im running Freenet 0.7 (latest version downloaded on
December 23rd) on a Windows xp sp2 machine with an
Intel Pentium 4 3.2Ghz dual core with 1.5GB ram of DDR
400 and my CPU is hitting near to 100% with no other
applications running.
Checking resources shows java.exe (freenet) chewing up
Freenet 0.7 build 1096 is now available, and will be mandatory on Monday
(sorry, we caught a BigBug...). Changes:
- CHK inserts: Fixed a major bug: We were never timing out waiting for
completion notifications, so if a node timed out then the CHK inserter would
continue to wait forever. So
Sorry folks. Freenet 0.7 build 1095 is now available. The main reason for this
build (so soon after 1094) is to fix a bug that was preventing new nodes from
being initialised properly. It also includes a patch from ET on Frost for SSL
support for the web interface, FCP etc, and some minor
Freenet 0.7 build 1096 is now available, and will be mandatory on Monday
(sorry, we caught a BigBug...). Changes:
- CHK inserts: Fixed a major bug: We were never timing out waiting for
completion notifications, so if a node timed out then the CHK inserter would
continue to wait forever. So
Freenet 0.7 build 1094 is now available. It's mandatory on Sunday. Please
upgrade. One major focus of recent builds has been to deal with the fact that
connections to seednodes were sending very big packets, which many firewalls
were dropping; this build should stop that. Also, we have lots of
Sorry folks. Freenet 0.7 build 1095 is now available. The main reason for this
build (so soon after 1094) is to fix a bug that was preventing new nodes from
being initialised properly. It also includes a patch from ET on Frost for SSL
support for the web interface, FCP etc, and some minor
Freenet 0.7 build 1093 is now available. Please upgrade, it will be mandatory
on Friday. It includes various improvements to the seed-node connection code,
so in particular our current seednodes should upgrade. It also includes some
major refactoring on the low-level CHK insert code, which
Freenet 0.7 build 1093 is now available. Please upgrade, it will be mandatory
on Friday. It includes various improvements to the seed-node connection code,
so in particular our current seednodes should upgrade. It also includes some
major refactoring on the low-level CHK insert code, which
Freenet 0.7 build 1092 is now available. Please upgrade. Changes include:
- Fixed a major bug which caused us to lose various critical files when we ran
out of disk space.
- More improvements to the announcement code.
- Various minor optimisations and bugfixes.
There has also been significant
901 - 1000 of 2017 matches
Mail list logo
