[freenet-dev] Fwd: Git Problem

[bbac...@googlemail.com]

I think I accidentally fixed the problem with the help found on some websites ^^
Hope this is ok now.


-- Forwarded message --
From:  
Date: Wed, Nov 11, 2009 at 21:41
Subject: Git Problem
To: Discussion of development issues 


Sorry folks, my first steps with Github. Checked out the source,
changed one file and somehow managed to commit it.
See here: 
http://github.com/freenet/plugin-Freetalk-staging/commit/d6998ad17063f49279f82d37a4ac61528c9b7fab

Unfortunately this is recognized as a full source replace. What
happened, what did I make wrong here?
And how to revert this on Github?

Thanks for help :)

Rgds, bback.

--
__
GnuPG key: ? (0x48DBFA8A)
Keyserver: ? pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__



-- 
__
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__

[freenet-dev] Git Problem

[bbac...@googlemail.com]

Sorry folks, my first steps with Github. Checked out the source,
changed one file and somehow managed to commit it.
See here: 
http://github.com/freenet/plugin-Freetalk-staging/commit/d6998ad17063f49279f82d37a4ac61528c9b7fab

Unfortunately this is recognized as a full source replace. What
happened, what did I make wrong here?
And how to revert this on Github?

Thanks for help :)

Rgds, bback.

-- 
__
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__

[freenet-dev] Website downloads page feedback

[Matthew Toseland]

On Tuesday 10 November 2009 23:12:03 Zero3 wrote:
> Feedback for the website downloads page:
> 
> "We strongly recommend you use the links on the start menu to shut down 
> Freenet when you play computer games, and start it back up afterwards. 
> We will implement a system tray icon for this in future."
> 
> This is implemented now.
> 
> "Freenet works best with Windows XP Professional. Freenet will run on 
> Vista and Windows 7 but the uninstaller is not perfect on those systems."
> 
> The wininstaller works smoothly on both XP and Vista now the beta has 
> been rolled out.
> 
> Windows 7 is *not* supported at this time. I've seen several Win7 bug 
> reports, so until I have time to look at Win7 support we should 
> discourage using Freenet on Win7.
> 
> "You can access Freenet later on via the Browse Freenet icon on the 
> desktop and your start menu. If the browser window isn't opened, "
> 
> On Windows, the main method of accessing Freenet is now via the tray 
> menu. Alternatively the start menu. We don't add a desktop shortcut by 
> default any more.
> 
> " for example because you used the headless installer"
> 
> Most people won't know what a "headless installer" is.
> 
> "Recommended: 1GHz or more processor with 512MB RAM or more (especially 
> if using Windows XP)"
> 
> As opposed to? Win2k? Vista? Win7?
> 
> "Windows users can upgrade to the latest-stable Freenet release by 
> clicking on "update.cmd" in the Freenet directory."
> 
> On Windows, this is now implemented in the tray manager.

So we probably need to split it up by OS? Or maybe not ...

We do need to mention that on 64-bit Windows we use a 32-bit JVM which may not 
be auto-updated, since this trips people up from time to time?
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/2009/3c197ae3/attachment.pgp>

[freenet-dev] Fwd: Git Problem

[Ian Clarke]

That pretty much describes how I resolved every problem I've ever had with git.

Ian.

On Wed, Nov 11, 2009 at 2:59 PM,   wrote:
> I think I accidentally fixed the problem with the help found on some websites 
> ^^
> Hope this is ok now.
>
>
> -- Forwarded message --
> From: ?
> Date: Wed, Nov 11, 2009 at 21:41
> Subject: Git Problem
> To: Discussion of development issues 
>
>
> Sorry folks, my first steps with Github. Checked out the source,
> changed one file and somehow managed to commit it.
> See here: 
> http://github.com/freenet/plugin-Freetalk-staging/commit/d6998ad17063f49279f82d37a4ac61528c9b7fab
>
> Unfortunately this is recognized as a full source replace. What
> happened, what did I make wrong here?
> And how to revert this on Github?
>
> Thanks for help :)
>
> Rgds, bback.
>
> --
> __
> GnuPG key: ? (0x48DBFA8A)
> Keyserver: ? pgpkeys.pca.dfn.de
> Fingerprint:
> 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
> __
>
>
>
> --
> __
> GnuPG key: ? (0x48DBFA8A)
> Keyserver: ? pgpkeys.pca.dfn.de
> Fingerprint:
> 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
> __
> ___
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>



-- 
Ian Clarke
CEO, Uprizer Labs
Email: ian at uprizer.com
Ph: +1 512 422 3588

