You just repeated what I said.  I suspect you don't understand that systemd disabled by default still leaves active systemd elements and hooks.  Devuan removes those.

Based on the user's results, it sounds like it didn't matter much.  I'm guessing the kali-rolling repo probably broke a metric shit-ton of critical packages during the installation process.

Glad you got it working.  Can you mark the thread as "solved" so future readers will know that your method "just works"?

golinux wrote:

ball wrote:

I'm well aware. I was suggesting using katoolin on Devuan or MX Linux.

MX Linux just has sysvinit enabled according to Debian's instructions.  All of systemd is still intact and can be enabled at user's request.  So how would that be different than trying katoolin on Debian itself?

MX Linux does not have systemd installed by default, and they strongly urge users not to use it.

You just repeated what I said.  I suspect you don't understand that systemd disabled by default still leaves active systemd elements and hooks.  Devuan removes those.

Just have to see if it'll nuke Devuan like it did MX Linux

ball wrote:

I'm well aware. I was suggesting using katoolin on Devuan or MX Linux.

MX Linux just has sysvinit enabled according to Debian's instructions.  All of systemd is still intact and can be enabled at user's request.  So how would that be different than trying katoolin on Debian itself?

MX Linux does not have systemd installed by default, and they strongly urge users not to use it.

E: Some packages could not be authenticated

This may be due to the insane firewall here. I can't even access the devuan web sites without a VPN (or most sites it seems). I'm running a crappy VPN now (so I can post here), but it still gives the error.
It did install for MX Linux, but it nuked the install completely.

Don't protest too loudly or you might reveal your autist level.

That's adorable.

Anyways, I just tried it out, and everything worked exactly as expected.  No dependencies broken or anything.  So good call on sharing that.

I'm well aware. I was suggesting using katoolin on Devuan or MX Linux.

MX Linux just has sysvinit enabled according to Debian's instructions.  All of systemd is still intact and can be enabled at user's request.  So how would that be different than trying katoolin on Debian itself?

...but Ubuntu isn't going to be much better, in that regard...

I'm well aware. I was suggesting using katoolin on Devuan or MX Linux.

I currently don't have a ton of bandwidth or time, and the libraries (brick and mortar kind) here are filtered all to hell. I'm going to make an attempt later today at the library but don't expect much. It'll be a shot in the dark and last couple times I tried this I ended back on BT5.

The point of this thread is to find out if someone else has tried this already as to not waste not only my time, but everyone else's. It's a little thing called communication. Don't protest too loudly or you might reveal your autist level.

When bt changed to kali, they inherited systemd hell from Debian.

A lot of people were very unhappy about that, to say the least...

...but Ubuntu isn't going to be much better, in that regard...

...so, your best bet is trying them out in a nonpersistent, throwaway, live environment, and reporting back to us, so as to provide the community some well-researched and tested insights...

...because in a persistent environment, you'll want to be careful when you repomix, especially in light of the systemd-ubuntu disclaimer above.