Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 30 Jan 2002 23:41:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 30 Jan 2002 23:41:43 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:53003 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Wed, 30 Jan 2002 23:41:30 -0500 Message-ID: <3C58CAE0.4040102@zytor.com> Date: Wed, 30 Jan 2002 20:41:04 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120 X-Accept-Language: en-us, en, sv MIME-Version: 1.0 To: "Eric W. Biederman" CC: Andrew Morton , linux-kernel@vger.kernel.org, Werner Almesberger , "Erik A. Hendriks" Subject: Re: [RFC] x86 ELF bootable kernels/Linux booting Linux/LinuxBIOS In-Reply-To: <3C586355.A396525B@zip.com.au> <3C58B078.3070803@zytor.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Eric W. Biederman wrote: > > I am reluctant to go with a bootimg like interface because having a > standard format encourages people to standardize. Though a good > argument can persuade me. I don't loose any flexibility in comparison > to bootimg because composing files on the fly is not significantly > harder than composing a bootable image in ram. > > Please tell me if I haven't clearly answered your concerns about > being locked into a single image. > I have to think about it. I'm not convinced that this particular flavour of standardization is a step in the right direction -- in fact, it is *guaranteed* to provide significant additional complexity for bootloaders, and bzImage support is still going to have to be provided for the forseeable future. Since you express that it will basically be necessary to stitch the ELF file together on the fly I don't see much point, quite frankly; it seems like extra complexity for no good reason. -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/