Differences
This shows you the differences between the selected revision and the current version of the page.
| howto:chroot_debian 2009/12/30 23:33 | howto:chroot_debian 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Install Debian Sarge - by Mike Gore and Manuel Treitinger ====== | + | ====== Install Debian Etch - by Mike Gore and Manuel Treitinger ====== |
| **Please feel free to update, cleanup or correct this page** | **Please feel free to update, cleanup or correct this page** | ||
| Line 6: | Line 5: | ||
| Note: this technique installs a Debian environment into the existing system, and does not require you to reflash or hack the NAS. | 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 easy way ===== | ||
| Line 21: | Line 25: | ||
| - The DNS-323 automatically boots into Debian and runs the SSH - daemon | - The DNS-323 automatically boots into Debian and runs the SSH - daemon | ||
| - | You can now log in via SSH, the default root password is 12345678. | + | 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!) | (Be aware that (sometimes) the NAS is only accessible via IP address at this moment!) | ||
| Line 30: | Line 34: | ||
| Note: Upgrading Debian to a current distribution is going to increase performance a lot. | Note: Upgrading Debian to a current distribution is going to increase performance a lot. | ||
| - | To upgrade to Debian Lenny : | + | **To upgrade to Debian Lenny :**\\ |
| - | Edit /etc/apt/sources.list.d/etch.list, replacing the word etch with 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. | + | 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. | ||
| - | Now we need to update the repository packages listing and upgrade to lenny. You may have GPG issues which you can resolve by following the guide **Here**: [[http://linux.com/community/blogs/Debian-Upgrading-to-Lenny-ERROR-no-public-key-available-for-the-following....html]] (Before running apt-get, be sure that you have DNS nameservers listed in /etc/resolv.conf) | + | 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]] | ||
| - | - apt-get update | + | Make sure that you have DNS nameservers listed in /etc/resolv.conf, and run : |
| - | - apt-get dist-upgrade | + | |
| - | 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. | ||
| - | *apt-get update | + | <code bash> |
| - | *apt-get upgrade | + | 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. | Now we have a reasonably current Linux system to play with. | ||
| Line 141: | Line 160: | ||
| </code> | </code> | ||
| - | Or for firmware 1.04: | + | Or for firmware 1.04+: |
| <code bash> | <code bash> | ||
| tar -xf lenny.tar | tar -xf lenny.tar | ||
| Line 155: | Line 174: | ||
| </code> | </code> | ||
| - | Or for firmware 1.04: | + | Or for firmware 1.04+: |
| <code bash> | <code bash> | ||
| chroot lenny /bin/bash | chroot lenny /bin/bash | ||
| Line 161: | Line 180: | ||
| # At this point you should have a shell in the new debian root | # 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 | # Fix the broken packages caused by the failed cdebootstrap - above | ||
| Line 184: | Line 205: | ||
| </code> | </code> | ||
| # check remaining dpkg errors if any | # 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 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. | *update by Michael (20th June 08) I had to delete /var/mail in sarge. etch was fine. | ||
| + | |||
| Line 217: | Line 235: | ||
| *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 | *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: | # (1) Edit your /etc/apt/sources.list so that includes some servers. For instance: | ||
| Line 235: | Line 252: | ||
| and empty /etc/apt/sources.list/etch.conf (or simple unlink it) | and empty /etc/apt/sources.list/etch.conf (or simple unlink it) | ||
| *Update by Vladimir Kovtun (19th Dec 08), tested well. | *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) | or (mdvx 19-Jan-09) | ||
