From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752389AbXD0Vp1 (ORCPT ); Fri, 27 Apr 2007 17:45:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752433AbXD0Vp0 (ORCPT ); Fri, 27 Apr 2007 17:45:26 -0400 Received: from smtp1.linux-foundation.org ([65.172.181.25]:50454 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752389AbXD0VpZ (ORCPT ); Fri, 27 Apr 2007 17:45:25 -0400 Date: Fri, 27 Apr 2007 14:44:32 -0700 (PDT) From: Linus Torvalds To: "Rafael J. Wysocki" cc: Pekka J Enberg , Nigel Cunningham , LKML Subject: Re: Back to the future. In-Reply-To: <200704272324.43359.rjw@sisk.pl> Message-ID: References: <1177567481.5025.211.camel@nigel.suspend2.net> <1177654110.4737.91.camel@nigel.suspend2.net> <200704272324.43359.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 27 Apr 2007, Rafael J. Wysocki wrote: > > Why do you think that keeping the user space frozen after 'snapshot' is a bad > idea? I think that solves many of the problems you're discussing. It makes it harder to debug (wouldn't it be *nice* to just ssh in, and do gdb -p when something goes wrong?) but we also *depend* on user space for various things (the same way we depend on kernel threads, and why it has been such a total disaster to try to freeze the kernel threads too!). For example, if you want to do graphical stuff, just using X would be quite nice, wouldn't it? But I do agree that doing everythign in the kernel is likely to just be a hell of a lot simpler for everybody. Linus