From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4485E647.7010205@domain.hid> Date: Tue, 06 Jun 2006 14:32:07 -0600 From: Jim Cromie MIME-Version: 1.0 Subject: Re: [Xenomai-core] Porting xeno-{info|load|test} to a busybox system References: <200605252134.08614.niklaus.giger@domain.hid> <44770814.5040009@domain.hid> <200605261852.45980.niklaus.giger@domain.hid> In-Reply-To: <200605261852.45980.niklaus.giger@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: niklaus.giger@domain.hid Cc: Jan Kiszka , xenomai@xenomai.org Niklaus Giger wrote: > Am Freitag, 26. Mai 2006 15:52 schrieb Jan Kiszka: > >> Niklaus Giger wrote: ... >> If anybody has a working target with a Xenomai + BusyBox combination and >> would be willing to test drive my changes, I would appreciate a feedback >> enormously. >> I hope this isnt waiting on my 'approval'. I think its a great idea, and has been on my (way too stagnant) list for a while. Your work has at least urged me to install busybox on my xeno-box. ;-) My only concern is whether we've sufficiently distinguished the issues: 1 - ash vs bash Its not entirely clear to me which flavors of sh busybox has: ash / dash / not-bash I gather u worked with ash, and it seems most valuable sh features work there just fine ( shell-functions, even 'job-control' of a fashion) 2 - busybox 'executables' only I coded in a lot of 'full linux' gimme's, like zgrep, script, etc. Niklaus has repaired many of these. I think a more thorough cleanup is possible, esp if things like 'script' are jettisoned for a simpler shell-functions or helper scripts. This all implies a re-write, which is on my list... (esp the job-control testing and repair)