Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750899AbVIFUkw (ORCPT ); Tue, 6 Sep 2005 16:40:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750900AbVIFUkw (ORCPT ); Tue, 6 Sep 2005 16:40:52 -0400 Received: from terminus.zytor.com ([209.128.68.124]:2027 "EHLO terminus.zytor.com") by vger.kernel.org with ESMTP id S1750899AbVIFUkv (ORCPT ); Tue, 6 Sep 2005 16:40:51 -0400 Message-ID: <431DFEC3.1070309@zytor.com> Date: Tue, 06 Sep 2005 13:40:35 -0700 From: "H. Peter Anvin" User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alon Bar-Lev CC: Linux Kernel Mailing List Subject: Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit References: <4315B668.6030603@gmail.com> <43162148.9040604@zytor.com> <20050831215757.GA10804@taniwha.stupidest.org> <431628D5.1040709@zytor.com> <431DF9E9.5050102@gmail.com> In-Reply-To: <431DF9E9.5050102@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1612 Lines: 41 Alon Bar-Lev wrote: > > Hello Peter, I've written a reply before but got no response... > > The idea of putting arguments in initramfs is not practical, since the > whole idea is to have the same image of system and affecting its > behavior using the boot loader... > No, you're wrong. The boot loader can synthesize an initramfs. > I would like to push forward the idea to extend the command-line size... > > All we need for start is an updated version of the "THE LINUX/I386 BOOT > PROTOCOL" document that states that in the 2.02+ protocol the boot > loader should set cmd_line_ptr to a pointer to a null terminated string > without any size restriction, specifying that the kernel will read as > much as it can. Already pushed to Andrew. I will follow it up with a patch to extend the command line, at least to 512. > After I get this update, I will try to work with GRUB and LILO so that > they will fix their implementation. Currently they claim that they > understand that they should truncate the string to 256. > > After that I will provide my simple patch for setting the maximum size > the kernel allocates in the configuration. > > BTW: Do you know why the COMMAND_LINE_SIZE constant is located in two > separate include files? No, I don't. It could be because one is included from assembly code in the i386 architecture. -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/