EBC Exercise 27 BusyBox - Revision history

Draneaw: /* configuring */

2012-11-08T05:26:21Z

‎configuring

Correlbn: /* Running a Web Server */

2012-11-06T18:17:07Z

‎Running a Web Server

Yoder at 14:12, 22 October 2012

2012-10-22T14:12:22Z

Yoder: /* Compiling BusyBox */

2012-10-22T14:04:43Z

‎Compiling BusyBox

Yoder: /* via bitbake */ Removed

2012-10-22T14:04:05Z

‎via bitbake: Removed

Yoder: /* Static Linking */

2012-10-19T20:38:32Z

‎Static Linking

Yoder: /* Configuring BusyBox */

2012-10-19T20:30:14Z

‎Configuring BusyBox

Yoder: /* Compiling BusyBox */ Added git instructions

2012-10-19T20:28:48Z

‎Compiling BusyBox: Added git instructions

Yoder: /* Compiling BusyBox */ Updated for Fall 2012

2012-10-19T18:20:06Z

‎Compiling BusyBox: Updated for Fall 2012

Yoder: /* Compiling BusyBox */

2012-10-19T18:17:05Z

‎Compiling BusyBox

@@ Line 19: / Line 19: @@
 === configuring ===
-You can now configure BusyBox.
+You can now configure BusyBox (In the event that none of the graphical tools work you can use "make config" to use the text based tool as a method of last resort).
   host$ '''make gconfig'''
 After saving the configuration changes to update the .config file, it is a simple matter of running make.
   host$ '''make -j9'''

@@ Line 53: / Line 53: @@
   beagle$ '''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. Hint: find httpd.c.
+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. Hint: find httpd.c.
 {{YoderFoot}}

@@ Line 3: / Line 3: @@
 {{YoderHead}}
-== Downloading and Compiling BusyBox ==
+== Getting BusyBox ==
 Get the busybox sources from the busybox site
@@ Line 9: / Line 10: @@
   host$ '''git clone git://busybox.net/busybox.git'''
   host$ '''cd busybox'''
   host$ '''source ~/.oe/crossCompileEnv.sh'''
   host$ '''make help'''
@@ Line 14: / Line 17: @@
   host$ '''make -j9'''       # use -j''X'' for ''X-1'' cores
-== Configuring BusyBox ==
+=== configuring ===
 You can now configure BusyBox.
@@ Line 26: / Line 29: @@
 My make took about 1.5 minutes to compile (25 seconds with make -j8!).
 Copy it to your Beagle and test it out.  Just typing '''busybox''' will tell you what commands it knows.  Try some of them.
   host$ '''scp busybox root@beagle:.'''
@@ Line 33: / Line 37: @@
 Try some other commands...
-== Shrinking BusyBox ==
+== Playing with BusyBox ==
-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.
+=== shrinking ===
-== Static Linking ==
+How big is the '''busybox''' file?  The default configuration for busybox has it many things (some 400).  Reconfigure it to do just the commands you use.  How big is it now? 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 in your status report.
 Some embedded systems are so small they don't have shared libraries.  Recompile busybox to be statically linked. (Hint: look in configuration) How big it is?  Does it still work?
-== Running a Web Server ==
+=== Running a Web Server ===
-Configure busybox to be a web server. Look under '''Networking Untilites''', select '''httpd'''.  How much more space does it take?
+Configure busybox to be a web server. Look under '''Networking Utilites''', select '''httpd'''.  How much more space does it take?
   beagle$ '''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. Hint: find httpd.c.
 {{YoderFoot}}

@@ Line 3: / Line 3: @@
 {{YoderHead}}
-== Compiling BusyBox ==
+== Downloading and Compiling BusyBox ==
-===via git ===
 Get the busybox sources from the busybox site

@@ Line 13: / Line 13: @@
   host$ '''make defconfig'''
   host$ '''make -j9'''       # use -j''X'' for ''X-1'' cores
 == Configuring BusyBox ==

← Older revision		Revision as of 20:28, 19 October 2012
Line 4:		Line 4:

	== Compiling BusyBox ==		== Compiling BusyBox ==
		+	===via git ===
		+	Get the busybox sources from the busybox site
		+
		+	host$ '''git clone git://busybox.net/busybox.git'''
		+	host$ '''cd busybox'''
		+	host$ '''source ~/.oe/crossCompileEnv.sh'''
		+	host$ '''make help'''
		+	host$ '''make defconfig'''
		+	host$ '''make -j9''' # use -j''X'' for ''X-1'' cores
		+
		+	=== via bitbake ===

	We'll attack getting BusyBox like we did getting the kernel ([[EBC Exercise 01 Using bitbake for Kernel and U-boot]]) though the paths will be slightly different. Make sure you have commented out		We'll attack getting BusyBox like we did getting the kernel ([[EBC Exercise 01 Using bitbake for Kernel and U-boot]]) though the paths will be slightly different. Make sure you have commented out

@@ Line 15: / Line 15: @@
   host$ '''source  ~/.oe/environment-oecore'''
   host$ '''time bitbake busybox'''
-  host$ '''cd ~/BeagleBoard/oe/build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi'''
+  host$ '''cd ~/BeagleBoard/oe/build/tmp-angstrom_v2012_05-eglibc/work/beagleboard-angstrom-linux-gnueabi'''
   host$ '''ls'''
@@ Line 22: / Line 22: @@
 When you did ''ls'' did you see '''BusyBox'''?  I didn't.  Do this to find it:
-  host$ '''cd cd ~/BeagleBoard/oe/build/tmp-angstrom_2010_x-eglibc/work'''
+  host$ '''cd cd ~/BeagleBoard/oe/build/tmp-angstrom_v2012_05-eglibc/work'''
   host$ '''find . -name "*busybox*"'''

@@ Line 18: / Line 18: @@
   host$ '''ls'''
-My bitbake took about 1.5 minutes to download and compile.
+My bitbake took about 4.5 minutes to download and compile.
 When you did ''ls'' did you see '''BusyBox'''?  I didn't.  Do this to find it: