[BusyBox] Ctrl-C doesn't works
pfeiffer at swac.de
Thu May 6 11:11:49 UTC 2004
Meanwhile I found out that it doesn't works only when I use the serial
console. After logging in via SSH Ctrl-C works perfect.
As far as I can see, there are all devices available in /dev (and the same
kernel works well when I don't use BusyBox).
On Thu, 6 May 2004 08:13:55 +0100, David Cannings <lists at edeca.net> wrote:
> On Thursday 06 May 2004 06:19, Michael Pfeiffer wrote:
>> currently I'm using BusyBox v1.00-pre8. There Ctrl-C doesn't works, so
>> it is impossible to break any program with it. In some older archives I
>> found the infomration that may be possible when busybox is running
>> somehow with pid 1. But thats not the case here.
>> So what could be the reason for this problem?
> Quite possibly your kernel has been compiled with devfs support and
> BusyBox hasn't, or the kernel hasn't been compiled with devfs support but
> you forgot to populate /dev with the required nodes.
> busybox mailing list
> busybox at mail.busybox.net
Mit freundlichen Grüßen / Best Regards
S.W.A.C. Schmitt-Walter Automation Consult GmbH
Ödenpullach Haus 1
Mail: pfeiffer at swac.de
More information about the busybox