@pid_eins So kind of like telinit 1 followed by telinit...

@pid_eins So kind of like telinit 1 followed by telinit 5?

I gotta say I don't quite like it, certainly it shouldn't be offered to users easily or automatically if no new kernels available, that makes triage a lot harder.

Speaking practically because getting the kernel out of whacky driver states, or the EC out of its whackyness is the main reason I need to reboot on a ThinkPad :D

Like 28 Apr 2023 at 5:14 | Wall-to-wall | Open on mastodon.social

5 comments

James Henstridge

@juliank @pid_eins The ability to preserve file descriptors is a pretty big difference.

Imagine running a web server and being able to restart all of user space without dropping an incoming connection. The listening port 80 socket would remain open with incoming connections queued until the web server is ready again.

28 Apr 2023 at 8:16 | Open on aus.social

bluca

@juliank @pid_eins the main use case here is unattended systems that have every tight requirements on service interruption tolerance, rather than laptops, as it pretty much has to be paired with kernel livepatching

28 Apr 2023 at 9:40 | Open on fosstodon.org

varx/tech

@bluca @juliank @pid_eins It certainly seems cool, but also like a great way to introduce extremely arcane bugs into a long-running system. :-)

30 Apr 2023 at 2:32 | Open on infosec.exchange

Lennart Poettering

@juliank well, there's a rootfs pivot between the telinit steps. And its a telinit that can pass through fds for .socket units and fdstore. And there's also a "telinit u" in between. And its more than "telinit 1" btw, because we also tear down early boot.

So its considerably different actually.

28 Apr 2023 at 11:41 | Open on mastodon.social

Julian Andres Klode 🏳️‍🌈

@pid_eins yeah much nicer and made for it rather than how I abused sysvinit to reboot my user space :)

28 Apr 2023 at 11:43 | Open on mastodon.social

Go Up