KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

add documentation fixes from #1285

Browse source 
SVN-Revision: 6319
This commit is contained in:
Felix Fietkau 2007-02-18 16:46:46 +00:00
parent 912e5867ef
commit 4941b6c4bd
2 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/adding.tex
View file

@ -121,15 +121,15 @@ Scroll over the firmware to find printable words that can be significant.
\subsubsection{Amount of flash memory} \subsubsection{Amount of flash memory}
Linux can hardly fit in a 2MB flash device, once you have open the device and Linux can hardly fit in a 2MB flash device, once you have opened the device and
located the flash chip, try to find other the Internet its characteristics. If located the flash chip, try to find its characteristics on the Internet. If
your flash chip is a 2MB or less device, your device is most likely to run a your flash chip is a 2MB or less device, your device is most likely to run a
proprietary OS such as WindRiver VxWorks, or a custom manufacturer OS like Zyxel ZynOS. proprietary OS such as WindRiver VxWorks, or a custom manufacturer OS like Zyxel ZynOS.
OpenWrt does not currently run on devices which have equal or less than 2MB of OpenWrt does not currently run on devices which have 2MB or less of flash memory.
flash memory. This limitation will probably not be worked around since those This limitation will probably not be worked around since those devices are most
devices are most of the time micro routers, or Wireless Access Points, which are of the time micro-routers, or Wireless Access Points, which are not the main
not the main OpenWrt target. OpenWrt target.
\subsubsection{Pluging a serial port} \subsubsection{Pluging a serial port}
@ -140,8 +140,8 @@ easily notice if the device uses a Linux kenrel or something different.
\subsection{Finding and using the manufacturer SDK} \subsection{Finding and using the manufacturer SDK}
Once you are sure your device run a Linux based firmware, you will be able to start Once you are sure your device run a Linux based firmware, you will be able to start
hacking on it. If the manufacturer respect the GPL, it will have release with the hacking on it. If the manufacturer respected the GPL, it will have released a Sample
device, a Sample Development Kit. Development Kit with the device.
\subsubsection{GPL violations} \subsubsection{GPL violations}

4
docs/init-scripts.tex
View file

@ -24,8 +24,8 @@ This is done by the wrapper script \texttt{/etc/rc.common}.
script should provide. \texttt{start()} is called when the user runs \texttt{/etc/init.d/httpd start} script should provide. \texttt{start()} is called when the user runs \texttt{/etc/init.d/httpd start}
or (if the script is enabled and does not override this behavior) at system boot time. or (if the script is enabled and does not override this behavior) at system boot time.
Enabling and disabling init scripts is done by running \texttt{/etc/init.d/\textit{name} start} Enabling and disabling init scripts is done by running \texttt{/etc/init.d/\textit{name} enable}
or \texttt{/etc/init.d/\textit{name} stop}. This creates or removes symbolic links to the or \texttt{/etc/init.d/\textit{name} disable}. This creates or removes symbolic links to the
init script in \texttt{/etc/rc.d}, which is processed by \texttt{/etc/init.d/rcS} at boot time. init script in \texttt{/etc/rc.d}, which is processed by \texttt{/etc/init.d/rcS} at boot time.
The order in which these scripts are run is defined in the variable \texttt{START} in the init The order in which these scripts are run is defined in the variable \texttt{START} in the init