Remove all untranslated documents for Danish

6 files changed, 0 insertions, 425 deletions

diff --git a/da/post-install/further-reading.xml b/da/post-install/further-reading.xml
deleted file mode 100644
index 0eb4b93ba..000000000
--- a/da/post-install/further-reading.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 16554 untranslated -->
-
- <sect1 id="further-reading"><title>Further Reading and Information</title>
-<para>
-
-If you need information about a particular program, you should first
-try <userinput>man <replaceable>program</replaceable></userinput>, or
-<userinput>info <replaceable>program</replaceable></userinput>.
-
-</para><para>
-
-There is lots of useful documentation in
-<filename>/usr/share/doc</filename> as well.  In particular,
-<filename>/usr/share/doc/HOWTO</filename> and
-<filename>/usr/share/doc/FAQ</filename> contain lots of interesting
-information.  To submit bugs, look at
-<filename>/usr/share/doc/debian/bug*</filename>.  To read about
-Debian-specific issues for particular programs, look at
-<filename>/usr/share/doc/(package name)/README.Debian</filename>.
-
-</para><para>
-
-The 
-<ulink url="http://www.debian.org/">Debian web site</ulink> 
-contains a large quantity of documentation about Debian.  In
-particular, see the 
-<ulink url="http://www.debian.org/doc/FAQ/">Debian FAQ</ulink> and the 
-<ulink url="http://lists.debian.org/">Debian Mailing List Archives</ulink>.  
-The Debian community is self-supporting; to subscribe to
-one or more of the Debian mailing lists, see the 
-<ulink url="http://www.debian.org/MailingLists/subscribe">
-Mail List Subscription</ulink> page.
-
-</para><para>
-
-A general source of information on GNU/Linux is the 
-<ulink url="http://www.tldp.org/">Linux Documentation Project</ulink>. 
-There you will find the HOWTOs and pointers to other very valuable
-information on parts of a GNU/Linux system.
-
-</para>
-
- </sect1>
diff --git a/da/post-install/kernel-baking.xml b/da/post-install/kernel-baking.xml
deleted file mode 100644
index 8b808858f..000000000
--- a/da/post-install/kernel-baking.xml
+++ /dev/null
@@ -1,203 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 16990 untranslated -->
-
- <sect1 id="kernel-baking"><title>Compiling a New Kernel</title>
-<para>
-
-Why would someone want to compile a new kernel? It is often not
-necessary since the default kernel shipped with Debian handles most
-configurations. However, it is useful to compile a new kernel in order
-to:
-
-<itemizedlist>
-<listitem><para>
-
-handle special hardware needs, or hardware conflicts with the pre-supplied
-kernels
-
-</para></listitem>
-<listitem><para>
-
-handle hardware or options not included in the stock kernel, such as
-APM or SMP
-
-</para></listitem>
-
-<listitem arch="x86"><para>
- 
-The compact and idepci flavors don't come with sound. Although
-the vanilla kernel does, it might not work for other reasons.  
-
-</para></listitem>
-<listitem><para>
-
-optimize the kernel by removing useless drivers to speed up boot
-time
-
-</para></listitem>
-<listitem><para>
-
-use options of the kernel which are not supported by the default
-kernel (such as network firewalling)
-
-</para></listitem>
-<listitem><para>
-
-run a updated or development kernel
-
-</para></listitem>
-<listitem><para>
-
-impress your friends, try new things
-
-</para></listitem>
-</itemizedlist>
-
-</para>
-
-  <sect2><title>Kernel Image Management</title>
-<para>
-
-Don't be afraid to try compiling the kernel.  It's fun and profitable. 
-
-</para><para>
-
-To compile a kernel the Debian way, you need some packages:
-<classname>kernel-package</classname>,
-<classname>kernel-source-&kernelversion;</classname> (the most recent version
-at the time of this writing), <classname>fakeroot</classname> and a
-few others which are probably already installed (see
-<filename>/usr/share/doc/kernel-package/README.gz</filename> for the
-complete list).
-
-</para><para>
-
-This method will make a .deb of your kernel source, and, if you have
-non-standard modules, make a synchronized dependent .deb of those
-too. It's a better way to manage kernel images;
-<filename>/boot</filename> will hold the kernel, the System.map, and a
-log of the active config file for the build.
-
-</para><para>
-
-Note that you don't <emphasis>have</emphasis> to compile your kernel
-the ``Debian way''; but we find that using the packaging system to
-manage your kernel is actually safer and easier.  In fact, you can get
-your kernel sources right from Linus instead of
-<classname>kernel-source-&kernelversion;</classname>, yet still use the
-<classname>kernel-package</classname> compilation method.
-
-</para><para>
-
-Note that you'll find complete documentation on using
-<classname>kernel-package</classname> under
-<filename>/usr/share/doc/kernel-package</filename>.  This section just
-contains a brief tutorial.
-
-</para><para arch="sparc">
-
-If you are compiling a kernel for UltraSPARC you will need to be sure
-you have installed the <classname>egcs64</classname> package. This is
-the preferred compiler for 64bit SPARC kernels. The default
-<command>gcc</command> will also compile 64bit kernels, but is not as
-stable. Plus, if you do not use <classname>egcs64</classname> and you
-encounter kernel problems, you will most likely be asked to recompile
-the kernel using <classname>egcs64</classname> in order to verify your
-problem still exists. After installing <classname>egcs64</classname>
-be sure to run <userinput>update-alternatives --config
-sparc64-linux-gcc</userinput> as root, and be sure that
-<classname>egcs64</classname> is being used for this program. 
-
-</para><para>
-
-Hereafter, we'll assume your kernel source will be located in
-<filename>/usr/local/src</filename> and that your kernel version is
-&kernelversion;.  As root, create a directory under
-<filename>/usr/local/src</filename> and change the owner of that
-directory to your normal non-root account.  As your normal non-root
-account, change your directory to where you want to unpack the kernel
-sources (<userinput>cd /usr/local/src</userinput>), extract the kernel
-sources (<userinput>tar xjf
-/usr/src/kernel-source-&kernelversion;.tar.bz2</userinput>), change your
-directory to it (<userinput>cd
-kernel-source-&kernelversion;/</userinput>). 
-
-</para><para>
-
-Now, you can configure your kernel.  Run <userinput>make
-xconfig</userinput> if X11 is installed, configured and being run,
-<userinput>make menuconfig</userinput> otherwise (you'll need
-<classname>ncurses-dev</classname> installed). Take the time to read
-the online help and choose carefully. When in doubt, it is typically
-better to include the device driver (the software which manages
-hardware peripherals, such as Ethernet cards, SCSI controllers, and so
-on) you are unsure about.  Be careful: other options, not related to a
-specific hardware, should be left at the default value if you do not
-understand them.  Do not forget to select ``Kernel module loader'' in
-``Loadable module support''
-
-<phrase arch="alpha"> and ``Enhanced Real Time
-Clock Support'' in ``Character devices'' (they are </phrase>
-<phrase arch="not-alpha"> (it is </phrase>
-
-not selected by default).  If not included, your Debian installation
-will experience problems.
-
-</para><para>
-
-Clean the source tree and reset the <classname>kernel-package</classname>
-parameters.  To do that, do <userinput>make-kpkg clean</userinput>.
-
-</para><para>
-
-Now, compile the kernel: 
-<userinput>fakeroot make-kpkg --revision=custom.1.0 kernel_image</userinput>. 
-The version number of ``1.0'' can be changed at will; this is just a
-version number that you will use to track your kernel builds.
-Likewise, you can put any word you like in place of ``custom'' (e.g.,
-a host name).  Kernel compilation may take quite a while, depending on
-the power of your machine.
-
-</para><para condition="supports-pcmcia">
-
-If you require PCMCIA support, you'll also need to install the
-<classname>pcmcia-source</classname> package.  Unpack the gzipped tar file
-as root in the directory <filename>/usr/src</filename> (it's important that
-modules are found where they are expected to be found, namely,
-<filename>/usr/src/modules</filename>).  Then, as root, do <userinput>make-kpkg
-modules_image</userinput>.  
-
-</para><para>
-
-Once the compilation is complete, you can install your custom kernel
-like any package.  As root, do <userinput>dpkg -i
-../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>.
-The <replaceable>subarchitecture</replaceable> part is an optional
-sub-architecture,
-<phrase arch="x86"> such as ``i586'', </phrase>
-depending on what kernel options you set.
-<userinput>dpkg -i kernel-image...</userinput> will install the
-kernel, along with some other nice supporting files.  For instance,
-the <filename>System.map</filename> will be properly installed
-(helpful for debugging kernel problems), and
-<filename>/boot/config-&kernelversion;</filename> will be installed,
-containing your current configuration set.  Your new
-<classname>kernel-image-&kernelversion;</classname> package is also clever
-enough to automatically use your platform's boot-loader to run an
-update on the booting, allowing you to boot without re-running the
-boot loader.  If you have created a modules package, e.g., if you have
-PCMCIA, you'll need to install that package as well.
-
-</para><para>
-
-It is time to reboot the system: read carefully any warning that the
-above step may have produced, then <userinput>shutdown -r now</userinput>.
-
-</para><para>
-
-For more information on <classname>kernel-package</classname>, read
-the fine documentation in <filename>/usr/share/doc/kernel-package</filename>.
-
-</para>
-  </sect2>
- </sect1>
diff --git a/da/post-install/new-to-unix.xml b/da/post-install/new-to-unix.xml
deleted file mode 100644
index c011f5583..000000000
--- a/da/post-install/new-to-unix.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 16556 untranslated -->
-
-
- <sect1 id="unix-intro">
- <title>If You Are New to Unix</title>
-<para>
-
-If you are new to Unix, you probably should go out and buy some books
-and do some reading.  The 
-<ulink url="ftp://rtfm.mit.edu/pub/usenet/news.answers/unix-faq/faq/">
-Unix FAQ</ulink>
-contains a number of references to books and Usenet news groups which
-should help you out.  You can also take a look at the 
-<ulink url="http://www.camelcity.com/~noel/usenet/cuuf-FAQ.htm">
-User-Friendly Unix FAQ</ulink>.
-
-</para><para>
-
-Linux is an implementation of Unix.  The 
-<ulink url="http://www.tldp.org/">Linux Documentation Project (LDP)</ulink> 
-collects a number of HOWTOs and online books
-relating to Linux.  Most of these documents can be installed locally;
-just install the <classname>doc-linux-html</classname> package (HTML
-versions) or the <classname>doc-linux-text</classname> package (ASCII
-versions), then look in <filename>/usr/share/doc/HOWTO</filename>.  
-International versions of the LDP HOWTOs are also available as Debian 
-packages.
-
-</para>
-
- </sect1>
diff --git a/da/post-install/orientation.xml b/da/post-install/orientation.xml
deleted file mode 100644
index d4ba05f3f..000000000
--- a/da/post-install/orientation.xml
+++ /dev/null
@@ -1,109 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 16557 untranslated -->
-
-
- <sect1 id="debian-orientation"><title>Orienting Yourself to Debian</title>
-<para>
-
-Debian is a little different from other distributions.  Even if you're
-familiar with Linux in other distributions, there are things you
-should know about Debian to help you to keep your system in a good,
-clean state.  This chapter contains material to help you get oriented;
-it is not intended to be a tutorial for how to use Debian, but just a
-very brief glimpse of the system for the very rushed.
-
-</para>
-
-  <sect2><title>Debian Packaging System</title>
-<para>
-
-The most important concept to grasp is the Debian packaging system.
-In essence, large parts of your system should be considered under the
-control of the packaging system.  These include:
-
-<itemizedlist>
-<listitem><para>
-
-<filename>/usr</filename> (excluding <filename>/usr/local</filename>)
-
-</para></listitem>
-<listitem><para>
-
-<filename>/var</filename> (you could make
-<filename>/var/local</filename> and be safe in there)
-
-</para></listitem>
-<listitem><para>
-
-<filename>/bin</filename>
-
-</para></listitem>
-<listitem><para>
-
-<filename>/sbin</filename>
-
-</para></listitem>
-<listitem><para>
-
-<filename>/lib</filename>
-
-</para></listitem>
-</itemizedlist>
-
-For instance, if you replace <filename>/usr/bin/perl</filename>, that
-will work, but then if you upgrade your <classname>perl</classname>
-package, the file you put there will be replaced.  Experts can get
-around this by putting packages on ``hold'' in
-<command>aptitude</command>.
-
-</para><para>
-
-One of the best installation methods is apt. You can use the command
-line version <command>apt-get</command> or full-screen text version
-<application>aptitude</application>.  Note apt will also let you merge
-main, contrib, and non-free so you can have export-restricted packages
-as well as standard versions.
-
-</para>
-  </sect2>
-
-  <sect2><title>Application Version Management</title>
-<para>
-
- 
-Alternative versions of applications are managed by update-alternatives. If
-you are maintaining multiple versions of your applications, read the
-update-alternatives man page.
-
-</para>
-  </sect2>
-
-  <sect2><title>Cron Job Management</title>
-<para>
-
-Any jobs under the purview of the system administrator should be in
-<filename>/etc</filename>, since they are configuration files.  If you
-have a root cron job for daily, weekly, or nightly runs, put them in
-<filename>/etc/cron.{daily,weekly,monthly}</filename>.  These are
-invoked from <filename>/etc/crontab</filename>, and will run in
-alphabetic order, which serializes them.
-
-</para><para>
-
-On the other hand, if you have a cron job that (a) needs to run as a
-special user, or (b) needs to run at a special time or frequency, you
-can use either <filename>/etc/crontab</filename>, or, better yet,
-<filename>/etc/cron.d/whatever</filename>.  These particular files
-also have an extra field that allows you to stipulate the user under
-which the cron job runs.
-
-</para><para>
-
-In either case, you just edit the files and cron will notice them
-automatically. There is no need to run a special command. For more
-information see cron(8), crontab(5), and
-<filename>/usr/share/doc/cron/README.Debian</filename>.
-
-</para>
-  </sect2>
- </sect1>
diff --git a/da/post-install/post-install.xml b/da/post-install/post-install.xml
deleted file mode 100644
index 9cd02993c..000000000
--- a/da/post-install/post-install.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 16559 untranslated -->
-
-<chapter id="post-install">
- <title>Next Steps and Where to Go From Here</title>
-
-&new-to-unix.xml;
-&orientation.xml;
-&further-reading.xml;
-&kernel-baking.xml;
-
-</chapter>
diff --git a/da/post-install/shutdown.xml b/da/post-install/shutdown.xml
deleted file mode 100644
index e326be12d..000000000
--- a/da/post-install/shutdown.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 21690 untranslated -->
-
-
- <sect1 id="shutdown">
- <title>Shutting Down the System</title>
-
-<para>
-
-To shut down a running Linux system, you must not reboot with the
-reset switch on the front or back of your computer, or just turn off
-the computer.  Linux must be shut down in a controlled manner,
-otherwise files may be lost and disk damage incurred. You can press
-the key combination <keycombo> <keycap>Ctrl</keycap>
-<keycap>Alt</keycap> <keycap>Del</keycap> </keycombo>
-<phrase arch="powerpc;m68k"> or <keycombo> <keycap>Control</keycap>
-<keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh
-systems</phrase>. You may also log in as
-root and type <userinput>shutdown -h now</userinput>,
-<userinput>reboot</userinput>, or <userinput>halt</userinput> if
-either of the key combinations do not work or you prefer to type
-commands.
-
-</para>
- </sect1>