| 1 |
On Thu, Jul 13, 2017 at 12:30:12PM +0200, Kristian Fiskerstrand wrote: |
| 2 |
> On 07/12/2017 05:42 PM, William Hubbs wrote: |
| 3 |
> > OpenRC 0.28 will mount efivars read only by default due to concerns |
| 4 |
> > about users bricking systems by writing to this filesystem unexpectedly. |
| 5 |
> > |
| 6 |
> > Here is the newsitem covering this change. |
| 7 |
> |
| 8 |
> Although the changes seems sensible, I'm wondering if a news item is |
| 9 |
> necessary for this case versus other documentation and script updates to |
| 10 |
> reflect this change. For one thing it seems it will have minimal effect |
| 11 |
> on a running system and not needing a migration path / configuration |
| 12 |
> updates except in cases where bootloader installs are done; how |
| 13 |
> intuitive is the feedback in this process when it is read-only? |
| 14 |
|
| 15 |
I have no idea; I've never used an efi system. |
| 16 |
|
| 17 |
For people who are not using efi systems, and as long as you don't mess |
| 18 |
with your boot loader, you are correct that this change means nothing. |
| 19 |
There is no migration path and nothing really for a user to do. |
| 20 |
|
| 21 |
This is already documented in NEWS.md upstream and in the ChangeLog. |
| 22 |
|
| 23 |
I can spin up the release in an hour or so, and if there is no need for a |
| 24 |
newsitem, I will consider the newsitem canceled. |
| 25 |
|
| 26 |
William |
Archives