summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkaloz <kaloz@3c298f89-4303-0410-b956-a3cf2f4a3e73>2011-02-11 14:04:00 +0000
committerkaloz <kaloz@3c298f89-4303-0410-b956-a3cf2f4a3e73>2011-02-11 14:04:00 +0000
commitaba0269ef0ed00ed207ee5dc7a46700cc5ade4c1 (patch)
tree928cc371a3d3459c4af26f010eb11788b7d7d089
parent4ac384525980f1e857d3e68c5b4a0ababc08e6d3 (diff)
[docs]: kamikaze has been released long ago
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25464 3c298f89-4303-0410-b956-a3cf2f4a3e73
-rw-r--r--docs/build.tex7
-rw-r--r--docs/network.tex2
2 files changed, 4 insertions, 5 deletions
diff --git a/docs/build.tex b/docs/build.tex
index 6828a2318..6e1539acf 100644
--- a/docs/build.tex
+++ b/docs/build.tex
@@ -41,11 +41,10 @@ So let's take a look at OpenWrt and see how this all works.
\subsubsection{Download OpenWrt}
-This article refers to the "Kamikaze" branch of OpenWrt, which can be downloaded via
-subversion using the following command:
+OpenWrt can be downloaded via subversion using the following command:
\begin{Verbatim}
-$ svn checkout svn://svn.openwrt.org/openwrt/trunk kamikaze
+$ svn checkout svn://svn.openwrt.org/openwrt/trunk openwrt-trunk
\end{Verbatim}
Additionally, there is a trac interface on \href{https://dev.openwrt.org/}{https://dev.openwrt.org/}
@@ -88,7 +87,7 @@ $ ./scripts/feeds update
Those packages can be used to extend the functionality of the build system and need to be
symlinked into the main trunk. Once you do that, the packages will show up in the menu for
-configuration. From kamikaze you would do something like this:
+configuration. You would do something like this:
\begin{Verbatim}
$ ./scripts/feeds search nmap
diff --git a/docs/network.tex b/docs/network.tex
index 793a39822..e4efd8df9 100644
--- a/docs/network.tex
+++ b/docs/network.tex
@@ -1,4 +1,4 @@
-The network configuration in Kamikaze is stored in \texttt{/etc/config/network}
+The network configuration is stored in \texttt{/etc/config/network}
and is divided into interface configurations.
Each interface configuration either refers directly to an ethernet/wifi
interface (\texttt{eth0}, \texttt{wl0}, ..) or to a bridge containing multiple interfaces.