Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10636] BR2_SYSTEM_DHCP is removed from .config and breaks auto eth0
Date: Fri, 05 Jan 2018 16:58:51 +0000	[thread overview]
Message-ID: <bug-10636-163-CXkwO6e7LY@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10636-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10636

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |yann.morin.1998 at free.fr
         Resolution|---                         |INVALID

--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Patrice,

BR2_SYSTEM_DHCP is only available if you use the default skeleton, and any
of busybox, ifupdown or systemd-networkd package.

If you use your own custom skeleton, you are responsible for providing the
necessary files (usually /etc/network/interfaces) in your custom skeleton.

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-01-05 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 12:02 [Buildroot] [Bug 10636] New: BR2_SYSTEM_DHCP is removed from .config and breaks auto eth0 bugzilla at busybox.net
2018-01-05 13:11 ` [Buildroot] [Bug 10636] " bugzilla at busybox.net
2018-01-05 15:30 ` bugzilla at busybox.net
2018-01-05 16:58 ` bugzilla at busybox.net [this message]
2018-01-05 17:23 ` bugzilla at busybox.net

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=bug-10636-163-CXkwO6e7LY@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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