mirror of https://github.com/tLDP/LDP
Removed excess <para> tags.
This commit is contained in:
parent
db87dea01c
commit
7aed525d8b
|
@ -14,11 +14,7 @@ initrd is mainly designed to allow system startup to occur
|
|||
in two phases, where the kernel comes up with a minimum set
|
||||
of compiled-in drivers, and where additional modules are
|
||||
loaded from initrd.
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
Operation
|
||||
---------
|
||||
|
||||
|
@ -42,11 +38,7 @@ Note that changing the root directory does not involve unmounting
|
|||
it. It is therefore possible to leave processes running on initrd
|
||||
during that procedure. Also note that file systems mounted under
|
||||
initrd continue to be accessible.
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
Usage scenarios
|
||||
---------------
|
||||
|
||||
|
@ -78,11 +70,7 @@ The procedure would work as follows:
|
|||
The key role of initrd here is to re-use the configuration data
|
||||
during normal system operation without requiring the use of a
|
||||
bloated "generic" kernel or re-compiling or re-linking the kernel.
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
A second scenario is for installations where Linux runs on systems
|
||||
with different hardware configurations in a single administrative
|
||||
domain. In such cases, it is desirable to generate only a small set
|
||||
|
|
Loading…
Reference in New Issue