Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hello All!
First post here...thanks for all the GREAT info everyone has contributed to make these DNS-3xx hacks possible!
Also, big THANKS to fonz for his major contributions.
I have a DNS-321 with ffp 0.5 and have read about and observed certain files/folders that seem to be overwritten after reboot.
One solution I have seen is to create a startup script that copies your custom versions back to their pre-reboot locations.
Personally I have seen this after adding a new user, creating a home directory/password/etc and running store-passwd.sh...and the changes don't seem to stick after reboot.
My Questions:
Is there a list compiled of which files/folders will need to be re-copied after reboot?
Is there any explanation as to why this happens?
I was looking into using DebNAS...can anyone confirm if this issue is present with it as well?
Here's my list so far, with sources in parenthesis:
- /etc/hosts (http://eldapo.lembobrothers.com/2010/07 … me-server/)
- /etc/resolv.conf (http://eldapo.lembobrothers.com/2010/07 … me-server/)
- /etc/services (http://eldapo.lembobrothers.com/2010/07 … me-server/)
- ? added user's home directory (my experience + http://dns323.kood.org/forum/viewtopic.php?id=4822)
- /ffp/etc/sshd_config (coment by 'andy' http://nas-tweaks.net/40/installation-o … many-more/)
Offline
Everything, besides the files stored on the HDDs you stick into the DNS-323 is stored on some non-volatile memory. When the DNS-323 boots, it loads it all into memory. If you change any of those, it appears as if you're manipulating files but it's all happening in memory, but the contents of that non-volatile memory does not change. That's why after a reboot or power-cycle it all reverts back.
This is called a RAM Drive (http://en.wikipedia.org/wiki/RAM_disk).
No need to build a list, this includes everything besides the stuff under /mnt/HD_a2 and /mnt/HD_b2 (or wherever you mount your HDDs or USB storage).
Offline
All executable scripts in /ffp/start/ are invoked during the boot, so this is the conventional place to put scripts that will modify the initial state of the root filesystem (for example to add new crontab entry).
Offline
Interesting...Thanks for the quick response!
So the RAM disk is the 2x32MB RAM, which is loaded up using the 8MB ROM at boot? Does it serve double duty as a RAM disk and regular main memory RAM for the kernel?
If I'm understanding you right, basically EVERY configuration/change you make to the system needs to be done by a startup script(s), if you want those changes to stick after a reboot.
Except of course, the files you save by invoking store-passwd.sh:
/etc/passwd
/etc/group
/etc/shadow
/etc/samba/smbpasswd
Cheers, JF
Offline
Since I started to use ffp I haven't encountered many situations in which I'd need to tweak the original configuration. When I'm not satisfied with a piece of built-in software I install a version from a ffp package, which is usually newer and can be configured according to my needs.
Offline