On 06/26/2010 11:14 PM, Denys Vlasenko wrote: > On Saturday 26 June 2010 19:22, Christian Ruppert wrote: >> 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. > > No one said that you need to. > > http://busybox.net/FAQ.html#job_control says: > > "Your should run your shell on a normal tty such as tty1 or ttyS0 and > everything > will work perfectly". > > It does not say "set your console= kernel parameter to tty1 or ttyS0". > > Please try running "sh </dev/tty1 >/dev/tty1 2>/dev/tty1" >
Still the same... "sh: can't access tty; job control turned off" -- Regards, Christian Ruppert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
