Re: Improving the performance of system boot by eliding unused rc.d scripts and caching the result
David Holland <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.userlevel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Aug 19, 2026 at 06:43:20AM -0400, Greg Troxel wrote: > > Is there any reason for the barrier scripts to physically exist? > > Picking one arbitrarily, > > # $NetBSD: LOGIN,v 1.8 2022/03/02 01:55:18 gutteridge Exp $ > > # PROVIDE: LOGIN > # REQUIRE: DAEMON > > I can see how you can impute that LOGIN provides LOGIN, but someplace > the information the LOGIN requires DAEMON has to exist. > > How would you store and configuration manage the ordering requirements > among barrier scripts? Just off the top of my head, you could: - hardwire the barrier sequence (admittedly not a great plan) - put it on the rcorder command line - put it all in a single non-executable file -- David A. Holland [email protected]