2019-02-20: Fixed: Inreto.de is down. Changed download links to funplug.wolf-u.li mirror 2015-10-12: Added: Support for the NAS326. 2015-09-13: Fixed: Squashed this bug: A /mnt/HD_a2 link was not available for the NAS5XX. Only after_booting.sh is changed. 2015-09-03: Added: Support for the NAS540 and NAS520. Only for firmware 5.10+. Older firmwares with a 64kB page size are not supported. 2014-12-02: Added: Recognition support for the 310S and 320S. 2013-11-24: Added: Cleanup after download also removes 'fp.master' stuff Script also supports EMCLifeline, although that needs a different starter, which is supplied with the lifeline package (see Iomega wiki). Support for 'embedded FFP' (as opposed to 'downloaded FFP'), as preparation for a new zypkg. Recognition support for the NSA325v2 2012-10-20: Changed: In addition to the root shell, now also the admin shell is changed to /ffp/bin/sh for unchrooted installations. Fixed: Patched this bug: http://forum.nas-central.org/viewtopic.php?p=27453#p27453 The patch will only be supplied on a fresh install of FFP. 2012-09-03: Changed: Instead of hijacking /etc/profile, now the root shell is changed in /etc/passwd for unchrooted installation. User 'user' is removed. It seems nobody uses it, and at least one person has had an intruder on that account. Added some clean 'disable' functionality for the zypkg version. Cleaned up the logfile, as some messages were read as errors by users. Cleaned up unneeded directories for unchrooted installations. after_booting.sh will create them when needed. Removed the execute_outside_chroot helper thread for the TDC Homebox, as it seems to stop the FFP boot. Added a /etc/mtab symlink When /ffp/etc/ffp.version fails, /ffp/etc/ffp_version is used for chroot/no chroot decisions. 2012-05-28: Changed: On an eabi system (fw >= 4.40) ffp is by default no longer chrooted. On a not chrooted system /etc/profile is adapted, to add ffp globally. On a chrooted system with a writable rootfs /i-data and /e-data are no longer doubled, but moved, and the orignal /i-data and /e-data directories are exchanged by symlinks to the new locations (which are inside the chroot) On a chrooted 3xx or Medion box /etc is no longer hijacked by a bindmount, but by a symlink. The ffp start and stop function is streamlined. It's now (theoretically) possible to stop ffp and start it again. An option is added to auto-enable ssh on installation Removed the possibility to change the root password at an unchrooted installation. 2012-03-19: Fixed: An USB device is mounted by process myhotplug, on /mnt/sdxn. Then process zyshd will create a mountpoint in /e-data, and move the mount. It turned out that sometimes FFP was started from the /mnt mountpoint. This caused problems. 2012-03-17: Changed: Starting with firmware 4.40 the NSA-310 uses /etc/Zy_Private as salt. So I changed nsa310_check_file_C0 to use another salted_checksum. 2012-03-06: Changed: Instead of 0.7/oarm now 0.7/oabi is installed. Fixed: execute_outside_chroot didn't work on oabi boxes. I built a work-around, but am not content yet. The work-around has as side-effect that all executions are logged. This can be a problem when eeecute_outside_chroot is called frequently. Don't know what happens if the logfile exceeds the size of usb partition 1, about 10 MB. 2012-01-31: Added: Support for FFP 0.7 Automatic detection of OABI/EABI support. Changed: By default FFP 0.7 is installed. The 'arm' version when EABI is supported, else oarm. 2012-01-14: Fixed: Bug which disabled unchrooted FFP in 2012-01-13 2012-01-13: Fixed: Solved this issue: http://forum.nas-central.org/viewtopic.php?f=249&t=4947 http://forum.nas-central.org/viewtopic.php?f=249&t=5163#p21501 execute_outside_chroot and exit_ffp didn't work on a NSA3x0. Added: Expanded the list of recognized boxes. Added the 310, 325, STG100, STG211 and STG212 (The STG212 is a Medion) Support for sticks which are initially mounted read-only. Support for FFP 0.6. Support for the Medion P89626/P89630 mkdosfs, for boxes which don't have it in their initramfs Some environment values in a FFP shell. (CHROOTDIR, FFPVERSION, FFPROOT) 2011-07-15: Fixed: FFPStick didn't work on NSA220, fw <2.30 Changed: Splitted usb_key_func.sh in two files: usb_key_func.sh and fun_plug.sh Sequence of bind-mounts, to get less clutter Repartitioning is now done while the firmware waits for usb_key_func.sh to exit Added: symlink /mnt/HD_a2 directory /sys 'crappy USB stick' support relatime or noatime remount of ext3 partition execute_outside_chroot function exit_ffp function 'dummy' symlinks to work around the firmware "rm ` find /mountpoint/of/stick -type l `" Options added (in after_booting.sh): Create a /ffp symlink in rootfs do not chroot ffp change the root password when not chrooted add users (and specify password) when not chrooted 2011-03-23: The adjustment of 2011-03-09 contained a bug, which is fixed in this version 2011-03-09: Solved this issue: http://zyxelforum.de/ffp-stick-telnet-funzt-nicht--t1867.html On a NSA-320 without NFS installed, a symlink /etc/exports exists which points to nothing. 2010-12-21: Solved this issue: http://zyxelforum.de/nsa320-ffp-raid1-mounten-t1845.html On a NSA-320 only user-defined shares were available, the default shares didn't work in combination with the FFPstick. 2010-11-09: Tried to solve the issue from this thread: http://forum.nas-central.org/viewtopic.php?f=228&t=2181 2010-11-02: Initial release of 3rd generation FFP-stick