Daniel F. Dickinson

Hi, Glad to see someone using this; I've been dealing with personal stuff for some months now and haven't been working on this as I'd like. On 2018-04-17 03:35 AM,...

Should this work be first done in meta-openembedded/meta-oe (currently libubox lives there in recipes-devtools)?

Per the ML, should this be closed? We can already (with my updates) use meta-openwrt to use procd as init_manager and dev_manager, and since you mentioned you didn't think it...

ok; I'll keep the work I've been doing on that then, but incorporate it into meta-openwrt first; not sure if I'll figure out a way to have both use cases...

I got procd building an launching gettys with just ubus and libuci as dependencies. The interface rather weird though for starting services and such (openwrt uses funky wrappers to use...

I guess the question is whether is worth introducing another init system into OE-core, even for poky-tiny, when it would require adding initscripts for every package you wanted to use...

Procd can be used with the meta-openwrt stack but not standalone at the moment.

@kraj @MatthiasMichel I've looked over procd and netifd and [openwrt]firewall enough to know that there is too much openwrt-specific 'stuff' going on for me to think it a good idea...

Are you including netifd and using it or are you using hostapd directly? What processes are running? How are you trying to bring up the wireless? This layer is relatively...

On 2018-05-09 08:29 AM, sandeepyedire wrote: > @cshoredaniel > We are including netifd and using it. > when we try apply the wifi config and try bringing up wlan0 is...