From: Lucas Ramage <ramage.lucas94@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] newsitem: openrc-0.28 mounts efivars read only
Date: Fri, 14 Jul 2017 11:02:35 +0000 [thread overview]
Message-ID: <CAKkjsY-=8xGZt_HciKwrNoDspF3ATW6MjSyqwkEf-gL+cL-FMA@mail.gmail.com> (raw)
In-Reply-To: <a0025ab4-2073-ebd4-ea11-abae9bc6e2e7@verfeiert.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
The documentation is being updated. There is no need to worry about that.
On Thu, Jul 13, 2017, 8:09 PM DarKRaveR <dark@verfeiert.org> wrote:
> Am 12.07.2017 um 22:03 schrieb Mike Gilbert:
> > On Wed, Jul 12, 2017 at 11:42 AM, William Hubbs <williamh@gentoo.org>
> wrote:
> >> OpenRC 0.28 will mount efivars read only by default due to concerns
> >> about users bricking systems by writing to this filesystem unexpectedly.
> >>
> >> Here is the newsitem covering this change.
> >>
> >> William
> >>
> > This will break boot loader installers, like grub-install and bootctl
> > (systemd-boot). Please update any relevant documents on the wiki, or
> > find someone who can do it for you.
> >
>
> Not only bootloader installers.
> It will break things like efibootmgr which can be used to change EFI
> bootmanager's behavior/configuration.
> I am not sure how sane these tools react when efivar is RO.
>
> Regards
>
> -Sven
>
>
[-- Attachment #2: Type: text/html, Size: 1358 bytes --]
next prev parent reply other threads:[~2017-07-14 11:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 15:42 [gentoo-dev] newsitem: openrc-0.28 mounts efivars read only William Hubbs
2017-07-12 15:50 ` M. J. Everitt
2017-07-12 20:03 ` Mike Gilbert
2017-07-12 21:44 ` William Hubbs
2017-07-12 23:04 ` Matt Turner
2017-07-13 0:29 ` Lucas Ramage
2017-07-13 0:42 ` Matt Turner
2017-07-13 1:27 ` Lucas Ramage
2017-07-13 6:30 ` Andrew Savchenko
2017-07-13 11:09 ` Rich Freeman
2017-07-13 11:35 ` M. J. Everitt
2017-07-13 12:17 ` Andrew Savchenko
2017-07-13 14:29 ` Mike Gilbert
2017-07-13 14:35 ` Ben Kohler
2017-07-13 14:58 ` Andrew Savchenko
2017-07-13 15:06 ` Andrew Savchenko
2017-07-13 15:40 ` Rich Freeman
2017-07-13 16:45 ` Mike Gilbert
2017-07-13 16:47 ` Mike Gilbert
2017-07-13 11:43 ` Andrew Savchenko
2017-07-13 11:54 ` Rich Freeman
2017-07-13 12:14 ` Andrew Savchenko
2017-07-13 12:45 ` Rich Freeman
2017-07-13 2:38 ` Mike Gilbert
2017-07-14 0:09 ` DarKRaveR
2017-07-14 11:02 ` Lucas Ramage [this message]
2017-07-13 10:30 ` Kristian Fiskerstrand
2017-07-13 13:52 ` William Hubbs
2017-07-13 23:30 ` William Hubbs
[not found] ` <CAJ0EP434FLFWQCTTqNr16oij=VfYem4ARr+C_-9NoQPBucWKmw@mail.gmail.com>
2017-07-14 0:05 ` Mike Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKkjsY-=8xGZt_HciKwrNoDspF3ATW6MjSyqwkEf-gL+cL-FMA@mail.gmail.com' \
--to=ramage.lucas94@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox