Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] set simple network setup via the system configuration submenu
Date: Wed, 10 Dec 2014 00:04:00 +0100	[thread overview]
Message-ID: <20141210000400.35feddd5@free-electrons.com> (raw)
In-Reply-To: <1418114924-18826-1-git-send-email-jeremy.rosen@openwide.fr>

Dear J?r?my Rosen,

On Tue,  9 Dec 2014 09:48:44 +0100, J?r?my Rosen wrote:
> This patch allows the setup of simple /etc/network/interfaces (or
> /etc/systemd/network/80-buildroot.network if networkd is enabled) via the
> configuration menus instead of using an overlay

So, we discussed this tonight during the patchwork review with Yann,
Peter and Samuel, and the general opinion is that this is too
complicated, and we don't want to handle all those cases through
configuration options, and we instead want to leave that to
project-specific customization through a rootfs overlay or a post-build
script.

However, we would be willing to accept a patch that adds a single
string option that allows to specify one network interface on which
DHCP should be used. It would basically add "inet <foo> dhcp"
to /etc/network/interfaces if non-empty, and otherwise do nothing. The
default should be nothing, so that we keep the existing behavior.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-12-09 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09  8:48 [Buildroot] [PATCH v5 1/1] set simple network setup via the system configuration submenu Jérémy Rosen
2014-12-09  9:02 ` Thomas Petazzoni
2014-12-09  9:23   ` Jeremy Rosen
2014-12-09 23:04 ` Thomas Petazzoni [this message]

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=20141210000400.35feddd5@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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