Me: *joins a company-wide video call where I need to present*

My work laptop: HEY BEN SEEMS LIKE A GREAT TIME FOR UPDATES I’M JUST GOING TO RANDOMLY CONNECT AND DISCONNECT YOUR WEBCAM, MONITORS, KEYBOARD, AND MIKE HAVE A SAFE AND SECURE DAY!

@bendaubney Ouch.

My personal peev is when I'm trying to leave quickly, Windows installed some update in the background, and then on shutting down it starts with "Installing update, 5%, don't turn off the machine".

...8%
Come on, I've got a bus to catch
...12%

When I say shutdown, I frickin' expect the computer to do that.

@hl @bendaubney heh systemd is the same…

@mirabilos @hl @bendaubney not last time I checked, it doesn't force updates on you on shut down? :p Or maybe some exotic distro does this for some reason heh

@hl Ah, I rewatched Office Space last night where this exact scenario happens. More common than you’d think.

@fun @bendaubney @hl not updates (though that’s also part of systemd’s planned feature set, IIRC even already available) but “a stop job is running 1:30…”, possibly multiple times

@mirabilos @bendaubney @hl Oh, that's not updating while shutting down then. And I see that kind of stuff in non-systemd as well, some daemon just taking a while to stop

@mirabilos @bendaubney @hl Honestly not as bad as upgrading your whole computer while shutting down with no user consent at all

@fun @bendaubney @hl again,

part of systemd’s planned feature set, IIRC even already available

… so, yes, systemd can and will do updating while shitting down.

@mirabilos @bendaubney @hl at least it would be optional or something, (though I wouldn't know how you could do that, except maybe via immutable rootfs and ota updates)

@bendaubney @hl @fun systemd? something optional? "my way or the highway"

in trixie, systemd complains that /usr/sbin has not been merged into /usr/bin yet (something that’s not even on the horizon for Debian, yet not patched out)…