From: Brent Sink <brents_3@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] NetworkManager ignores conf file
Date: Tue, 16 May 2017 02:16:14 +0000 [thread overview]
Message-ID: <BN6PR03MB29145B5D4EE66DD6893A7532BFE60@BN6PR03MB2914.namprd03.prod.outlook.com> (raw)
Hello,
It seems that NetworkManager does not create a /etc/NetworkManager/NetworkManager.conf file. I tried adding it but it seems to ignore it. I'm trying to prevent NetworkManager from taking control of eth0, but everything I've tried has not worked. Would Buildroot be building NM to look for the .conf file in a different location?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170516/4dcafd10/attachment.html>
reply other threads:[~2017-05-16 2:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BN6PR03MB29145B5D4EE66DD6893A7532BFE60@BN6PR03MB2914.namprd03.prod.outlook.com \
--to=brents_3@hotmail.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 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.