3 ms·
> The FreeBSD system initialization artifacts are not monolithic. And nobody claimed that... . The claim was that FreeBSD is monolithic in the same way that th
by diffeomorphism 7y ago
> The FreeBSD system initialization artifacts are not monolithic.
And nobody claimed that... . The claim was that FreeBSD is monolithic in the same way that the systemd project (logind, nspawn etc. ) is monolithic.
> Not according to here[0].
Okay, let's click on that. First sentence "It doesn't". What were you trying to argue again?
> Know that an init system, any init system, does not design nor define an Operating System.
Are you purposely confusing systemd-init and systemd the project? Because your argument is the same as "GNU does not design or define an OS", which many people would call plain wrong.
- AdieuToLogic 7y ago> > Not according to here[0]. > Okay, let's click on that. First sentence "It doesn't". What were you trying to argue again? And the second sentence says: What it requires is a service that implements the same set of APIs as systemd-logind. Since GNOME requires either systemd-logind or something that behaves exactly as systemd-logind, how does that not express a transitive dependency on systemd? So what are you trying to argue again? > > Know that an init system, any init system, does not design nor define an Operating System. > Are you purposely confusing systemd-init and systemd the project? No, what I stated I thought was quite clear: an init system does not design nor define an Operating System. This is orthogonal to the question you present. 0 - https://www.quora.com/Why-does-GNOME-3-require-systemd https://www.quora.com/Why-does-GNOME-3-require-systemd