Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: cshored@cshore.thecshore.com
Cc: Openembedded-devel@lists.openembedded.org
Subject: Re: Some experimental layers and conclusions
Date: Thu, 27 Apr 2017 09:06:09 -0400	[thread overview]
Message-ID: <20170427130608.GA15538@linux-uys3> (raw)
In-Reply-To: <093b01d2bf21$fdcb22a0$f96167e0$@cshore.thecshore.com>

Hi Daniel,

Very interesting report, thanks for the info!

On Thu 2017-04-27 @ 02:46:24 AM, cshored@cshore.thecshore.com wrote:
> * OE doesn't have good *router* networking support (i.e. nothing like
> OpenWrt/LEDE's netifd and friends for a headless system, that one can
> configure by editing a text file, or by using a WebUI for handling multiple
> interfaces and VLANs and bridged (or not) wireless and wired networks, with
> easy firewall configuration).

I wonder Khem's if meta-openwrt could have helped here? It looks like it has a
recipe for netifd and friends:

	https://layers.openembedded.org/layerindex/branch/master/layer/meta-openwrt/

Out of curiosity, did you try using musl? You don't mention which C library
you're using. I'd be curious to know if musl can help with size reduction.

Is toybox mature enough to be used in these situations?

	http://layers.openembedded.org/layerindex/recipe/28902/

Best regards,
	Trevor


  reply	other threads:[~2017-04-27 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27  6:46 Some experimental layers and conclusions cshored
2017-04-27 13:06 ` Trevor Woerner [this message]
     [not found]   ` <006e01d2c147$48974e40$d9c5eac0$@cshore.thecshore.com>
2017-05-05  8:06     ` cshored

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170427130608.GA15538@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=cshored@cshore.thecshore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox