On 9/8/14, 4:17 AM, Jan Rome wrote:
> Hello,
>
> I'd like to report an obscure bug I came across in pfsense which runs on
> top of FreeBSD.
>
> If I run a bash script in which I have
>
> read -r -n1 -p "prompt: "
>
> and instead of providing input, i ctrl-c the script,
>
> the ash shell doesn'
On 9/9/14, 4:02 AM, Jan Rome wrote:
> I use ash to run a script which has #!/bin/bash
> if I run bash and then run the script, the script exits to bash, and if i
> then exit bash back to ash, I dont see the problem.
The reason is the same as the one in my reply from yesterday to a different
report
I use ash to run a script which has #!/bin/bash
if I run bash and then run the script, the script exits to bash, and if
i then exit bash back to ash, I dont see the problem.
Best regards,
Jan
On 9.9.2014 1:58, Ryan Cunningham wrote:
This isn't clear to me. Are you using the Almquist Shell to
This isn't clear to me. Are you using the Almquist Shell to execute BASH to run
your script, or is BASH already running when the script is executed?
--
Sent from my iPad
> On Sep 8, 2014, at 1:17 AM, Jan Rome wrote:
>
> Hello,
>
> I'd like to report an obscure bug I came across in pfsense wh
Hello,
I'd like to report an obscure bug I came across in pfsense which runs on
top of FreeBSD.
If I run a bash script in which I have
read -r -n1 -p "prompt: "
and instead of providing input, i ctrl-c the script,
the ash shell doesn't recover the terminal properly; backspace echos ^?
and
