From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: Network script handling changes Date: Mon, 31 Oct 2005 17:05:54 +0000 Message-ID: <20051031170554.GE7630@leeni.uk.xensource.com> References: <20051031165254.GD7630@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20051031165254.GD7630@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Xen Developers List-Id: xen-devel@lists.xenproject.org On Mon, Oct 31, 2005 at 04:52:54PM +0000, Ewan Mellor wrote: > I have made some changes to the way the network scripts are handled, in order > to make it easier for those of you with non-standard configurations. And just a note about my rationale: The intention is to move network-related stuff out of Xend and into the scripts, where possible. It is still useful for some people (especially the developers) for Xend to be able to alter the network configuration when it starts, but in many cases it makes more sense for the init.d scripts to do it. Given this, and for reasons of general cleanliness, I don't want Xend to need to understand network-specific parameters like bridge names -- it is better for Xend to just pass command line options through opaquely. Then, distros or users are free to add whichever parameters they like without needing to patch Xend. Ewan.