[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Grub get and set efi variables
From: |
Andrei Borzenkov |
Subject: |
Re: Grub get and set efi variables |
Date: |
Wed, 2 Dec 2015 16:00:57 +0300 |
On Wed, Dec 2, 2015 at 3:53 PM, Ignat Korchagin <address@hidden> wrote:
> Let's add utf16 later then (if needed). I also noticed a typo in one
> error string in my above patch (it was checking that command receives
> one argument, but prints that two arguments expected), so here is the
> updated one.
>
It is much more difficult to remove anything than to add it later.
Unless we have use case right now, I'd skip it.
> So, finally, should I remove the "raw" parser (as per Vladimir's
> request). Personally, I would keep it. It might be useful to modify
> the hexdump command, that it can dump the contents of a variable. Then
> those pieces will fit together: storing raw value in the variable and
> examining it with hexdump cmd.
>
hexdump does not support showing variable if that is what you mean. By
the same logic, unless we have current use case we probably should not
add it initially.
- Re: Grub get and set efi variables, Ignat Korchagin, 2015/12/02
- Re: Grub get and set efi variables,
Andrei Borzenkov <=
- Re: Grub get and set efi variables, Vladimir 'phcoder' Serbinenko, 2015/12/02
- Re: Grub get and set efi variables, Ignat Korchagin, 2015/12/02
- Re: Grub get and set efi variables, Andrei Borzenkov, 2015/12/03
- Re: Grub get and set efi variables, Ignat Korchagin, 2015/12/03
- Re: Grub get and set efi variables, Ignat Korchagin, 2015/12/09
- Re: Grub get and set efi variables, Andrei Borzenkov, 2015/12/12
- Re: Grub get and set efi variables, Ignat Korchagin, 2015/12/14
- Re: Grub get and set efi variables, Ignat Korchagin, 2015/12/14