On Jun 27, 2017, at 3:53 AM, Theodore Ts'o wrote:
> On Mon, Jun 26, 2017 at 08:46:48AM +0200, Felipe A Rodriguez wrote:
>>> So when you say that enabling the 64-bit file system feature causes a
>>> regression by causing Grub to fail to be able to read the root file
>>> system, I have to respectfu
On Mon, Jun 26, 2017 at 08:46:48AM +0200, Felipe A Rodriguez wrote:
> > So when you say that enabling the 64-bit file system feature causes a
> > regression by causing Grub to fail to be able to read the root file
> > system, I have to respectfully disagree. I do it all the time when I
> > reboot
On Mon, Jun 26, 2017 at 08:46:48AM +0200, Felipe A Rodriguez wrote:
> On Jun 26, 2017, at 4:40 AM, Theodore Ts'o wrote:
> > On Sun, Jun 25, 2017 at 08:16:39PM +0200, Felipe A Rodriguez wrote:
> >> Sysllinux chain-loading is not a factor (GRUB 2.00 still fails to
> >> boot w/o it). GRUB 2.02 does
On Jun 26, 2017, at 4:40 AM, Theodore Ts'o wrote:
> On Sun, Jun 25, 2017 at 08:16:39PM +0200, Felipe A Rodriguez wrote:
>>
>> Sysllinux chain-loading is not a factor (GRUB 2.00 still fails to
>> boot w/o it). GRUB 2.02 does resolve the issue. The command line
>> for 2.02 required a “-p” switch
On Sun, Jun 25, 2017 at 08:16:39PM +0200, Felipe A Rodriguez wrote:
>
> Sysllinux chain-loading is not a factor (GRUB 2.00 still fails to
> boot w/o it). GRUB 2.02 does resolve the issue. The command line
> for 2.02 required a “-p” switch which 2.00 does not. This probably
> caused an uncaught
On Jun 24, 2017, at 9:08 PM, Felipe A Rodriguez wrote:
> On Jun 23, 2017, at 11:29 PM, Christian Hesse wrote:
>
>> Theodore Ts'o on Fri, 2017/06/23 15:53:
>>> +grub-devel
>>>
>>> On Sat, Jun 10, 2017 at 04:00:20PM +0200, Felipe A Rodriguez wrote:
Upgrading from e2fsprogs-1.42.13 to e2fsp
