So read/write efi is needed to set what happens when the computer boots and to see what state it was/is (relating to boot stuff). To see the state you don't ne

So read/write efi is needed to set what happens when the computer boots and to see what state it was/is (relating to boot stuff). To see the state you don't need write permission, obviously. When things are set, they are set by a few very specialized tools. Those are the facts everybody can agree on, right ? Can we also agree that mounting and unmounting the efi filesystem is really easy ? I assume it can be mounted on multiple points. So is there a problem in re/mounting it read/write only when needed ? >At the time this issue was raised, nobody knew shit. We had no idea that removing certain variables might prevent a machine from booting. If we had done, I'd have written the filesystem differently. That's the difference between systemd devs and people capable of critical thinking. You'r a good programmer, if you ask me. (edit: just to be clear, i don't see you as a systemd dev; even if you are (idk), you are not the one making high level design decisions (of which this is, kind of, one))