[freenet-dev] Website downloads page feedback

[Zero3]

Feedback for the website downloads page:

"We strongly recommend you use the links on the start menu to shut down 
Freenet when you play computer games, and start it back up afterwards. 
We will implement a system tray icon for this in future."

This is implemented now.

"Freenet works best with Windows XP Professional. Freenet will run on 
Vista and Windows 7 but the uninstaller is not perfect on those systems."

The wininstaller works smoothly on both XP and Vista now the beta has 
been rolled out.

Windows 7 is *not* supported at this time. I've seen several Win7 bug 
reports, so until I have time to look at Win7 support we should 
discourage using Freenet on Win7.

"You can access Freenet later on via the Browse Freenet icon on the 
desktop and your start menu. If the browser window isn't opened, "

On Windows, the main method of accessing Freenet is now via the tray 
menu. Alternatively the start menu. We don't add a desktop shortcut by 
default any more.

" for example because you used the headless installer"

Most people won't know what a "headless installer" is.

"Recommended: 1GHz or more processor with 512MB RAM or more (especially 
if using Windows XP)"

As opposed to? Win2k? Vista? Win7?

"Windows users can upgrade to the latest-stable Freenet release by 
clicking on "update.cmd" in the Freenet directory."

On Windows, this is now implemented in the tray manager.

- Zero3

Re: [freenet-dev] Website downloads page feedback

[Matthew Toseland]

On Tuesday 10 November 2009 23:12:03 Zero3 wrote:
 Feedback for the website downloads page:
 
 We strongly recommend you use the links on the start menu to shut down 
 Freenet when you play computer games, and start it back up afterwards. 
 We will implement a system tray icon for this in future.
 
 This is implemented now.
 
 Freenet works best with Windows XP Professional. Freenet will run on 
 Vista and Windows 7 but the uninstaller is not perfect on those systems.
 
 The wininstaller works smoothly on both XP and Vista now the beta has 
 been rolled out.
 
 Windows 7 is *not* supported at this time. I've seen several Win7 bug 
 reports, so until I have time to look at Win7 support we should 
 discourage using Freenet on Win7.
 
 You can access Freenet later on via the Browse Freenet icon on the 
 desktop and your start menu. If the browser window isn't opened, 
 
 On Windows, the main method of accessing Freenet is now via the tray 
 menu. Alternatively the start menu. We don't add a desktop shortcut by 
 default any more.
 
  for example because you used the headless installer
 
 Most people won't know what a headless installer is.
 
 Recommended: 1GHz or more processor with 512MB RAM or more (especially 
 if using Windows XP)
 
 As opposed to? Win2k? Vista? Win7?
 
 Windows users can upgrade to the latest-stable Freenet release by 
 clicking on update.cmd in the Freenet directory.
 
 On Windows, this is now implemented in the tray manager.

So we probably need to split it up by OS? Or maybe not ...

We do need to mention that on 64-bit Windows we use a 32-bit JVM which may not 
be auto-updated, since this trips people up from time to time?


signature.asc
Description: This is a digitally signed message part.
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Git Problem

[bbackde]

Sorry folks, my first steps with Github. Checked out the source,
changed one file and somehow managed to commit it.
See here: 
http://github.com/freenet/plugin-Freetalk-staging/commit/d6998ad17063f49279f82d37a4ac61528c9b7fab

Unfortunately this is recognized as a full source replace. What
happened, what did I make wrong here?
And how to revert this on Github?

Thanks for help :)

Rgds, bback.

-- 
__
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Fwd: Git Problem

[bbackde]

I think I accidentally fixed the problem with the help found on some websites ^^
Hope this is ok now.


-- Forwarded message --
From:  bbac...@googlemail.com
Date: Wed, Nov 11, 2009 at 21:41
Subject: Git Problem
To: Discussion of development issues devl@freenetproject.org


Sorry folks, my first steps with Github. Checked out the source,
changed one file and somehow managed to commit it.
See here: 
http://github.com/freenet/plugin-Freetalk-staging/commit/d6998ad17063f49279f82d37a4ac61528c9b7fab

Unfortunately this is recognized as a full source replace. What
happened, what did I make wrong here?
And how to revert this on Github?

Thanks for help :)

Rgds, bback.

--
__
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__



-- 
__
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Fwd: Git Problem

[Ian Clarke]

That pretty much describes how I resolved every problem I've ever had with git.

Ian.

