On Thu, Sep 23, 2021 at 08:59:14PM -0600, Chris Murphy wrote:
> On Wed, Jul 28, 2021 at 6:23 AM Daniel Kiper wrote:
> >
> > At this point I am not fully convinced the /boot/grub should be on
> > a separate filesystem. Though after going through this thread it seems
> > to me we should add full wri
On Wed, Jul 28, 2021 at 6:23 AM Daniel Kiper wrote:
>
> At this point I am not fully convinced the /boot/grub should be on
> a separate filesystem. Though after going through this thread it seems
> to me we should add full write support to the GRUB for a simple file
> system. The FAT looks like a
CC-ing a few folks who may be interested in this thread...
First of all, sorry for late reply but I am really busy. I hope I will
be able to reply in more timely manner starting from now.
On Thu, May 27, 2021 at 04:08:45PM -0600, Chris Murphy wrote:
> On Thu, May 27, 2021 at 2:59 AM Michael Chang
On Thu, May 27, 2021 at 03:49:14PM -0300, Luiz Angelo Daros de Luca wrote:
> This was already discussed in this ML a couple of times.
>
> It is not uncommon for some FS to have an unused header space. This
> happens for btrfs and SUSE patches grub2 to use it:
> https://build.opensuse.org/package/v
On Thu, May 27, 2021 at 12:49 PM Luiz Angelo Daros de Luca
wrote:
>
> My proposal would be an additional source for grubenv. SUSE still uses
> the FS /boot/grub2/grubenv to store a
> env_block variable (as well as other variables) that, if present, will
> point to where an additional grubenv shoul
On Thu, May 27, 2021 at 2:59 AM Michael Chang wrote:
>
> On Wed, May 26, 2021 at 08:36:05PM -0600, Chris Murphy wrote:
> > So is the next era going to be we recommend /boot on FAT?
>
> No. I meant a new partition type only for grubenv files and keep
> everything else as is. The filesystem can be e
This was already discussed in this ML a couple of times.
It is not uncommon for some FS to have an unused header space. This
happens for btrfs and SUSE patches grub2 to use it:
https://build.opensuse.org/package/view_file/openSUSE:Factory/grub2/grub2-grubenv-in-btrfs-header.patch?expand=1.
It is a
On Wed, May 26, 2021 at 08:36:05PM -0600, Chris Murphy wrote:
> On Wed, May 26, 2021 at 3:17 AM Michael Chang via Grub-devel
> wrote:
> >
> > On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
> > > Hi,
> > >
> > > It's not possible for GRUB pre-boot environment to write to grubenv
> >
On Wed, May 26, 2021 at 3:17 AM Michael Chang via Grub-devel
wrote:
>
> On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
> > Hi,
> >
> > It's not possible for GRUB pre-boot environment to write to grubenv
> > when it's on Btrfs, ZFS, LVM, mdadm raid, or LUKS. Also, at least XFS
> > up
On Wed, May 26, 2021 at 2:08 AM Konrad Rzeszutek Wilk
wrote:
>
> On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
> > Hi,
> >
> > It's not possible for GRUB pre-boot environment to write to grubenv
> > when it's on Btrfs, ZFS, LVM, mdadm raid, or LUKS. Also, at least XFS
> > upstream
On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
> Hi,
>
> It's not possible for GRUB pre-boot environment to write to grubenv
> when it's on Btrfs, ZFS, LVM, mdadm raid, or LUKS. Also, at least XFS
> upstream is super skeptical of anything except kernel code making any
> kind of modi
> On 26. May 2021, at 11:07, Konrad Rzeszutek Wilk
> wrote:
>
> On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
>> Hi,
>>
>> It's not possible for GRUB pre-boot environment to write to grubenv
>> when it's on Btrfs, ZFS, LVM, mdadm raid, or LUKS. Also, at least XFS
>> upstream i
On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
> Hi,
>
> It's not possible for GRUB pre-boot environment to write to grubenv
> when it's on Btrfs, ZFS, LVM, mdadm raid, or LUKS. Also, at least XFS
> upstream is super skeptical of anything except kernel code making any
> kind of modi
13 matches
Mail list logo
