Sujet : Re: Syst?me D
De : sebastian (at) *nospam* here.com.invalid (Sebastian)
Groupes : comp.os.linux.advocacyDate : 19. May 2024, 11:37:28
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v2ch8m$3ala3$1@dont-email.me>
References : 1 2 3 4 5
User-Agent : tin/2.6.2-20221225 ("Pittyvaich") (Linux/6.1.0-18-amd64 (x86_64))
Lawrence D'Oliveiro <
ldo@nz.invalid> wrote:
On 23 Apr 2024 17:16:02 GMT, Andrzej Matuch wrote:
On Tue, 23 Apr 2024 15:50:08 +0000, candycanearter07 wrote:
I don't get why, but systemd hate is pretty common.
Because it removes some of the control users have over the services run
on their system.
I don?t see why. It gives you very fine-grained control.
For example, with sysvinit, if you don?t like the existing sysvinit
script, you have to write an entire new one (perhaps copying/pasting from
the existing one). With systemd, you can create ?drop-in? unit files that
modify an existing config without replacing it completely. Much less work
for small changes.
One thing you can't do with Systemd is write a simple shell script that
runs when the system finishes booting, without having to learn any of
the ins and outs of Systemd. Some distros used to have a unit file to
run /etc/rc.local like SysVInit does, but it wasn't guaranteed to run
last, so it wasn't even really equivalent to a real /etc/rc.local.
But it was often good enough.
So of course they got rid of it, so now if you want something to run
at boot, you have to figure out how to write and install a unit file.
Or, just install FreeBSD, which might actually be easier.