Dokumentacja

NewsForge: FSF Reaches Out to Social Activists
2006 may be remembered as the year that the Free Software Foundation (FSF) reached out to the community...

Wolfmanz Bytes: Ubuntu and TeamSpeak 2
In the last week or so I made a move from Kubuntu over to Ubuntu. I did this because I was going to give XGL/Compiz a try...

InfoWorld: Open Source Risky? Nah. Just If You Hire an Attorney Who Doesn't Grok It
I came across this opinion piece by Paul Barton, an attorney at Field Fisher Waterhouse LLP today. I wish he would have attended the Open Source Business Conference before writing his piece...

SearchOpenSource: Open Source Servers Serve Up Challenges
As an experiment, I recently set out to install Mambo, an open source content management system, on a PC running Windows XP Professional...

LinuxDevices: Skype Debuts Linux-Powered Cordless Phone
Skype on Aug. 31 introduced a pair of cordless VoIP phones that work without being connected to a computer, via a DECT basestation that attaches directly to broadband and POTS lines...

next: building curses and dialog up: making linux installation disks previous: building uclibc contents

building busybox

first cd into the $myboot/busybox-0.60.5 subdirectory.

edit the file conf.h as follows:

add or remove support for programs you do or do not want. for each program there is a #define bb_xxx line that can be commented out or not. i uncommented the following lines, some of these commands are expected to be useful in install scripts, others are necessary for network access or modules and of course i wanted the vi editor: bb_cmp, bb_expr, bb_ifconfig, bb_insmod, bb_ping, bb_rmmod, bb_route, bb_vi and bb_wget.
add or remove features that you do or do not want by uncommenting or commenting th corresponding feature line. i uncommented the following: bb_feature_use_termios, bb_feature_mount_nfsmount and bb_feature_ifconfig_status.

edit the makefile as follows:

uncomment the cc= line below the comment about uclibc and change it to cc=${myboot}/uclibc-dev/bin/gcc
you could enable lfs support, as it is already selected in uclibc as well.

now build the program.

 make make prefix=$myboot/rootfs install

because you have linked with the dynamic uclibc library and these are not installed in the host system's /lib directory, the program cannot run. there is a trick to work around it: by using the chroot command, you can run a program whose root directory is the specified directory. become root and type the following command:

 /usr/sbin/chroot $myboot/rootfs /bin/sh

the shell that you are now in is the shell inside the $myboot/rootfs directory. this shell thinks that this rootfs directory is in fact the root directory: even the shared libraries of uclibc in the /lib directory will be found. type the command ls / and it will be clear. exit the chroot subshell with control-d and everything will be back to normal.

now you have most common unix utilities including an editor and a shell and you've spent only 614kb of disk space!

next: building curses and dialog up: making linux installation disks previous: building uclibc contents

lennart benschop 2003-07-16

Linux FAQ's & Manuals

building busybox