Date: Thu, 18 Oct 2001 11:27:52 -0700 From: "David O'Brien" <dev-null@NUXI.com> To: Gordon Tetlow <gordont@gnf.org> Cc: arch@freebsd.org, kevin.way@overtone.org Subject: Re: New rc.d init script roadmap Message-ID: <20011018112752.B20348@dragon.nuxi.com> In-Reply-To: <Pine.LNX.4.33.0110180933040.30874-100000@smtp.gnf.org>; from gordont@gnf.org on Thu, Oct 18, 2001 at 09:46:13AM -0700 References: <20011018091927.A18621@dragon.nuxi.com> <Pine.LNX.4.33.0110180933040.30874-100000@smtp.gnf.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 18, 2001 at 09:46:13AM -0700, Gordon Tetlow wrote: > > Can you look at Kevin's work and see if you two could merge it into one > > prototype? > > I just looked briefly at it. I think we are actually in about the same > place, although he's a bit further along on the scripts. Although most of > them are directly from NetBSD and not a conversion of the existing FreeBSD > boot scripts/order. That is what we want -- as small a deveration from the NetBSD ones as possible. Otherwise there is no way they will accept our changes (unless they clearly give a measurable enhancement). We want to share this common source as much as possible -- gratuitous changes from the NetBSD rc.d system will not benefit anyone. Going from our existing RC scripts to an rc.d system is a big enough upheaval that we(FreeBSD) can accept a large change from our existing RC scripts (ie, a direct conversion is not as needed). > > I have sent patches to NetBSD to make rcorder compile properly. > > But I have not bothered to put the pressure on them needed until we had a > > working prototype -- so we could push back all of our changes at once. > > I don't know much about the NetBSD folks, but it might be easier to give > them smaller sets so they don't get a single monolithic patch to try an > integrate into their codebase. From my talks to my contact there, being able to show the whole working system in FreeBSD makes a better argument for them to change some things, than small nebulous changes. This is also another reason to not diverge in the rc.d scripts when possible. > > I also fail to see why this is "milestone 1". These things should be > > done as part of the patch + tarball that should be put up for prototype > > testing. > > I was hoping to do this more or less in tree. That would also give people > that don't want to download a patch an option of simply flipping a switch > in /etc/rc.conf and trying out the new system. We don't want to pull files off the vendor branch until we are sure we need(want) to. Thus a patch is what we're most like going to have to work with until we are happy with things. > It's also M1 because it was > necessary piece before rewriting all of the boot scripts. (It also > happened to be the amount that I was able to create/test last night =) I already posted patches in the past to add rcorder to our /usr/src (building and installing rcorder). :-) > > > M4 > > > Add true dependency checking to the infrastructure so that starting nfsd > > > will start mountd and rpcbind > > > > The dependency checking is part of /etc/rc.d/*. Is there something > > missing you have found? > > Well, once I have booted my machine, I might want to start an nfs server. > If I just ran /etc/rc.d/nfsd start, it would fail, because that script > doesn't know enought to start mountd (which in turn doesn't know enough to > start rpcbind). I had an idea on how to make that all work. But we need to > crawl before we start sprinting. Something must have been missing from your conversion of the rc.d scripts, because such dependancy infomation is inherent in the NetBSD rc.d scripts. > There is one main issue to resolve before I go through and rewrite the > rc.d scripts. Do we want to keep the existing FreeBSD scripts as much as > possible? No. (as justified above) > or do we want them to look like NetBSD's? I prefer the former > myself. I think Kevin's implementation has gone more for the latter. Yes. (as justified above) -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011018112752.B20348>