title: MobaXterm Busybox strange setup
body: <p>I am using MobaXterm portable.
  I found a strange setup, summarized here.</p>
  
  <p>External commands in <code>/bin</code> work fine. E.g., with <code>/bin/ssh.exe</code> I can <code>ssh</code> ok.</p>
  
  <p>Internal commands are</p>
  
  <ol>
  <li><p>"redirected" to busybox, as</p>
  
  <pre><code>$ which cat
  /bin/cat
  $ ll /bin/cat
  lrwxrwxrwx    1 USER001  UsersGrp        16 Jul 24 07:42 /bin/cat -&gt; /bin/busybox.exe
  </code></pre></li>
  <li><p>at the same time aliased to files that apparently do not exist.</p>
  
  <pre><code>$ type cat
  cat is aliased to `/bin/cat.exe'
  </code></pre></li>
  </ol>
  
  <p>These aliases apparently take precedence over files in PATH, so the commands do not work.</p>
  
  <pre><code>$ cat myfile
  bash: /bin/cat.exe: No such file or directory
  </code></pre>
  
  <p>If I unalias, <code>cat</code> does not look for <code>/bin/cat.exe</code> but for <code>/bin/busybox.exe</code>, and everything is "back to normal".</p>
  
  <pre><code>$ unalias cat
  $ cat myfile
  Hello world
  ...
  </code></pre>
  
  <p><strong>How can I get normal behaviour (either without aliases or with the presence of the alias targets)?</strong>
  I mean not to write my own unaliases in <code>.bashrc</code>, this shouldn´t be needed.
  Moreover, perhaps I would be breaking something.</p>
  
  <p><strong>Why would MobaXterm setup things like this?</strong></p>
  
  <p>PS: In the initial state, even <code>ls</code> does not work, for the same reason.
  But <code>ll</code> works, since</p>
  
  <pre><code>$ type ll
  ll is aliased to `_bbf ls -l'
  $ type _bbf
  _bbf is a function
  ...
  </code></pre>