problems with /dev/console and "job control"

walter harms wharms at bfs.de
Sat Jun 26 21:09:15 UTC 2010



Christian Ruppert schrieb:
> On 06/26/2010 06:35 PM, Denys Vlasenko wrote:
>> On Saturday 26 June 2010 17:02, Christian Ruppert wrote:
>>> On 06/26/2010 04:46 PM, Denys Vlasenko wrote:
>>>> On Saturday 26 June 2010 13:30, Christian Ruppert wrote:
>>>>> Hey guys,
>>>>>
>>>>> I try to setup busybox properly for my initrd although I don't get it
>>>>> working with "job control".
>>>>> I thought that console=... would help (kernel cmdline) but it doesn't.
>>>>>
>>>>> It works so far (at least CTRL+C) if I use openvt -s but that is no
>>>>> solution for me.
>>>>> I use my own /init script which later calls "exec /bin/sh" to enter a
>>>>> rescue shell but CTRL+C etc. isn't working. :(
>>>> Does this answer your question?
>>>>
>>>> http://busybox.net/FAQ.html#job_control
>>> Not really because how can I run the shell in a real console there?
>>> I have no ttySX at all and other console= values doesn't seem to work.
>> So you do not know what is your tty?
> I do.. I'll rephrase it:
> I don't have a serial cable connected or anything else so I can't test
> different console= parameter.
> 
> # dmesg|grep console
> console [tty0] enabled
> 
> But still "no job control"
> 
>> Please post complete dmesg output, and ls -l /dev/*tty*
> See attached dmesg.
> from tty -> tty63 everything crw-rw---- root:root
> ttyS devices also exists but they're not available.
> 

But you have a network running ?
so you can use netconsole to send the bootmessages etc
via network.

You can also send data via "netcat". are you aware of that ?

re,
 wh



More information about the busybox mailing list