Systemd and LMDE (The future)
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Systemd and LMDE (The future)
Amidst all the raging debate between the zealous anti-systemd freaks and the systemd apologists, i've noticed Linux Mint (LMDE) has quietly gone about it's business and stuck to init without making a huge fuss about it. Even though i haven't a clue about the nitty-gritties of this whole systemd v/s init and sysvinit business, as an average user i am curious to know the rationale behind it and what are LMDE's plans in this regard for the future, now that Debian has adopted systemd as the de facto standard.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Linux User #481272 Reg: 15th Sept., 2008
Re: Systemd and LMDE (The future)
The Linux Mint developers don't have anything against systemd init. AFAIK they recognize it as a useful tool for building operating systems, with the systemd project making strides to provide for a common userland for Linux distros (though not yet in-tree like on Unix and BSD). Despite Debian 8 switching to systemd by default, Linux Mint decided during development of LMDE 2 that it was still early (for Linux Mint) to use it by default and would delay adoption of systemd init for at least one cycle to let any issues be ironed out. Likely with Linux Mint 18 (based on Ubuntu LTS 16.04) and LMDE 3 (based on Debian 9) a switch will be made to systemd init.
So the reason is more a kind of "wait and see what happens to Ubuntu and Debian using it by default, before we use it".
So the reason is more a kind of "wait and see what happens to Ubuntu and Debian using it by default, before we use it".
Re: Systemd and LMDE (The future)
The great thing about GNU/Linux is that there is no "one size fits all" solution and so it is perfectly acceptable for different distros to approach things in different ways.mzsade wrote:... what are LMDE's plans in this regard for the future, now that Debian has adopted systemd as the de facto standard.
I wouldn't get too "hung-up" about "standards"... As Andrew S. Tanenbaum sagely observed; "The nice thing about standards is that you have so many to choose from."
Re: Systemd and LMDE (The future)
From what I have heard on the Debian forums, is the average user doesn't even notice any difference.
Re: Systemd and LMDE (The future)
+1 Makes perfect sense to me, it's not as if Debian has switched over to systemd in it's entirety, i know for a fact that network services are still managed by NetworkManager and not networkd. And thanks for replying to a question that had already been answered here, http://blog.linuxmint.com/?p=2764. Sorry for not looking it up first.xenopeek wrote:The Linux Mint developers don't have anything against systemd init. AFAIK they recognize it as a useful tool for building operating systems, with the systemd project making strides to provide for a common userland for Linux distros (though not yet in-tree like on Unix and BSD). Despite Debian 8 switching to systemd by default, Linux Mint decided during development of LMDE 2 that it was still early (for Linux Mint) to use it by default and would delay adoption of systemd init for at least one cycle to let any issues be ironed out. Likely with Linux Mint 18 (based on Ubuntu LTS 16.04) and LMDE 3 (based on Debian 9) a switch will be made to systemd init.
So the reason is more a kind of "wait and see what happens to Ubuntu and Debian using it by default, before we use it".
...Similar to Linux Mint 17.x, LMDE 2 “Betsy” will be using the traditional sysvinit. The move to systemd could happen with Linux Mint 18 and LMDE 3, giving this new technology and the Linux ecosystem 2 years (or more) to mature and to iron out integration and compatibility issues. Cinnamon in particular is built without systemd support by default and the development team is planning to change this in version 2.6 to give the DE the ability to switch at runtime between systemd and consolekit/upower without the need to recompile anything.
Linux User #481272 Reg: 15th Sept., 2008
Re: Systemd and LMDE (The future)
Goodbye Mint!
I can't take the instability and nightmare of SystemD. I'll be migrating all my machines, and all 300+ of my client machines to Devuan. My reputation is too valuable to throw away on junk software.
viewtopic.php?f=61&t=214262&p=1211782#p1211782
If you want the whole story on what a nightmare of broken crap SystemD is. No surprise either. Everything Poettering touches goes to s#!+ right away.
I can't take the instability and nightmare of SystemD. I'll be migrating all my machines, and all 300+ of my client machines to Devuan. My reputation is too valuable to throw away on junk software.
viewtopic.php?f=61&t=214262&p=1211782#p1211782
If you want the whole story on what a nightmare of broken crap SystemD is. No surprise either. Everything Poettering touches goes to s#!+ right away.
Re: Systemd and LMDE (The future)
... you know that Mint 17 is supported until 2019, right? Why so dramatic?rhY wrote:Goodbye Mint!
If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!
Re: Systemd and LMDE (The future)
Sorry for being dramatic. SUPER frustrated. Literally every OS I use is broken in the latest version due to SystemD.
Mint
Debian
Proxmox
All broken since taking the D. Crashes, Memory overruns, instability, lock ups. On a big variety of hardware, too: laptops, desktops, servers, VMs.
I'm incredibly frustrated by the rigged vote that got systemD into Debian in the first place, and now I have a TON of extra non-billable work to work around that asinine decision.
*FRUSTRATED*
Mint
Debian
Proxmox
All broken since taking the D. Crashes, Memory overruns, instability, lock ups. On a big variety of hardware, too: laptops, desktops, servers, VMs.
I'm incredibly frustrated by the rigged vote that got systemD into Debian in the first place, and now I have a TON of extra non-billable work to work around that asinine decision.
*FRUSTRATED*