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: [gentoo-dev] newsitem: openrc-0.28 mounts efivars read only
Date: Wed, 12 Jul 2017 10:42:36 -0500	[thread overview]
Message-ID: <20170712154236.GA10286@whubbs1.gaikai.biz> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 195 bytes --]

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


[-- Attachment #1.2: 2017-07-15-efivars_readonly.en.txt --]
[-- Type: text/plain, Size: 668 bytes --]

Title: Mounting efivars read only
Author: William Hubbs <williamh@gentoo.org>
Content-Type: text/plain
Posted: 2017-07-15
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <=sys-apps/openrc-0.28

OpenRC 0.28 mounts efivars read only due to concerns about changes in
this file system making systems unbootable.  If you need to change something
in this path, you will need to re-mount it read-write, make the change
and re-mount it read-only.

Also, you can override this behavior by adding a line for efivars to
fstab if you want efivars mounted read-write.

For more information on this issue, see the following url:

https://github.com/openrc/openrc/issues/134

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

             reply	other threads:[~2017-07-12 15:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 15:42 William Hubbs [this message]
2017-07-12 15:50 ` [gentoo-dev] newsitem: openrc-0.28 mounts efivars read only 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
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=20170712154236.GA10286@whubbs1.gaikai.biz \
    --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