On 13.03.2015 10:30, Guillermo Rodriguez Garcia wrote:
There are many configuration options in BB that must be defined at
build time. I don't see why this one would be different.

You can activate both as the default (with cost of some byte overhead of code size), and let the user of the binary decide which mechanism he prefers, or even flip temporarily (without system interruption).


Users that want a functional solution will not probably care much
about the underlying implementation.

Exactly that means, using only one mechanism, is forcing those users to do it in a specific way, with all sort of consequences.

Those who want to tailor BB to fit their preferences most likely don't have a 
problem with building
their own BB.

Ok, and what's than wrong with my intended approach? You will be able to opt out most of the parts, if you like, even the parser / handler (think of you want to handle device management in a script without reinventing the event plug mechanism). It is a modular system, just tie those functions together you like.

A device handler could be:

#!/bin/sh
while read -tTIMEOUT message
  do
    # now split the received message
    ...
    # and setup your device node entries
    ...
  done
exit 0

... or think vise versa: Let someone find a new, ultra solution mechanism, but still want to use the conf parser / device handler back end. So opt out the plug mechanisms and let in the parser, then use a small external program with the ultra new solution mechanism (until it may be added as another optional mechanism in Busybox, like netlink).

A modular system, put together the required parts. Only cave-eat should be, you need to fire up some kind of a service daemon for the device management system ... else this start of the service daemon (fifo manager is just another name for it) needs to be coupled with some other part ... which hit Laurent's wishes, poking me for clarity and functional separation.

_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to