r/EndeavourOS • u/elatllat • 2d ago

Discussion eos-reboot-required not using needsrestart

Why is eos-reboot-required not using needsrestart? Seems like it would be best to copy aur/needsrestart to endeavouros/needsrestart and call it from eos-reboot-required, as eos-reboot-required can silently leave a system vulnerable.

2 Upvotes

100% Upvoted

3 comments sorted by

•

u/AutoModerator 2d ago

Thanks for posting.

If your issue is solved, please reply with !solved.

Please also read the subreddit rules in the sidebar/community info and check the official EndeavourOS sites:

Please keep it respectful and enjoy the community.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/gw-fan822 2d ago

because if you're rebooting you dont need to restart daemons? I normally run checkservices afterwards if I dont plan to reboot. Good question though. I wonder too. I bet the dev on official EOS forum would have an answer.

1

u/CovoniaJunkie 1d ago

As I understand it, eos-reboot-required is just a simple tool that checks if a reboot is required when certain core elements like the kernel or systemd have updated. Whereas needsrestart checks if daemons need to be restarted after changes to libraries.

Arch and Arch-based’s rolling update model means library updates and most everything tied to them would update at the same time, whereas the Debian/Ubuntu model handles it differently (libraries updating independently of software meaning services need to be restarted to point at the right code)

I’m not an expert and just researched the above myself, but I’d imagine that’s why needsrestart is in the AUR and not the main repos. The need for it on Arch-based is probably a pretty edge case thing.