From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1iVa0H-0006i2-L0 for mharc-grub-devel@gnu.org; Fri, 15 Nov 2019 06:43:05 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:38737) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVa0F-0006fZ-72 for grub-devel@gnu.org; Fri, 15 Nov 2019 06:43:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iVa0E-00068k-2v for grub-devel@gnu.org; Fri, 15 Nov 2019 06:43:03 -0500 Received: from dibed.net-space.pl ([84.10.22.86]:46710) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.71) (envelope-from ) id 1iVa0D-00067X-OV for grub-devel@gnu.org; Fri, 15 Nov 2019 06:43:02 -0500 Received: from router-fw.i.net-space.pl ([192.168.52.1]:41258 "EHLO tomti.i.net-space.pl") by router-fw-old.i.net-space.pl with ESMTP id S1912429AbfKOLmy (ORCPT ); Fri, 15 Nov 2019 12:42:54 +0100 X-Comment: RFC 2476 MSA function at dibed.net-space.pl logged sender identity as: dkiper Date: Fri, 15 Nov 2019 12:42:52 +0100 From: Daniel Kiper To: Michael Chang Cc: The development of GNU GRUB , Vladimir 'phcoder' Serbinenko , "dave@jikos.cz" , "pmenzel@molgen.mpg.de" , "terrelln@fb.com" Subject: Re: [PATCH] btrfs: disable zstd support for i386-pc Message-ID: <20191115114252.z5xxticja274cluq@tomti.i.net-space.pl> References: <20191105091949.29559-1-mchang@suse.com> <20191107115235.pxkvffcohbsho443@tomti.i.net-space.pl> <20191113110050.omph6xptgsc2ppe2@tomti.i.net-space.pl> <20191114095345.GA3688@mazu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191114095345.GA3688@mazu> User-Agent: NeoMutt/20170113 (1.7.2) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 84.10.22.86 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, 15 Nov 2019 11:43:04 -0000 On Thu, Nov 14, 2019 at 09:53:54AM +0000, Michael Chang wrote: > On Wed, Nov 13, 2019 at 12:00:50PM +0100, Daniel Kiper wrote: > > On Thu, Nov 07, 2019 at 12:52:35PM +0100, Daniel Kiper wrote: > > > On Wed, Nov 06, 2019 at 11:15:04AM -0800, Vladimir 'phcoder' Serbinenko wrote: > > > > Please don't do it this way. The right solution is to move it to separate > > > > module and include zstd module when needed. Not everybody uses btrfs > > > > embedded area. I recommend not to use it. Using mbr gap or BBP is the > > > > recommended way. > > > > > > I will put the cat among the pigeons. Maybe we should finally stop > > > pretending that the GRUB supports small MBR gaps. Otherwise we will > > > be fighting with such issues endlessly. > > > > Bumping the thread... Nobody objects? Hmmm... > > I don't think we are able to give up MBR gap support, simply because no > other way out in creating the area for bootloader embedding. However we Nope, I do not propose that... > should consider to correct this claim in manual. > > "You must ensure that the first partition starts at least 31 KiB (63 > sectors) from the start of the disk" > > to reflect the fact that 31 KiB is no longer applicable and the ideal > size should be above 1MB (or such). You should go check with your disk > tools to find the suitable parameter to fulfill the requirement, for eg, > the partition alignment would mostly affect this. Exactly! However, there are some legacy systems which do not boot if MBR gap does not end at 63 sectors boundary. Hence, maybe we should suggest chainloading, using e.g. SYSLINUX, in a such cases. Anyway, may I ask you to prepare a patch for GRUB manual which describes the problem? Daniel