+- Discussion board (https://carsoncitylinux.org/mybb)
+-- Forum: Carson City LUG (https://carsoncitylinux.org/mybb/forumdisplay.php?fid=1)
+--- Forum: Distro Discussion (https://carsoncitylinux.org/mybb/forumdisplay.php?fid=4)
+--- Thread: Thoughts on systemd? (/showthread.php?tid=3)
Thoughts on systemd? - nan60 - 04-24-2024
Just something that came to my mind as a good question for discussion to get this forum going. Systemd is a hot topic and I’m curious what’s everyone’s thoughts are on it and what PID 1 should be.
RE: Thoughts on systemd? - admin - 04-24-2024
Systemd works just fine for me. If we go to something else I would have to find another way to run efibootmgr to change the boot order. As it stands right now I have a systemd service that runs a shell script to set efibootmrg to boot Debian first. I don't seem to be able to set it that way permanently.
Of course it would be even better if you could show me how to make whatever efibootmgr is modifying read only.
--glenn
RE: Thoughts on systemd? - nan60 - 04-24-2024
Are you talking about uefi boot order? AFAIK you can set it using efibootmgr directly using the --bootorder argument.
RE: Thoughts on systemd? - admin - 04-24-2024
That's what the shell script does, but it reverts to windoze first after booting.
--glenn
RE: Thoughts on systemd? - nan60 - 04-24-2024
I’d try this, seems to be a somewhat common problem with buggy UEFI systems and how they manage boot order according to this arch forum thread: “the UEFI firmware on your motherboard is defective and is booting $ESP/EFI/Microsoft/Boot/bootmgfw.efi rather than the specified $ESP/EFI/BOOT/BOOTX64.EFI”. Also, in regards to making it read only, I believe some UEFIs have an option to lock boot options, so I would check for that.
RE: Thoughts on systemd? - LukeT - 04-24-2024
(04-24-2024, 08:56 AM)nan60 Wrote: Just something that came to my mind as a good question for discussion to get this forum going. Systemd is a hot topic and I’m curious what’s everyone’s thoughts are on it and what PID 1 should be.
svchost.exe 2.0 bloatware
PID1 is sacred and should be lean and mean
RE: Thoughts on systemd? - admin - 04-24-2024
Thank you for getting me interested in my uefi boot options again. I was able to change it in the bios and get it to stick. That's a big plus for the forum, I'm sure glad we did it.
--glenn
RE: Thoughts on systemd? - nan60 - 04-24-2024
(04-24-2024, 11:57 AM)admin Wrote: I was able to change it in the bios and get it to stick.That's really great to hear. UEFI can be really annoying sometimes (as can Windows)
RE: Thoughts on systemd? - cheetah2003 - 04-26-2024
To be clear, Systemd has nothing to do with booting the linux kernel. The tool that controls the actual bootup of the computer and selecting an operating system to boot would be something like grub or the Windows Boot Manager. Both are capable of booting linux and Windows, though in the case of Windows Boot Manager, the startup partition would still need grub to properly boot a linux kernal.
Systemd and it's predecessor init, are the first process run by the linux kernel after boot is complete and all hardware is identified. Systemd replaced a previous tool used to manage the system startup sequence called init. As the initial post indicates, it's pid 1. The first process run by the kernal after boot is complete.
Both of these utilities are responsible for starting all the system and user processes to bring a system up to a usable state, typically dictated by a runlevel. Both typically start and stop other processes as the system requests, creating dependencies (like the network should be started and configured before attempting to start a network dependent service like a VPN.) and ordered starting/stopping of services.
Functionality synopsis aside, both utilities have their pros and cons, as with any tool. Systemd is much more aware of the system level utilities running, and depends more on them to properly bring a system up from 'kernal is booted' to 'desktop on the screen', or 'login prompt.' Init on the other hand is much more of the old UNIX paradigm where a tool should do exactly one thing and do it well. But modern linux environments have basically outgrown init.
I was skeptical of systemd initially, but after learning it's abilities and see it do the job it's designed to do well, I'm a fan. It simplified a lot of things, and makes the startup sequence easier to control. Also feels a lot less clunky than init and it's various script directories in /etc and using numerical prefixes on shell scripts to control load orders.
On Debian at least, systemd has gone above and beyond regarding backwards compatibility with old init scripting methods of doing things, so that's a big bonus to me. On all my installations of Debian, I'm still using some init scripts and some systemd 'module config' files. So..yeah!
Hope this helps someone.