@adamm
Please note:
The dev2 repo for PlugApps depends on a newer kernel than CE provides in the base image. I would suggest *against* using that repo for the time being. Once we have built an up-to-date kernel for the Pro, that repo should be available.

@Oddballhero
SATA works, SATA II capable at that. It will not accept a port multiplier, and it is not hotswap capable (at this time, we know that the kernel doesn't like the idea, and the system will freeze.) I've yet to document the mod I made to my case to house an eSATA port, but that speed difference is *definitive* in every respect.

As for the kernel, we have built custom kernels from source that *do* support CE services. We'll just have to figure out the best way to handle that.

Ok, some issues with the Pro and it's indexing. Always check your drive indicator light for activity. Unlike the V2 or dockstar, the indexing routines seem to be more aggressive and you can't do much while it is going on. Do an "fdisk -l" to see if the drive is even showing up. Also, you may want to perform e2fsck on the drive since interupting the indexing in any sort of way will corrupt it (this gave me fits for a while since I could have sworn that I umounted it before shutting down / or ejected the drive). I became quite paranoid for a while always watching the drive activity light. I have a bunch of files that may be of help at http://tech.groups.yahoo.com/group/nslu2-general/files/Plug%20Files/ . The mount can be at the end of rcS or a script containing it. On my guide is a shell of a script for shutting down with an inittab entry which would be advisable. Definitely sync and umount the disks before shutting down, rebooting or removing any drives. I actually installed the e2fsprogs and moved e2fsck onto the nand just to be able to check my drives (or used my desktop). Use "mount" to see if the drive is already automounted such as "/tmp/.cemnt/mnt_sda1", you might not be able to mount it on /opt except with "mount -o bind /temp/.cemnt/mnt_sda1 /opt". Anyway, good luck, have patience. Everything stabilized after about a week (although earlier in the week, I wanted to throw it against the wall or beat it with a golf club). Might have been when it finally upgraded to 2.5.9. Everytime I add a drive, there is a minor hiccup as it indexes and then it settles down.
Good Luck!

Addendum:
Sometimes the Pro needs a delay after booting before mounting the drive. Put a sleep 5 up to sleep 10 before you mount your drives.

@adamm

I too having same problem not able to mount through rcS. Did added '/bin/mount /dev/sda /opt' at end and as you said can mount after logging.

Did you find the solution. ?

@adamm

Yes adding sleep does the magic. I am not sure but my usb flash drive comes as sda and hard drive as sdb1, saw this through mount cmd. I don't have much knowledge but found that /dev/sda did worked after adding sleep for me.

I have two more question, I did installed transmission but I won't be able to put that in startup script since my 2 TB HD takes around 1-2 minute to be mounted. Else I guess only way is say sleep 120. ?

My biggest bummer is dropbear because it's not allowing me to do port forwarding even after -a option. I even installed open ssh and put 'AllowTcpForwarding yes' in sshd_config but still getting error msg in log 'server denied forwarded connection'.

The delay in your HD may be due to routines that check the indices to see if they need to be updated, you may have a lot of files on your HD. Also, as above, if your index files are corrupt, it may cause the routines to hang.
Things to watch out for on your home setup, you may have dyndns implemented to handle dynamic routing external to your modem, but internally, if you are using dhcp to let the pogoplug acquire an address, that may continually change when you reboot it. So the port-forwarding you set on you router/modem may not work. You need to set in your router that the pogoplug's mac address always gets the same static internal IP (192.168.xxx.xxx). Also if you are using a separate router from you modem, you may need to check your settings so you don't end up with a double NAT situation. Check that your modem is bridged. Or setup up dual port forwarding (but then you have to watch out what ip address gets allocated on the router and setup a static ip). Needless to say, if you only have an integrated router/modem, you only have one port forward to worry about and allocate a static address to the pogoplug. You don't have to disable your firewall. Also some router/modems don't allow loopback. So you can access your pogoplug external to your network with your dyndns domain name but not internally in you network. For that you have to use the internal IP.

Finally ...

What I found was that pogoplug was not able to map host name to IP address. The problem was that dns lookup using ssh tunnel doesn't work in pogoplug. So I disabled that option and now do dns lookup differently.

To answer 2 posts at the same time:
Dhival:
Did you solve your DNS problem? Whichever router you are using for DHCP even if it is static does not seem to provide DNS info and you need to edit setup dnsmasq or some dns server for your system.

Rustybytes:
I don't use squeezecenter so it doesn't affect me but for Adamm's benefit, to see who is the maintainer (different ones for different packages and all are volunteers) on optware just search through the file http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/stable/Packages or do "ipkg info packagename" and this will give the maintainer and their email address. Once you have that information contact them. If it mentions NSLU2 Linux then post to the group http://tech.groups.yahoo.com/group/nslu2-general/ a request for update. Chances are the person that may answer you is Brian Zhou who is the Optware Package Manager (and may have built the package). A caveat, currently, I believe there are a bunch of updates but they had a problem with their build machine (Ubuntu) which they are redoing, so have some patience. There are a number of developers waiting to put their package updates back on line (NSLU2-linux has been around since 2004 so machines are getting old). They also have other OS and packages that they maintain on multiple processors and devices (not limited to ARM, yeah it has gone beyond the original NSLU2). Actually some of the original contributors are also involved with smart phones and platforms like Meego, Openmoko, and OE.

If you want to try plugapps, their repository is at http://plugboxlinux.org/arm/