how to build busybox for a thin client system

David Seikel won_fang at yahoo.com.au
Thu Aug 3 09:17:59 UTC 2006


On Thu, 03 Aug 2006 17:10:16 +0800 "Joey S. Eisma"
<jeisma at pimes.com.ph> wrote:

> hi!
> 
> a thin client system that uses busy box has on its package
> directories, contain these files:
> 
> -rwxr-xr-x  1 admin admin 242344 2006-07-14 11:53 [
> -rwxr-xr-x  1 admin admin 242344 2006-07-14 11:53 ash
> -rwxr-xr-x  1 admin admin  10632 2006-07-14 11:53 aumix
> -rwxr-xr-x  1 admin admin 242344 2006-07-14 11:53 awk
> -rwxr-xr-x  1 admin admin 242344 2006-07-14 11:53 basename
> -rwxr-xr-x  1 admin admin 242344 2006-07-14 11:53 busybox

<snip>

> i believe these are all forked from busybox, how do i build busybox
> to be able to have the same set of files?
> 
> what im really trying to do is to have udhcpc be able to use ports
> other than the standard 67/68. have already made changes 
> networking/udhcp/dhcpd.h to use ports 1067/1068. now i need to
> overwrite the the existing udhcpc. running "make defconfig" only
> created a single "busybox" binary. i need to have the same structure
> as above, hoping not to break the thin client system.

Note how most of those are the exact same size as busybox?  They are
hard linked to it.  So hard link things to your new busybox.  Busybox
has an install option that does that for you.

-- 
Stuff I have no control over could be added after this line.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20060803/2da0d35a/attachment-0002.pgp 


More information about the busybox mailing list