Attachment 5932 Details for Bug 34855

[patch] Suggested documentation changes

uefi_rollout.xml.patch (text/plain), 2.01 KB, created by Erik Damrose on 2014-06-02 14:28 CEST

(hide)

Description:

Filename:

MIME Type:

Creator: Erik Damrose

Created: 2014-06-02 14:28 CEST

Size: 2.01 KB

patch

obsolete

>--- rollout.xml.orig	2014-06-02 14:26:45.078713401 +0200
>+++ rollout.xml	2014-06-02 14:36:23.862704019 +0200
>@@ -322,15 +322,15 @@
> <section id="rollout:uefi">
>   <title>Rollout of UEFI systems</title>
>   <para>
>-	In the default setting, Univention Corporate Client uses a BIOS-based boot. Alternatively, for
>-	systems which no longer support a BIOS boot, there is the possibility of generating UCC images
>+	Univention Corporate Client uses a BIOS-based boot by default. Alternatively, for
>+	systems which no longer support a BIOS boot, it is possible to generate UCC images
> 	with which the rollout and operation can be performed via the <emphasis>Unified Extensible
> 	Firmware Interface</emphasis> standard.
>   </para>
> 
>   <para>
> 	Not all UEFI-compatible systems also support UEFI booting via PXE. This should be checked in
>-	advance and consideration given to updating the UEFI firmware.
>+	advance and consideration given to update the UEFI firmware.
>   </para>
> 
>   <para>
>@@ -340,16 +340,16 @@
>   </para>
> 
>   <para>
>-	As standard, the <filename>pxelinux.0</filename> boot loader is used for the rollout of BIOS-based
>-	systems and assigned in the &ucsUMC; via a <guimenu>DHCP Boot</guimenu> policy. A
>+	By default, the <filename>pxelinux.0</filename> boot loader is used for the rollout of BIOS-based
>+	systems and assigned in the &ucsUMC; via a <guimenu>DHCP Boot</guimenu> policy. An
> 	UEFI-compatible boot loader must be assigned via this type of policy for the UEFI
> 	rollout. <filename>syslinux.efi32</filename> must be assigned as the <guimenu>Boot
> 	filename</guimenu> for i386 systems and <filename>syslinux.efi64</filename> for amd64 systems.
>   </para>
> 	
>   <para>
>-	If a UEFI-compatible image has been generated and the DHCP boot policy defined, the rollout of
>-	a UEFI system is then no different from the standard rollout via the BIOS.
>+	If an UEFI-compatible image has been generated and the DHCP boot policy defined, the rollout of
>+	an UEFI system is no different from the standard rollout via the BIOS.
>   </para>
> </section>
>

Actions: View | Diff

Attachments on bug 34855: 5932