This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Apr 26 09:34:04 2024 Delivery-date: Mon, 19 Jun 2006 14:05:54 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932400AbWFSMFE (ORCPT ); Mon, 19 Jun 2006 08:05:04 -0400 Received: from spirit.analogic.com ([204.178.40.4]:31244 "EHLO spirit.analogic.com") by vger.kernel.org with ESMTP id S932399AbWFSMFD convert rfc822-to-8bit (ORCPT ); Mon, 19 Jun 2006 08:05:03 -0400 Received: from chaos.analogic.com ([10.112.50.11]) by phoenix.analogic.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 19 Jun 2006 08:05:01 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Received: from chaos.analogic.com (localhost [127.0.0.1]) by chaos.analogic.com (8.12.11/8.12.11) with ESMTP id k5JC514L027510; Mon, 19 Jun 2006 08:05:01 -0400 Received: (from linux-os@localhost) by chaos.analogic.com (8.12.11/8.12.11/Submit) id k5JC516n027509; Mon, 19 Jun 2006 08:05:01 -0400 X-OriginalArrivalTime: 19 Jun 2006 12:05:01.0663 (UTC) FILETIME=[97BBFEF0:01C69398] content-class: urn:content-classes:message Subject: Re: emergency or init=/bin/sh mode and terminal signals Date: Mon, 19 Jun 2006 08:05:01 -0400 Message-Id: In-Reply-To: <20060619114617.GM4253@implementation.labri.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: emergency or init=/bin/sh mode and terminal signals Thread-Index: AcaTmJfFSU4FDtOeTqGL50itlNUztQ== References: <20060618212303.GD4744@bouh.residence.ens-lyon.fr> <20060619114617.GM4253@implementation.labri.fr> From: "linux-os \(Dick Johnson\)" To: "Samuel Thibault" Cc: Reply-To: "linux-os \(Dick Johnson\)" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 19 Jun 2006, Samuel Thibault wrote: > linux-os (Dick Johnson), le Mon 19 Jun 2006 07:37:02 -0400, a =E9crit= : >> I don't think this is the correct behavior. You can't allow some >> terminal input to affect init. It has been the de facto standard >> in Unix, that the only time one should have a controlling terminal >> is after somebody logs in and owns something to control. If you want >> a controlling terminal from your emergency shell, please exec /bin/l= ogin. > > Ok, but people don't know that: they're given a shell, and wonder why= on > hell ^C doesn't work... > > Samuel Maybe, but you shouldn't modify the kernel for "training". The kernel needs to be sacrosanct. Cheers, Dick Johnson Penguin : Linux version 2.6.16.4 on an i686 machine (5592.88 BogoMips). New book: http://www.AbominableFirebug.com/ _ =1A=04 **************************************************************** The information transmitted in this message is confidential and may be = privileged. Any review, retransmission, dissemination, or other use of= this information by persons or entities other than the intended recipi= ent is prohibited. If you are not the intended recipient, please notif= y Analogic Corporation immediately - by replying to this message or by = sending an email to DeliveryErrors@analogic.com - and destroy all copie= s of this information, including any attachments, without reading or di= sclosing them. Thank you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel"= in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/