Wow, I've been around and around (e.g. BuC Dev. Guide, Chapter 1. 
Development) trying everything under the sun to get a busybox built - I 
did get it built using buildtool, but then observed that 1.2.x doesn't 
have the arp command which I assume was patched in. I was seeking the 
patch, in .svn land, I found the busybox config files, there was a 
folder for 1.00 but it was empty - the folder 0.60 had a .config but I 
figured it was too old... 
(http://leaf.cvs.sourceforge.net/leaf/src/bering-uclibc/configs/busybox/).

So here I am having given up on doing it myself :( asking the list if 
someone might compile a busybox with basically all the features 
active... then again I'm recalling that kernel module version checking 
tripped me up so I had to turn that off, and there were a couple of 
applets that wanted libm that I turned off... Is the thing to do here is 
provide someone the config file I ended up with?

Or maybe someone has already built something that's basically what I'm 
looking for ... the one applet I really wanted for my router was usleep, 
but I thought it'd be nice to have a more or less fully-featured busybox 
since I sometimes use a LEAF micro setup as a quickie drive management OS.

Or if I'm really close but just need some info or direction to do it 
myself - when I use my new busybox the bootup panics since it thinks 
that vars PKGPATH & LRP are empty (I'm sure they're not) ... and I'm 
missing the arp applet, etc :)

Thanks for any thoughts or help,
scott

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to