From: Simon Horman Subject: Re: Re: x86: fix to parse multiboot command line passed by latest grub Date: Tue, 8 Dec 2009 09:00:00 +1100 Message-ID: <20091207215959.GI3336@verge.net.au> References: <4B1CBB98.3050408@cn.fujitsu.com> <20091207105455.GE5040@const.bordeaux.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20091207105455.GE5040@const.bordeaux.inria.fr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Samuel Thibault , Keir Fraser , Wei Yongjun , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Mon, Dec 07, 2009 at 11:54:55AM +0100, Samuel Thibault wrote: > Keir Fraser, le Mon 07 Dec 2009 09:57:41 +0000, a =C3=A9crit : >=20 > > Or get grub2 guys to give us a flag to detect > > this stupid compatibility breakage. >=20 > They said multiboot never asserted anything about the command line and > thus implementation were allowed to vary without notice. The rationale > for grub's behavior change is that the user has to migrate from grub1 > syntax to grub2 syntax anyway. They broke it because they could? :-)