[BusyBox] Enabling non-default programs

[Thomas Cameron]

Nick,
	These options are not turned off because of faultyness or low
quality.  These options are turned off because they are more specific to
a particular need.  For instance, when you run 'make menuconfig' in the
Linux kernel source directory, you'll notice many options not selected.
This is because they are not needed in a general sense.  Obviously, if
you need one of these components, you may enable them, and compile away.
You will find that BusyBox is a rather stable system, but keep in mind
that it is under constant development.  Anyway, just wanted to give my
$.02

---------------------------------------------
Thomas Cameron
CEI Systems
---------------------------------------------
"Everything I know, I learned from Open Source"


-----Original Message-----
From: Nick Popoff [mailto:busybox at tre.bloodletting.com] 
Sent: Monday, March 25, 2002 3:35 PM
To: busybox at busybox.net
Subject: [BusyBox] Enabling non-default programs



First off, I want to say that this project absolutely rocks.  I'm
creating a RH72 based 32Mb ide-flash image for my company and using
BusyBox has saved me a ton of time and has worked very well so far.

Right now I'm filling in the blanks of programs I need for my image that
BusyBox didn't provide, and I just noticed that it supports a number of
things like ifconfig but does not compile them in by default.  Should I
be scared to enable them?  Are they turned off by default because they
aren't yet ready as good replacements for "real" program?  I'd love to
be able to just turn them all on but I don't want to discover later that
that was a bad idea. :-)  Any advice would be much appreciated.  Thanks
again...

-Nick

_______________________________________________
busybox mailing list
busybox at busybox.net http://busybox.net/mailman/listinfo/busybox