Re: [uClinux-dev] small but powerful init and shell processes
You can build busybox with just 'msh' and 'test' configured, no other applets, then it's much smaller. Of course you'll only activate the busybox features that actually are needed. If you have XIP, there is still a significant reduction from doing this, because the data section is much smaller. Of course you are right here but as only part of the data sections needs to be I initialized, I suppose the effect will be significantly smaller that what you see without XIP. -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
[uClinux-dev] small but powerful init and shell processes
Hi, I'm looking for a combination of init and shell that does not result in serious memory fragmentation and is powerful enough to execute scripts with conditions, run applications in background and start shell on a serial console upon request. I've tried to use simpleinit + sash from uClinux distribution and busybox. First combination is tiny but sash has problems with conditions and starting applications in background. Busybox is nice but fat. It becomes noticeable when several copies are loaded into memory: init, getty and shell. Any suggestions? -- Best regards, Andrei mailto:andrei.marty...@web.de ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] small but powerful init and shell processes
First combination is tiny but sash has problems with conditions and starting applications in background. sash in fact can't do conditions but AFAIK there is no problem with starting applications in background by appname Busybox is nice but fat. It becomes noticeable when several copies are loaded into memory: init, getty and shell. if your arch does not support XIP, busybox in fact is loaded multiple times. this might be a problem. That is why in my projects, I don't use msh from busybox as default shell. You could use sash as default shell and msh from busybox when appropriate. See http://www.nioswiki.com/Initialization_Script -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] small but powerful init and shell processes
Michael Schnell wrote: if your arch does not support XIP, busybox in fact is loaded multiple times. this might be a problem. That is why in my projects, I don't use msh from busybox as default shell. You could use sash as default shell and msh from busybox when appropriate. See http://www.nioswiki.com/Initialization_Script You can build busybox with just 'msh' and 'test' configured, no other applets, then it's much smaller. If you have XIP, there is still a significant reduction from doing this, because the data section is much smaller. -- Jamie ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