On Wed, Nov 11, 2009 at 2:59 PM,  bbac...@googlemail.com wrote:
 I think I accidentally fixed the problem with the help found on some websites 
 ^^
 Hope this is ok now.


 -- Forwarded message --
 From:  bbac...@googlemail.com
 Date: Wed, Nov 11, 2009 at 21:41
 Subject: Git Problem
 To: Discussion of development issues devl@freenetproject.org


 Sorry folks, my first steps with Github. Checked out the source,
 changed one file and somehow managed to commit it.
 See here: 
 http://github.com/freenet/plugin-Freetalk-staging/commit/d6998ad17063f49279f82d37a4ac61528c9b7fab

 Unfortunately this is recognized as a full source replace. What
 happened, what did I make wrong here?
 And how to revert this on Github?

 Thanks for help :)

 Rgds, bback.

 --
 __
 GnuPG key:   (0x48DBFA8A)
 Keyserver:   pgpkeys.pca.dfn.de
 Fingerprint:
 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
 __



 --
 __
 GnuPG key:   (0x48DBFA8A)
 Keyserver:   pgpkeys.pca.dfn.de
 Fingerprint:
 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
 __
 ___
 Devl mailing list
 Devl@freenetproject.org
 http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl




-- 
Ian Clarke
CEO, Uprizer Labs
Email: i...@uprizer.com
Ph: +1 512 422 3588
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Website downloads page feedback

[Matthew Toseland]

On Tuesday 10 November 2009 23:12:03 Zero3 wrote:
 Feedback for the website downloads page:
 
 We strongly recommend you use the links on the start menu to shut down 
 Freenet when you play computer games, and start it back up afterwards. 
 We will implement a system tray icon for this in future.
 
 This is implemented now.
 
 Freenet works best with Windows XP Professional. Freenet will run on 
 Vista and Windows 7 but the uninstaller is not perfect on those systems.
 
 The wininstaller works smoothly on both XP and Vista now the beta has 
 been rolled out.
 
 Windows 7 is *not* supported at this time. I've seen several Win7 bug 
 reports, so until I have time to look at Win7 support we should 
 discourage using Freenet on Win7.
 
 You can access Freenet later on via the Browse Freenet icon on the 
 desktop and your start menu. If the browser window isn't opened, 
 
 On Windows, the main method of accessing Freenet is now via the tray 
 menu. Alternatively the start menu. We don't add a desktop shortcut by 
 default any more.
 
  for example because you used the headless installer
 
 Most people won't know what a headless installer is.
 
 Recommended: 1GHz or more processor with 512MB RAM or more (especially 
 if using Windows XP)
 
 As opposed to? Win2k? Vista? Win7?
 
 Windows users can upgrade to the latest-stable Freenet release by 
 clicking on update.cmd in the Freenet directory.
 
 On Windows, this is now implemented in the tray manager.

Updated with all the above suggestions, rewritten quite a bit. It's a bit 
longer now, but most people just click the button on the homepage; it should be 
clearer.


signature.asc
Description: This is a digitally signed message part.
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Some feedback from a hostile environment

[Matthew Toseland]

On Tuesday 10 November 2009 17:18:01 Zero3 wrote:
 Matthew Toseland wrote:
  https://bugs.freenetproject.org/view.php?id=3697
  Zero3, any chance of writing the total system memory to a file in the 
  wininstaller in the near future?
 
 No problem.
 
 1) I assume we are talking about physical memory here?

Yes.
 
 2) Do we look at total memory available or memory currently free?

Probably total memory, you could write both though.
 
 3) Exactly what should it write, and where?

Create a file, write the total available memory, in bytes, or with the SI 
multipliers we use for units (e.g. 1024M).

But you should probably also rewrite the wrapper.conf's wrapper.java.maxmemory= 
for a sane default based on the available memory. I have given an algorithm or 
list on the relevant bug: Don't automatically set it below 128M, but scale it 
up to 512 if we have a lot of RAM...
 
 4) Shall I implement this in the installer (only set once) or the 
 launcher? (set every time user launches Freenet via our shortcuts)

Good question, it's essential in the installer, it's useful in the launcher.
 
 5) Would it be a good idea to deny installation if the user doesn't meet 
 the minimum requirements?

Another good question. If trying to install on 128MB on XP, maybe we should 
fail it? OTOH it could conceivably work if they use a really lightweight 
browser? IMHO we can set the wrapper memory limit down to 96MB if we need to, 
but we will need to warn the user in this case - hence the node needs to see 
the limit for purposes of the first-time wizard as well as the wrapper.conf.


