Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760613AbZA3Aip (ORCPT ); Thu, 29 Jan 2009 19:38:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758661AbZA3Ai3 (ORCPT ); Thu, 29 Jan 2009 19:38:29 -0500 Received: from terminus.zytor.com ([198.137.202.10]:43067 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758333AbZA3Ai2 (ORCPT ); Thu, 29 Jan 2009 19:38:28 -0500 Message-ID: <49824BFA.3000203@zytor.com> Date: Thu, 29 Jan 2009 16:38:18 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Mikael Pettersson CC: LKML , x86@kernel.org Subject: Re: RFC: running out of x86 boot loader IDs References: <49823683.6060201@zytor.com> <18818.19160.962399.20413@harpo.it.uu.se> In-Reply-To: <18818.19160.962399.20413@harpo.it.uu.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 812 Lines: 19 Mikael Pettersson wrote: > Why do we need a boot loader id at all? The purpose of a boot loader, > whatever it may be, is to load the kernel according to certain protocols. > Once that's done, why would the kernel care who/what loaded it? A couple of reasons... a) Bugs happen. Sometimes bugs are latent, and we later find ourselves in an unenviable position of not being able to work around a problem unless we know that we were loaded by with . b) Distro installers or other distro components sometimes find this useful. -hpa -- 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/