From owner-freebsd-current Tue Oct 24 14:58:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7F32037B4CF for ; Tue, 24 Oct 2000 14:58:50 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id e9OLw8421388; Tue, 24 Oct 2000 14:58:08 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Warner Losh Cc: bv@wjv.com, freebsd-current@FreeBSD.ORG Subject: Re: new rc.network6 and rc.firewall6 In-Reply-To: Message from Warner Losh of "Tue, 24 Oct 2000 12:31:57 MDT." <200010241831.MAA17525@harmony.village.org> Date: Tue, 24 Oct 2000 14:58:08 -0700 Message-ID: <21384.972424688@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The scripts themselves have the ordering dependencies. The startup > system runs them in the proper order. I don't know if this is > pre-computed or redone each boot. I'm really curious about this, myself. One of the reasons the SYSV scripts have the numeric prefix is so that you know exactly what order things will be started in. With the NetBSD stuff, this is not immediately obvious though I guess one could have a top level rc file with an explicit ordering similar to our various subdir Makefiles, but that also gives you another location to edit when dropping in a new startup file. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message