[freenet-support] Important news for users of stable dual-network nodes -- Please read!

[Conrad J. Sabatier]

Please excuse the crossposting, but I felt this was important enough to
make sure it was seen by those who may not be subscribed to this or that
list.

The following will be appearing later today in DFI's News section:

Feb 25, 2005:  Finally got around to committing to CVS an overlooked
update to the stable version of src/freenet/Version.java.  I had updated
the unstable version of this file several weeks ago (see Jan 20, 2005
below), but forgot to sync up the one in stable.  As a result, there was
a mismatch between the protocol version stable was expecting unstable
nodes to be using, and the one unstable nodes actually were using. 
Those of you running dual-network nodes should start seeing better
results now, as more and more stable users update their nodes to include
this latest update.  Sorry for not taking care of this sooner! 

-- 
Conrad J. Sabatier [EMAIL PROTECTED] -- In Unix veritas
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Two questions

[Conrad J. Sabatier]

On Thu, 24 Feb 2005 07:02:39 +0100, Marco A. Calamari
[EMAIL PROTECTED] wrote:

 On Wed, 2005-02-23 at 21:44 -0800, Todd Walton wrote:
  On Wed, 23 Feb 2005 10:41:36 +0100, Marco A. Calamari
  [EMAIL PROTECTED] wrote:
   
   the fact that [FIND] is still the one of 24/12/2004 is due
I'm using the stable Freenet ?
  
  No.  FIND is a DBR.  If you can load it, then it's been inserted
  very recently.  23/12/2004 is the date of the proprietor's most
  recent comment.  It's just that he hasn't found reason to comment
  since then.
 
 Many thanks for your answer, but the site say
 
 index generated 2004 12 22.
 
 Of course it is inserted every day, but seems to me
  unmantained since then.

That is correct.  Sonax, maintainer of FIND, has been having problems
with the spider used to generate the index, and hasn't had the time or
inclination to fix it.

He's still inserting the site daily, but the actual index data has not
been updated in a couple of months now.

I've offered to help him resolve whatever issues are involved, but he
says he just doesn't have the time or motivation to do it at this time. 
Perhaps at some (hopefully near) future date.

  
   SOmenone haave suggestion about the HTL to unse for insertion
in both stable and unstable Freenet ?
  
  I use 25, and let the network reduce it as it sees fit.  MaxHTL
  (what the network reduces HTL to) is something like 20 these days.
 
 I had positive results inserting with htl=6 in stable.
 
  
  Someone else would likely have something better to say about that.
 
 I really hope so ;)
 
 Ciao.   Marco

I follow the advice given by FIW (the Freesite Insertion Wizard), i.e.,
for DBR sites, use a lower HTL (say, 15) than for an edition site or a
one-shot site (where you may want to use, say, 25).  This makes sense,
and seems to work well enough.

The reasoning behind this is that the more frequently a site's data is
updated, the less need for very deep insertions, as much of the data
will be unchanged from one insert to the next, therefore a certain
amount of redundancy is involved, resulting in an automatic
reinforcement of the data within the network.

