Just more of this, IMO:
Distrowatch and Init
Re: Distrowatch and Init
The DW criticism about being under the radar is from just one person, innit? (get it?! Heh)
I like the fact that MX uses sysvinit, doesn't toot its horn about it, yet has quietly moved into 3rd place and garnered good reviews.
Shows the continued viability of sysvinit in creating a quality distro, and that even users who don't care about the init issue or don't even know MX is not using systemd, like it so much.
To me, that is vindication of sysvinit's relevance in "modern" distros and that it is not just the anti systemd crowd who are attracted to MX.
Make no mistake, I like that MX is not using systemd as init. I think it's important for devs of other software to see that there are non-techy distros that don't use systemd and the devs should thus not include unnecessary systemd dependencies by default.
Even though I also use systemd distros, i wouldn't want that to be a monopoly because I don't like its ever spreading (and unnecessary) encroachment into non init tasks.
There have also recently been various systemd bugs popping up in rolling distros like manjaro.
I like the fact that MX uses sysvinit, doesn't toot its horn about it, yet has quietly moved into 3rd place and garnered good reviews.
Shows the continued viability of sysvinit in creating a quality distro, and that even users who don't care about the init issue or don't even know MX is not using systemd, like it so much.
To me, that is vindication of sysvinit's relevance in "modern" distros and that it is not just the anti systemd crowd who are attracted to MX.
Make no mistake, I like that MX is not using systemd as init. I think it's important for devs of other software to see that there are non-techy distros that don't use systemd and the devs should thus not include unnecessary systemd dependencies by default.
Even though I also use systemd distros, i wouldn't want that to be a monopoly because I don't like its ever spreading (and unnecessary) encroachment into non init tasks.
There have also recently been various systemd bugs popping up in rolling distros like manjaro.
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
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
Re: Distrowatch and Init
As someone who knows "just enough to be dangerous," I was convinced that nothing could out do Debian Stable. I was using the MX Repo for more up to date versions of firefox. Since I have started using MX Linux full time, like Debian Stretch, MX Linux "just works." It feels more responsive than Stretch. I don't know if it is my imagination, but, it feels more responsive. The main beef I have with systemd, is when I was shutting down, and it would take one and a half minutes or more. I would follow the suggestions to change systemd settings, and it work; mostly. Like I said, I know just enough to be dangerous. I try to remember that when I start to comment.
Re: Distrowatch and Init
I wish Debian had left systemd alone instead of adopting it. If MX can straddle the fence I'm OK with that. I do have concerns it will be harder to do as time goes on, and I've seen a few issues by not having it. But I've also seen systemd slow down boot up with crazy processes. Like I said--really wish Debian had not used it.
Re: Distrowatch and Init
@KBD,
Actually, I was looking for an "MX type distro" to appear after Debian drank the kool-aid.
I tried quite a few before I found MX first public trials.
I would probably have still been running Debian testing and doing upgrades on Friday afternoons
to have the weekend to recover in case something broke.
Actually, I was looking for an "MX type distro" to appear after Debian drank the kool-aid.
I tried quite a few before I found MX first public trials.
I would probably have still been running Debian testing and doing upgrades on Friday afternoons
to have the weekend to recover in case something broke.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
Re: Distrowatch and Init
On some of my systems the move to systemd caused really slow boot times. It is still shocking how quickly Debian jumped on that ship. I wish they did not always follow Red Hat's lead.Richard wrote: ↑Fri Dec 28, 2018 11:00 pm @KBD,
Actually, I was looking for an "MX type distro" to appear after Debian drank the kool-aid.
I tried quite a few before I found MX first public trials.
I would probably have still been running Debian testing and doing upgrades on Friday afternoons
to have the weekend to recover in case something broke.
Re: Distrowatch and Init
To be fair, sysvinit was not being maintained when Debian made their decision. I'm pretty sure that was the deciding factor for a lot of the voters. Debian has never liked keeping moribund packages around if they didn't need to.
Not that I agreed with their decision, but I do understand it.
Since then Jesse Smith has taken over sysvinit maintenance and appears to be doing a good job with it.
Not that I agreed with their decision, but I do understand it.
Since then Jesse Smith has taken over sysvinit maintenance and appears to be doing a good job with it.
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Re: Distrowatch and Init
Am not a developer or an IT person, just a regular everyday ex-windows user that uses MX for privacy reasons. My understanding is that the systemd code base is so huge that it even crossed 1 million lines of codes as of late 2017 and has never had a security audit.
That's the reason people promote other inits.
Its a similar reason why Wireguard is becoming more popular over openvpn because of its smaller code base.
Its a security and privacy nightmare in my opinion.
That's the reason people promote other inits.
Its a similar reason why Wireguard is becoming more popular over openvpn because of its smaller code base.
Its a security and privacy nightmare in my opinion.
Last edited by mystic on Sat Dec 29, 2018 11:23 am, edited 1 time in total.
Re: Distrowatch and Init
Linux distros that dont't run systemd are very trendy right now:
Perhaps the critic on DW got it backward. A few years ago people (on Slashdot at least) were bemoaning the fact that all leading distros were using systemd. We've made a leading distro that uses sysvinit and we don't feel the need to boast about it. This means it is not a novelty.
Five of the top six spots and seven of the top nine. Not bad.Perhaps the critic on DW got it backward. A few years ago people (on Slashdot at least) were bemoaning the fact that all leading distros were using systemd. We've made a leading distro that uses sysvinit and we don't feel the need to boast about it. This means it is not a novelty.
You do not have the required permissions to view the files attached to this post.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman