Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1jAGWL-0003En-FN for mharc-grub-devel@gnu.org; Fri, 06 Mar 2020 12:12:21 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:45766) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAGWJ-0003Ed-FO for grub-devel@gnu.org; Fri, 06 Mar 2020 12:12:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jAGWI-0002Cd-8q for grub-devel@gnu.org; Fri, 06 Mar 2020 12:12:19 -0500 Received: from mail-ot1-x343.google.com ([2607:f8b0:4864:20::343]:38253) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jAGWI-0002AW-3C for grub-devel@gnu.org; Fri, 06 Mar 2020 12:12:18 -0500 Received: by mail-ot1-x343.google.com with SMTP id i14so3132639otp.5 for ; Fri, 06 Mar 2020 09:12:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=gDnXMKXTjohL16vaW20G7jBu+n5SqFer3B+UPkQn438=; b=m4wwRpO4GFM05JtKGYamd5dIDl09083w8kxoLcP1lyebAxRuQAG/cfvkz+GzYeqONW GSUmXGCe76m/k4/8PF5knE2To5vVPZUHN83AOz6N6zrUYY+Tmvylrc257GdWIVHEmrB4 k0kWZXoph0719+SQhxQ7NPk0VRvu3ZTEF5iJ7u66FjnopBZN3zZmneteGCGpLi5/miwm 8TUofcwf3zW+KtBDt2LmuhTy45f/G8+wD6U4yWPwptmNXqGHrVFcCHoUlT/YcHiyAWzm s9+dq1bh7ejI//Y40jVgFFLhE/vp6JuNn47F7tA6y0dxkGvYUjlDpacPu3WFAUQOxCoJ 7j0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=gDnXMKXTjohL16vaW20G7jBu+n5SqFer3B+UPkQn438=; b=UvEJa227SLOdYE2X4Y/x8D0G140RQrdW3t1SUp6stCbc1OIgqZJEGFfMU9qrw1ne/S B+uTwCBXDTd/PCTTpeZZxzfnd21WEZD15i9jZYTDLBVzehc3u8+TQcJM573MTHi1pgso XtVd3gh0mBVpef8UtS8aKkze3c8LaBpNoQZoJykl6qBDwv7WmBxgpqZgqHhY2nWjHk2Y Y1OyVKOR9lx4dMknD8j7U4CBOIR3plrd818oP3CMw2l5jEGHm7tmHLc24XppNJ75gY6Z r7eC1Hv4W9PJW/29Dk4uYscysN/zwdVoV6nwX5x9rLALdGA7AAX+EbQO33PxOHX1ZS/X FKGg== X-Gm-Message-State: ANhLgQ0XdJrhbuj26dLU3J7vJR/piHFax2eTiEMAJUvjl/ubMoTV931R LAeZJS5Qui1d8T9WzlVCAIBb4fvk X-Google-Smtp-Source: ADFU+vulzVf0b+2moVEJxXvTq0ZNO1L+9dGgodatgZR/l92qxyELa5KxQHEw4KUPsPt6J/Kc4H7xKA== X-Received: by 2002:a9d:7a97:: with SMTP id l23mr3375152otn.302.1583514735933; Fri, 06 Mar 2020 09:12:15 -0800 (PST) Received: from [192.168.0.91] (cpe-70-123-227-116.satx.res.rr.com. [70.123.227.116]) by smtp.gmail.com with ESMTPSA id p5sm2793056otp.4.2020.03.06.09.12.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 06 Mar 2020 09:12:15 -0800 (PST) Subject: Re: [PATCH v2 08/12] kern: Make grub_error() more verbose To: grub-devel@gnu.org References: <20200304115851.3474263-1-javierm@redhat.com> <20200304115851.3474263-9-javierm@redhat.com> <20200306114206.gb7e5d5v5mwejviz@tomti.i.net-space.pl> <20200306124349.hveii6rg7ygzl5gs@tomti.i.net-space.pl> <10c3d93a-ffd4-3cb0-07b3-776954c53d65@slint.fr> From: Bruce Dubbs Message-ID: Date: Fri, 6 Mar 2020 11:12:14 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::343 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2020 17:12:20 -0000 On 3/6/20 11:03 AM, David Michael wrote: > On Fri, Mar 6, 2020 at 9:02 AM Didier Spaier wrote: >> Le 06/03/2020 à 13:43, Daniel Kiper a écrit : >>> If we go that way then we have to care about them by the end of the >>> universe. And this means more and more issues like [1]. If somebody >>> wants to use new GRUB then he/she have to reinstall the machine or >>> something like that. IMO we should not care about users who do not want >>> upgrade their machines or whatnot. Or at least their choices cannot >>> impact GRUB development too much. And I think that this MBR constraint >>> is hindering the project too much at this point. So, as above... >>> >>> Sorry for being blunt... >> >> Sorry to be off topic... In case of a GUID partition table, if I >> understand the UEFI specification[1], as the first usable LBA should be >> greater than or equal to 34 for a 512 bytes block size or 6 for a >> 4096 bytes logical block size, it could begin after a gap of 24K. >> >> Then, if we assume that the first partition begins @ 1MiB, can't GRUB >> use the space unused between the first usable LBA and 1MiB instead of >> a Bios Boot partition, in case of "legacy" booting and a GPT? I ask as >> then a Bios Boot partition wouldn't be necessary any more. > > It would be best to use a boot partition so the core.img space is > reserved by the GPT, Just a terminology issue here. Please don't call it a boot partition. It conflicts with those who mount /boot as a separate partition. Please call it a grub partition. -- Bruce but I once wanted to tack i386-pc GRUB onto an > existing UEFI GPT disk, so I wrote the commands that do what you're > describing here: > > https://github.com/dm0-/installer/blob/master/examples/systems/fitpc.sh#L151-L178 > > I may be misremembering, but I think the core.img size was limited to > around half a megabyte, so it should be safe to write it to the unused > ~1MiB before the first partition after the GPT. But yes, using the > boot partition would probably be for the best if you are formatting a > new disk. > > Thanks. > > David > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel >