| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
stub/sysext: pick up confexts from ESP, too
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This does what we do for system extension also for configuration
extension.
This is complicated by the fact that we previously looked for
<uki-binary>.d/*.raw for system extensions. We want to measure sysexts
and confexts to different PCRs (13 vs. 12) hence we must distinguish
them, but *.raw would match both kinds.
This commit solves this via the following mechanism: we'll load confexts
from *.confext.raw and sysexts from *.raw but will then enclude
*.confext.raw from the latter. This preserves compatibility but allows
us to somewhat reasonable distinguish both types of images.
The documentation is updated not going into this detail though, and
instead now claims that sysexts shall be *.sysext.raw and confexts
*.confext.raw even though we actually are more lenient than this. This
is simply to push people towards using the longer, more descriptive
suffixes.
I added an XML comment (<!-- … -->) about this to the docs, so that
whenever somebody notices the difference between code and docs
understands why and leaves it that way.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Distributions apparently only compile a subset of TPM2 drivers into the
kernel. For those not compiled it but provided as kmod we need a
synchronization point: we must wait before the first TPM2 interaction
until the driver is available and accessible.
This adds a tpm2.target unit as such a synchronization point. It's
ordered after /dev/tpmrm0, and is pulled in by a generator whenever we
detect that the kernel reported a TPM2 to exist but we have no device
for it yet.
This should solve the issue, but might create problems: if there are TPM
devices supported by firmware that we don't have Linux drivers for we'll
hang for a bit. Hence let's add a kernel cmdline switch to disable (or
alternatively force) this logic.
Fixes: #30164
|
|
|
|
| |
Closes #30507.
|
|
|
|
|
|
| |
This effectively reverts 9b88f20aba6a78baf18d89e99ff31d5ee40856b8.
We do not support MPLS routes, only IPv4 or IPv6 routes are supported.
|
| |
|
| |
|
|
|
|
| |
<arg> is not allowed inside <title>.
|
| |
|
|
|
|
| |
Inline text is not allowed.
|
|
|
|
| |
<option> is not allowed in <cmdsynopsis>.
|
| |
|
|
|
|
| |
<funcsynopsis> doesn't allow block content.
|
|
|
|
| |
<arg> is not allowed inside <term>.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
DocBook validation fixes (part 2)
|
| |
| |
| |
| |
| |
| |
| |
| | |
DocBook document model doesn't allow mixing of <refsection> with the
numbered variants (<refsect1> etc.). Therefore, any document that
included something from standard-conf.xml was invalid. Fortunately, all
the includes are at the 1st level, hence let's just change
standard-conf.xml to use <refsect1> to fix that.
|
| |
| |
| |
| | |
Follow-up for 13a69c120bc584e90f863f821710b3b5294cd206 .
|
| |
| |
| |
| | |
<funcsynopsis> doesn't allow block content.
|
| | |
|
| |
| |
| |
| | |
<arg> is not allowed inside <title>.
|
| |
| |
| |
| | |
<arg> is not allowed inside <title>.
|
| |
| |
| |
| |
| |
| | |
The id attribute is of type ID, defined at
https://www.w3.org/TR/1998/REC-xml-19980210#id . It may contain only
selected non-alphanumeric characters; '@' is not among them.
|
| |
| |
| |
| | |
DocBook's document model doesn't allow block content after a section.
|
| |
| |
| |
| |
| | |
<cmdsynopsis> doesn't allow inline content, like the redir. operator
here. And std. output is not an argument anyway...
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
DocBook validation fixes (part 1)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
<varlistentry> allows one or more <term>s, but exactly one <listitem>.
|
| |
| |
| |
| |
| | |
Unfortunately, version-info includes and standard-options includes are
not composable...
|
| | |
|
| | |
|
| | |
|
| | |
|