MX Linux Forum

Hi All

I guess I am still new, I don't know the bit deal of systemd!
I have only scratched the surface of what appears to be a can of worms...
The reason this came up is that I noticed that sometimes the system is a little slow to start. I have previously ran systemd blame and it would appear that there is no systemd....

I think more googling might be in order for me to understand the impact of systemd... but in the mean time is there a tool similar to this that will identify anything that is slowing up the system.

I did get the fingerprint reader on the go, but the system would never recognise the already coded prints. That was not too big a deal on logging in, just wait for it to time out, but every sudo command was becomming a joke!

For background and future reference: https://mxlinux.org/wiki/system/systemd

Cheers Jerry

I did get the fingerprint reader on the go

Can you please post your procedure in a separate thread in the Software forum? I saw your question on Reddit and was able to install it on an HP ElitePro notebook, but couldn't get the scanner to function--not sure if it works, maybe I have to go into the BIOS(?). Never took the time to pursue it. So a good How-To would be useful to all.

Systemd should be faster to boot on a spinning drive, but I don't see much difference on an SSD. Plus without systemd, I get a nice terminal screen with progress % shown when I hibernate and resume, while a systemd boot just gives me a frozen screen until the machine turns off.

Systemd often won't start all your services due to race conditions so you have to use scripts to delay the start-up of some of them. It's a problem for distros that use systemd as init. Linux Mint now has a GUI for setting start-up delays. There is also the famous 90 second shut down time-out. The init part of systemd is the worst part because boot/restart/shut-down are crucial.

Someone else can tell you about systemd benefits for system administrators. I'm sure there are benefits if you fall into that category. Distrowatch did a boot time comparison between Systemd and SysV and they were pretty similar.

Systemd is actively developed as was mentioned in another thread, but is also the enemy of alternative inits. Not a great fit for "The universal operating system" if you ask me. Debian provides images for many architectures so I wonder how that works with systemd.

Because of tooth pain I think I got distracted. Systemd shouldn't be a problem on different architectures as long as it's Linux. Debian once had an experimental BSD? kernel and that project probably got dropped because of Systemd.

Jerry3904 wrote:

I did get the fingerprint reader on the go

Can you please post your procedure in a separate thread in the Software forum? I saw your question on Reddit and was able to install it on an HP ElitePro notebook, but couldn't get the scanner to function--not sure if it works, maybe I have to go into the BIOS(?). Never took the time to pursue it. So a good How-To would be useful to all.

Attempted - probably dire - but its how I did it.

Stevo wrote:Systemd should be faster to boot on a spinning drive, but I don't see much difference on an SSD. Plus without systemd, I get a nice terminal screen with progress % shown when I hibernate and resume, while a systemd boot just gives me a frozen screen until the machine turns off.

I agree - it is nice to see something in action. I might not know what is being done, but I hate just looking at a frozen screen.

dreamer wrote:Systemd often won't start all your services due to race conditions so you have to use scripts to delay the start-up of some of them. It's a problem for distros that use systemd as init. Linux Mint now has a GUI for setting start-up delays. There is also the famous 90 second shut down time-out. The init part of systemd is the worst part because boot/restart/shut-down are crucial.

Someone else can tell you about systemd benefits for system administrators. I'm sure there are benefits if you fall into that category. Distrowatch did a boot time comparison between Systemd and SysV and they were pretty similar.

Systemd is actively developed as was mentioned in another thread, but is also the enemy of alternative inits. Not a great fit for "The universal operating system" if you ask me. Debian provides images for many architectures so I wonder how that works with systemd.

Quite insightful, thank you.

I suppose - I just wanted to see what the hold up was when booting. And then opened a can of worms I am still to understand!
Its very windows to have a slow shutdown time, hanging on some application but not telling you what. Also having to manually add scripts on start up will get boring fast!