Less frequently inserted data, on the other hand, basically only gets
one chance to take, and will benefit from the deeper insertion (God,
this sounds dirty, doesn't it?), distributing the data as far as
possible into the network initially, helping it to later disseminate to
other nodes more easily.

Of course, there are other factors to consider as well.  Some of
the more popular edition/one-shot sites may be accessed much more
frequently than some DBR sites, thereby helping the data to propagate
throughout the network, whereas some less popular DBR sites may actually
benefit from deeper insertion.

It's not a perfect science; there are really no hard-and-fast rules. 
Just common sense and good judgement, basically, combined with how long
you're willing to wait for your inserts to complete.  :-)

HTH

-- 
Conrad J. Sabatier [EMAIL PROTECTED] -- In Unix veritas
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Re: [freenet-support] Freenet and Solaris 10

[Conrad J. Sabatier]

On Sat, 19 Feb 2005 21:08:08 +, Matthew Toseland
[EMAIL PROTECTED] wrote:

 Try running it in bash?
 
 $ /bin/bash
 $ source start-freenet.sh
 ...

Really, we should fix this.  I ran into the same thing under FreeBSD.
The syntax used for some of the tests is a little weird and not quite
standard.

If you'd like, I'll take care of it.

Conrad

 On Thu, Feb 17, 2005 at 07:57:45PM -0500, Robert Webber wrote:
  Hello:
  
  I am trying to run freenet on Solaris 10 (3/05) for Sparc.
  
  I have downloaded the archive and validated that it is intact. When
  I run freenet for the first time, the installer builds the
  freenet.conf file, but the application fails with the following
  error:
  
  start-freenet.sh: test: unknown operator ==
  
  The start-freenet.sh script produced a few informational messages
  that might be important, might be not. Here is the output of the
  session:
  
  (BTW I used the default options)
  
  $ sh start-freenet.sh
  Detected freenet-ext.jar
  Detected freenet.jar
  It appears that this is your first time running Freenet. You
  should read the README file as it contains important instructions
  and advice.
  
  First we must generate a freenet.conf file. I will now run
  Freenet in configure mode, and it will ask you a number of
  questions. If you don't understand the question, hitting enter
  without typing anything will go with the default which is likely
  to be the right thing.
  
  no random in shell, enter a FNP port number + ENTER
  
  Freenet Configuration
  Running in simple mode. Some preferences will be skipped.
  You can choose the default preferences by just hitting ENTER
  
  Setting: listenPort
  The port to listen for incoming FNP (Freenet Node Protocol)
  connections on. INFO: Native CPUID library jcpuid not loaded,
  reason: 'Dont know jcpuid library name for os type 'SunOS'' - will
  not be able to read CPU information using CPUIDINFO: Native
  BigInteger library jbigi not loaded, reason: 'Dont know jbigi
  library name for os type 'SunOS'' - using pure java
  Config error: listenPort= - Value could not be parsed - format error
  perhaps? - expected Integer (whole number, up to 2,147,483,648,
  kKmMgG accepted - example 2.1m = 2,100,000) - detail:
  java.lang.NumberFormatException: empty String
  java.lang.NumberFormatException: empty String
  at
  sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecim
  al.java:994) at
  java.lang.Double.parseDouble(Double.java:482) at
  freenet.config.Params.parseInt(Params.java:413) at
  freenet.config.Params.getInt(Params.java:383) at
  freenet.config.Setup.setParam(Setup.java:463) at
  freenet.config.Setup.dumpConfig(Setup.java:210) at
  freenet.node.Main.main(Main.java:420)
  listenPort [64490]
  
  
  Setting: seedFile
  A file containing one or more node references which will be
  incorporated into the node's routing table on startup.  A reference
  is only added if there is no previously existing reference to that
  node.  When this node announces, it will announce to the nodes
  listed in this file. seedFile [seednodes.ref]
  
  
  Setting: storeSize
  The byte size of the data store directory.
  The maximum sized file that will be cached is 1/100th of
  this value.  We recommend the default 256MB, to cache the largest
  common file size on freenet, 1MB plus some headers, with plenty of
  elbowroom, but any size about 101MB should be adequate (a 1MB chunk
  is not exactly 1MB...). Note that if you increase settings such as
  maximumThreads, you may need to use a larger store.
  storeSize [268435456]
  
  
  Setting: inputBandwidthLimit
  If nonzero, specifies an independent limit for incoming data only,
  in bytes per second. A 512kbps broadband (DSL or cable) connection
  is 64kB/sec, but you may want to use other things than Freenet on
  it. However, Freenet's background usage should be close to the
  output limit most of the time. You may want to set this and then set
  doLowLevelInputLimiting=false, in order to have more accurate
  pending-transfers load. You SHOULD do this if your connection has
  more outbound than inbound bandwidth. inputBandwidthLimit [0]
  
  
  Setting: outputBandwidthLimit
  If nonzero, specifies an independent limit for outgoing data only,
  in bytes per second. Not entirely accurate. If you need exact
  limiting, do it at the OS level. A typical broadband connection has
  either a 128kbps or a 256kbps uplink, this equates to 16kB/sec and
  32kB/sec respectively. You will need to keep some bandwidth back for
  other apps and for downloads (yes, downloading uses a small amount
  of upload bandwidth). We suggest therefore limits of 12000 for a
  128kbps upload connection, or 24000 for a 256kbps upload connection.
  Most broadband connections have far more download bandwidth than
  upload bandwidth... just because you have 1Mbps download, does not
  mean you have 1Mbps upload; if you do not know what your