public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] newsitem: openrc-0.28 mounts efivars read only
Date: Thu, 13 Jul 2017 08:52:23 -0500	[thread overview]
Message-ID: <20170713135223.GA31706@linux1.home> (raw)
In-Reply-To: <23f293f8-1fe9-7fee-d300-51796537d6ee@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

On Thu, Jul 13, 2017 at 12:30:12PM +0200, Kristian Fiskerstrand wrote:
> On 07/12/2017 05:42 PM, William Hubbs 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.
> 
> Although the changes seems sensible, I'm wondering if a news item is
> necessary for this case versus other documentation and script updates to
> reflect this change. For one thing it seems it will have minimal effect
> on a running system and not needing a migration path / configuration
> updates except in cases where bootloader installs are done; how
> intuitive is the feedback in this process when it is read-only?

I have no idea; I've never used an efi system.

For people who are not using efi systems, and as long as you don't mess
with your boot loader, you are correct that this change means nothing.
There is no migration path and nothing really for a user to do.

This is already documented in NEWS.md upstream and in the ChangeLog.

I can spin up the release in an hour or so, and if there is no need for a
newsitem, I will consider the newsitem canceled.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-07-13 13:52 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
2017-07-13 10:30 ` Kristian Fiskerstrand
2017-07-13 13:52   ` William Hubbs [this message]
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=20170713135223.GA31706@linux1.home \
    --to=williamh@gentoo.org \
    --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