How do I fix pwd (print working directory) on Cyanogenmod 7?

Question

I recently started using Cyanogenmod and I noticed some odd behavior in the shell for certain commands. The command works as expected in the Terminal app directly on the phone, but strange things occur when connected by ssh. For instance pwd:

/data/dropbear # pwd

/data/dropbear # which pwd
/system/xbin/pwd
/data/dropbear # busybox pwd
/data/dropbear
/data/dropbear # ls -l /system/xbin/pwd
lrwxrwxrwx    1 root     root             7 Apr  1 23:30 pwd -> busybox

As you can see, pwd prints a blank line ![enter image description here][1]when typed normally at the command line. Even though it is just a link to busybox. I've fooled around with other embedded systems (DD-WRT), and noticed busybox was set up the same way - and works. The way it's behaving here breaks functionality with WinSCP, which depends on pwd when it connects.

I thought I could be a little clever here and use WinSCP to transfer files to my phone over my wireless lan. But as you can see it isn't quite working yet. For the record I'm using a Motorola Droid, Cyanogenmod 7 RC4, and also PuTTy from a Windows 7 machine.

Answer 1

Can you replace the pwd symbolic link with a script that just runs 'busybox pwd'?

Or would an alias work?

Answer 2

The reason for the different behavior is that dropbear was using a different shell than the terminal app. A workaround would be to just use the same shell as the terminal app:

echo "/system/bin/sh" > /data/dropbear/.profile

Note that this is in contrast to the Cyanogenmod wiki, which instructs you to use the busybox shell: /system/xbin/busybox sh