From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] set simple network setup via the system configuration submenu
Date: Tue, 21 Oct 2014 10:50:01 +0200 (CEST) [thread overview]
Message-ID: <1111084647.26814618.1413881401004.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20141021103611.7e43d2b4@free-electrons.com>
----- Mail original -----
[<snip>]
>
> I certainly don't like to push back stuff, but I'm wondering if this
> isn't too much complexity compared to just having people use an
> overlay
> containing their own /etc/network/interfaces. We will never be able
> to
> handle all the possible cases, with multiple network interfaces, hook
> scripts called before/after bringing up/down interfaces, etc.
>
> What is the opinion of other Buildroot developers?
>
just to clarify...
the point of the patch is not to allow all possible configurations that
network/interfaces can handle, but just allow to easily set an IP address
or enable DHCP without having to add an overlay. For anything more
complex an overlay is the way to go.
I originally thought that putting more stuff in would be a good
idea but I have revised my position on that and now I think it
should be limited to the minimal required subset
* static ipv4
* ipv4 dhcp
* networkd support
if ipv6 becomes popular enough it could trivially be added but
let's keep this for a followup
Regards
J?r?my
next prev parent reply other threads:[~2014-10-21 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 14:14 [Buildroot] [PATCH v2] set simple network setup via the system configuration submenu Jérémy Rosen
2014-10-20 21:29 ` André Erdmann
2014-10-21 8:23 ` Jeremy Rosen
2014-10-22 19:39 ` André Erdmann
2014-10-23 10:02 ` Jeremy Rosen
2014-10-21 8:36 ` Thomas Petazzoni
2014-10-21 8:50 ` Jeremy Rosen [this message]
2014-10-21 18:00 ` Yann E. MORIN
2014-10-22 7:21 ` Jeremy Rosen
2014-10-22 16:12 ` Arnout Vandecappelle
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=1111084647.26814618.1413881401004.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--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