>>>> tito <[email protected]> 26.06.14 14.33 Uhr >>>
  p, li { white-space: pre-wrap; }  >On Thursday 26 June 2014 14:05:34 Frank 
Ihle wrote:
 >> Dear BusyBox,
 >> 
 >> due to we consider about using BusyBox on our Embedded System, I have some 
 >> questions left whose answers couldn't be found on the BusyBox >homepage or 
 >> documentation. 
 >> 
 >> I hope somebody can give me a bit more information, probably these 
 >> questions/answers could be put on the BusyBox homepage, since I think >that 
 >> other developers trying to get into touch with BusyBox are interested in 
 >> these kind of information too.
 >> 
 >> Here are the questions:
 >> 
 >> (1) What is the minimum footprint in flash memory of BusyBox ?
 >Footprint depends on the build: statically or dynamically linked
 >and on the number of features and/or appletts you compile in.


Yes that's right, but that's why I was asking about the minimum footprint - 
let's say when statically linked. I just try to get some kind of "offical" 
numbers, since many people talk about it's small footprint.



 >> (2) Is there a number for the latency to handle events (e.g. interrupt 
 >> latency) ?
 >Don't know.
 >> (3.1) Is there an investigation about power consumption with BusyBox during 
 >> sleep modes ?
 >Don't know.
 >> (3.2) Is there an investigation about power consumption with BusyBox during 
 >> normal/(full) operation mode?
 >Don't know.
 >> (4) Are sleep modes configurable ?
 >Don't know.
 >> (5) How many GPIO user out/inputs can be used e.g.: for user interaction 
 >> (buttons, LEDS, dip-switches ...) ?
 >I think this is not related to busybox
 >> (6) Is there a (stateless/statefull) firewall for BusyBox ?
 > think this is not related to busybox. Use iptables?
 >> (7.1) Does BusyBox provide a Network stack ?
 >Run: make menuconfig
 >and look under Networking utilities


Alright, according to my question, is the answer in this Thread 
(http://stackoverflow.com/questions/19349923/tcp-ip-stack-in-busybox) then 
wrong? There they say there is no TCP/IP stack in BusyBox.


 >> (7.2) Does BusyBox provide a Bluetooth stack ?
 >>Would say no.
 >> (7.3) Does BusyBox provide a ZigBee stack ?
 >Would say no.
 >> (7.4) Does BusyBox provide a ZWave stack ?
 >Would say No.
 >> (7.5) Does Busybox provide a 6LOWPAN stack ?
 >Wouls say no.
 >> (8.1) Due to BusyBox seems to be written in C, is it still possible to 
 >> execute a C++ application successfully ?
 >Yes, If your system has the relevant c++ libraries.
 >> (8.2) Is it possible to execute a Java application ?
 >Yes, if your system has the relevant java runtime environment.
 >> (9) Can applications be debugged while they are executed on the target ?
 >Yes, with strace and/or by enabling Busybox Settings -> Debugging options  at 
 >compile time. 
 >> (10) What is the long-term availability of BusyBox? Can it be expected to 
 >> be available for at least 10 years ?
 >You download the source, you will have it forever.


Maybe I should have asked differently: will BusyBox be developped and supported 
in future or e.g.: will there be a successor program and therefore BusyBox 
would be left on a final state ?



 >> (11) Is remote login to a target possible, that is running with BusyBox? 
 >> (e.g. with telnet or SSH) 
 >Telnet yes. SSH only if you install a separate SSH server (e.g. Dropbear)
 >> I apologize for questions, that may have already been answered. Thanks for 
 >> your help.
 >> 
 >> Kind Regards
 >> 
 >> Frank Ihle
  
 >Hope this helps.


Yes it did, many thanks

_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to