On Fri Jan 04, 2002 at 05:05:34PM +0100, Laurent Bonnaud wrote:
>
> Adam> Hmm, wouldn't this be a busybox bug? But I try, ona fully
> Adam> installed system:
> Adam>
> Adam> # busybox ping arroz
> Adam>
> Adam> and ctrl-c works fine. Wierd.
>
> I had done the same test and got the result.
On 04 Jan 2002 17:05:34 +0100
Laurent Bonnaud <[EMAIL PROTECTED]> wrote:
> Adam> Hmm, wouldn't this be a busybox bug? But I try, ona fully
> Adam> installed system:
> Adam>
> Adam> # busybox ping arroz
> Adam>
> Adam> and ctrl-c works fine. Wierd.
>
> I had done the same test and got the re
Adam> Hmm, wouldn't this be a busybox bug? But I try, ona fully
Adam> installed system:
Adam>
Adam> # busybox ping arroz
Adam>
Adam> and ctrl-c works fine. Wierd.
I had done the same test and got the result. That's why I reported
this bug against boot-floppies instead of busybox.
Are you
On Mon, Dec 24, 2001 at 03:38:08PM -0500, Adam Di Carlo wrote:
> Hmm, wouldn't this be a busybox bug? But I try, ona fully installed
> system:
>
> # busybox ping arroz
>
> and ctrl-c works fine. Wierd.
Umm, perhaps this is nonsense, but if busybox is running as PID 1, it won't
get the TERM
Package: boot-floppies
Version: 3.0.17
Severity: normal
Hi,
I did a successful network installation with the udma100-ext3
boot-floppies. I only had one minor problem. In the Alt-F2 virtual
console, I used ping to check if the network worked. Unfortunately,
Ctrl-c did not work to stop ping.
5 matches
Mail list logo