From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1YnU1N-0003f2-NA for mharc-grub-devel@gnu.org; Wed, 29 Apr 2015 11:35:33 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40799) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnU1L-0003es-CA for grub-devel@gnu.org; Wed, 29 Apr 2015 11:35:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnU1K-00012g-6T for grub-devel@gnu.org; Wed, 29 Apr 2015 11:35:31 -0400 Received: from mo6-p00-ob.smtp.rzone.de ([2a01:238:20a:202:5300::9]:64434) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnU1J-00012C-Su for grub-devel@gnu.org; Wed, 29 Apr 2015 11:35:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1430321727; l=1979; s=domk; d=aepfle.de; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Subject:To:From:Date; bh=7Gen3zc3rI7oXBKpyJAkrXLpMtHvAKQ/hh4cQZRp+qU=; b=Oq5MbciNrhBCBRxoMHyK5ixq7GAOusYICOYAK4UJdMPonTh6648MXYD6eN/WObBRqj8 XuPO2pup7QFLXNiBZ7inhUcTj8oWLzgukSW/PvoTX3fgXb43Ianl3UzcDy2bWYAY4gSY0 eh/p0Xp5iFnhxfxWTwxNLQqO2Uqroaa7lLU= X-RZG-AUTH: :P2EQZWCpfu+qG7CngxMFH1J+yackYocTD1iAi8x+OWi/zfN1cLnBYfssUt1SQsSlJPHNSnsuG/FaLOSSn4wXo16Sj/Z/Wg== X-RZG-CLASS-ID: mo00 Received: from probook.fritz.box ([2001:a60:10fc:4601:1ec1:deff:feb9:bb48]) by smtp.strato.de (RZmta 37.5 AUTH) with ESMTPSA id R01dc8r3TFZRxjj (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (curve sect571r1 with 571 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Wed, 29 Apr 2015 17:35:27 +0200 (CEST) Received: by probook.fritz.box (Postfix, from userid 1000) id 3BEC550292; Wed, 29 Apr 2015 17:35:27 +0200 (CEST) Date: Wed, 29 Apr 2015 17:35:27 +0200 From: Olaf Hering To: The development of GNU GRUB Subject: Re: passing options to grub in xen,openfirmware and efi Message-ID: <20150429153527.GA12448@aepfle.de> References: <20150423080306.GA15265@aepfle.de> <5540F299.4020304@gmail.com> <20150429151011.GA5931@aepfle.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.22.rev6346 (2013-10-29) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:238:20a:202:5300::9 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2015 15:35:32 -0000 On Wed, Apr 29, Vladimir 'phcoder' Serbinenko wrote: > > On Apr 29, 2015 5:10 PM, "Olaf Hering" wrote: > > > > On Wed, Apr 29, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > > > > > I'm aware of the problem and I fully agree with you. Automatic install > > > doesn't use those and I think the reason for it was to specify root in > > > early days of porting. I don't think it's used for anything nowadays. > > > > For PV guests the use case is simple: provide a generic grub binary, > > which recognizes optional knobs from the domU.cfg. This will be used to > > select one of the configured devices as root. > More details on this one please. Both command line and grub binary are on host. > How is managing changing one is different from the other? Not sure what you are asking, but: The distro provides a static binary, which has a certain level of features. And some of the features can be controlled from the outside by some knobs. The feature is to select a certain drive without user interaction, and the knob is a string in the cmdline in the PV domU case. > > > Also unless there is a good usecase for having command line parsing, I'm > > > all for killing existing ieee1275 parsing altogether and not introducing > > > any parsing in the future. > > So you want to dumb it down to the 80s PC level, even if some firmware > > implementations can set knobs?! > "It's shiny and new" or "this is from 80s" are fallacies and not arguments. Its not new that a firmware provides an interface to query its properties AND that a firmware provides an interface the adjust properties. OF does that. EFI maybe, no idea. And in some sense a PV guest via its cmdline does that as well. I have however not looked how the cmdline is passed to the PV kernel and how its retrieved in the PV kernel. My laptop with its BIOS provides nothing like that because the concept is based on the PC from the 80s. Or whatever. Olaf