Re: On linux, potentially setting INIT_SYSTEM=systemd?

[nia <nia%NetBSD.org@localhost>]

On Sun, Sep 29, 2024 at 08:29:40AM -0400, Greg Troxel wrote:
> nia <nia%NetBSD.org@localhost> writes:
> 
> > I'd suggest making this an OPSYS_HAS variable (defined in
> > mk/platform/Linux.mk) instead, if it's to affect a PLIST rather than
> > express a user preference.
> 
> Good point.
> 
> However, I still don't think we can define OPSYS_HAS based on looking at
> files, because that's not going to be stable.   It's not a property of
> Linux to have systemd, but rather that some Linux systems have it.
> 
> So perhaps set at bootstrap time, perhaps defaulting to guessing based
> on presence, but settable, and the choice of init system ending up in
> mk.conf.
> 

There are some systemd files that have to exist on any systemd system,
like shared libraries, otherwise stuff would be broken.

In theory, you could create a broken chroot. But users who do that
should face the consequences. ;)