:: Re: [DNG] Bad UEFI: was Systemd at …
Top Page
Delete this message
Reply to this message
Author: KatolaZ
Date:  
To: Simon Hobson
CC: dng@lists.dyne.org
Subject: Re: [DNG] Bad UEFI: was Systemd at work: rm -rf EFI
On Thu, Feb 04, 2016 at 10:02:51PM +0000, Simon Hobson wrote:
> Arnt Karlsen <arnt@???> wrote:
>
> > ..me, I do not see any point in keeping it mounted at all.
> > Whenever such a need arises, it should be mounted read-only.
> > If a need to write to /sys/firmware/efi/efivars should happen,
> > the machine should first be taken off-line, backed-up etc out
> > of production and into a maintenance mode, where mounting
> > /sys/firmware/efi/efivars read-write, _may_ be warranted.
>
>
> Yes, in an ideal world where everyone is a "full time admin". But in the real world, more systems are used by "average users" who just expect "stuff to work". So IMO, you either build stuff that works (or at least is up-front about what's wrong), or you leave these people stuck with "stuff that's broken" and regardless of how right you are, the pi**ed off user will be moaning about how "rubbish and complicated this Linux is - best go back to Windows".
>


I don't get why any of those occasional "sysadmin-wannabe" users you
have described above would ever need to mess around with their UEFI by
hand. If you need to do that, you should first *know* what you are
doing.

My2Cents

KatolaZ

--
[ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ]
[ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ]
[ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ]
[ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ]