On the one hand, forking is what drives Free Software. It allows us to innovate, adapt software to new needs, etc. Without it, the FOSS community would not be as strong as it is.

On the other hand, Debian's board took a vote, and the anti-systemd people lost. Democracy happened. Democracy is good. Those people who created this fork are a bunch of malcontents that are whining because they didn't get their way. This isn't a "downstream branch" like Ubuntu, which strengthens the community by sending patches upstream. This is breaking up of a strong community, and it's now going to be inherently weaker.

That's actually dead simple to do. Most already have one that's been stable for years.

AMD is completely out of the game and the thrust of their current design work seems to have entirely ceded low power x86 to Intel in favor of better performing hybrid CPU/GPU products.

The complaint by the anti-systemd crowd is that the systemd crowd is actively promoting things becoming dependent on systemd. It's not that they can't maintain a systemd free distro, it's just that nobody wants to spend all of their time undoing the work of the village idiot. You must have missed the articles about organizing a Debian fork. Or the whole uselessd thing. If systemd would just keep their fingers out of everyone else's pie, nobody would much care what they do or don't do.

I have fixed the btrfs/systemd problem. I gave systemd the boot and now the VM just works.

It is actually kinda funny to me after hearing all the systemd can do anything! systemd is great, all hail systemd cheerleading not to mention the excessive delight of some of the fans that people might have problems avoiding it and then a really simple problem comes up and literally the whole community is stumped. Not just a little stumped, they actually have no idea how to handle the situation even in principle. Meanwhile, going back to sysvinit fixed it right up.

I have validated a systemd-less solution that should be good for a few years at least.

I already indicated I would simply not use systemd, I don't know why you keep telling me to do what I have indicated I am already doing.

I don't suppose you could toss me one of those links you found where the problem is actually solved, could you? I do like keeping options open...

All of the ones I saw consisted of a bunch of people shrugging and wondering what the proper way is to handle it might be.

My sister used to raise her own turkeys. Up close they looked like something from a paleontology textbook, but they were still good-natured, very curious creatures. They would always come up to you and inspect you, talking all the time. Maybe they were just demanding food. Dunno.

They ate good stuff, they had a big enough pen that they could run around to their heart's content, they were basically happy turkeys. And it showed: they had a wonderful flavour and a nice texture.

...laura

That's because they don't properly trim trees, they hack off whatever might be near the lines. If they would actually trim the trees so they don't look like the crippled survivors of a war, people wouldn't gripe.

There are a couple trees near me that they 'trimmed' such that they will almost inevitably fall over onto the road sooner or later. That's what happens when you cut all the branches off of one side. It's a classic "somebody else's problem now" sort of 'solution'

Or get it for $253.

Although they are regulated to death, power companies want to maximize profit, and there are no rules that say they have to invest in improving infrastructure "as long as everything is working fine." They have no motivation at all to seek out aging sections of their power grid and replace them during normal operation. Rather, they are entirely reactive. When power goes out, they fix it on demand. Nothing more. Moreover, whenever there are major storms that take out massive swaths of their network, they cry for help from the government to pay for the repairs becuase they "can't afford it." The only reason they do anything at all when power does go out is because they'd be slapped by regulators if they didn't. Otherwise they'd be perfectly happy to leave paying customers without power the way Comcast leaves paying customers without internet service.

Just imagine if power delivery were government-run. It would be even worse, because there would be no profit incentive.

I would say a complete inability to mount a degraded btrfs (which figures heavily in future plans) is hardly some obscure bug.

As for use something else, that's my intention. I gave systemd it's shot and it failed miserably. A bug like that shows that they aren't even trying to make the thing robust.

The question I asked about a workaround is a fairly fundamental thing to not know about systemd. That is, how to get it to run something needed to meet dependencies and how to get it to not run something.