EBC Exercise 27 BusyBox
We'll attack getting BusyBox like we did getting the kernel (ECE497 Lab02 Installing The Angstrom Distribution) though the paths will be slightly different. Make sure you have commented out
# INHERIT += " rm_work "
in the local.conf file. See ECE497 Lab02 Installing The Angstrom Distribution for details.
Check and see what you already have for previous installations:
$ source ~/.oe/environment-2008 $ time bitbake busybox $ cd ~/BeagleBoard/oe/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi $ ls
My bitbake took about 3 minutes to download and compile.
When you did ls did you see BusyBox? I didn't. Do this to find it:
$ cd ~/BeagleBoard/oe/build/tmp-angstrom_2008_1/work $ find . -name "*busybox*"
The find command will find all files and directories that contain the name
BusyBox is not a Beagle specific compile, so it appears in a different location. Change to the BusyBox directory and look around. Can you find the source? Hint: they aren't in a git directory.
You can now configure BusyBox.
After saving the configuration changes to update the .config file, it is a simple matter of running make.
My make took about 1 minute to compile.
Copy it to your Beagle and test it out. Just typing busybox will tell you what commands it knows. Try some of them.
$ busybox $ busybox ls
For extra fun try.
$ busybox httpd
Yup, you are now running a web server. Your task is to figure out where to put the web pages it is serving. If you get something interesting going post your Beagle's address here.
|mr814.dhcp.rose-hulman.edu||Mark A. Yoder||My first Beagle web page.|
How big is the busybox file? Try making it smaller by removing commands you don't use. How big is it if you just have ls? How much bigger is it when you add httpd? Try your own combinations. Report your findings to the class.