Unison - Revision history

Pedro: /* Unpack and build the OCAML compiler */

Pedro — Thu, 24 Jul 2008 13:38:02 GMT

Unpack and build the OCAML compiler

← Older revision		Revision as of 13:38, 24 July 2008
Line 45:		Line 45:
	You may get an error while compiling the ocamtools, specifically: Unbound Value “name_of_insrtuctions” : Error 2		You may get an error while compiling the ocamtools, specifically: Unbound Value “name_of_insrtuctions” : Error 2

-	This has to do with an error in the make file in the tools directory to generate the opnames.ml file. A sed command ~~in the TeraStation~~ is giving an error so the file is not generated appropriately and it stays empty.	+	This has to do with an error in the make file in the tools directory to generate the opnames.ml file. A sed command is giving an error during make so the file is not generated appropriately and it stays empty. For simplicity you can [http://pastie.org/239949 download] the correct version of the opnames.ml, and place it in you ocaml-3.09.3/tools directory, then rerun “gmake world”.
-		+
-	For simplicity you can [http://pastie.org/239949 download] the correct version of the opnames.ml, and place it in you ocaml-3.09.3/tools directory, then rerun “gmake world”.	+

	I could not compile OCAML 3.10.2 on the TeraStation Live, so I used the OCAML 3.09.3 and it all worked fine, after the opnames.ml fix.		I could not compile OCAML 3.10.2 on the TeraStation Live, so I used the OCAML 3.09.3 and it all worked fine, after the opnames.ml fix.

Pedro: /* Requirements */

Pedro — Thu, 24 Jul 2008 13:36:47 GMT

Requirements

← Older revision		Revision as of 13:36, 24 July 2008
Line 20:		Line 20:
	* OCAML compiler source (I used 3.10.1)		* OCAML compiler source (I used 3.10.1)
	* Unison binaries (I used 2.27.57)		* Unison binaries (I used 2.27.57)
		+
		+	This procedure works on the TeraStation Live with stock firmware, you'll just need to install the compilation tools

	====Install Openlink====		====Install Openlink====

Pedro: /* Unpack and build the OCAML compiler */

Pedro — Thu, 24 Jul 2008 13:34:44 GMT

Unpack and build the OCAML compiler

← Older revision		Revision as of 13:34, 24 July 2008
Line 40:		Line 40:
	* Type "make clean" - this cleans up all the rubbish made during install		* Type "make clean" - this cleans up all the rubbish made during install
	* Should all be installed now! Type "ocaml -version" to check everything has built. "The Objective Caml toplevel, version 3.10.1" should appear.		* Should all be installed now! Type "ocaml -version" to check everything has built. "The Objective Caml toplevel, version 3.10.1" should appear.
		+
		+	You may get an error while compiling the ocamtools, specifically: Unbound Value “name_of_insrtuctions” : Error 2
		+
		+	This has to do with an error in the make file in the tools directory to generate the opnames.ml file. A sed command in the TeraStation is giving an error so the file is not generated appropriately and it stays empty.
		+
		+	For simplicity you can [http://pastie.org/239949 download] the correct version of the opnames.ml, and place it in you ocaml-3.09.3/tools directory, then rerun “gmake world”.
		+
		+	I could not compile OCAML 3.10.2 on the TeraStation Live, so I used the OCAML 3.09.3 and it all worked fine, after the opnames.ml fix.

	====Make the Unison tool====		====Make the Unison tool====

Pedro: /* Install development tools */

Pedro — Thu, 24 Jul 2008 13:28:00 GMT

Install development tools

← Older revision		Revision as of 13:28, 24 July 2008
Line 27:		Line 27:
	Again, this is documented elsewhere. It provides the critical binaries such as gcc and make for the linkstation.		Again, this is documented elsewhere. It provides the critical binaries such as gcc and make for the linkstation.

		+	On a TeraStation you can follow these [http://www.sodan.ecc.u-tokyo.ac.jp/~okayama/memo/pkgsrc-arm/ instructions]. One small detail if you use these you need to type gmake instead of make in the compilation procedures described next.

	====Unpack and build the OCAML compiler====		====Unpack and build the OCAML compiler====

Pedro: /* Make the Unison tool */

Pedro — Thu, 24 Jul 2008 13:24:00 GMT

Make the Unison tool

← Older revision		Revision as of 13:24, 24 July 2008
Line 49:		Line 49:
	* To test the build now type "unison - version." It should respond with "unison version 2.27.57"		* To test the build now type "unison - version." It should respond with "unison version 2.27.57"
	* Great! The real hard work is over.		* Great! The real hard work is over.
		+
		+	These instructions work for the TeraStation Live as well. Here's a link the pre-built binary of [http://www.filedropper.com/unison-22757tar unison 2.27.57] compiled on a TS Live.

	===FreeLink===		===FreeLink===

Goat: added explanations of the sync task

Goat — Mon, 17 Mar 2008 20:39:14 GMT

added explanations of the sync task

← Older revision		Revision as of 20:39, 17 March 2008
Line 1:		Line 1:
	{{Articles\|LS2\|LS1\|HG\|LSPro\|Kurobox\|KuroboxPro\|OpenLink\|FreeLink}}		{{Articles\|LS2\|LS1\|HG\|LSPro\|Kurobox\|KuroboxPro\|OpenLink\|FreeLink}}
	==Introduction==		==Introduction==
-	This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware or using apt-get with FreeLink firmware	+	This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware or using apt-get with FreeLink firmware. Note that this also is fully functional with Freelink on the Arm devices through apt-get.

	From the Unison website: Unison is a file-synchronization tool for Unix and Windows (and now the Linkstation ;-). It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other.		From the Unison website: Unison is a file-synchronization tool for Unix and Windows (and now the Linkstation ;-). It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other.
Line 58:		Line 58:
	* You should now install the Unison tool to your PC if you haven't done so already. Windows, Mac and various Linux binaries are available - just make sure you use the same version as on the linkstation or it won't work.		* You should now install the Unison tool to your PC if you haven't done so already. Windows, Mac and various Linux binaries are available - just make sure you use the same version as on the linkstation or it won't work.
	* From your PC, you're now going to test the communication with the linkstation. Make a directory a.tmp and populate it with a couple of small files. Create a new empty directory on the linkstation. We'll use unison to copy the new files to it!		* From your PC, you're now going to test the communication with the linkstation. Make a directory a.tmp and populate it with a couple of small files. Create a new empty directory on the linkstation. We'll use unison to copy the new files to it!
-	* Open up a terminal window and type "unison -testserver /mnt/local/~~tmp.~~a ssh://root@192.168.1.8//mnt/hda/share/~~tmp.~~a". The "-testserver" option means nothing is copied, it's just ~~a test~~. "/mnt/local/~~tmp.~~a" is the absolute path to my new local directory. "ssh://root@192.168.1.8//mnt/hda/share/tmp.a" describes the directory on the linkstation. Replace with your linkstation name/IP as appropriate.	+	* Open up a terminal window and type "unison -testserver /mnt/local/a.tmp ssh://root@192.168.1.8//mnt/hda/share/a.tmp". The "-testserver" option means nothing is copied, it's just testing the ability to connect to the server. "/mnt/local/a.tmp" is the absolute path to my new local directory. "ssh://root@192.168.1.8//mnt/hda/share/tmp.a" describes the directory on the linkstation. Replace with your linkstation name/IP as appropriate.
-	* If this is successful it should respond with ~~...~~ Try this command again but remove the -testserver switch. The files should be synced to the linkstation.	+	* If this is successful it should respond with [no output] Try this command again but remove the -testserver switch. The files should be synced to the linkstation.
		+	* The utility is verbose, and explains if its identified a new backup destination.
		+	Looking for changes
		+	Warning: No archive files were found for these roots. This can happen either
		+	because this is the first time you have synchronized these roots,
		+	or because you have upgraded Unison to a new version with a different
		+	archive format.
		+
		+	Update detection may take a while on this run if the replicas are
		+	large.
		+
		+	Unison will assume that the 'last synchronized state' of both replicas
		+	was completely empty. This means that any files that are different
		+	will be reported as conflicts, and any files that exist only on one
		+	replica will be judged as new and propagated to the other replica.
		+	If the two replicas are identical, then no changes will be reported.
		+	Press return to continue.[<spc>]
		+
		+	It will then display the files to be copied and show the direction of the sync.
		+
		+	Reconciling changes
		+
		+	local LSPro
		+	dir ----> / [f]
		+
		+	* f stands for follow Unisons recommendation. these are the options available by pressing ?
		+	Commands:
		+	<ret> or f or <spc> follow unison's recommendation (if any)
		+	I ignore this path permanently
		+	E permanently ignore files with this extension
		+	N permanently ignore paths ending with this name
		+	m merge the versions
		+	d show differences
		+	x show details
		+	l list all suggested changes
		+	p or b go back to previous item
		+	g proceed immediately to propagating changes
		+	q exit unison without propagating any changes
		+	/ skip
		+	> or . propagate from from local to LSPro
		+	< or , propagate from from LSPro to local
		+
		+	* Once you have agreed or modified any of the actions, it runs the sync.
		+	Proceed with propagating updates? [] y
		+	Propagating updates
		+
		+	The graphical versions are also useful, and offer the ability to do Profiles, but be sure to use the same versions on each of the machines running Unison.

	==Next Steps==		==Next Steps==

Ramuk at 20:58, 23 February 2008

Ramuk — Sat, 23 Feb 2008 20:58:40 GMT

← Older revision		Revision as of 20:58, 23 February 2008
Line 1:		Line 1:
-	{{Articles\|LS2\|LS1\|HG\|LSPro\|Kurobox\|~~KuroBoxpro~~\|OpenLink\|FreeLink}}	+	{{Articles\|LS2\|LS1\|HG\|LSPro\|Kurobox\|KuroboxPro\|OpenLink\|FreeLink}}
	==Introduction==		==Introduction==
	This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware or using apt-get with FreeLink firmware		This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware or using apt-get with FreeLink firmware

Ramuk: added instructions for using freelink

Ramuk — Sat, 23 Feb 2008 20:57:14 GMT

added instructions for using freelink

← Older revision		Revision as of 20:57, 23 February 2008
Line 1:		Line 1:
-	{{Articles\|LS2\|OpenLink}}	+	{{Articles\|LS2\|LS1\|HG\|LSPro\|Kurobox\|KuroBoxpro\|OpenLink\|FreeLink}}
	==Introduction==		==Introduction==
-	This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware~~. I haven't tested on any other configuration but there should be no reason for it not to work in principle.~~	+	This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware or using apt-get with FreeLink firmware

	From the Unison website: Unison is a file-synchronization tool for Unix and Windows (and now the Linkstation ;-). It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other.		From the Unison website: Unison is a file-synchronization tool for Unix and Windows (and now the Linkstation ;-). It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other.
Line 11:		Line 11:
	There are a number of ways to use Unison but the way described here (and recommended on unison website) is to run the unison application as a server on the linkstation. Data is then transferred using the client application over SSH.		There are a number of ways to use Unison but the way described here (and recommended on unison website) is to run the unison application as a server on the linkstation. Data is then transferred using the client application over SSH.

		+	==Installation Instructions==
		+	===OpenLink===
		+	====Requirements====
	You will need:		You will need:
-	* Linkstation LS2(MIPS)	+	* Linkstation LS2(MIPS)
	* MIPSel development tools		* MIPSel development tools
	* Openlink 0.52 firmware		* Openlink 0.52 firmware
Line 18:		Line 21:
	* Unison binaries (I used 2.27.57)		* Unison binaries (I used 2.27.57)

-	=~~=Installation Instructions==~~	+	====Install Openlink====
-	===Install Openlink===	+
	This is the first step as documented elsewhere on this site. You need to enable dropbear access for SSH.		This is the first step as documented elsewhere on this site. You need to enable dropbear access for SSH.

-	===Install development tools===	+	====Install development tools====
	Again, this is documented elsewhere. It provides the critical binaries such as gcc and make for the linkstation.		Again, this is documented elsewhere. It provides the critical binaries such as gcc and make for the linkstation.


-	===Unpack and build the OCAML compiler===	+	====Unpack and build the OCAML compiler====
	Unison is written in OCAML. To build unison you must first compile the OCAML toolchain. Latest source code is available as a tar from here: http://caml.inria.fr/		Unison is written in OCAML. To build unison you must first compile the OCAML toolchain. Latest source code is available as a tar from here: http://caml.inria.fr/

Line 38:		Line 40:
	* Should all be installed now! Type "ocaml -version" to check everything has built. "The Objective Caml toplevel, version 3.10.1" should appear.		* Should all be installed now! Type "ocaml -version" to check everything has built. "The Objective Caml toplevel, version 3.10.1" should appear.

-	===Make the Unison tool===	+	====Make the Unison tool====
	* Grab the Unison source code from http://www.cis.upenn.edu/~bcpierce/unison		* Grab the Unison source code from http://www.cis.upenn.edu/~bcpierce/unison
	* It's important to use the same version on client and server. I run ubuntu which has Unison 2.13.16 available in the package manager. However I couldn't get this version running on linkstation. I eventually installed version 2.27.57 on the linkstation and my ubuntu PC.		* It's important to use the same version on client and server. I run ubuntu which has Unison 2.13.16 available in the package manager. However I couldn't get this version running on linkstation. I eventually installed version 2.27.57 on the linkstation and my ubuntu PC.
Line 48:		Line 50:
	* Great! The real hard work is over.		* Great! The real hard work is over.

-	===Testing Unison===	+	===FreeLink===
		+	Use apt-get to install unison
		+	apt-get install unison
		+
		+
		+	==Testing Unison==
	* You should now install the Unison tool to your PC if you haven't done so already. Windows, Mac and various Linux binaries are available - just make sure you use the same version as on the linkstation or it won't work.		* You should now install the Unison tool to your PC if you haven't done so already. Windows, Mac and various Linux binaries are available - just make sure you use the same version as on the linkstation or it won't work.
	* From your PC, you're now going to test the communication with the linkstation. Make a directory a.tmp and populate it with a couple of small files. Create a new empty directory on the linkstation. We'll use unison to copy the new files to it!		* From your PC, you're now going to test the communication with the linkstation. Make a directory a.tmp and populate it with a couple of small files. Create a new empty directory on the linkstation. We'll use unison to copy the new files to it!

Ramuk at 20:45, 23 February 2008

Ramuk — Sat, 23 Feb 2008 20:45:28 GMT

← Older revision		Revision as of 20:45, 23 February 2008
Line 1:		Line 1:
-	{{Articles\|LS2}}	+	{{Articles\|LS2\|OpenLink}}
	==Introduction==		==Introduction==
	This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware. I haven't tested on any other configuration but there should be no reason for it not to work in principle.		This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware. I haven't tested on any other configuration but there should be no reason for it not to work in principle.

Ramuk at 20:44, 23 February 2008

Ramuk — Sat, 23 Feb 2008 20:44:43 GMT

← Older revision		Revision as of 20:44, 23 February 2008
Line 1:		Line 1:
		+	{{Articles\|LS2}}
	==Introduction==		==Introduction==
	This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware. I haven't tested on any other configuration but there should be no reason for it not to work in principle.		This document describes how to install and run the Unison file synchronisation software on Linkstation LS2(MIPS) with OpenLink firmware. I haven't tested on any other configuration but there should be no reason for it not to work in principle.