how to build busybox for a thin client system

[Joey S. Eisma]

David Seikel wrote:
> 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.
>   
yep. i noticed the sizes, where is that option to do hard links?

thank you!

joey