All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] Allow a single DHCP configuration via	the system configuration submenu
Date: Mon, 16 Feb 2015 09:46:28 +0100 (CET)	[thread overview]
Message-ID: <81393811.181114.1424076388497.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <87y4nzx7bh.fsf@dell.be.48ers.dk>


----- Mail original -----
> >>>>> "Steve" == Steve Kenton <skenton@ou.edu> writes:
> 
>  >>> 
>  >>>> +config BR2_SIMPLE_DHCP
>  >>> 
>  >>> We're not completely consist with this, but the new system
>  >>> options
>  >>> are
>  >>> called BR2_SYSTEM_*, so I've renamed to the option.
>  >>> 
>  > On this topic, what about the following idea?
> 
>  > If the interface name is blank do not perform DHCP as currently
>  > If the interface name is "*" then run something like this script
>  > to automatically find and use the first network interface for DHCP
>  > I'd like to be able to use the same BR config on slightly
>  > different
>  > boards that may sometimes have different network interface
>  > names/orders
>  > The kernel handles that OK with modules so maybe buildroot could
>  > to?
> 
> So those boards have network interfaces not using eth%d names? That
> sounds pretty uncommon to me. Another approach would simply be add an
> init script to rename those to eth0 with nameif.
> 

there is the (still pretty uncommon) case of networkd that does interface
naming based on the physical layout and not the module loading order

interfaces are never named eth* in that case.



Regards

Jeremy Rosen

      parent reply	other threads:[~2015-02-16  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 13:08 [Buildroot] [PATCH v4] Allow a single DHCP configuration via the system configuration submenu Jérémy Rosen
2015-01-16 15:19 ` Thomas Petazzoni
2015-01-16 15:30   ` Jeremy Rosen
2015-02-02 16:36 ` Peter Korsgaard
2015-02-02 16:38   ` Jeremy Rosen
2015-02-14 16:18     ` Steve Kenton
2015-02-15 20:12       ` Peter Korsgaard
2015-02-15 22:04         ` Steve Kenton
2015-02-15 22:11           ` Peter Korsgaard
2015-02-16  3:06             ` Steve Kenton
2015-02-16  8:46         ` Jeremy Rosen [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=81393811.181114.1424076388497.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.