Entware Installation on DD-WRT: Difference between revisions

No edit summary
No edit summary
Line 53: Line 53:
</syntaxhighlight><br />
</syntaxhighlight><br />


* Next, save the following as a StartUp Script;<syntaxhighlight>
*Next, save the following as a StartUp Script;<syntaxhighlight>
mount -o bind /opt/ModifiedProfile /etc/profile
mount -o bind /opt/ModifiedProfile /etc/profile
sleep 1
sleep 1
/opt/etc/profile
/opt/etc/profile
</syntaxhighlight>I know I said I wouldn't explain things in  
</syntaxhighlight>I know I said I wouldn't explain things in


* I know I promised  
*I know I promised


===OpenWRT Choice===
===OpenWRT Choice===
Of course you could always install OpenWRT instead of DD-WRT and none of the above is necessary.  But that opens a whole new can of worms with different problems.  For instance, installing the latest (as of 1.2020) version of OpenWRT on a Linksys WRT3200ACM router, which is at the very top end of DD-WRT / OpenWRT hardware, there is no facility within the GUI as it is initially installed to mount, share, or do anything with a USB or eSATA drive.  All of that functionality, which has to be added to OpenWRT via a command line is available from DD-WRT right out of the box.  Once you know what you're doing, both firmware choices are equally configurable, in an equally easy fashion, in their own unique ways, each with their own advantages and disadvantages.  Apples and Oranges.  Your choice.
Of course you could always install OpenWRT instead of DD-WRT and none of the above is necessary.  But that opens a whole new can of worms with different problems.  For instance, installing the latest (as of 1.2020) version of OpenWRT on a Linksys WRT3200ACM router, which is at the very top end of DD-WRT / OpenWRT hardware, there is no facility within the GUI as it is initially installed to mount, share, or do anything with a USB or eSATA drive.  All of that functionality, which has to be added to OpenWRT via a command line is available from DD-WRT right out of the box.  Once you know what you're doing, both firmware choices are equally configurable, in an equally easy fashion, in their own unique ways, each with their own advantages and disadvantages.  Apples and Oranges.  Your choice.
=== Other Thoughts ===
Even though it never seems to be explicitly stated, NVRAM and JFFS sizes are determined by the hardware's capabilities and set in the firmware.  Both NVRAM (where startup scripts and commands are stored) and JFFS content are stored on the flash chips inside the router.  But what if I don't want to use JFFS and want to increase available NVRAM.  I haven't found a way to decrease the amount of flash memory allocated or reserved for to / for JFFS (even if it isn't utilized) and reallocate it to NVRAM.  Both are stored on the flash chips in the router, so this is completely valid thought from a technical perspective.  However, because the size of each storage area seems to be hard coded in the firmware (which I sort of confirmed by researching and finding anecdotal comments that implied these limits are set in firmware, but nothing explicit), one is SOL if one wants to change the settings.  For my WZR-600DHP router, there is 64 KB of NVRAM and just under 20 MB of JFFS storage space available.  64K of storage is all of the RAM my Commodore 64K had.  It seemed like so much then, and thinking about it now, they really made efficient use of that small amount of RAM (large in those days).  Ah, the good 'ole days, but I digress.


<br />
<br />