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 Tue, Aug 18, 2026 at 09:51:44AM -0400, Mouse wrote:
>  > > - the barrier scripts (e.g. LOGIN)
>  > 
>  > > The barrier scripts are needed only for ordering, [...]
>  > 
>  > If this really bothers someone, perhaps there could be a way for a
>  > script to declare itself a barrier script?  Perhaps something a la
>  > make's .PHONY, perhaps a naming convention, perhaps something else.
>
> 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?

This is 6 tiny files.  I don't think it's a problem, and it's easier for
humans to read and reason about rc.d scripts with them present, instead
of imputed information.