move manual to top-level directory, split out of debian-installer package

8 files changed, 858 insertions, 0 deletions

diff --git a/da/boot-new/boot-new.xml b/da/boot-new/boot-new.xml
new file mode 100644
index 000000000..651c27f70
--- /dev/null
+++ b/da/boot-new/boot-new.xml
@@ -0,0 +1,290 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 21672 untranslated -->
+
+<chapter id="boot-new">
+ <title>Booting Into Your New Debian System</title>
+
+ <sect1 id="base-boot"><title>The Moment of Truth</title>
+<para>
+
+Your system's first boot on its own power is what electrical engineers
+call the <quote>smoke test</quote>.
+
+</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>.
+
+</para>
+
+  <sect2 arch="m68k"><title>BVME 6000 Booting</title>
+<para>
+
+If you have just performed a diskless install on a BVM or Motorola
+VMEbus machine: once the system has loaded the
+<command>tftplilo</command> program from the TFTP server, from the
+<prompt>LILO Boot:</prompt> prompt enter one of:
+
+<itemizedlist>
+<listitem><para>
+
+<userinput>b6000</userinput> followed by &enterkey;
+to boot a BVME 4000/6000
+
+</para></listitem><listitem><para>
+
+<userinput>b162</userinput> followed by &enterkey;
+to boot an MVME162
+
+</para></listitem><listitem><para>
+
+<userinput>b167</userinput> followed by &enterkey;
+to boot an MVME166/167
+
+</para></listitem>
+</itemizedlist>
+
+</para>
+
+   </sect2>
+
+  <sect2 arch="m68k"><title>Macintosh Booting</title>
+
+<para>
+
+Go to the directory containing the installation files and start up the
+<command>Penguin</command> booter, holding down the
+<keycap>command</keycap> key.  Go to the
+<userinput>Settings</userinput> dialogue (<keycombo>
+<keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate
+the kernel options line which should look like
+<userinput>root=/dev/ram video=font:VGA8x16</userinput> or similar.
+
+</para><para>
+
+You need to change the entry to
+<userinput>root=/dev/<replaceable>yyyy</replaceable></userinput>.
+Replace the <replaceable>yyyy</replaceable> with the Linux name of the
+partition onto which you installed the system
+(e.g. <filename>/dev/sda1</filename>); you wrote this down earlier.
+The <userinput>video=font:VGA8x8</userinput> is recommended especially
+for users with tiny screens. The kernel would pick a prettier (6x11)
+font but the console driver for this font can hang the machine, so
+using 8x16 or 8x8 is safer at this stage.  You can change this at any
+time.
+
+</para><para>
+
+If you don't want to start GNU/Linux immediately each time you start,
+uncheck the <userinput>Auto Boot</userinput> option. Save your
+settings in the <filename>Prefs</filename> file using the
+<userinput>Save Settings As Default</userinput> option.
+
+</para><para>
+
+Now select <userinput>Boot Now</userinput> (<keycombo>
+<keycap>command</keycap> <keycap>B</keycap> </keycombo>) to start your
+freshly installed GNU/Linux instead of the RAMdisk installer system.
+
+</para><para>
+
+Debian should boot, and you should see the same messages as
+when you first booted the installation system, followed by some new
+messages. 
+
+</para>
+   </sect2>
+
+
+  <sect2 arch="powerpc"><title>OldWorld PowerMacs</title>
+<para>
+
+If the machine fails to boot after completing the installation, and
+stops with a <prompt>boot:</prompt> prompt, try typing
+<userinput>Linux</userinput> followed by &enterkey;. (The default boot
+configuration in <filename>quik.conf</filename> is labeled Linux). The
+labels defined in <filename>quik.conf</filename> will be displayed if
+you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt>
+prompt. You can also try booting back into the installer, and editing
+the <filename>/target/etc/quik.conf</filename> placed there by the
+<guimenuitem>Install <command>Quik</command> on a Hard
+Disk</guimenuitem> step. Clues for dealing with
+<command>quik</command> are available at <ulink
+url="&url-powerpc-quik-faq;"></ulink>.
+
+</para><para>
+
+To boot back into MacOS without resetting the nvram, type
+<userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS
+has not been removed from the machine). To obtain an OpenFirmware
+prompt, hold down the <keycombo> <keycap>command</keycap>
+<keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap>
+</keycombo> keys while cold booting the machine. If you need to reset
+the OpenFirmware nvram changes to the MacOS default in order to boot
+back to MacOS, hold down the <keycombo> <keycap>command</keycap>
+<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap>
+</keycombo> keys while cold booting the machine.
+
+</para><para>
+
+If you use <command>BootX</command> to boot into the installed system,
+just select your desired kernel in the <filename>Linux
+Kernels</filename> folder, un-choose the ramdisk option, and add
+a root device corresponding to your installation;
+e.g. <userinput>/dev/hda8</userinput>.
+
+</para>
+   </sect2>
+
+
+  <sect2 arch="powerpc"><title>NewWorld PowerMacs</title>
+<para>
+
+On G4 machines and iBooks, you can hold down the
+<keycap>option</keycap> key and get a graphical screen with a button
+for each bootable OS, &debian; will be a button with a small penguin
+icon.
+
+</para><para>
+
+If you kept MacOS and at some point it changes the OpenFirmware
+<envar>boot-device</envar> variable you should reset OpenFirmware to
+its default configuration.  To do this hold down the <keycombo>
+<keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap>
+<keycap>r</keycap> </keycombo> keys while cold booting the machine.
+
+</para><para>
+
+The labels defined in <filename>yaboot.conf</filename> will be
+displayed if you press the <keycap>Tab</keycap> key at the
+<prompt>boot:</prompt> prompt.
+
+</para><para>
+
+Resetting OpenFirmware on G3 or G4 hardware will cause it to boot
+&debian; by default (if you correctly partitioned and placed the
+Apple_Bootstrap partition first).  If you have &debian; on a SCSI disk
+and MacOS on an IDE disk this may not work and you will have to enter
+OpenFirmware and set the <envar>boot-device</envar> variable,
+<command>ybin</command> normally does this automatically.
+
+</para><para>
+
+After you boot &debian; for the first time you can add any additional
+options you desire (such as dual boot options) to
+<filename>/etc/yaboot.conf</filename> and run <command>ybin</command>
+to update your boot partition with the changed configuration.  Please
+read the <ulink url="&url-powerpc-yaboot-faq;">yaboot HOWTO</ulink>
+for more information.
+
+</para>
+   </sect2>
+ </sect1>
+
+ <sect1 id="base-config">
+ <title>Debian Post-Boot (Base) Configuration</title>
+
+<para>
+
+After booting, you will be prompted to complete the configuration of
+your basic system, and then to select what additional packages you
+wish to install.  The application which guides you through this
+process is called <classname>base-config</classname>. Its concept is
+very similar to the &d-i; from the first stage.  Indeed,
+<classname>base-config</classname> consists of a number of specialized
+components, where each component handles one configuration task,
+contains <quote>hidden menu in the background</quote> and also uses
+the same navigation system.
+
+</para><para>
+
+If you wish to re-run the <classname>base-config</classname> at any
+point after installation is complete, as root run
+<userinput>base-config</userinput>.
+
+</para>
+
+&module-bc-timezone.xml;
+&module-bc-shadow.xml;
+&module-bc-ppp.xml;
+&module-bc-apt.xml;
+&module-bc-packages.xml;
+&module-bc-install.xml;
+&module-bc-mta.xml;
+
+ </sect1>
+
+ <sect1 id="login">
+ <title>Log In</title>
+
+<para>
+
+After you've installed packages, you'll be presented with the login
+prompt.  Log in using the personal login and password you
+selected. Your system is now ready to use.
+
+</para><para>
+
+If you are a new user, you may want to explore the documentation which
+is already installed on your system as you start to use it. There are
+currently several documentation systems, work is proceeding on
+integrating the different types of documentation. Here are a few
+starting points.
+
+</para><para>
+
+Documentation accompanying programs you have installed is in
+<filename>/usr/share/doc/</filename>, under a subdirectory named after
+the program.  For example, the APT User's Guide for using
+<command>apt</command> to install other programs on your system, is
+located in
+<filename>/usr/share/doc/apt/guide.html/index.html</filename>.
+
+</para><para>
+
+ 
+In addition, there are some special folders within the
+<filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are
+installed in <emphasis>.gz</emphasis> format, in
+<filename>/usr/share/doc/HOWTO/en-txt/</filename> and
+<filename>/usr/share/doc/HOWTO/en-txt/mini/</filename>. The
+<filename>/usr/share/doc/HTML/index.html</filename> contains
+browse-able indexes of documentation installed by
+<command>dhelp</command>.
+
+</para><para>
+
+One easy way to view these documents is to <userinput>cd
+/usr/share/doc/</userinput>, and type <userinput>lynx</userinput>
+followed by a space and a dot (the dot stands for the current
+directory).
+
+</para><para>
+
+You can also type <userinput>info
+<replaceable>command</replaceable></userinput> or <userinput>man
+<replaceable>command</replaceable></userinput> to see documentation on
+most commands available at the command prompt. Typing
+<userinput>help</userinput> will display help on shell commands. And
+typing a command followed by <userinput>--help</userinput> will
+usually display a short summary of the command's usage. If a command's
+results scroll past the top of the screen, type <userinput>|
+more</userinput> after the command to cause the results to pause
+before scrolling past the top of the screen. To see a list of all
+commands available which begin with a certain letter, type the letter
+and then two tabs.
+
+</para><para>
+
+For a more complete introduction to Debian and GNU/Linux, see
+<filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>.
+
+</para>
+
+ </sect1>
+</chapter>
diff --git a/da/boot-new/modules/apt.xml b/da/boot-new/modules/apt.xml
new file mode 100644
index 000000000..12d2a208b
--- /dev/null
+++ b/da/boot-new/modules/apt.xml
@@ -0,0 +1,97 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 18642 untranslated -->
+
+ <sect2 id="configure-apt">
+ <title>Configuring APT</title>
+
+<para>
+
+The main means that people use to install packages on their system is
+via a program called <command>apt-get</command>, from the
+<classname>apt</classname> package.<footnote>
+
+<para>
+
+Note that the actual program that installs packages is called
+<command>dpkg</command>.  However, this package is more of a low-level
+tool.  <command>apt-get</command> will invoke <command>dpkg</command>
+as appropriate; it is a higher-level too, however, because it knows to
+install other packages which are required for the package you're
+trying to install, as well as how to retrieve the package from your
+CD, the network, or wherever.
+
+</para>
+</footnote>
+
+APT must be configured, however, so that it knows where to retrieve
+packages from.  The helper application which assists in this task is
+called <command>apt-setup</command>.
+
+</para><para>
+
+The next step in your configuration process is to tell APT where other
+Debian packages can be found.  Note that you can re-run this tool at
+any point after installation by running <command>apt-setup</command>,
+or by manually editing <filename>/etc/apt/sources.list</filename>.
+
+</para><para>
+
+If an official CD-ROM is in the drive at this point, then that CD-ROM
+should automatically be configured as an apt source without prompting.
+You will notice this because you will see the CD-ROM being scanned.
+
+</para><para>
+
+For users without an official CD-ROM, you will be offered an array of
+choices for how Debian packages are accessed: FTP, HTTP, CD-ROM, or
+a local file system.
+
+</para><para>
+
+You should know that it's perfectly acceptable to have a number of
+different APT sources, even for the same Debian archive.
+<command>apt-get</command> will automatically pick the package with
+the highest version number given all the available versions.  Or, for
+instance, if you have both an HTTP and a CD-ROM APT source,
+<command>apt-get</command> should automatically use the local CD-ROM
+when possible, and only resort to HTTP if a newer version is available
+there.  However, it is not a good idea to add unnecessary APT sources,
+since this will tend to slow down the process of checking the network
+archives for new versions.
+
+</para>
+
+  <sect3 id="configure-apt-net">
+  <title>Configuring Network Package Sources</title>
+
+<para>
+
+If you plan on installing the rest of your system via the network, the
+most common option is to select the <userinput>http</userinput>
+source.  The <userinput>ftp</userinput> source is also acceptable, but
+tends to be a little slower making connections.
+
+</para><para>
+
+The next step during the configuration of network packages sources is
+to tell <command>apt-setup</command> which country you live in.  This
+configures which of the official Debian Internet mirror network you
+connect to.  Depending on which country you select, you will be given
+a list of possible machines.  Its generally fine to pick the one on
+the top of the list, but any of them should work.
+
+</para><para>
+
+If you are installing via HTTP, you will be asked to configure your
+proxy server.  This is sometimes required by people behind firewalls,
+on corporate networks, etc.
+
+</para><para>
+
+Finally, your new network package source will be tested.  If all goes
+well, you will be prompted whether you want to do it all over again
+with another network source.
+
+</para>
+  </sect3>
+ </sect2>
diff --git a/da/boot-new/modules/install.xml b/da/boot-new/modules/install.xml
new file mode 100644
index 000000000..d0998127e
--- /dev/null
+++ b/da/boot-new/modules/install.xml
@@ -0,0 +1,39 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 18597 untranslated -->
+
+ <sect2 id="debconf">
+ <title>Prompts During Software Installation</title>
+
+<para>
+
+Each package you selected with <command>tasksel</command> or
+<command>aptitude</command> is
+downloaded, unpacked and then installed in turn by the
+<command>apt-get</command> and <command>dpkg</command> programs. If
+a particular program needs more information from the user, it will
+prompt you during this process. You might also want to keep an eye on
+the output during the process, to watch for any installation errors
+(although you will be asked to acknowledge errors which prevented
+a package's installation).
+
+</para>
+
+  <sect3 arch="powerpc" id="xserver">
+  <title>Settings for the X Server</title>
+
+<para>
+
+On iMacs, and some older Macintoshes as well, the X Server software
+doesn't calculate appropriate video settings. You will need to choose
+the 'Advanced' option during configuration of the video settings. For
+the monitor's horizontal sync range, enter 59-63. You can leave the
+default for vertical refresh range.
+
+</para><para>
+
+The mouse device should be set to
+<userinput>/dev/input/mice</userinput>.
+
+</para>
+  </sect3>
+ </sect2>
diff --git a/da/boot-new/modules/mta.xml b/da/boot-new/modules/mta.xml
new file mode 100644
index 000000000..5290c4254
--- /dev/null
+++ b/da/boot-new/modules/mta.xml
@@ -0,0 +1,93 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+ <sect2 id="base-config-mta">
+ <title>Configuring Your Mail Transport Agent</title>
+
+<para>
+
+Today, email is a very important part of many people's life, so it's
+no surprise Debian lets you configure your mail system right as a part
+of the installation process. The standard mail transport agent in
+Debian is <command>exim4</command>, which is relatively small,
+flexible, and easy to learn.
+
+</para><para>
+
+You may ask if this is needed even if your computer is not connected
+to any network. The short answer is: Yes. The longer explanation: Some
+system utilities (like <command>cron</command>,
+<command>quota</command>, <command>aide</command>, &hellip;) may send
+you important notices via email.
+
+</para><para>
+
+So on the first screen you will be presented with several common mail
+scenarios. Choose the one that most closely resembles your needs:
+
+</para>
+
+<variablelist>
+<varlistentry>
+<term>internet site</term>
+<listitem><para>
+
+Your system is connected to a network and your mail is sent and
+received directly using SMTP. On the following screens you will be
+asked a few basic questions, like your machine's mail name, or a list of
+domains for which you accept or relay mail.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>mail sent by smarthost</term>
+<listitem><para>
+
+In this scenario is your outgoing mail forwarded to another machine,
+called a <quote>smarthost</quote>, which does the actual job for
+you. Smarthost also usually stores incoming mail addresed to your
+computer, so you don't need to be permanently online. That also means
+you have to download your mail from the smarthost via programs like
+fetchmail. This option is suitable for dial-up users.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>local delivery only</term>
+<listitem><para>
+
+Your system is not on a network and mail is sent or received only
+between local users. Even if you don't plan to send any messages, this
+option is highly recommended, because some system utilities may send
+you various alerts from time to time (e.g. beloved <quote>Disk quota
+exceeded</quote>). This option is also convenient for new users,
+because it doesn't ask any further questions.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>no configuration at this time</term>
+<listitem><para>
+
+Choose this if you are absolutely convinced you know what you are
+doing. This will leave you with an unconfigured mail system &mdash;
+until you configure it, you won't be able to send or receive any mail
+and you may miss some important messages from your system utilities.
+
+</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>
+
+If none of these scenarios suits your needs, or if you need a finer
+setup, you will need to edit configuration files under the
+<filename>/etc/exim4</filename> directory after the installation is
+complete. More information about <command>exim4</command> may be found
+under <filename>/usr/share/doc/exim4</filename>.
+
+</para>
+ </sect2>
diff --git a/da/boot-new/modules/packages.xml b/da/boot-new/modules/packages.xml
new file mode 100644
index 000000000..ccfed03d9
--- /dev/null
+++ b/da/boot-new/modules/packages.xml
@@ -0,0 +1,128 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 18767 untranslated -->
+
+ <sect2 id="install-packages">
+ <title>Package Installation</title>
+
+<para>
+
+Next you will be offered a number of pre-rolled software
+configurations offered by Debian. You could always choose, package by
+package, what you want to install on your new machine.  This is the
+purpose of the <command>aptitude</command> program, described below.
+But this can be a long task with around &num-of-distrib-pkgs; packages
+available in Debian!
+
+</para><para>
+
+So, you have the ability to choose <emphasis>tasks</emphasis> first,
+and then add on more individual packages later.  These tasks loosely
+represent a number of different jobs or things you want to do with
+your computer, such as <quote>desktop environment</quote>,
+<quote>web server</quote>, or <quote>print server</quote>.
+
+<footnote>
+<para>
+
+You should know that to present this list,
+<command>base-config</command> is merely invoking the
+<command>tasksel</command> program.  For manual package
+selection, the
+<command>aptitude</command> program is being run.  Any of these can be
+run at any time after installation to install (or remove) more
+packages.  If you are looking for a specific single package, after
+installation is complete, simply run <userinput>apt-get install
+<replaceable>package</replaceable></userinput>, where
+<replaceable>package</replaceable> is the name of the package you are
+looking for.
+</para>
+</footnote>
+
+</para><para>
+
+If you do want to choose what to install on a package by package basis,
+select the <quote>manual package selection</quote> in
+<command>tasksel</command>.
+
+</para><para>
+
+Once you've selected your tasks, select
+<guibutton>Ok</guibutton>. At this point,
+<command>aptitude</command> will install the packages you've
+selected. Note, even if you did not select any tasks at all, any standard,
+important, or required priority packages that are not yet present on
+your system will be installed.  This functionality is the same as
+running <userinput>tasksel -s</userinput> at the command line, and
+currently involves
+a download of about 37M of archives. You will be shown the number of
+packages to be installed, and how many kilobytes of packages, if any,
+need to be downloaded.
+
+</para><para>
+
+Of the &num-of-distrib-pkgs; packages available in Debian, only
+a small minority are covered by tasks offered in the Task Installer.
+To see information on more packages, either use <userinput>apt-cache
+search <replaceable>search-string</replaceable></userinput> for some
+given search string (see the <citerefentry>
+<refentrytitle>apt-cache</refentrytitle> <manvolnum>8</manvolnum>
+</citerefentry> man page), or run
+<command>aptitude</command> as described below.
+
+</para>
+
+ <sect3 id="aptitude">
+ <title>Advanced Package Selection with <command>aptitude</command></title>
+
+<para>
+
+<command>Aptitude</command> is a modern program for managing
+packages. <command>aptitude</command> allows you to
+select individual packages, set of packages matching given criteria
+(for advanced users), or whole tasks.
+
+</para><para>
+
+The most basic keybindings are:
+
+<informaltable>
+<tgroup cols="2">
+<thead>
+<row>
+  <entry>Key</entry><entry>Action</entry>
+</row>
+</thead>
+
+<tbody>
+<row>
+  <entry><keycap>Up</keycap>, <keycap>Down</keycap></entry>
+  <entry>Move selection up or down.</entry>
+</row><row>
+  <entry>&enterkey;</entry>
+  <entry>Open/collapse/activate item.</entry>
+</row><row>
+  <entry><keycap>+</keycap></entry>
+  <entry>Mark package for installation.</entry>
+</row><row>
+  <entry><keycap>-</keycap></entry>
+  <entry>Mark package for removal.</entry>
+</row><row>
+  <entry><keycap>d</keycap></entry>
+  <entry>Show package dependencies.</entry>
+</row><row>
+  <entry><keycap>g</keycap></entry>
+  <entry>Actually download/install/remove packages.</entry>
+</row><row>
+  <entry><keycap>q</keycap></entry>
+  <entry>Quit current view.</entry>
+</row><row>
+  <entry><keycap>F10</keycap></entry>
+  <entry>Activate menu.</entry>
+</row>
+</tbody></tgroup></informaltable>
+
+For more commands see the online help under the <keycap>?</keycap> key.
+
+</para>
+  </sect3>
+ </sect2>
diff --git a/da/boot-new/modules/ppp.xml b/da/boot-new/modules/ppp.xml
new file mode 100644
index 000000000..a707fd2b1
--- /dev/null
+++ b/da/boot-new/modules/ppp.xml
@@ -0,0 +1,112 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 18642 untranslated -->
+
+ <sect2 arch="not-s390" id="PPP">
+ <title>Setting Up PPP</title>
+
+<para>
+
+If your computer is not connected to a network, you will next be asked
+whether you wish to install the rest of the system using PPP.
+
+</para><para>
+
+If you do choose to configure PPP at this point, a program named
+<command>pppconfig</command> will be run.  This program helps you
+configure your PPP connection.  <emphasis>Make sure, when it asks you
+for the name of your dialup connection, that you name it
+<userinput>provider</userinput>.</emphasis>
+
+</para><para>
+
+Hopefully, the <command>pppconfig</command> program will walk you
+through a pain-free PPP connection setup.  However, if it does not
+work for you, see below for detailed instructions.
+
+</para><para>
+
+In order to setup PPP, you'll need to know the basics of file viewing
+and editing in GNU/Linux.  To view files, you should use
+<command>more</command>, and <command>zmore</command> for compressed
+files with a <userinput>.gz</userinput> extension.  For example, to
+view <filename>README.debian.gz</filename>, type <userinput>zmore
+README.debian.gz</userinput>.  The base system comes with an editor
+named <command>nano</command>, which is very simple to use, but does
+not have a lot of features. You will probably want to install more
+full-featured editors and viewers later, such as
+<command>jed</command>, <command>nvi</command>,
+<command>less</command>, and <command>emacs</command>.
+
+</para><para>
+
+Edit <filename>/etc/ppp/peers/provider</filename> and replace
+<userinput>/dev/modem</userinput> with
+<userinput>/dev/ttyS<replaceable>&num;</replaceable></userinput> where
+<replaceable>&num;</replaceable> stands for the number of your serial
+port. In Linux, serial ports are counted from 0; your first serial
+port <phrase arch="i386">(i.e., <userinput>COM1</userinput>)</phrase>
+is <filename>/dev/ttyS0</filename> under Linux.
+
+<phrase arch="powerpc;m68k">On Macintoshes with serial ports, the
+modem port is <filename>/dev/ttyS0</filename> and the printer port is
+<filename>/dev/ttyS1</filename>.</phrase>
+
+The next step is to edit
+<filename>/etc/chatscripts/provider</filename> and insert your
+provider's phone number, your user-name and password. Please do not
+delete the <quote>\q</quote> that precedes the password. It hides the
+password from appearing in your log files.
+
+</para><para>
+
+Many providers use PAP or CHAP for login sequence instead of text mode
+authentication.  Others use both.  If your provider requires PAP or
+CHAP, you'll need to follow a different procedure.  Comment out
+everything below the dialing string (the one that starts with
+<quote>ATDT</quote>) in
+<filename>/etc/chatscripts/provider</filename>, modify
+<filename>/etc/ppp/peers/provider</filename> as described above, and
+add <userinput>user <replaceable>name</replaceable></userinput> where
+<replaceable>name</replaceable> stands for your user-name for the
+provider you are trying to connect to.  Next, edit
+<filename>/etc/ppp/pap-secrets</filename> or
+<filename>/etc/ppp/chap-secrets</filename> and enter your password
+there.
+
+</para><para>
+
+You will also need to edit <filename>/etc/resolv.conf</filename> and
+add your provider's name server (DNS) IP addresses.  The lines in
+<filename>/etc/resolv.conf</filename> are in the following format:
+<userinput>nameserver
+<replaceable>xxx.xxx.xxx.xxx</replaceable></userinput> where the
+<replaceable>x</replaceable>s stand for numbers in your IP
+address. Optionally, you could add the
+<userinput>usepeerdns</userinput> option to the
+<filename>/etc/ppp/peers/provider</filename> file, which will enable
+automatic choosing of appropriate DNS servers, using settings the
+remote host usually provides.
+
+</para><para>
+
+Unless your provider has a login sequence different from the majority
+of ISPs, you are done! Start the PPP connection by typing
+<command>pon</command> as root, and monitor the process using
+<command>plog</command> command. To disconnect, use
+<command>poff</command>, again, as root.
+
+</para><para>
+
+Read <filename>/usr/share/doc/ppp/README.Debian.gz</filename> file for
+more information on using PPP on Debian.
+
+</para><para>
+
+For static SLIP connections, you will need to add the
+<userinput>slattach</userinput> command (from the
+<classname>net-tools</classname> package) into
+<filename>/etc/init.d/network</filename>. Dynamic SLIP will require
+the <classname>gnudip</classname> package.
+
+</para>
+ </sect2>
diff --git a/da/boot-new/modules/shadow.xml b/da/boot-new/modules/shadow.xml
new file mode 100644
index 000000000..e4ac0ce1e
--- /dev/null
+++ b/da/boot-new/modules/shadow.xml
@@ -0,0 +1,69 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 18642 untranslated -->
+
+ <sect2 id="base-config-users">
+ <title>Setting Up Users And Passwords</title>
+
+  <sect3 id="base-config-root">
+  <title>Set the Root Password</title>
+
+<para>
+
+The <emphasis>root</emphasis> account is also called the
+<emphasis>super-user</emphasis>; it is a login that bypasses all
+security protection on your system. The root account should only be
+used to perform system administration, and only used for as short
+a time as possible.
+
+</para><para>
+
+Any password you create should contain at least 6 characters, and
+should contain both upper- and lower-case characters, as well as
+punctuation characters.  Take extra care when setting your root
+password, since it is such a powerful account.  Avoid dictionary
+words or use of any personal information which could be guessed.
+
+</para><para>
+
+If anyone ever tells you they need your root password, be extremely
+wary. You should normally never give your root password out, unless you
+are administering a machine with more than one system administrator.
+
+</para>
+  </sect3>
+
+  <sect3 id="make-normal-user">
+  <title>Create an Ordinary User</title>
+
+<para>
+
+The system will ask you whether you wish to create an ordinary user
+account at this point.  This account should be your main personal
+log-in.  You should <emphasis>not</emphasis> use the root account for
+daily use or as your personal login.
+
+</para><para>
+
+Why not?  Well, one reason to avoid using root's privileges is that it
+is very easy to do irreparable damage as root.  Another reason is that
+you might be tricked into running a <emphasis>Trojan-horse</emphasis>
+program &mdash; that is a program that takes advantage of your
+super-user powers to compromise the security of your system behind
+your back. Any good book on Unix system administration will cover this
+topic in more detail &mdash; consider reading one if it is new to you.
+
+</para><para>
+
+You will first be prompted for the user's full name. Then you'll be asked
+for a name for the user account; generally your first name or something
+similar will suffice and indeed will be the default. Finally, you will be
+prompted for a password for this account.
+
+</para><para>
+
+If at any point after installation you would like to create another
+account, use the <command>adduser</command> command.
+
+</para>
+  </sect3>
+ </sect2>
diff --git a/da/boot-new/modules/timezone.xml b/da/boot-new/modules/timezone.xml
new file mode 100644
index 000000000..e7edc7917
--- /dev/null
+++ b/da/boot-new/modules/timezone.xml
@@ -0,0 +1,30 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 19108 untranslated -->
+
+ <sect2 id="base-config-tz">
+ <title>Configuring Your Time Zone</title>
+
+<para>
+
+After a welcome screen, you will be prompted to configure your time zone.
+First select whether the hardware clock of your system is set to local
+time or Greenwich Mean Time (GMT or UTC). The time displayed in the dialog
+may help you decide on the correct option.
+<phrase arch="m68k;powerpc">Macintosh hardware clocks are normally
+set to local time. If you want to dual-boot, select local time instead of
+GMT.</phrase>
+<phrase arch="i386">Systems that (also) run Dos or Windows are normally
+set to local time. If you want to dual-boot, select local time instead of
+GMT.</phrase>
+
+</para><para>
+
+Depending on the location selected at the beginning of the installation
+process, you will next be shown either a single timezone or a list of
+timezones relevant for that location. If a single timezone is shown, choose
+<guibutton>Yes</guibutton> to confirm or choose <guibutton>No</guibutton>
+to select from the full list of timezones. If a list is shown, select your
+timezone from the list, or select Other for the full list.
+
+</para>
+ </sect2>