Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 13 Jul 2001 06:07:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 13 Jul 2001 06:07:48 -0400 Received: from [213.97.45.174] ([213.97.45.174]:30220 "EHLO pau.intranet.ct") by vger.kernel.org with ESMTP id ; Fri, 13 Jul 2001 06:07:31 -0400 Date: Fri, 13 Jul 2001 12:07:17 +0200 (CEST) From: Pau Aliagas X-X-Sender: To: Rik van Riel cc: "Albert D. Cahalan" , "C. Slater" , Subject: Re: Switching Kernels without Rebooting? In-Reply-To: Message-ID: 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 Thu, 12 Jul 2001, Rik van Riel wrote: > On Thu, 12 Jul 2001, Albert D. Cahalan wrote: > > > I think I see a business opportunity here. > > [snip technically risky idea] > > > The 24x7 places might be willing to pay somebody to do this. > > Unlikely. They need hardware redundancy anyway, so they'll > just upgrade their cluster node-by-node, without doing > risky and potentially data-corrupting things like live > kernel upgrades. I see business in a different way: instead of ISP or ASP you provide a backup cluster node where you can migrate your processes before rebooting. Everything keeps on working, no magic involved. So we can invent the CNP (Cluster Node Provider) Pau - 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/