Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Is elogind solution for MX systemd question? [OK]

Feel free to talk about anything and everything in this board. Just don't post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.

No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.

Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.

You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
rasat
Forum Regular
Forum Regular
Posts: 334
Joined: Tue Dec 19, 2017 1:19 pm

Is elogind solution for MX systemd question? [OK]

#1

Post by rasat » Tue May 21, 2019 4:12 pm

Head_on_a_Stick wrote:
Tue May 21, 2019 12:23 pm
The current release version of Devuan is ASCII, based on stretch, but their development branches are beowulf & ceres, which are based on buster & sid.
I was running beowulf briefly and it works very well indeed, they have now removed libsystemd0 and the Debian developers have adopted their version of elogind:
https://packages.debian.org/buster/elogind
Thank you Head_on_a_Stick, I think you gave a good solution. To confirm what you wrote, I installed Devuan ASCII (stretch). Installed Gnome using elogind, and works very well. Both Xfce (sysV) and Gnome (systemd) in same install. Next, upgrade to Beawulf (buster) which upgraded smoothly, and works well.

Code: Select all

amurt@rasatPC:~$ dpkg -S /sbin/init
sysvinit-core: /sbin/init
Is elogind the solution by learning from Devuan?? MX will remain as created in first place without becoming a systemd only.
Last edited by rasat on Thu May 30, 2019 5:20 pm, edited 3 times in total.

User avatar
Head_on_a_Stick
Forum Regular
Forum Regular
Posts: 477
Joined: Sun Mar 17, 2019 3:37 pm

Re: Is elogind solution for MX systemd question??

#2

Post by Head_on_a_Stick » Tue May 21, 2019 4:21 pm

The elogind package allows for removal of libsystemd0 but antiX solved that "problem" quite a while ago, IIUC.
"The state, therefore, is the most flagrant, the most cynical, and the most complete negation of humanity." — Mikhail Bakunin

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 5120
Joined: Wed Jul 12, 2006 4:05 pm

Re: Is elogind solution for MX systemd question??

#3

Post by timkb4cq » Tue May 21, 2019 4:25 pm

If MX stays sysvinit (my preference) it will certainly use elogind.
If it goes systemd it will not.

The problem, as I understand it, is that without the no longer developed systemd-shim it's not possible to be able to boot into either one as we can now since elogind & systemd conflict.

There is also the issue of third party software releases for debian buster omitting init files since they assume systemd will be present. This is a manageable issue for most programs - but if I'm not mistaken (and I certainly could be) things like snapd would require rewriting rather large parts of the program to make it work without systemd.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

rasat
Forum Regular
Forum Regular
Posts: 334
Joined: Tue Dec 19, 2017 1:19 pm

Re: Is elogind solution for MX systemd question??

#4

Post by rasat » Tue May 21, 2019 6:12 pm

timkb4cq wrote:
Tue May 21, 2019 4:25 pm
The problem, as I understand it, is that without the no longer developed systemd-shim it's not possible to be able to boot into either one as we can now since elogind & systemd conflict.
As I mentioned in OP, I did the test with Xfce and Gnome, and works well with elogind as well as other systemd required apps... elogind seem to replace systemd-shim. What though arises the question by using elogind, can Debian repo be used? Are there packages what must be modified. If so, taken from Devuan backport?

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 12136
Joined: Sun Dec 16, 2007 1:17 pm

Re: Is elogind solution for MX systemd question?

#5

Post by dolphin_oracle » Tue May 21, 2019 6:20 pm

While they serve a similar function elogind is not a drop in replacement for the systemd-shim. But it gets you a long way there.

Many packages just need rebuilt in debian to work with elogind, but its possible. Antix has been doing this the entire 17 series
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-18.3
lenovo s21e - antiX-19 beta 2 (live-USB)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Head_on_a_Stick
Forum Regular
Forum Regular
Posts: 477
Joined: Sun Mar 17, 2019 3:37 pm

Re: Is elogind solution for MX systemd question??

#6

Post by Head_on_a_Stick » Wed May 22, 2019 1:55 am

rasat wrote:
Tue May 21, 2019 6:12 pm
taken from Devuan backport
The elogind package is available directly from the Debian buster repositories but it is intended for machines that run without any systemd packages at all.

