ffp-reloaded

You can boot directly into ffp and run it without firmware.

WARNING: This is highly experimental. A serial connection may be required to track down problems.

To boot the ffp kernel using the approach described here, you will need a working reloaded module that supports your kernel. The modules included in the ffp-reloaded package (see Installation below) should work with D-Link firmwares up to 1.4 (1.5?) on a DNS-323.

You should also install the latest busybox package (>= 1.11.1).

Download and install ffp-reloaded and linux-kernel packages from inreto.de

telnet bob
cd /path/to/downloaded/packages
funpkg -i ffp-reloaded-0.1-1.tgz linux-kernel-2.6.25.1-1.tgz

Before the first boot, you need to create some essential files, directories and links. We assume that ffp is installed (and later booted) from /mnt/HD_a2.

Create required device files:

cd /ffp/boot
sh ./make-devs.sh /mnt/HD_a2/dev

Create and link required directories:

cd /mnt/HD_a2
ln -s ffp/etc ffp/bin ffp/sbin .
ln -s ffp usr
mkdir -p proc sys

Now setup the user database:

cp /etc/passwd /etc/shadow /etc/group /ffp/etc
cd /ffp/etc/example
cp passwd shadow group /ffp/etc

Note that /mnt/HD_a2 will become the root directory (/) after booting. So home directories in passwd that point to /mnt/HD_a2/… will not work.

• Workaround 1: Remove /mnt/HD_a2 from paths: sed -i 's@/mnt/HD_a2@@' /ffp/etc/passwd
• Workaround 2: Create /mnt/HD_a2 link for use after boot: mkdir /mnt/HD_a2/mnt; ln -s / /mnt/HD_a2/mnt/HD_a2

Alternatively, /ffp/etc/examples contains passwd, shadow and group files that only contain root (with empty password). You can use these examples if you don't want to use the firmware files.

Configure network name resolution (DNS):

cp /etc/hosts /etc/resolv.conf /ffp/etc

To boot into ffp:

cd /ffp/boot
nohup ./boot.sh

Your current telnet session will be aborted, but you should be able to relogin in a few seconds. You can check the new kernel version with:

uname -a

• The included kernel support kernel-level NFS.
• /mnt/HD_a2 doesn't exist anymore after booting into ffp. You might need to adjust some config files (exports, mediatomb, …)

• There's no fan control yet.
• A start script that selects the proper set of config files for ffp with and without firmware.