Re: Improving the performance of system boot by eliding unused rc.d scripts and caching the result

[Greg Troxel <gdt%lexort.com@localhost>]

David Holland <dholland-tech%netbsd.org@localhost> writes:

> 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

I can see those working -- but I don't see how that's an improvement,
weighing the benefit of dropping these tiny files and invoking them vs
the cost of adding additional mechanisms, absent benchmarks that show
the current situation hurts.

After all, anyone truly concerned about performance would port systemd
to NetBSD and vibe-code optimizations.