Entware Installation on DD-WRT: Difference between revisions

Line 65:

</syntaxhighlight>I know I said I wouldn't explain things, but it needs to be said for the above short script. The mount command effectively replaces the DD-WRT version of the profile file (this is the BASH login script for users). The rc.unslung start command is what the Entware installation script said to add to the Startup Script. RC.UNSLUNG starts all the installed services for Entware.

* The first useful item to install is an updated version of BusyBox (Google it). Use the below commands<syntaxhighlight lang="abap">

*The first useful item to install is an updated version of BusyBox (Google it). Use the below commands<syntaxhighlight lang="abap">

opkg update

opkg install busybox

Line 77:

===Other Thoughts===

If you're like me and working from Windows and also like to take advantage of all those nice little GUI perks like network file sharing (SAMBA in the linux) world, there's one thing (well, lots, but just pointing out one here) to watch out for. Do not create a script file in Windows via a shared network directory on the router and expect it to run as a bash login script. It won't work. Also there are differences in text files including 'carriage return / line feed' in Windows and just 'line feed' in Linux among several others that will prevent the Linux OS from "reading" the script file properly, so don't edit in notepad. Once the file is created in Linux (or copied from another Linux OS) editors like TextPad work great.

To create a zero byte file with DD-WRT's built in VI command, do the following: type vi WhatEverNameOfFile to start the editor, within VI type :x (that's a colon followed by an x), then press enter. That file can be edited via a shared network directory with a program like TextPad.

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.

@@ Line 65: / Line 65: @@
 </syntaxhighlight>I know I said I wouldn't explain things, but it needs to be said for the above short script.  The mount command effectively replaces the DD-WRT version of the profile file (this is the BASH login script for users).  The rc.unslung start command is what the Entware installation script said to add to the Startup Script.  RC.UNSLUNG starts all the installed services for Entware.
-* The first useful item to install is an updated version of BusyBox (Google it).  Use the below commands<syntaxhighlight lang="abap">
+*The first useful item to install is an updated version of BusyBox (Google it).  Use the below commands<syntaxhighlight lang="abap">
 opkg update
 opkg install busybox
@@ Line 77: / Line 77: @@
 ===Other Thoughts===
 If you're like me and working from Windows and also like to take advantage of all those nice little GUI perks like network file sharing (SAMBA in the linux) world, there's one thing (well, lots, but just pointing out one here) to watch out for.  Do not create a script file in Windows via a shared network directory on the router and expect it to run as a bash login script.  It won't work.  Also there are differences in text files including 'carriage return / line feed' in Windows and just 'line feed' in Linux among several others that will prevent the Linux OS from "reading" the script file properly, so don't edit in notepad.  Once the file is created in Linux (or copied from another Linux OS) editors like TextPad work great.
+To create a zero byte file with DD-WRT's built in VI command, do the following: type vi WhatEverNameOfFile to start the editor, within VI type :x (that's a colon followed by an x), then press enter.  That file can be edited via a shared network directory with a program like TextPad.
 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.