From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1CKbJp-0004GA-LN for mharc-grub-devel@gnu.org; Thu, 21 Oct 2004 07:41:21 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CKbJo-0004Eo-FV for grub-devel@gnu.org; Thu, 21 Oct 2004 07:41:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CKbJn-0004EH-Ut for grub-devel@gnu.org; Thu, 21 Oct 2004 07:41:20 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CKbJn-0004E4-RG for grub-devel@gnu.org; Thu, 21 Oct 2004 07:41:19 -0400 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CKbBv-0000zs-5A for grub-devel@gnu.org; Thu, 21 Oct 2004 07:33:11 -0400 Received: from localhost (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 9CE49F6A9C5B for ; Thu, 21 Oct 2004 13:33:10 +0200 (CEST) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Thu, 21 Oct 2004 13:33:50 +0200 User-Agent: KMail/1.6.1 References: <200410211253.10450.okuji@enbug.org> <20041021112630.GA22854@artax.karlin.mff.cuni.cz> In-Reply-To: <20041021112630.GA22854@artax.karlin.mff.cuni.cz> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410211333.50293.okuji@enbug.org> Subject: Re: device syntax X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 11:41:20 -0000 On Thursday 21 October 2004 13:26, Tomas Ebenlendr wrote: > Hmm, and what if there are quotes, or newlines in name? I think that > we should be able to pass /any/ string to bios/firmware. Question is > what characters we want to escape. If escaped characters will be e.g. > quotes, the need of using this will be very little. If we escape > commas, many names will get horrible. So what about this solution, > extended by '\' as escaping character, using \" for char '"', \\ for > '\' and \xxx for nonprintable or other characters? That should be supported by the command-line interface, surely. Okuji