From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964777AbWFSPrz (ORCPT ); Mon, 19 Jun 2006 11:47:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932514AbWFSPry (ORCPT ); Mon, 19 Jun 2006 11:47:54 -0400 Received: from iona.labri.fr ([147.210.8.143]:26310 "EHLO iona.labri.fr") by vger.kernel.org with ESMTP id S932497AbWFSPrx (ORCPT ); Mon, 19 Jun 2006 11:47:53 -0400 Date: Mon, 19 Jun 2006 17:47:46 +0200 From: Samuel Thibault To: Jan Engelhardt Cc: linux-kernel@vger.kernel.org Subject: Re: emergency or init=/bin/sh mode and terminal signals Message-ID: <20060619154746.GS4253@implementation.labri.fr> Mail-Followup-To: Samuel Thibault , Jan Engelhardt , linux-kernel@vger.kernel.org References: <20060618212303.GD4744@bouh.residence.ens-lyon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jan Engelhardt, le Mon 19 Jun 2006 14:08:28 +0200, a écrit : > >Hi, > > > >There's a long-standing issue in init=/bin/sh mode: pressing control-C > >doesn't send a SIGINT to programs running on the console. The incurred > >typical pitfall is if one runs ping without a -c option... no way to > >stop it! > > Worse, I can observe same behavior when using "-b", i.e. init=/sbin/init > called with -b (read: `/sbin/init -b`), That's equivalent to the "emergency" mode. Samuel