I finally managed to get a cross compiler that works with the pogoplug, I first tried various custom build of the GNU C++ cross compiler on the Mac but none of them succeeded in creating binaries that were compatible with my little pink pogoplug.
Anyway, instead of boring you with various evening’s development woos… I will just tell you what I ended up doing which was to use VirtuaBox with ubuntu x86 and use this tar file (eg: bunzip2 it, tar xvf into $HOME)
Then to compile it I first had to setup the makefile for rsync:
# export PATH=$HOME/pogoplug-gcc/bin:$PATH
# CC=arm-none-linux-gnueabi-gcc ./configure --build=arm-linux\
--host=arm-none-linux-gnueabi --target=arm-linux
Then to build is was easy… I just did…
# CC=arm-none-linux-gnueabi-gcc make
Next, I found a small USB thumb drive, formatted in ext3 using ubuntu, placed it into the pogoplug, logged into it, remount’ed the drives using:
# mount -o remount exec /tmp/.cemnt/mnt_sdb1
You may need to change the mnt point, use mount to find it..
Now you will be able to use rsync via ssh and use –rsync-path to point to rsync on your ext3 drive.
I required, I make the rsync exe + md5 sum available… just shout!
I am now officially tickle pink with excitement…
Here is what my Apple Software update said:
Digital Raw Compatibility Update:
This update extends RAW image compatibility for Aperture 3 and iPhoto ’09 for the following cameras:
Hasselblad H3DII-50
Leica M9
Leica X1
Olympus E-P1
Olympus E-P2
Panasonic Lumix DMC-GF1
Pentax K-7
Pentax K-x
Sony Alpha DSLR-A500
Sony Alpha DSLR-A550
Sony Alpha DSLR-A850
Thank you Apple!
Okay.. I got my pogoplug last week and I have been playing around with it and it is now time to change the root password… so guess what happened…
bash-3.2# passwd
Changing password for root
New password:
Retype password:
passwd: cannot update password file /etc/shadow
bash-3.2#
The good news, the file system is read-only, so it was pretty simple to work around, just use mount…
bash-3.2# mount -o rw,remount /
-bash-3.2# passwd
Changing password for root
New password:
Retype password:
Password for root changed by root
-bash-3.2# mount -o ro,remount /
Well Done Amy! – The picture is from Boston.com see link below:

Amy Williams of Great Britain and Northern Ireland eyes the track ahead in the women’s skeleton run 2 on day 7 of the 2010 Vancouver Winter Olympics on February 18, 2010. (Clive Mason/Getty Images)
re: http://www.boston.com/bigpicture/2010/02/vancouver_2010_part_1_of_2.html
For the last couple of months I have working on Visual Studio 2010 and this include Microsoft CLR v4 and I was recently asked how to write a test that determines at runtime which CLR is being used and what assemblies it uses. I replies would use reflection. So I dropped my friend a mega simple demo… and here it is.
$set ilusing"System.Reflection"
01 myAssembly type "Assembly".
01 usedAssemblyName type "AssemblyName".
set myAssembly to type "Assembly"::"GetExecutingAssembly"
display "My exe is " myAssembly::"FullName"
display "and is using CLR " myAssembly::"ImageRuntimeVersion"
display "and is loaded from " myAssembly::"Location"
display "the initial method of this program was "
myAssembly::"EntryPoint"::"Name"
display "This assembly references -> "
perform varying usedAssemblyName
through myAssembly::"GetReferencedAssemblies"
display "-> " usedAssemblyName
end-perform
And the output of the program is:
My exe is clrver, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
and is using CLR v2.0.50727
and is loaded from d:\clrver.exe
the initial method of this program was _MF_ENTRYThis assembly references ->
-> mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
-> MicroFocus.COBOL.Runtime, Version=3.6.0.0, Culture=neutral,
PublicKeyToken=0412c5e0b2aaa8f0