p.s. why is "original" folder is there? does it get ignored by the script?
It's due to the chrooted nature of your FFP. FFP needs a directory or symlink /ffp, and on my NSA220 / was readonly, actually the rootfs was a squashfs in flash.
So to be able to get a /ffp, I had to chroot it, which means ffp 'sees' another / than the firmware does. (chroot means CHange ROOT).
A large part of the firmware tree is more or less visible by an complicated system of mounts, symlinks and bindmounts.
And due to a reason I cannot remember at the moment, I couldn't put the firmware /etc in /etc, so it's in /ffp/etc/original. But for the firmware it's still /etc!
Maybe chrooting is no longer necessary on the latest firmware. You can try to edit the header of after_booting.sh. There is a variable CHROOT=auto, you could change that in CHROOT=no. After a reboot the stick will try
to not chroot, and fallback on chroot if that fails. ffpboot.log can tell you.
If you want to try this, make sure your loginless telnet daemon still works, as I have no idea if you will be able to login over ssh. In unchrooted state the firmware /etc/passwd is in charge.
httpd: Could not open configuration file /usr/local/apache2/conf/httpd.conf: No such file or directory
I guess that directory is somehow included (maybe indirect) in one of the conf file. Try to find and follow all includes.
-- how do I execute httpd and tell it to restart? Or how do I restart apache so it would start 2 instances?
The idea is that you and the firmware maintain their own instance of httpd. So the firmware uses it's own startscript, and you yours. About restarting, well, have a look if you can tell apache to create a pid file. In that fill the daemon writes it's pid, so you know who to kill. Something like
if [ -e /ffp/run/httpd ] ; then
kill ` cat /ffp/run/httpd `
-- in my copy of httpd_zld, how do I specify to use some folder from the hard drive and not from ffp stick?
By specifying a document root on harddisk?
-- what will happen to the edited httpd.sh and my copies of httpd.conf and httpd_zld.conf after I reboot NAS?
Nothing. You copied them to /ffp/etc/, which is safely on stick. (With exception of /ffp/etc/original/)