From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9055 invoked by uid 1002); 13 Oct 2003 22:09:37 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 8872 invoked from network); 13 Oct 2003 22:09:37 -0000 Mime-Version: 1.0 (Apple Message framework v606) In-Reply-To: <200310131456.00906.mjc@ispvip.biz> References: <200310131456.00906.mjc@ispvip.biz> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stroller Date: Mon, 13 Oct 2003 23:09:22 +0100 To: gentoo-dev@gentoo.org X-Mailer: Apple Mail (2.606) Subject: Re: [gentoo-dev] Proposal: networking startup script rewrite X-Archives-Salt: a3f6e2d9-bfac-44a9-9cdb-6600f261ea21 X-Archives-Hash: 2ad391be58d4f3d4afe6943dfce9fdfd On 13 Oct 2003, at 7:56 pm, Michael J. Cohen wrote: > After wrestling with our current net implementation to get bridged > interfaces > and vlans working, which ended in me just setting up things in > local.start, I > figured a rewrite of our network scripts is in order. > > I have made a primitive version of the rewrite available here: > http://325i.org/proposed-net-replacement > > It is useless in its current state and only provided as an example. Michael, I'm not really sure what you regard as the failings of the current /init.d/net configuration. I have to say that I spent a couple of days struggling with it myself, and although I did whine about it at the time (see my postings ) the upshot is that I rather like it the way it is. I'd agree that if a script to call `brctl` appropriately was installed by net-misc/bridge-utils then it would make configuration a lot easier, but this is a simple addition to a single package, rather than a rewrite of the whole framework. I really would like to see such an inclusion, considering that the bridging code is, I believe, incorporated into the upcoming 2.6. Bridging works fine here & fairly seamlessly with the current framework. I found that everything fell into place once I moved /etc/conf.d/net to /etc/conf.d/net.eth0 & /etc/conf.d/net.eth1, so that it's contents (particularly with respect to gateways) are ignored by my /etc/conf.d/net.br0 script. Not much in addition is required to get everything up & running - I would have been glad to provide my scripts, if I had seen your posting to -user. I don't know much (erm... well, anything) about VLANs, so I'm probably missing some of your reasoning against the current system. Actually, I don't know much about anything, so maybe you could explain (like an RFC or a GLEP, maybe?), listing the problems of the current system & how your solution would resolve them..? I'm sorry if I seem biased or antagonistic, but really don't like the idea of uniting the network scripts in anyway like you describe. I may have struggled with them myself, but that's only because I'm so incompetent - I got there in the end. I once tried parsing one of Mandrake's network initialisation scripts, but floundered wildly - with Gentoo you know intuitively to look for iptables stuff in /etc/conf.d/iptables and so on. The only improvements I'd no ask for in the init scripts are more commenting - I'm firmly of the school that believes in 2 lines of comments for every line of code. I'd like to see all code human-readable for a newbie to the language. Stroller. -- gentoo-dev@gentoo.org mailing list