[BusyBox] can't access tty: job control turned off - SOLVED

[Gad]

Gad wrote:
> tom at ceisystems.com wrote:
> 
>> Gad,
>>     When you built BusyBox, did you enable the "-e" and "-n"
>> features?  This could be the source of your problem.  If you're not
>> sure, you could forward your .config file to the list.
>>
>> Good Luck,
>> Thomas Cameron
>> CEI Systems
>>
>>
>> -----Original Message-----
>> From: Gad [mailto:bugchong at tpg.com.au] Sent: Friday, September 12, 
>> 2003 10:22 PM
>> To: Thomas Cameron
>> Cc: bug1 at optushome.com.au; busybox at codepoet.org
>> Subject: Re: [BusyBox] can't access tty: job control turned off
>>
>>
>> tom at ceisystems.com wrote:
>>
>>> I'd be interested in seeing your startup scripts.  With the 
>>> information you provided, we can not really tell if you're trying to 
>>> tell echo to do something it can not, or what have you.
>>>
>>> Good Luck,
>>> Thomas Cameron
>>> CEI Systems
>>>
>>>
>>> -----Original Message-----
>>> From: Glenn McGrath [mailto:bug1 at optushome.com.au]
>>> Sent: Friday, September 12, 2003 7:32 AM
>>> To: busybox at codepoet.org
>>> Subject: Re: [BusyBox] can't access tty: job control turned off
>>>
>>>
>>> On Fri, 12 Sep 2003 19:51:23 +1000
>>> Gad <bugchong at tpg.com.au> wrote:
>>>
>>>
>>>
>>>> While I'm at it:
>>>>
>>>> I'm making a boot floppy with 1.00-pre3 and uClibc 0.9.21. When I
>>>> boot, I get:
>>>>
>>>> Enter 'help' for a list of built in commands.
>>>>
>>>> -sh: can't access tty; job control turned off
>>>> -sh: echo: Function not implemented
>>>> -sh: echo: Function not implemented
>>>> -sh: echo: Function not implemented
>>>> -sh: echo: Function not implemented
>>>> / #
>>>
>>>
>>>
>>> I dont know where "Function not implemented" is coming from, grep 
>>> doesnt find it, from the message it looks like its coming from the 
>>> echo command in a shell script.
>>>
>>> The job control turned off message has been mentioned a few times on 
>>> the lists, you might have some luck searching the archives.
>>>
>>
>> The startup scripts come from the documentation in 0.60.5 (which 
>> explains how to make a boot floppy):
>>
>> /etc/profile:
>> # /etc/profile: system-wide .profile file for the Bourne shells
>>
>> echo
>> echo -n "Processing /etc/profile... "
>> # no-op
>> echo "Done"
>> echo
>>
>> /etc/inittab:
>> ::sysinit:/etc/init.d/rcS
>> ::respawn:-/bin/sh
>> tty2::askfirst:-/bin/sh
>> ::ctrlaltdel:/bin/umount -a -r
>>
>> /etc/init.d/rcS:
>> #! /bin/sh
>> /bin/mount -a
>>
>>
>> Gad
>>
> 
> Yes, I enabled both options:
> [*] echo (basic SUSv3 versions taking no options
> [*]    Enable echo options (-n and -e)
> 
> In the .config file:
> 
> CONFIG_ECHO=y
> CONFIG_FEATURE_FANCY_ECHO=y
> 
> 
> Gad
> 

After changing the /etc/inittab like Erik suggested, doing make 
distclean (!!!) and recompiling, the problem is gone.

The floppy now boots ok and is usable. I'll soon put it on my website, 
it someone is interested in a boot floppy :-)

Thanks everyone for your help,
Gad

-- 
http://yallara.cs.rmit.edu.au/~gabraham