RAMDISK IMAGES(2): ash has no job control ??? ... can't access tt y; job control turned off

Hi,

I am looking at a ramdisk image ... I am curious if anyone could give me a
tip as to why when my bash starts I have no "job contol" (ctrl-z etc) ... se
below ...

BusyBox v0.60.5 (2003.01.09-00:51+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
sh: can't access tty; job control turned off

As always thanks,

Jim

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Hi,

I am looking at a ramdisk image ... I am curious if anyone could give me a
tip as to why when my bash starts I have no "job contol" (ctrl-z etc) ... se
below ...

BusyBox v0.60.5 (2003.01.09-00:51+0000) Built-in shell (ash)

busybox builtin shell has no job control by default - for ash you have to
enable it at compile time.

hofrat

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

James,

At 11:19 AM 1/12/2003, you wrote:

I am looking at a ramdisk image ... I am curious if anyone could give me a
tip as to why when my bash starts I have no "job contol" (ctrl-z etc) ... se
below ...

BusyBox v0.60.5 (2003.01.09-00:51+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
sh: can't access tty; job control turned off

Look at inittab for busybox.

There should be the line which starts shell on system console:

::askfirst:-/bin/sh

Change it to somethinbg like:

ttyS0::askfirst:-/bin/sh

where the first name is the name of your console device, in this case I
have console on serial port


  Eugene Surovegin <mailto:ebs@innocent.com>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

At 11:24 AM 1/12/2003, you wrote:

quoted

I am looking at a ramdisk image ... I am curious if anyone could give me a
tip as to why when my bash starts I have no "job contol" (ctrl-z etc)

... se

quoted

below ...

BusyBox v0.60.5 (2003.01.09-00:51+0000) Built-in shell (ash)

busybox builtin shell has no job control by default - for ash you have to
enable it at compile time.

If ash has been built _without_ job control support it will _never_
complain about it,
especially it will never print out that "job control turned off".

If you look at the source code of ash in busybox, you'll see that this
particular message means that shell cannot access controlling tty.


  Eugene Surovegin <mailto:ebs@innocent.com>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/