Differences
This shows you the differences between the selected revision and the current version of the page.
| talk:howto:ffp-reloaded 2013/02/04 13:35 | talk:howto:ffp-reloaded 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | At last some raitoanltiy in our little debate. | + | TODO: |
| + | |||
| + | == /mnt/HD_xx mounts == | ||
| + | |||
| + | Configuration files for some services have explicit references to /mnt/HD_xx. | ||
| + | To keep the ffp-reloaded environment compatible, you can create the mount points and add entries to /ffp/etc/fstab. | ||
| + | Example for /mnt/HD_a2: | ||
| + | <code> | ||
| + | # mkdir -p /mnt/HD_a2 | ||
| + | # echo '/dev/sda2 /mnt/HD_a2 ext2 defaults 0 0' >>/ffp/etc/fstab | ||
| + | </code> | ||
| + | |||
| + | |||
| + | |||
| + | ==== Tested with Firmware 1.05 of Custom Build ==== | ||
| + | |||
| + | The methodology of reloading the Linux kernel does work from the v1.05 custom firmware, FrodoII_firmware, which has telnet turned on inside the firmware. | ||
| + | |||
| + | It seems to me that it should be possible to execute the Debian chrooted installation in /mnt/HD_a2/linux by following this approach: | ||
| + | |||
| + | cd /mnt/HD_a2/ | ||
| + | for i in `ls linux/` ; do | ||
| + | ln -s $i | ||
| + | done | ||
| + | ./ffp/boot/boot.sh | ||
| + | |||
| + | Unfortunately, it doesn't work, and I don't (yet) have a serial console set up to figure out why not. Anyone who has a serial console care to try the above, and let me know what I'm doing wrong? | ||