signature.asc
Description: This is a digitally signed message part.
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Website downloads page feedback

[Zero3]

Matthew Toseland wrote:
 On Tuesday 10 November 2009 23:12:03 Zero3 wrote:
 Feedback for the website downloads page:

 We strongly recommend you use the links on the start menu to shut down 
 Freenet when you play computer games, and start it back up afterwards. 
 We will implement a system tray icon for this in future.

 This is implemented now.

 Freenet works best with Windows XP Professional. Freenet will run on 
 Vista and Windows 7 but the uninstaller is not perfect on those systems.

 The wininstaller works smoothly on both XP and Vista now the beta has 
 been rolled out.

 Windows 7 is *not* supported at this time. I've seen several Win7 bug 
 reports, so until I have time to look at Win7 support we should 
 discourage using Freenet on Win7.

 You can access Freenet later on via the Browse Freenet icon on the 
 desktop and your start menu. If the browser window isn't opened, 

 On Windows, the main method of accessing Freenet is now via the tray 
 menu. Alternatively the start menu. We don't add a desktop shortcut by 
 default any more.

  for example because you used the headless installer

 Most people won't know what a headless installer is.

 Recommended: 1GHz or more processor with 512MB RAM or more (especially 
 if using Windows XP)

 As opposed to? Win2k? Vista? Win7?

 Windows users can upgrade to the latest-stable Freenet release by 
 clicking on update.cmd in the Freenet directory.

 On Windows, this is now implemented in the tray manager.
 
 So we probably need to split it up by OS? Or maybe not ...
 
 We do need to mention that on 64-bit Windows we use a 32-bit JVM which may 
 not be auto-updated, since this trips people up from time to time?

Until Linux and Mac has tray support, I guess we should split it up.

Yea, if that is the case (i can't figure out what is up and down with 
this 32-bit vs. 64-bit stuff), we should mention that people with 64-bit 
Windows without Java will be offered to install a 32-bit Java.

- Zero3
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Some feedback from a hostile environment

[Matthew Toseland]

On Tuesday 10 November 2009 19:18:12 Robert Hailey wrote:
 
 On Nov 9, 2009, at 7:35 AM, Matthew Toseland wrote:
 
  Some Chinese feedback: Main point is there are a lot of old PCs with  
  very limited RAM, although new ones have plenty of RAM. Broadband is  
  however reasonable in general, making it a better candidate than  
  Iran. Suggested making startup on startup configurable,  
  substantially reducing memory footprint etc. My worry with the  
  former is that opennet won't last forever, and low-uptime darknet is  
  very problematic.
 
  IMHO we could reasonably cut our default memory limit to 128M. The  
  main issues are:
  - Sorting out Library memory issues (bug #3685)
  - Sorting out Freetalk memory issues (I haven't seen OOMs from  
  Freetalk recently, maybe this really is fixed?)
  - Sorting out - or ignoring - the startup memory spike on big  
  inserts (4G needs 192MB).
 
  On fast systems, a higher memory limit means less CPU spent in  
  garbage collection, so maybe there is an argument for reinstating  
  the panel in the wizard that asks the user how much memory to  
  allocate...
 
  Our friend has also localised the wininstaller (this is subject to  
  technical issues Zero3 hopefully will be able to resolve), and jSite  
  (I will deal with this soon).
 
 Since I have freenet installed on an old machine, my observations...  
 It made the computer all but unusable! On a hunch, I cut it's  
 datastore size to a minimum and found that the impact was not  
 noticeable.
 
 I'm not sure exactly what was going on, slow hard drive, vm/page  
 thrashing, ??? but maybe there are simpler variables (like store size)  
 which will both improve performance and reduce memory footprint.

So if the system memory is low we should limit the datastore size? That is 
logical...
 
 It might be beneficial to run tests on memory consumption for various  
 setups (number of peers, concurrent requests, datastore size).

What was the size before and after? And the memory limit etc? AFAIK we use 
approx 1MB of RAM for every 2GB of store...
 
 And on a side note, it might also be helpful to know how long a  
 request has to wait in line to clear the datastore/bloom filter check,  
 or place benchmarks in to make stats of all requests. Then we might be  
 able to tell the user your node can't keep up with your requested   
 {datastore size, number of peers}

Good idea to have that stat, and maybe a useralert based on it, although I'm 
skeptical that we can reliably diagnose the cause - maybe we can with knowing 
the current system memory total?


signature.asc
Description: This is a digitally signed message part.
___
Devl mailing list
Devl@freenetproject.org
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl