From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eumx.net ([91.82.101.43]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1U3pJC-0006Ys-AP for openembedded-core@lists.openembedded.org; Fri, 08 Feb 2013 15:52:14 +0100 Message-ID: <51150D5D.2030403@communistcode.co.uk> Date: Fri, 08 Feb 2013 14:36:13 +0000 From: Jack Mitchell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130109 Thunderbird/17.0.2 MIME-Version: 1.0 To: Patches and discussions about the oe-core layer Subject: New netbase changes X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: ml@communistcode.co.uk List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 14:52:14 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Now that netbase has been split up into netbase and init-ifupdown, what is the best way of removing init-ifupdown. I notice that it is in packagroup-core-boot, which I would rather not keep a local copy of. The only solution that comes to mind (bar local packagegroup-core-boot copy) is that we have a NETWORK_MANAGER variable and that it becomes another virtual-runtime type thing? I can't think of a situation where you would want more than one network manager on a machine at any one time... -- Jack Mitchell (jack@embed.me.uk) Embedded Systems Engineer http://www.embed.me.uk --