Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-17 Thread Rich Freeman
On Thu, Aug 17, 2017 at 3:09 PM, Marc Joliet wrote: > > I'm somewhat confused about the whole thing. Wasn't the core problem of > accidentally bricking devices solved by the kernel by making > a subset of EFI variables immutable? (Actaully, I found the commit, which > says that

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-17 Thread Marc Joliet
Am Dienstag, 15. August 2017, 22:02:19 CEST schrieb Mike Gilbert: > On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman wrote: > > On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: > >> I can't recall if I did this myself in a moment of security induced > >>

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-17 Thread Mick
On Thursday 17 Aug 2017 11:25:04 Mike Gilbert wrote: > On Thu, Aug 17, 2017 at 10:29 AM, Peter Humphrey wrote: > > On Tuesday 15 August 2017 22:12:41 Mick wrote: > >> On Tuesday 15 Aug 2017 16:02:19 Mike Gilbert wrote: > >> > On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-17 Thread Mike Gilbert
On Thu, Aug 17, 2017 at 10:29 AM, Peter Humphrey wrote: > On Tuesday 15 August 2017 22:12:41 Mick wrote: >> On Tuesday 15 Aug 2017 16:02:19 Mike Gilbert wrote: >> > On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman wrote: >> > > On Tue, Aug 15, 2017 at 11:04

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-17 Thread Peter Humphrey
On Tuesday 15 August 2017 22:12:41 Mick wrote: > On Tuesday 15 Aug 2017 16:02:19 Mike Gilbert wrote: > > On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman wrote: > > > On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: > > >> I can't recall if I did this

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-15 Thread Mick
On Tuesday 15 Aug 2017 16:02:19 Mike Gilbert wrote: > On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman wrote: > > On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: > >> I can't recall if I did this myself in a moment of security induced > >> inspiration. I

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-15 Thread Mike Gilbert
On Tue, Aug 15, 2017 at 2:17 PM, Rich Freeman wrote: > On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: >> >> I can't recall if I did this myself in a moment of security induced >> inspiration. I doubt I did. So how did this happen? What is

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-15 Thread J. Roeleveld
On 15 August 2017 20:17:20 GMT+02:00, Rich Freeman wrote: >On Tue, Aug 15, 2017 at 11:04 AM, Mick >wrote: >> >> I can't recall if I did this myself in a moment of security induced >> inspiration. I doubt I did. So how did this happen? What is

Re: [gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-15 Thread Rich Freeman
On Tue, Aug 15, 2017 at 11:04 AM, Mick wrote: > > I can't recall if I did this myself in a moment of security induced > inspiration. I doubt I did. So how did this happen? What is responsible for > mounting this fs? > It looks like this never did turn into a news

[gentoo-user] efibootmgr "Could not prepare Boot variable: Read-only file system"

2017-08-15 Thread Mick
After some years of trouble free UEFI use on a PC with a Kaveri APU, I've suddenly come across a problem of incorrectly mounted efivarfs. I realised something was amiss when I tried to set up a new kernel I had just copied into /boot/EFI/BOOT/ # tree /boot /boot ├── 42GHz2400MHz.CMO └── EFI