Precedence: list
MIME-Version: 1.0
In-Reply-To: <20120309225041.43308a57@alpinelinux.org>
References: <20120309225041.43308a57@alpinelinux.org>
Date: Sat, 10 Mar 2012 11:43:59 +0100
Message-ID: <CAFivhPkRWYHnMDwVV=YZVtQgrat2g-KO4u1P-u8rp81ramiOHQ@mail.gmail.com>
Subject: Re: [alpine-devel] Configuring bridges
From: Florian Heigl <florian.heigl@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

2012/3/9 Natanael Copa <ncopa@alpinelinux.org>:
> I created a package called "bridge" which has the if-pre-up.d script
> for creating bridges. I rewrote it from scratch because the debian
> version was a bit ugly.

nice :)

> I was thinking shipping this script and vlan and bonding scripts with
> alpine-baselayout. However, those will consume a few kb and generate a
> few extra forks every boot up - even if they are unused - so I think it
> might make sense to ship them separately.

Just a warning with bonding, there is a few dragons hiding with bonding.
When one uses LACP on one bond and active/passive failover on another
then there have to be special methods for loading the bonding module.
I don't remember how Debian handles it, just remember each Linux flavor
has it's own way for this. And there will be a few hooks for it somewhere.

Mind the gap!

-- 
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---