Bug or feature? [LWN.net]

Bug or feature?

Posted Jun 30, 2026 21:50 UTC (Tue) by rgmoore (✭ supporter ✭, #75)
In reply to: Bug of feature? by bronson
Parent article: Xsnow "protestware" in Debian

I think the correct initial response is for the higher ups at Debian to have a polite talk with the Debian packager and ask them to remove the misfeature from the Debian version. If they refuse, they should be ordered to do so. If they continue to refuse, xsnow should be removed from the distribution. I also think this should be seen as a warning about the general class of problem, and Debian should write some kind of general rule/guideline for what to do the next time it comes up.

It's a little bit more complicated because the Debian packager is also the upstream maintainer, but I think Debian only has the right to control what's in their distribution. If the packager really wants to keep this upstream, they should have the option to keep it as long as it's removed from the version distributed by Debian. Other distributions can make their own decisions about what to do with the packages they distribute.

That said, I have some confidence Debian will eventually come up with a satisfactory decision. The democratic processes used by Debian can be very slow to play out, but they do a remarkably good job of making the right decision time after time.

Bug or feature?

Posted Jun 30, 2026 23:46 UTC (Tue) by pizza (subscriber, #46) [Link] (15 responses)

> I think the correct initial response is for the higher ups at Debian to have a polite talk with the Debian packager and ask them to remove the misfeature from the Debian version. If they refuse, they should be ordered to do so. If they continue to refuse, xsnow should be removed from the distribution. I also think this should be seen as a warning about the general class of problem, and Debian should write some kind of general rule/guideline for what to do the next time it comes up.

You have this backwards; the rule/guideline has to come first, before any arbitrary "enforcement" occurs.

> The democratic processes used by Debian can be very slow to play out, but they do a remarkably good job of making the right decision time after time.

The decision would only be "right" insofar as _any_ decision makes the course of action clear, putting an end to the issue. [1]

Relatedly, I can think of many [1] who would disagree as to the "correctness" of various GRs when the vote didn't go the way they wanted.

[1] Not counting the many times where the answer is (e) all of the above or (f) no decision
[2] eg so-called "Veteran Unix Admins". Granted, Debian was probably far better off after said VUAs angrily stomped off.

About the Devuan excision

Posted Jul 1, 2026 0:33 UTC (Wed) by alx.manpages (subscriber, #145117) [Link] (14 responses)

[off-topic]

I have both Debian and Devuan systems (both Sid), and the Devuan systems are significantly and consistently more stable. Every now and then (to be fair, not more than once a year, but that's way more than I'm used to) I get systemd bugs that prevent me from booting. I am planning to stop using vanilla Debian rather soon (whenever I find time to do it).

I didn't like how Debian acted back then, and wish it had kept better support for non-systemd. To some degree, I think the way the VUAs acted was warranted by the context. I think an option in pkgsel similar to the choice of desktop environment would be good; that's more or less what Devuan does.

And from my experience, I've seen the systemd maintainers be consistently hard to deal with and offensive. I also understand them, due to the attacks they've received in the many years they've been doing that, but they aren't much different from what they criticize, or at least that's what I observed. Having been bullied should not be a reason to treat others badly.

About the Devuan excision

Posted Jul 1, 2026 1:11 UTC (Wed) by pizza (subscriber, #46) [Link] (13 responses)

> I get systemd bugs that prevent me from booting.

In the ...15 years since Fedora switched to systemd by default, I can't ever recall ending up in a situation where a *systemd* issue prevented a system from booting. (As opposed to massive filesystem corruption, hardware flakiness, buggy distro scripts/units, etc) Meanwhile, let's not pretend that plenty of bugs didn't exist prior to systemd's adoption and/or in non-systemd boot flows.

All I can say is that overall things are *vastly* more robust and reliable than they used to be.

> I didn't like how Debian acted back then, and wish it had kept better support for non-systemd.

....That would have required folks to Show Up And Do The Work(tm), which hadn't been happening for quite some time.

The Devuan proponents could have accomplished everything they claim to have wanted from within the Debian umbrella [1] but chose to leave instead of working cooperatively to maintain or develop alternatives. [2]

[1] ie by actively maintaining the non-systemd infrastructure and dealing with the reality that various user-facing upstreams were choosing to depend on systemd features.
[2] IIUC Gentoo continues to lead the way on that front.

About the Devuan excision

Posted Jul 1, 2026 1:34 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link] (12 responses)

> I can't ever recall ending up in a situation where a *systemd* issue prevented a system from booting.

I have. At this point, systemd is a freaking mess with its tons of options and services.

In particular, my breakage was caused by a unit (systemd-update-done.service) that starts _once_ on boot after a system upgrade (I bet you didn't know it exists?). It's a fine idea, except that it has DIFFERENT dependencies compared with a normal boot.

And in my case it caused a lockup because it started before the network, and was depending on all the local devices being up. How does it define "local"? By checking the source device. If it's a regular SCSI device, then it's local.

Eeeexcept that iSCSI devices are also detected as "local" but they actually do need network.

Yes, there's a bug in the systemd bug tracker. It's been there for years.

About the Devuan excision

Posted Jul 1, 2026 3:08 UTC (Wed) by pizza (subscriber, #46) [Link] (10 responses)

> In particular, my breakage was caused by a unit (systemd-update-done.service) that starts _once_ on boot after a system upgrade (I bet you didn't know it exists?). It's a fine idea, except that it has DIFFERENT dependencies compared with a normal boot.

Is that a "systemd" bug, or that your particular distro's "system upgrade" flow/tooling doesn't correctly declare its dependencies ? Either way it appears to be trivially fixable by adding a local drop-in that that overrides the "After=local-fs.target" with "After=network.target" .

(I mean, an init script that a distro upgrade sets up to run only once after a system upgrade would break the same way for similar dependency issues. Or more likely, fail silently leaving things in a [not-so-]subtly incorrect state afterwards)

About the Devuan excision

Posted Jul 1, 2026 4:05 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link] (3 responses)

It's a systemd bug, as it's a part of the default systemd installation. The distro is Fedora, btw.

> (I mean, an init script that a distro upgrade sets up to run only once after a system upgrade would break the same way for similar dependency issues. Or more likely, fail silently leaving things in a [not-so-]subtly incorrect state afterwards)

Probably. Or maybe not. The issue here is that systemd is a huge mess at the moment. It seems to do _everything_, but it does almost nothing completely right.

The core process supervision and journaling are OK. Everything around it is not. Mount units are a particular disaster area. I dare anyone to say that THIS is acceptable: https://github.com/systemd/systemd/blob/ee9a70ccc7a35b224...

About the Devuan excision

Posted Jul 1, 2026 14:32 UTC (Wed) by pizza (subscriber, #46) [Link]

> Mount units are a particular disaster area.

If mount units are a "disaster area" then the previous status quo mudball (static /etc/fstab + autofs + bespoke distro scripts that keeled over when you stray off the beaten path and/or something inevitably went wrong, no meaningful dependency tracking vs the filesystem(s) being online/accessible, etc) was an extinction-level-event asteroid impact.

Is it perfect? far from it. But it's still a *huge* net improvement.

About the Devuan excision

Posted Jul 2, 2026 8:17 UTC (Thu) by intelfx (subscriber, #130118) [Link] (1 responses)

> The issue here is that systemd is a huge mess at the moment. It seems to do _everything_, but it does almost nothing completely right.

It does most of the things pretty much right. People used to split hairs over "completely" since computing happened, and will do so for the foreseeable future.

> The core process supervision and journaling are OK. Everything around it is not. Mount units are a particular disaster area. Mount units are a particular disaster area. I dare anyone to say that THIS is acceptable: https://github.com/systemd/systemd/blob/ee9a70ccc7a35b224...

You are sensationalizing. If that's the worst you have, I'd say we are in pretty damn good place.

This is not an article about systemd

Posted Jul 2, 2026 18:49 UTC (Thu) by corbet (editor, #1) [Link]

I think that the systemd wars, beyond having been mostly settled years ago, are somewhat off-topic here. Let's not relitigate that one yet again.

About the Devuan excision

Posted Jul 1, 2026 4:06 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]

> Either way it appears to be trivially fixable by adding a local drop-in that that overrides the "After=local-fs.target" with "After=network.target" .

Well, yeah. I fixed it this way. After struggling to debug the issue that happened once in a while for an unknown reason.

About the Devuan excision

Posted Jul 1, 2026 5:31 UTC (Wed) by zdzichu (subscriber, #17118) [Link] (4 responses)

Easier to put "_netdev" in the fstab where the iSCSI volumes are mounted. Either way, a configuration bug, not a systemd one. And not Xsnow related.

About the Devuan excision

Posted Jul 1, 2026 5:39 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link] (3 responses)

fstab? Are you a caveman? You're supposed to use mount units: https://www.freedesktop.org/software/systemd/man/latest/s... And I don't believe that they support _netdev override.

Which is ironic, because /etc/fstab generator supports them.

About the Devuan excision

Posted Jul 1, 2026 6:24 UTC (Wed) by mb (subscriber, #50428) [Link]

>In general, configuring mount points through /etc/fstab is the preferred approach to manage mounts for humans.

About the Devuan excision

Posted Jul 1, 2026 9:23 UTC (Wed) by farnz (subscriber, #17727) [Link] (1 responses)

If you're writing a mount unit, you can add the appropriate dependencies yourself; systemd-fstab-generator uses _netdev to choose a different set of After and WantedBy directives, nothing more.

About the Devuan excision

Posted Jul 1, 2026 20:18 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]

Not quite. systemd also has special treatment of mount units for shutdown and for containers. It's a minor thing, true, but it also reinforces my point. There are too many moving pieces in systemd that can have unexpected side-effects.

I'm not a systemd hater, and I absolutely LOVE not having to cargo-cult /etc/init.d scripts.

But I'm not at all positive about systemd's ability to carry out its stated goal: building a coherent low-level infrastructure layer. The same pattern keeps repeating again and again: systemd adds some component in an MVP fashion and then gives up on making it fit with the rest of the system before moving on to the next shiny thing. And/or takes shortcuts that shouldn't be taken.

About the Devuan excision

Posted Jul 1, 2026 12:20 UTC (Wed) by alx.manpages (subscriber, #145117) [Link]

Oh, that might have been the cause of one of my recent (last month or so) boot problems. It failed to boot right after an upgrade, and I was worried that I might have one of those week-long no-boot bugs, but then I tried booting again the day after, and it worked. I could never reproduce it again. I didn't understand what happened, but if the first boot after upgrade is different, that could explain it.