diff options
| author | Frans Pop <elendil@planet.nl> | 2006-12-25 20:08:46 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-12-25 20:08:46 +0000 |
| commit | 7b45786a24ade38b26b02b5c0ce612a890d10b50 (patch) | |
| tree | b90cb7f5143bfadcd464a8b0550c651ebe67b94e /en | |
| parent | 62110794711177d6581d5bf3f81cb41c2d74d6c3 (diff) | |
| download | installation-guide-7b45786a24ade38b26b02b5c0ce612a890d10b50.zip | |
-Fix broken closing tag
- Remove references to deleted sections
Diffstat (limited to 'en')
| -rw-r--r-- | en/boot-installer/trouble.xml | 2 | ||||
| -rw-r--r-- | en/preparing/pre-install-bios-setup.xml | 11 | ||||
| -rw-r--r-- | en/using-d-i/modules/x86/lilo-installer.xml | 3 |
3 files changed, 2 insertions, 14 deletions
diff --git a/en/boot-installer/trouble.xml b/en/boot-installer/trouble.xml index d9abbe447..9fa9b6e10 100644 --- a/en/boot-installer/trouble.xml +++ b/en/boot-installer/trouble.xml @@ -414,7 +414,7 @@ custom kernel later (see <xref linkend="kernel-baking"/>). <para> If you get through the initial boot phase but cannot complete the install, -the menu option <guimenuitem>Save debug logs<guimenuitem> may be helpful. +the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml index 03be8cd7b..224b66f8f 100644 --- a/en/preparing/pre-install-bios-setup.xml +++ b/en/preparing/pre-install-bios-setup.xml @@ -56,17 +56,6 @@ FIXME: more description of this needed. </para><para arch="x86"> -The very best motherboards support parity RAM and will actually tell -you if your system has a single-bit error in RAM. Unfortunately, they -don't have a way to fix the error, thus they generally crash -immediately after they tell you about the bad RAM. Still, it's better -to be told you have bad memory than to have it silently insert errors -in your data. Thus, the best systems have motherboards that support -parity and true-parity memory modules; see -<xref linkend="Parity-RAM"/>. - -</para><para arch="x86"> - If you do have true-parity RAM and your motherboard can handle it, be sure to enable any BIOS settings that cause the motherboard to interrupt on memory parity errors. diff --git a/en/using-d-i/modules/x86/lilo-installer.xml b/en/using-d-i/modules/x86/lilo-installer.xml index 9b2ead402..87053e2bf 100644 --- a/en/using-d-i/modules/x86/lilo-installer.xml +++ b/en/using-d-i/modules/x86/lilo-installer.xml @@ -63,8 +63,7 @@ If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use -some other way to get back into Debian! For more information on this -please read <xref linkend="reactivating-win"/>. +some other way to get back into Debian! </para> </sect3> |