summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2006-12-24 18:31:28 +0000
committerFrans Pop <elendil@planet.nl>2006-12-24 18:31:28 +0000
commit2fcceb9fbc18f4c7cb9af626aa1f3389d0e1fe1c (patch)
treeba535c719a2b76a11b4d885d5db4bf34c43cfe00
parent2e6662a39d68206a857b20862ff402e45025b23f (diff)
downloadinstallation-guide-2fcceb9fbc18f4c7cb9af626aa1f3389d0e1fe1c.zip
Clarify what happens on first boot and how to get help to in case of problems
-rw-r--r--debian/changelog4
-rw-r--r--en/boot-new/boot-new.xml46
2 files changed, 40 insertions, 10 deletions
diff --git a/debian/changelog b/debian/changelog
index 03f7e37cb..5f0abfeb3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -102,8 +102,10 @@ installation-guide (2006xxxx) UNRELEASED; urgency=low
- As lynx is no longer installed, suggest w3m as text based browser.
- Explain how to browse /usr/share/doc/ using a graphical web browser.
- Mention documentation packages.
+ - Clarify what happens on first boot and how to get help to in case of
+ problems.
- -- Frans Pop <fjp@debian.org> Sun, 24 Dec 2006 17:38:21 +0100
+ -- Frans Pop <fjp@debian.org> Sun, 24 Dec 2006 19:28:55 +0100
installation-guide (20060726) unstable; urgency=low
diff --git a/en/boot-new/boot-new.xml b/en/boot-new/boot-new.xml
index 402523655..dd1a2f2b2 100644
--- a/en/boot-new/boot-new.xml
+++ b/en/boot-new/boot-new.xml
@@ -10,17 +10,45 @@
Your system's first boot on its own power is what electrical engineers
call the <quote>smoke test</quote>.
+</para><para arch="x86">
+
+If you did a default installation, the first thing you should see when you
+boot the system is the menu of the <classname>grub</classname> or possibly
+the <classname>lilo</classname> bootloader.
+The first choices in the menu will be for your new Debian system. If you
+had any other operating systems on your computer (like Windows) that were
+detected by the installation system, those will be listed lower down in the
+menu.
+
+</para><para>
+
+If the system fails to start up correctly, don't panic. If the installation
+was successful, chances are good that there is only a relatively minor
+problem that is preventing the system from booting Debian. In most cases
+such problems can be fixed without having to repeat the installation.
+One available option to fix boot problems is to use the installer's
+built-in rescue mode (see <xref linkend="rescue"/>).
+
</para><para>
-If you are booting directly into Debian, and the system doesn't start
-up, either use your original installation boot media, or insert the
-custom boot floppy if you have one, and reset your system. This way,
-you will probably need to add some boot arguments like
-<userinput>root=<replaceable>root</replaceable></userinput>, where
-<replaceable>root</replaceable> is your root partition, such as
-<filename>/dev/sda1</filename>.
-Alternatively, see <xref linkend="rescue"/> for instructions on using
-the installer's built-in rescue mode.
+If you are new to Debian and Linux, you may need some help from more
+experienced users.
+<phrase arch="x86">For direct on-line help you can try the IRC channels
+#debian or #debian-boot on the OFTC network. Alternatively you can contact
+the <ulink url="&url-list-subscribe;">debian-user mailing list</ulink>.</phrase>
+<phrase arch="not-x86">For less common architectures like &arch-title;,
+your best option is to ask on the
+<ulink url="&url-list-subscribe;">debian-&arch-listname; mailing
+list</ulink>.</phrase>
+You can also file an installation report as described in
+<xref linkend="submit-bug"/>. Please make sure that you describe your problem
+clearly and include any messages that are displayed and may help others to
+diagnose the issue.
+
+</para><para arch="x86">
+
+If you had any other operating systems on your computer that were not detected
+or not detected correctly, please file an installation report.
</para>