From owner-freebsd-questions@FreeBSD.ORG Tue Jan 13 08:59:44 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C408216A4CE for ; Tue, 13 Jan 2004 08:59:44 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFB3C43D5A for ; Tue, 13 Jan 2004 08:59:31 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 17D271D5; Tue, 13 Jan 2004 10:59:31 -0600 (CST) Date: Tue, 13 Jan 2004 10:59:31 -0600 From: Tillman Hodgson To: FreeBSD-Questions Message-ID: <20040113165931.GN66765@seekingfire.com> References: <20040112221218.GI66765@seekingfire.com> <44u130lg73.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44u130lg73.fsf@be-well.ilk.org> User-Agent: Mutt/1.4.1i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers Subject: Re: ngctl and rc.conf X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 16:59:44 -0000 On Mon, Jan 12, 2004 at 09:45:20PM -0500, Lowell Gilbert wrote: > Tillman Hodgson writes: > > > Howdy folks, > > > > What's the best way to build ng_one2many interfaces into rc.conf such > > that they're brought up (live) at the "normal" time so that: > > > > 1) configuration remains centralized in rc.conf > > 2) other pieces that depend on a network being present don't fail in > > enlightening ways? > > > > I want to avoid the "make a shell script in /usr/local/etc/rc.d" > > approach. > > Nobody else has written this shell script for you, so you can't just > configure it in rc.conf and turn it on. If you want, you can add it > to rc.network and submit the patches in a PR, so future upgrades will > include it. I'll play around with it and see what I can come up with -- at first blush it doesn't look difficult, just time-consuming to ensure that it fails gracefully under misconfiguration. -T -- "Seeing yourself as you want to be is the key to personal growth." - Unknown