<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Boot on systemd中文文档</title><link>http://systemd.cn/tags/boot/</link><description>Recent content in Boot on systemd中文文档</description><generator>Hugo</generator><language>zh</language><copyright>[© CC BY 4.0](https://creativecommons.org/licenses/by/4.0/legalcode)</copyright><atom:link href="http://systemd.cn/tags/boot/index.xml" rel="self" type="application/rss+xml"/><item><title>自动启动评估</title><link>http://systemd.cn/docs/Booting/AUTOMATIC_BOOT_ASSESSMENT/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://systemd.cn/docs/Booting/AUTOMATIC_BOOT_ASSESSMENT/</guid><description>&lt;h1 id="自动启动评估"&gt;自动启动评估&lt;a class="anchor" href="#%e8%87%aa%e5%8a%a8%e5%90%af%e5%8a%a8%e8%af%84%e4%bc%b0"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;systemd provides support for automatically reverting back to the previous
version of the OS or kernel in case the system consistently fails to boot. The
&lt;a href="https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting"&gt;UAPI.1 Boot Loader Specification&lt;/a&gt;
describes how to annotate boot loader entries with a counter that specifies how
many attempts should be made to boot it. This document describes how systemd
implements this scheme.&lt;/p&gt;
&lt;p&gt;The many different components involved in the implementation may be used
independently and in combination with other software to, for example, support
other boot loaders or take actions outside of the boot loader.&lt;/p&gt;</description></item><item><title>引导加载程序接口</title><link>http://systemd.cn/docs/Booting/BOOT_LOADER_INTERFACE/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://systemd.cn/docs/Booting/BOOT_LOADER_INTERFACE/</guid><description>&lt;h1 id="引导加载程序接口"&gt;引导加载程序接口&lt;a class="anchor" href="#%e5%bc%95%e5%af%bc%e5%8a%a0%e8%bd%bd%e7%a8%8b%e5%ba%8f%e6%8e%a5%e5%8f%a3"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;systemd can interface with the boot loader
to receive performance data and other information,
and pass control information.
This is only supported on EFI systems.
Data is transferred between the boot loader and systemd in EFI variables.
All EFI variables use the vendor UUID &lt;code&gt;4a67b082-0a4c-41cf-b6c7-440b29bb8c4f&lt;/code&gt;.
Variables will be listed below using the Linux efivarfs naming,
&lt;code&gt;&amp;lt;name&amp;gt;-&amp;lt;vendoruuid&amp;gt;&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;The EFI Variable &lt;code&gt;LoaderTimeInitUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f&lt;/code&gt;
contains the timestamp in microseconds when the loader was initialized.
This value is the time spent in the firmware for initialization.
It is formatted as numeric, NUL-terminated, decimal string, in UTF-16.&lt;/p&gt;</description></item><item><title>恢复出厂设置</title><link>http://systemd.cn/docs/Booting/FACTORY_RESET/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://systemd.cn/docs/Booting/FACTORY_RESET/</guid><description>&lt;h1 id="恢复出厂设置"&gt;恢复出厂设置&lt;a class="anchor" href="#%e6%81%a2%e5%a4%8d%e5%87%ba%e5%8e%82%e8%ae%be%e7%bd%ae"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;In various scenarios it is important to be able to reset operating systems back
into a &amp;ldquo;factory state&amp;rdquo;, i.e. where all state, user data and configuration is
reset so that it resembles the system state when it was originally shipped.&lt;/p&gt;
&lt;p&gt;systemd natively supports a concept of factory reset, that can both act as a
specific implementation for UEFI based systems, as well as a series of hook
points and a template for implementations on other systems.&lt;/p&gt;</description></item></channel></rss>