On Thu, Nov 14, 2024 at 7:07 PM Stan Johnson <userm57@xxxxxxxxx> wrote:
On 11/13/24 2:01 PM, John Paul Adrian Glaubitz wrote:
SysVInit uses a huge set of bash scripts where every action involves
spawning
a new shell while systemd does all of that in C. Compiled C code is definitely
faster on an m68k machine than hundreds of shell scripts.
Yes, compiled C code is faster than an equivalent script, but scripts
are much easier (for some of us) to edit and turn on and off than
systemd components.
systemctl disable foo.service is too hard?
Yes, it's too hard. And if I want to change something in foo.service
instead of disabling it, I'm sure there's a way to do that in systemd as
well, but using vi (or nano) to edit the equivalent sysvinit script is
easier for some of us. Also, if fubar.service is completely messed up,
then I might not be able to boot into the operating system that is
running systemd in order to use systemctl (especially on a slow system).
That's also my experience: when it fails, in 50% of the cases the
system doesn't boot sufficiently far to use systemctl.
But all of that is irrelevant for an alignment discussion...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
