While there are only two EXE files in c:\windows\sua\bin (just cat32.exe and fileinfo.exe) and a load of commands that would run but are missing an EXE extension!)
C:\Windows\SUA\bin>dir Volume in drive C has no label. Volume Serial Number is B411-D580
Directory of C:\Windows\SUA\bin 17/11/2014 11:09 AM <DIR> . 17/11/2014 11:09 AM <DIR> .. 18/01/2008 06:09 AM 172,032 at 18/01/2008 06:09 AM 172,032 atq 18/01/2008 06:09 AM 172,032 atrm 18/01/2008 01:45 AM 396,288 awk 18/01/2008 05:41 AM 115,200 banner 18/01/2008 01:45 AM 105,472 basename 18/01/2008 06:09 AM 172,032 batch 18/01/2008 07:01 AM 141,824 bp 18/01/2008 06:05 AM 46,605 c89 18/01/2008 06:05 AM 117,760 cal 18/01/2008 06:05 AM 140,800 calendar 18/01/2008 01:45 AM 118,784 cat 18/01/2008 01:45 AM 155,648 cat32 18/01/2008 01:45 AM 155,648 cat32.exe .....
There are EXE files for not all but most of the commands, in c:\windows\sua\common
C:\Windows\SUA\common>dir *.exe Volume in drive C has no label. Volume Serial Number is DC46-3C68 Directory of C:\Windows\SUA\common 01/18/2008 04:42 AM 97,280 basename.exe 01/18/2008 05:05 AM 135,168 cat.exe 01/18/2008 05:05 AM 134,144 chgrp.exe .... 01/18/2008 06:19 AM 121,856 wc.exe 29 File(s) 4,773,376 bytes 0 Dir(s) 126,438,662,144 bytes free C:\Windows\SUA\common>
There are some e.g. awk which don't have an exe file but are in c:\windows\sua\bin and you don't have to rename them to run them, they run from an SUA shell e.g. start..programs..subsystem for unix..c shell then ls /bin and awk shows there.
Also, I hadn't noticed initially but installing SUA does add C:\windows\sua\common\
and c:\windows\sua\usr\lib\"
(with a trailing backslash oddly enough), to the path.
Related followup question now answered - In Windows SUA(System for Unix Applications), I cannot get KSH to run commands. Even ls fails