Esther Fuhrmann
Jump to navigation
Jump to search
Toolchain
- Siehe BRN::Development::Toolchain (Mathias' Method)
Kernel
- Siehe BRN::Development::Kernel
- ab dem zweiten Mal: schneller compilieren
build.sh editieren
wichtig ist das "ccache\ "
#! /bin/sh make CROSS_COMPILE=mipsel-linux- CC=ccache\ mipsel-linux-gcc
madwifi.stripped
- build.sh
#!/bin/sh make TARGET=mips-le-elf KERNELPATH=$HOME/projects/brn/madmax/mips/kernel CC=ccache\ mipsel-linux-gcc
Click Kernelmodul bauen
- Kernel kompilieren (build.sh)
- Click kompilieren (erst conf_mips.sh, Warning ignorieren, cd linuxmodule/, make)
- im Verzeichnis linuxmodule: build.sh editieren
#! /bin/sh make TARGET=mips-le-elf CROSS_COMPILE=mipsel-linux- CC=ccache\ mipsel-linux-gcc
Click Modular Router
- Click Modular Router Homepage
- Click Modular Router, Eddie Kohler. Ph.D. thesis
- Dokumente zu Click von der PATS Research Group
Wer macht ähnliches?
checkout.sh
#!/bin/sh path=$HOME echo "Creating directories" mkdir -p $path/projects/brn/openwrt mkdir -p $path/projects/brn/madmax mkdir -p $path/projects/brn/madmax/mips/click mkdir -p $path/projects/brn/madmax/mips/kernel mkdir -p $path/projects/brn/madmax/mips/madwifi mkdir -p $path/projects/brn/madmax/mips/madwifi.stripped mkdir -p $path/projects/brn/madmax/mips/brn mkdir -p $path/projects/brn/madmax/x86 # checkout echo "Checking out" svn co svn://merkur/brn/archives/click-20051012/ $path/projects/brn/madmax/mips/click svn co svn://merkur/brn/platform/wgt634u/brn/src $path/projects/brn/madmax/mips/click/elements/brn svn co svn://merkur/brn/archives/madwifi-20051013/ $path/projects/brn/madmax/mips/madwifi svn co svn://merkur/brn/archives/madwifi_stripped-20051015/ $path/projects/brn/madmax/mips/madwifi.stripped svn co svn://merkur/brn/archives/linux-kernel-2.6.12-rc3/ $path/projects/brn/madmax/mips/kernel svn co svn://merkur/brn/platform/wgt634u/brn/ $path/projects/brn/madmax/mips/brn echo "Copying sources to x86 directory" cp -a $path/projects/brn/madmax/mips/click/ $path/projects/brn/madmax/x86/ #cp -a $path/projects/brn/madmax/mips/kernel $path/projects/brn/madmax/x86/ cp -a $path/projects/brn/madmax/mips/madwifi/ $path/projects/brn/madmax/x86/ cp -a $path/projects/brn/madmax/mips/madwifi.stripped/ $path/projects/brn/madmax/x86/ cp -a $path/projects/brn/madmax/mips/brn/ $path/projects/brn/madmax/x86/
How to (temporarily) set up a SDP independent from the running one
- First build everything for the new SDP. To do so, follow Bernhard's description, BUT there are two important differences:
- Change BRN_NEIGHBOR_BEACON_MAGIC in <YOUR_BUILD_DIR>/click/include/clicknet/brn.h to a unique value. (Otherwise there will be problems with an existing SDP!)
- Don't deploy your new package in the last step
- Then the following has to be done for every node that is part of the new SDP infrastructure
Put the new software onto the WGT
scp -r <YOUR_BUILD_DIR>/sdp/package/library/0 root@<wgt_to_be_changed>:/tmp/sdp/library/
Then telnet to the WGT and execute the following commands
killall S90sdp /usr/sbin/rcclick stop killall click echo 0 > /tmp/sdp/current_id rm /tmp/sdp/current ln -s /tmp/sdp/library/0 /tmp/sdp/current /usr/sbin/rcclick start /tmp/sdp
Now the new SDP should be running and you should be able to deploy software on "your" nodes without affecting the other ones. To get rid of it and restore the original SDP (the SDP the rest of the testbed is running) just reboot the WGT.