====== Install Debian Etch - by Mike Gore and Manuel Treitinger ======
**Please feel free to update, cleanup or correct this page**

**What is this?** This document shows how to setup Debian on the DNS-323.

Note: this technique installs a Debian environment into the existing system, and does not require you to reflash or hack the NAS.

**All downloads/methods below are using Debian for arm. This is more or less deprecated. See [[http://dns323.kood.org/forum/viewtopic.php?id=4330|forum post]] on howto install an armel version. **




===== The easy way =====

The easiest way to get a full Debian environment is to use DebNAS. It provides a full base system with SSH enabled by default and boots automatically. As it uses chroot, it is not going to harm your device and can be uninstalled by simply deleting one file ("fun_plug") and one folder ("linux") from your first volume. 

**Download**: [[http://mesh.dl.sourceforge.net/sourceforge/debnas/debnas-0.5.tar.bz2]]

To install:
  - Ensure you have the newest firmware (1.05 or newer).
  - Extract the downloaded archive
  - Copy the two extracted files linux.tar and fun_plug to the root directory of your first DNS-323 volume
  - Reboot the DNS-323
  - The DNS-323 is going to work for several minutes now and finally reboots
  - The DNS-323 automatically boots into Debian and runs the SSH - daemon

You can now log in via SSH, the default password for username root is 12345678.
(Be aware that (sometimes) the NAS is only accessible via IP address at this moment!)


Change the password immediately with the passwd command.
**Have fun!**

Note: Upgrading Debian to a current distribution is going to increase performance a lot.

**To upgrade to Debian Lenny :**\\ 
''Edit /etc/apt/sources.list.d/etch.list, replacing the word etch with lenny. 
I also changed the mirror url to a North American mirror rather than the German one by removing the de. in the url. You may also rename the filename from etch.list to lenny.list if you feel so inclined.''
<code xml>
NOTE: This does not work as written, lenny and etch are both archived, and as such, the repositories have moved. The following worked for me.

deb http://archive.debian.org/debian/ lenny main non-free contrib
deb http://archive.debian.org/debian-backports lenny-backports main
</code>


Now we need to update the repository packages listing and upgrade to lenny. You may have GPG issues which you can resolve by calling : 
<code bash>
apt-get install debian-archive-keyring
</code>
Or following the guide  **Here**: [[http://linux.com/community/blogs/Debian-Upgrading-to-Lenny-ERROR-no-public-key-available-for-the-following....html]]  

Make sure that you have DNS nameservers listed in /etc/resolv.conf, and run :


<code bash>
apt-get update
apt-get dist-upgrade
</code>

This will take a while to download and then upgrade. When it is done reboot Debian. I had to reboot using the command ‘reboot -f’. When Debian comes back up, it will be running Lenny. When it comes back up, update to make sure everything is current.

<code bash>
apt-get update
apt-get upgrade
</code>
Now we have a reasonably current Linux system to play with. 


===== The custom way  =====


==== 1. prerequisites =====

You should already have [[Telnet]] access to your device.

Or better, install ssh and disable Telnet.  See:

http://www.penoycentral.net/linuxnix/configuring-ssh-and-rsync-in-dlink-dns-323/


==== 2. base system ====

You have two options to proceed. You can either download a preconfigured image or create your own.

=== 2A. download a minimal image ===

  * Debian Etch 4.0 - [http://dev.skcserver.de/dns323/etch.tar] (169 Mb) 
  * Debian Etch 4.0 (U.S. mirror) - [http://www.bfaber.com/dl/etch.tar]

If you wish to use one of these, simply download it and proceed to step 3 below.

=== 2B. create a minimal image ===
** You will need a Debian Linux x86** system to create the install image. 
(My system is a Ubuntu Dapper x86 system)

Make sure you have **cdebootstrap smbfs** installed 
<code bash>
apt-get install cdebootstrap smbfs
</code>

**Note - I called my DNS-323 "disk"**

We will now mount the DNS-323 on the host Debian system. Your system has to be formatted with an admin password. I will use **disk** for the DNS-323 and **/mnt** for the mount points in this document - you can use whatever you like.

<code bash>
mount -t cifs  //disk/Volume_1 /mnt -o username=admin
</code>
**Or** use the IP address of the DNS-323
<code bash>
mount -t cifs  //10.0.0.1/Volume_1 /mnt -o username=admin
</code>

We will now "bootstrap" an ARM debian system using our x86 debian system
**note it will error out at the final install phase - this is just fine**
This process will create an ARM debian environment under a directory called **lenny**
<code bash>
cdebootstrap -aarm lenny lenny ftp://ftp.debian.org/debian
</code>
For the oldstable (**etch**) you should use the following
When you use this line, you should replace all "lenny" texts with "**etch**".
<code bash>
cdebootstrap -aarm etch etch ftp://ftp.debian.org/debian
</code>

Archive the **lenny** (or **etch**) directory we created with the bootstrap
<code bash>
tar pcvf lenny.tar lenny
</code>

Copy this tar file to **/mnt**
<code bash>
cp lenny.tar /mnt
</code>






==== 3. finalizing installation ====

*update by Berry (26th March 08) - If you have firmware 1.04 then make sure to turn off Oplocks now on the web interface before you untar (Advanced / Network access)

# On the host x86 system reboot the DNS-323 using the web interface

# Telnet or ssh to the DNS-323
telnet disk

**Note We are now logged into the DNS-323**

# CD to the hard disk we just copied everything to
<code bash>
cd /mnt/HD_a2
</code>

# At this point, you should untar the {lenny,etch}.tar file that you made above
<code bash>
./lnx_bin/busybox3 tar -xf lenny.tar
</code>

Or for firmware 1.04+:
<code bash>
tar -xf lenny.tar
</code>

# Replace lenny.tar with etch.tar above if you built an etch install

* Daniel (26 Oct 08) Alternatively with FFP 0.3 you may find that the correct command is: ./fun_plug.d/bin/busybox tar -xf etch.tar

# chroot into the partly bootstrapped sarge debian root
<code bash>
./lnx_bin/busybox3 chroot lenny /bin/bash
</code>

Or for firmware 1.04+:
<code bash>
chroot lenny /bin/bash
</code>

# At this point you should have a shell in the new debian root

*update by sm8ps (20100815): On Firmware 1.08 with the downloaded a minimal image from step 2A, none of the following was necessary. I could proceed straight to step 4. 

# Fix the broken packages caused by the failed cdebootstrap - above
** Note - 08 dec 2007 by Chris - I think before proceeding you want to be sure that /proc, /dev, and friends all contain 
 something reasonable - for example as set up by the mount commands in the fun_plug listed at the bottom of this page.
 Some of the installers seem to get confused when they can't find fstab, /dev, etc. **

*update by Richard (23rd Dec 07) I think Chris (above) is right, go through the fun_plug and type in the commands by hand. Also, do dpkg*deb first (below), then libc6.

*Daniel (26 Oct 08) with FFP 0.3 it is neccessary to change the fun_plug listed at the bottom of this page to reference folder fun_plug.d/bin whenever lnx_bin occurs, and replace "busybox3" with "busybox"

*update by Paul (18 Apr 08) This all seems much simpler with 1.04.  no need to do any of those things afaict.
<code bash>
cd /var/cache/bootstrap
dpkg --force-all -i libc6*deb
dpkg --force-all -i dpkg*deb
dpkg --force-all -i libc6*deb
</code>
# repeat next step several times until no more errors\\
(if you are using the downloaded sarge package the .deb files are located in "/var/cache/apt/archives" not in "/var/cache/bootstrap"!)\\
<code>
dpkg -iGREB . 
</code>
# check remaining dpkg errors if any

*update by Richard (23rd Dec 07) I had to delete /var/mail to get base_files to install properly

*update by Michael (20th June 08) I had to delete /var/mail in sarge.  etch was fine.








==== 4. customizing ====

# Edit your /etc/resolv.conf so that the system can find the Debian servers: See this [[howto:chroot_debian:resolv.conf|sample]]

# (for ETCH from link above) Edit your (create new) /etc/apt/apt.conf so that the system can download needed updates:
<code>
APT::Default-Release "etch";
</code>
*Add by Vladimir Kovtun (19th Dec 08), tested well.

# Add to /etc/bash.bashrc if you wish the APT-GET to use a your proxy server:
<code>
export http_proxy=http://192.168.1.254:8081/
export ftp_proxy=http://192.168.1.254:8081/
</code>
*Add by Vladimir Kovtun (18th Dec 08), tested well.

*Add by Jesper Møller (21st April 09), if you don't have a suitable proxy, be sure to fix the  fix /etc/resolv.conf to point to you DNS servers

# (1) Edit your /etc/apt/sources.list so that includes some servers.  For instance:
<code>
deb http://ftp1.ca.debian.org/debian stable main contrib non-free
deb http://security.debian.org stable/updates main contrib non-free
</code>
__OR__

# (2) Edit your /etc/apt/sources.list so that includes some servers.
  * It's 100% needed for Debian Etch 4.0 - [http://dev.skcserver.de/dns323/etch.tar] (169 Mb)
<code>
deb http://ftp1.ca.debian.org/debian etch main contrib non-free
deb http://ftp1.ca.debian.org/debian etch-proposed-updates main contrib non-free
deb http://security.debian.org etch/updates main contrib non-free
</code>
and empty /etc/apt/sources.list/etch.conf (or simple unlink it)
*Update by Vladimir Kovtun (19th Dec 08), tested well.

*update by sm8ps (20100815): As of 20100215, the support of Debian Etch has run out.
The above mentioned sources do not work anymore therefore.
The Debian archive, however, still contains the packages.
So for Etch one should use the following sources (and delete /etc/apt/sources.list.d/etch.list):

<code>
deb http://archive.debian.org/debian-archive/debian/ etch main contrib non-free
deb-src http://archive.debian.org/debian-archive/debian/ etch main contrib non-free
</code>

or (mdvx 19-Jan-09)
and empty /etc/apt/sources.list.d/etch.list 


# Update packages
<code bash>
apt-get update
apt-get install debian-archive-keyring
apt-get update
apt-get dist-upgrade
</code>
*Update by Vladimir Kovtun (19th Dec 08), tested well - first "apt-get update" for update keys for next updates.
# make root password
<code bash>
passwd root
</code>

# Go nuts installing packages
<code bash>
apt-get install gcc
apt-get install make
apt-get install unzip
apt-get install flex bison
apt-get install g++
</code>
# etc ....



===Create a **fun_plug** script===

If you would like Debian to automatically begin after it is installed, you will need to add some commands to your startup (fun_plug) script.

[[.:chroot_debian:fun_plug|Download the Debian Fun Plug Script here]]

Copy this fun_plug to /mnt  **we assume you still have the DNS-323 mounted**
On the DNS-323
<code bash>
cd /mnt/HD_a2
chmod 755 fun_plug
</code>

Create a **linuxrc** script
[[.:chroot_debian:linuxrc|Download the Debian linuxrc Script here]]

Copy this linuxrc to /mnt  (we assume you still have the DNS-323 mounted*
On the DNS-323
<code bash>
cd /mnt/HD_a2/sarge
chmod 755 linuxrc
</code>
# Note: be sure to install both the linuxrc script *and* the fun_plug script before rebooting!

# Note 2: Make sure you create your fun_plug and script files as unix file not windows text files.  I fell for this :(
Added by: James Alford 2009-01-11

** Reboot the DNS-323 and test **

=== Manual chroot to a Debian etch when using fonz funplug ===

To do a manual chroot to a "fresh" extracted Debian etch,
use the following command:

<code bash>
env -i TERM=vt102 USER=root $SBINDIR/chroot /mnt/HD_a2/etch /bin/bash -ls
</code>

(Try this if you get errors such as "sh: /mnt/HD_a2/fun_plug.d/bin/ls: No such file or directory" or 
"dpkg - error: PATH is not set")

If there are still issues like "dpkg - error: PATH is not set" export PATH into your chrooted system. First change to a bash shell of your etch/sarge by typing the previous command. The use export PATH:

<code bash>
env -i TERM=vt102 USER=root $SBINDIR/chroot /mnt/HD_a2/etch /bin/bash -ls
etch /> export PATH
</code>



[[howto:crosscompile|Cross Compile Software for the DNS-323]]