Message-ID: <49AC0799.5060306@turknet.net.tr>
Date: Mon, 02 Mar 2009 18:21:45 +0200
From: Tarkan Erimer <tarkan.erimer@turknet.net.tr>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Lubomir Rintel <lkundrak@v3.sk>
CC: Diego Calleja <diegocg@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Failover Kernel
References: <49A659D0.2040903@turknet.net.tr>	 <200902261802.56612.diegocg@gmail.com>  <49A80796.2070208@turknet.net.tr> <1235749850.4718.1.camel@localhost.localdomain>
In-Reply-To: <1235749850.4718.1.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-9; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 875
Lines: 18

Lubomir Rintel wrote:
>
> How is the backup kernel minimal? It is usually the very same kernel as
> the "primary" one. You can use the same initrd as well and do a full
> multiuser boot.
>
>   
Kdump's backup (in kdump terms, it is "Capture Kernel") kernel is with 
minimal set of features and modules (scsi drivers, network drivers etc.) 
to have small memory footprint and resources to just handle crash dump 
related things. So,it's not a full replacement of primary kernel. Also, 
the point is not to make boot when crash occured. The idea is to take 
control when a crash occured by backup kernel without any need to reboot.
--
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/