On Wed 30 Nov 2022 at 08:42:41 (+0100), to...@tuxteam.de wrote: > On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote: > > > I learned many many moons ago to not trust any update/upgrade process to not > > interfere with a running X session. I usually close apps I don't want data > > lost > > from before beginning an upgrade process. That usually means I log all the > > way out > > of X entirely, then start the upgrade from a vtty.
The only reasons I'd close down X are (a) a dist-upgrade from oldstable to stable (and the like), and (b) dpkg-reconfigure console-setup and keyboard-configuration after I've been tinkering with /etc/console-setup/remap.inc (which is currently two years old). The latter may now be cargo-cult, but I think it was advised in the past. Like you, I admit to being an fvwm user (since 1996; never used anything else). The one application I do avoid upgrading while it's running is Firefox, but that's mainly because it occasionally gives a new startup screen after an upgrade, and I want to read what it says. > > What I have noticed in Debian that I do not at all like, is when I boot to > > multi-user.target for the specific purpose of apt or apt-get upgrading, > > even when > > systemctl get-default returns multi-user.target, that if the DM is > > upgraded, X > > gets started shortly following. :( This is above my paygrade (and I don't run a DM), but could this follow from Debian's policy (occasionally complained about), that installing a daemon will start it immediately at the end of the process of installation? > Oh, something I forgot: besides no DM, my init system is still > SysV. This might or might not contribute to stability through > simplicity. No stability problems here with systemd. Nor with udev (apparently from the same stable, sorry for the pun), which someone mentioned this morning. In my experience, the only time udev might have been blamed was during the lenny/squeeze transition, where mixing lenny kernels with squeeze's udev was specifically warned against in the Release Notes (which too many don't seem to read). That transition looks about the time that udev hitched its wagon to systemd (first mention of systemd in its changelog, default rules moved from /etc into /lib), but it could have been coincidental. > My important apps (Emacs, then Emacs, then dunno ;-) don't lose > data "just because the system goes down", so I'm pretty relaxed. And not forgetting the robustness of ext4, that allegedly "unfashionable" filesystem. My most frequent cause of "crashes", by far, is powercuts. > Still, it never happened to me, and I dist-upgrade roughly once > a week. Same here, but running stable, so I normally only have to "dist-" when the kernel is upgraded. Otherwise I upgrade within a few hours of packages hitting the mirrors. Cheers, David.