For clarity: it is possible to boot under sysvinit in Debian buster without elogind.
"The state, therefore, is the most flagrant, the most cynical, and the most complete negation of humanity." — Mikhail Bakunin

rasat
Forum Regular
Forum Regular
Posts: 334
Joined: Tue Dec 19, 2017 1:19 pm

Re: Is elogind solution for MX systemd question?

#7

Post by rasat » Wed May 22, 2019 6:02 pm

dolphin_oracle wrote:
Tue May 21, 2019 6:20 pm
Many packages just need rebuilt in debian to work with elogind, but its possible. Antix has been doing this the entire 17 series
Curious what packages to rebuild, maybe taken directly from Devuan repo. The upgrade from ASCII (stretch) to Beawulf (buster) is a simple process by taking in consideration particular packages by adding a file /etc/apt/preferences.d/avoid_some_beo

Read more:
https://dev1galaxy.org/viewtopic.php?id=2301

As an useful consideration for MX future major upgrades, Devuan does it smoothly which would inspire MX users..... one time install with lifetime semi-automatic upgrade.

skidoo
Forum Guide
Forum Guide
Posts: 1446
Joined: Tue Sep 22, 2015 6:56 pm

Re: Is elogind solution for MX systemd question?

#8

Post by skidoo » Wed May 22, 2019 7:12 pm

rasat, d_o has repeatly replied stating what's what, but for some reason you're hearing what you want to hear.

You should boot the antiX19 alpha and havealookaround.
antiX does what you've described slightly more cleanly than devuan does.
Take note of the packages with ~0nosystemd suffixed names and/or apt-cache policy and/or browse the antiX nosystemd repository to see whatall packages have been customized.
Curious what packages to rebuild, maybe taken directly from Devuan repo.
or "directly from the antiX repo".
For some reason, you seem to be convinced that Devuan has something which antiX lacks.
Either are fine, fine for booting sysV init & using buster repositories.
Neither are fine for switching back and fro between choice of init.

rasat
Forum Regular
Forum Regular
Posts: 334
Joined: Tue Dec 19, 2017 1:19 pm

Re: Is elogind solution for MX systemd question?

#9

Post by rasat » Wed May 22, 2019 9:39 pm

I am not focusing on antiX because Gnome will not install. Goes beyond my tech knowledge to get it to work. What I did, convert MX 18.2 stretch with Devuan ascii repo, which work fine with all MX tools in place, except plymouth was removed.
https://mn3m.info/posts/migrating-from- ... to-devuan/

Just did a respin for testing. Uploading soon.
Image

Next test to upgrade to beawulf (buster).

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 4906
Joined: Sun May 27, 2007 5:37 am

Re: Is elogind solution for MX systemd question?

#10

Post by asqwerth » Wed May 22, 2019 11:57 pm

rasat wrote:
Wed May 22, 2019 9:39 pm
I am not focusing on antiX because Gnome will not install. Goes beyond my tech knowledge to get it to work. What I did, convert MX 18.2 stretch with Devuan ascii repo, which work fine with all MX tools in place, except plymouth was removed.
https://mn3m.info/posts/migrating-from- ... to-devuan/

Just did a respin for testing. Uploading soon.
Image

Next test to upgrade to beawulf (buster).
But it's the Buster/Beowulf upgrade that will be the real test for installing Gnome I believe, not the stretch to ascii conversion.

I'm not sure, but I think that Devuan's Stretch analogue (ASCII) might still not be fully systemd-free, so Gnome might still work on it. I'll be interested to hear the results of that (ie, Beowulf and Gnome) test.


(Devuan)...one time install with lifetime semi-automatic upgrade
The reason why semi-automatic rolling upgrades through different bases might be possible with Devuan Stable, like with pure Debian, is because the repos are kept in their conservative unchanged state. With MX packaging team, you can request and get newer versions of software to be packaged and used, but that may interfere with the upgrade path.

Like the MX website says here: https://mxlinux.org/mx-repos/
MX uses Debian Stable as a base, but updates a lot of the userland programs & libraries, and backports newer programs from testing by building them against the Stable base. That gives a better user experience but interferes with Debian’s dist-upgrade path....

So it’s a trade-off: better desktop user experience at the expense of having to do a quick fresh install (which lets you save /home if desired) when the Debian base changes, typically every 2-3 years.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

Post Reply

Return to “General”