From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How to modify /etc/network/interfaces file in a OE recipe
Date: Thu, 07 Oct 2010 16:54:10 -0600 [thread overview]
Message-ID: <4CAE4F92.5080107@mlbassoc.com> (raw)
In-Reply-To: <3ADCCD33-6EA5-43FA-84EE-31D6B7C5A005@mac.com>
On 10/07/2010 03:11 PM, Elvis Dowson wrote:
> Hi,
> Would someone be able to help me with modifying an omap3-console-image recipe, such that in the final image, the /etc/network/interfaces file gets edited as follows
>
> #auto eth0 <- remove # sign ( auto eth0 )
> #iface eth0 inet dhcp <- remove # sign ( iface eth0 inet dhcp )
> #iface eth1 inet dhcp
>
> I am using a Gumstix Overo + Chestnut43 expansion board, which has an inbuilt wired ethernet interface. I have to make this modification manually, to enable this interface each time. However, if I can modify the OE recipe somehow to do this it would be great. I know it can be done, but I don't know where to start and which file to modify.
Add the file the way you like it to .../openembedded/recipes/netbase/netbase/overo
and rebuild netbase. Use the beagleboard as an example.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-10-07 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 21:11 How to modify /etc/network/interfaces file in a OE recipe Elvis Dowson
2010-10-07 22:54 ` Gary Thomas [this message]
2010-10-08 3:26 ` Khem Raj
2010-10-08 6:36 ` Frans Meulenbroeks
2010-10-08 7:30 ` Petr Štetiar
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=4CAE4F92.5080107@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.org \
/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