Re: Moving Freenet to another partition

On May 27, 2011, at 2:46 PM, Dsoslglece wrote:
> Le 27/05/11 21:32, Daxter a écrit :
>> 
>> On May 27, 2011, at 2:28 PM, Dsoslglece wrote:
>>> Le 27/05/11 20:38, Daxter a écrit :
>>>> 
>>>> Hello all,
>>>> 
>>>> I want to move my Freenet folder to a larger partition in my computer which is running Mac OSX 10.6. I copied it over and moved the original folder in /Applications/ to the trash (not yet deleting it), and then attempted to run it from its new location. While starting up, however, it warned me that no seednodes.fref file existed and as such it could not connect to the opennet. A quick glance into /Applications/ and I found that Freenet had recreated a folder there and was repopulating it with a number of files, all of which probably were not properly loaded from the new location.
>>>> 
>>>> I have two theories as to what might be the cause:
>>>> 1) After I chose the install directory during the original installation, the install script changed a preference file telling Freenet to always look for such files in /Applications/Freenet/ (the original install location) instead of the current directory.
>>>> 2) regardless of where you choose to install Freenet, something has been hard-coded to look in /Applications/Freenet (for my OS at least).
>>>> 
>>>> Does anybody know why this is happening? I want to devote a larger portion of my HDD to Freenet, but this issue is preventing me from doing so.
>>> Normally, Freenet works anywhere  (at least on Mac snow leopard).
>>> For instance, I've got it on my hard disk, but localized in a encrypted sparse image bundle. 
>>> in fact, it is possible to take the whole folder containing it (after it has been shutted), putting it somewhere else, and start it again, and evrerything goes fine again.
>>> 
>>> The only thing then that has to be changed, is the path to it (for the commands), and also not to forget to indicate its new position to LittleSnitch…
>> 
>> You say that, and yet my experience proves otherwise. I originally installed it in my Applications folder and then tried relocating it to another partition. When starting via run.sh in the new directory, I had the issues mentioned in my first email.
> Well I can only speak from what I have personnally experienced. But, are you sure that you had the new path correctly indicated in terminal? 
> One of the surest method I know for this is to first enter : cd space, and then, slide the Freenet folder on top of terminal, then enter.
> By the way, normally, you don't even need to get the old folder out of reach in the garbage, you can have few FN Folders, as long as only one is started, no problem
> You could also have put the original folder in the new location and started it then… 
> 
> Maybe you could open both folders side by side and compare the content ans especially those files mentionned as missing…


After further testing, I am absolutely sure that something is wrong here. To make sure that my findings were true, I renamed my original Freenet folder in /Applications/ to Freenet22, and then attempted run.sh from the new location. Every time it recreated a folder with the following files in it. After checking that the folder had been recreated, I stopped Freenet and deleted the folder. I moved my new copy (on the larger partition) to a different directory, and the results were still the same. I even tried renaming the folder and it still happened. 

bookmarks.dat			downloads/				node.db4o.crypt			persistent-temp-43346/
bootID					extra-peer-data-43346/	opennet-10718			plugins/
client-throttle.dat			master.keys				openpeers-10718		temp-43346/
completed.list.downloads	node-43346				openpeers-old-10718		uptime.dat
completed.list.uploads	node-throttle.dat			peers-43346

_______________________________________________
Support mailing list
[email protected]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-request-RdDMkVZAZeuJnvDnx1genB2eb7JE58TQ@public.gmane.org?subject=unsubscribe