<div dir="ltr">This is an important lesson for me. I will be more respectful of /sys on my Linux systems from now on.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 2, 2016 at 2:55 PM, Dan Astoorian <span dir="ltr"><<a href="mailto:djast@ecf.utoronto.ca" target="_blank">djast@ecf.utoronto.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, 02 Feb 2016 14:40:48 EST, arocker@Vex.Net writes:<br>
><br>
> That seems a very clear description; thanks, Dan.<br>
<br>
</span>Thank you.<br>
<span class=""><br>
> Is there an original to cite?<br>
<br>
</span>The article on <a href="http://www.theregister.co.uk" rel="noreferrer" target="_blank">www.theregister.co.uk</a> that you linked to, which said:<br>
<br>
The directory in question is /sys/firmware/efi/efivars which is a<br>
special filesystem that presents the configuration settings for the<br>
computer's underlying UEFI firmware to the user.<br>
<br>
as well as the comments in the GitHub ticket referenced therein at:<br>
<br>
<a href="https://github.com/systemd/systemd/issues/2402" rel="noreferrer" target="_blank">https://github.com/systemd/systemd/issues/2402</a><br>
<br>
Particularly illuminating is the comment at:<br>
<br>
<a href="https://github.com/systemd/systemd/issues/2402#issuecomment-176806817" rel="noreferrer" target="_blank">https://github.com/systemd/systemd/issues/2402#issuecomment-176806817</a><br>
<br>
Regards,<br>
<span class="im HOEnZb"><br>
--<br>
Dan Astoorian, Systems Administrator<br>
Engineering Computing Facility<br>
University of Toronto<br>
</span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
u-u mailing list<br>
<a href="mailto:u-u@unixunanimous.org">u-u@unixunanimous.org</a><br>
<a href="https://unixunanimous.org/mailman/listinfo/u-u" rel="noreferrer" target="_blank">https://unixunanimous.org/mailman/listinfo/u-u</a><br>
</div></div></blockquote></div><br></div>