X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from [10.252.6.112] (unknown [74.117.189.39]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: nangel@nothome.org) by mail.alpinelinux.org (Postfix) with ESMTPSA id 4E6E5DC00D4 for ; Mon, 12 Mar 2012 02:05:44 +0000 (UTC) Message-ID: <4F5D5A17.2010505@alpinelinux.org> Date: Sun, 11 Mar 2012 19:06:15 -0700 From: Nathan Angelacos User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 To: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Configuring bridges References: <20120309225041.43308a57@alpinelinux.org> In-Reply-To: <20120309225041.43308a57@alpinelinux.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit > 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. > I'm in favor of a separate package; Alpine's great because it its opt-in, vs opt-out. When I need bonding and vlans and bridges I need them. But the other 90% of the time its nice to have a lean fast system. Oh the other hand, what do you name the package so that someone like me remembers to load it when needed? --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---