Terminal bug: missing prompt

[Brian J. Tarricone]

Ambrose Li wrote:
> On 25/02/2008, Jean-Marie Pacquet <jm at pacquet.net> wrote:
>> Oh no, it has nothing to do with luck. It's on purpose that /bin/sh is a
>>  link to /bin/bash on slackware. This allows to define a default shell
>>  for those who leave the field empty. So, if you want, you may define
>>  another default shell.
>>  ash is quite popular on slackware:
> [stuff deleted]
>>  There are many other choices than the old "sh".
> 
> No! It should not be like this. (I started as a Slackware user too.)
> 
> You cannot depend on /bin/sh being anything other than the
> traditional /bin/sh (ash if you want). This is for compatibility
> reasons; you can't link just any shell to /bin/sh and not
> expect to have problems with shell scripts...

Correct, though in practice, any shell that behaves mostly like sh will 
work -- bash is supposed to enter 'sh compatibility mode' when invoked 
as 'sh' via a symlink, but in reality it still supports a bunch of 
things that sh doesn't support, and the compat mode is far from 
perfect...  But yeah, if you link anything not Bourne-shell-compatible 
to /bin/sh, you're asking for trouble.

	-brian