For interesting topics. But remember this is a Linux Forum. Do not 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.
Because of the systemd-sysVinit energy here, I'm creating a thread where folks can share ideas on:
--- how-to clean systemd off *buntu, arch & other distros and/or
--- where to look for refuge from the 1 million lines of systemd baggage... :lipsrsealed:
By way of kicking things off and in honor of @rasat's fine work to remove systemd, I offer the following (links). I don't know how good these guides are, but they may offer some help.
Pax vobiscum, Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
dreamer wrote: ↑Mon Jun 03, 2019 7:31 pm
I let the pros remove systemd.
If I may recommend... then stick with MX & or antiX. No matter what happens on MX, I'm pretty certain @anticapitalista and his team on antiX will keep antiX systemd free.
Pax vobiscum, Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
manyroads wrote: ↑Mon Jun 03, 2019 7:45 pm........... I'm pretty certain @anticapitalista and his team on antiX will keep antiX systemd free.
I hope you are right, but the big problem for both AntiX and Devuan is the absence of systemd-shim in Buster: how can they solve it?
Or am I misunderstanding the problem?
Based on my non-tech layman's understanding, antiX just uses some clever means to filter out all systemd-related packages in Debian repos from being installed or pulled into antiX, so that the non-systemd analogues/replacements from antiX's nosystemd repo gets installed instead.
This is what antiX is already doing. It's already free of systemd packages.
MX up to version 18 is different because it was using Debian repos as is, without the antiX nosystemd repo. So MX contains systemd packages within, even though it boots into sysV by default. Up to Debian Stretch, the systemd-shim package in Debian's repo was maintained and allowed users of MX (and Debian users if they knew what to do, I guess) to choose to boot into either systemd or sysV normally while just running Debian repos. It was this freedom of choice of init that MX tried to keep.
That co-existence won't be possible anymore in Buster, because the shim package is no longer maintained. If you go full Debian, you will be on systemd. Having the sysV packages will now conflict with systemd packages.
If you want sysV, you have to do what antiX does and filter out the systemd stuff from Debian repos. Meaning your installation of a sysV-only system cannot be booted into systemd at all.
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
Thanks, asquerth: I see it more clearly now.
I hope that AntiX buster manages to solve its problems.
My other wish is that MX will forget about the 9% of users who want systemd (they could use straight debian instead) and just make MX sysviinit only.
GuiGuy wrote: ↑Tue Jun 04, 2019 10:04 am
I hope you are right, but the big problem for both AntiX and Devuan is the absence of systemd-shim in Buster: how can they solve it?
AntiX 19 is solving the absence of systemd-shim for lightweight DE and WM. @manyroads has created one prototype for Xfce. viewtopic.php?f=40&t=50543
What's also needed, MX 19 prototype which runs all DE including KDE and Gnome. Devuan does the job but beowulf packages will be slightly behind buster. Also it may not provide all packages. Most users will not mind running systemd in next MX major release (19). But when knowing the advantages of SysVinit speed and instant apps respond, its worthy to have an systemd-free alternative.
I am still curious to know what does it take to get AntiX to run all DE. Sounds better, as well as more acceptable by many MX users to have "MX powered by AntiX" than "Devuan". There is MX forum and community support. @manyroad can you get Gnome to run in your prototype?
Last edited by rasat on Tue Jun 04, 2019 11:46 am, edited 1 time in total.
GuiGuy wrote: ↑Tue Jun 04, 2019 11:22 am
Thanks, asquerth: I see it more clearly now.
I hope that AntiX buster manages to solve its problems.
My other wish is that MX will forget about the 9% of users who want systemd (they could use straight debian instead) and just make MX sysviinit only.
I will upload an xfce antiX19 alpha snapshot, later this week. It uses Buster; you'll see it works quite well. In the end (my layman's opinion) I think you can always use a flatpak of an app that might not be available in the antiX repos (or use a snap or appimage). I know that eats disk, but it keeps the 1 million line of code systemd corralled.
At lest that's how I understand things.
Pax vobiscum, Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
